Language

Version v10 · in force since 16 November 2026

Privacy policy

This page sets out, point by point, what data the Medaro portal collects, why, and how long it is kept. It describes how the portal actually handles data rather than offering general legal wording; only the site’s security measures are described in general terms, so that they are harder to get around. The document is marked version v10 — that is the version recorded in the consent log when you tick the box during registration, and in your subscription when you turn on notifications about new articles. What changed since version v9 is listed in the last section.

Who processes your data

Medaro is a medical directory for Armenia: a catalogue of doctors, clinics, pharmacies and laboratories, patient reviews, and a guide to compulsory health insurance. The portal does not provide medical care, does not book appointments and does not keep medical records.

The personal data controller is QWERTY LLC (Republic of Armenia), registration number 282.110.1073657, TIN 00922045. Postal address for legally significant correspondence: 44 Paronyan Street, Yerevan, Republic of Armenia. We accept personal data requests by e-mail at info@medaro.am — the same address is shown in the site footer.

The basis for processing

For registered users the basis is consent. During registration you tick two boxes: consent to the processing of personal data (this document, version v10) and consent to publishing your review under the portal rules. A doctor applying for verification ticks a third one — consent to the processing of education and licence documents for profile verification and to the publication of the details from them listed under “Doctor cards”. This consent also covers the review of the documents with the help of the Claude service by Anthropic (USA), which may use them to train its models (see “Who we share data with”). With a separate box the doctor agrees to the publication of their profile after verification.

Every consent is written to the log as a separate row: who agreed, to which document, in which version and at what minute. We do not write the IP address to that log.

A visitor without an account ticks nothing: the server request log, the anonymous site-search statistics, the Google Analytics and Cloudflare Web Analytics counters, the maps and — for visitors from Russia — the ru.medaro.am mirror together with its Google Analytics and Yandex Metrica counters work for everyone. What each of them collects, why and for how long is set out in the sections below. Notifications about new articles work differently: they are on only if you turned them on yourself — pressed the button on the site and then allowed notifications in the browser’s prompt. Those two actions are your consent; you can turn notifications off at any moment with a single tap (see “Notifications about new articles”). You also send a “Spotted an error?” message yourself: the form asks for an email address — as a rule, we send it a confirmation that the message has been received and, once the check is done, its outcome. By sending the form you agree that we use the address for emails about this message and, if needed, to ask you a question about it; the form cannot be sent without an address, but you can also simply write to us at info@medaro.am. Administrators also review “Spotted an error?” messages and letters to info@medaro.am, except letters about reviews and disputes over them, with the help of the Claude service by Anthropic (USA): by sending a message or a letter, you agree to this as well (see “Who we share data with”).

When this document changes in substance, we raise the version number, publish the new text on this same page and list what changed. Registered users who are signed in see a notice on the site that the policy has been updated, with a link to the new text. We do not collect consent again: the log keeps the record of the version you agreed to. If the log has no consent of yours because the checkmark was not saved when you registered, the site will ask you to confirm it when you sign in; the record appears at the moment you press “I accept”. If you do not agree with the new version, write to info@medaro.am and we will delete the account; what happens to your reviews is explained under “Your rights”.

What we store

Everything the portal collects about you when you use the site is listed here.

  • Account: email address, display name, interface language and role (patient, doctor, administrator). The password is stored only as an irreversible hash in the authentication service — we never see it. We do not ask for or store a phone number for the account. When registering, a doctor may give the phone number of their clinic if it is not yet in our directory: the moderator uses it to add the clinic to the catalogue. The account email is used for signing in, confirming registration and recovering the password. A moderator may also write to it — by hand, from info@medaro.am — about the moderation of your reviews, replies to reviews, disputes and applications. For example, to the author of a review — why the review was rejected and how to correct it, or, if a doctor has disputed the review, to ask for confirmation of the visit and to report the outcome of the check; to a doctor — about the decision on their reply to a review, on a dispute about a review or on their verification application. In addition, our program writes to a doctor about the progress of a verification application — also from info@medaro.am and in the language of the account: that the application has been received (and that new documents have been received after a rejection), that the profile has been published, or that the application has been rejected — with the reason given by the moderator and what needs to be corrected.
  • Sign-in sessions: the time of sign-in, the IP address and the browser string of every active session. The sign-in service keeps them to protect the account; the record is deleted when you log out. The sign-in service also keeps an event log (sign-in, sign-out, password change, turning the second sign-in step on and off, signing in with a code): the time and the account, without the IP address. To protect sign-in against password guessing, the sign-in service limits how often attempts can be made from one IP address, keeping that address only in memory. If a second sign-in step (a code from an app on the phone) is attached to an account, the sign-in service also keeps information about that app — its key, name and dates — a mark on each session of how the sign-in was confirmed, and, for each attempt to enter a code, its time, IP address and result. Records of attempts and an unfinished attachment are deleted after about a day, the sign-in mark together with the session, and the information about the app when it is detached.
  • Reviews: the text, the overall score and three facet scores, the language, the visit date, the doctor or organisation the review is about, the signature (“Name S.” or a pen name you choose), and the creation and publication dates. Your real name is never shown next to a review, and the internal link between a review and an account is closed at database level to everyone except you and a moderator.
  • Visit confirmation: the date of the visit, the confirmation method and — if you confirm with a receipt — the receipt file itself in private storage. The file is needed only for the check and is deleted afterwards under our procedure. If a doctor disputes a review, the author confirms the visit with a document sent by email to info@medaro.am. After the check we delete that email together with the document from our mailbox; only the outcome of the check remains in the moderator action log.
  • Doctor cards. Most cards were compiled by us from open sources — doctors’ pages on the websites of the clinics where the doctor works: name, specialty, position, place of practice, gender, photo and, where the clinic publishes them, education, work experience and the languages of consultation; for some doctors, work experience and education were added from open doctor directories, and education also from the open part of the state register of health workers (hrh.am); the consultation price is taken from the clinic’s price list. On the doctor’s page the block “Where this information comes from” gives a link to the source page and the date we took it; if a clinic has told us by letter whether the doctor sees patients there, we keep that mark with the date of the letter. Under each photo we state the clinic, a link to the page it was taken from, and the date. A doctor can ask at any time to correct the information or remove the photo: with the “Spotted an error?” button on their page (request type “Remove or replace the photo”) or by email to info@medaro.am. Every request is reviewed by a moderator. To make sure the request really comes from the doctor or their clinic, we may ask for confirmation — for example, an email from the clinic’s official address. If it is decided to remove the photo, we take it off the page and out of storage at once, and out of the Cloudflare cache and the site’s backup copy — at Cloudflare and on the ru.medaro.am mirror — the same day. A doctor who has verified the profile then changes the description, languages and consultation price themselves, while after verification the name, education, years of experience, specialties and place of work can be changed only by a moderator. A doctor whose documents a moderator has checked has the “Credentials verified” mark on their page. Pressing it shows exactly what was checked: the name — against the documents; the type of diploma, the university, the year of graduation and the specialty on the diploma; the type of certificate, its validity and the date it was checked against the register of health workers (hrh.am); the clinic where the doctor works and how this was confirmed — by the doctor’s page on the clinic’s website or by the same register, with the dates of the checks; the day of the check. We do not show a certificate whose validity has expired until a moderator checks it again. The documents themselves, their numbers, the exact date the diploma was issued, the moderator’s internal notes and the name of the person who checked are not shown on the page. The first hundred doctors published after verification get the mark “One of the first 100 verified doctors on Medaro” on their page. This reflects the order of verification, not an assessment of the doctor: it does not affect the position in search results and gives no paid advantages.
  • Information about organisations — clinics, pharmacies, laboratories. We take it from the organisations’ own websites and official pages, from open directories and maps, and the legal details and information about the head — from state registries and directories. Some of it concerns people: the name and position of the head of the legal entity (shown in the organisation’s legal details), the registered address, and the email addresses and phone numbers the organisation has published. You can ask for them to be corrected or removed with the “Spotted an error?” button on the organisation’s page or by email to info@medaro.am; every request is reviewed by a moderator.
  • Doctor verification documents (diploma, certificate, licence): held in private storage, where only that doctor and a portal administrator can open them. The documents themselves are never shown to patients. A moderator records the outcome of the check separately from the documents: the type, university, year, date of issue and specialty of the diploma; the type and validity of the certificate; the clinic, the address of the doctor’s page on its website and the dates of the checks against that page and against the register of health workers (hrh.am); the date the doctor started work at this clinic according to the register; who checked and when; and an internal note. At Medaro, only administrators see this record in full; when reviewing an application, they also use the Claude service by Anthropic, which sees both the documents and this record (see “Who we share data with”). On the doctor’s page, only what is listed under “Doctor cards” is shown from it. The licence number, if the doctor has entered it in the dashboard, is not shown on the page. Since 31 October 2026, your browser re-saves a photo of a document before sending it: the place and time it was taken, the phone model and other technical details stored in the picture never reach us. A PDF file is sent unchanged.
  • Doctors’ replies to reviews and reports about reviews, together with the reason given and the status of the case.
  • “Spotted an error?” messages: the text, the time it was sent, the page it refers to (its address and title), the request type, the page language and the email address you gave — the form cannot be sent without it; we no longer accept phone numbers. We also store the moderator’s decision and records of the emails to that address: when the “received” email and the email with the outcome of the check went out, and, if an email was not sent or bounced, why (for example, “the domain has no mail” or “the address does not exist”); if the address has been deleted — when and for what reason. The address is seen by moderators in the site’s admin panel, by our program that sends the emails and, when the message is reviewed, by the Claude service (see “Who we share data with”); it is not published on the site and is not added to any mailing list. We need this data to correct the information or consider a photo request; the address is for emails about this message (the confirmation of receipt and the outcome of the check) and, if needed, to ask you a question about it. So that the form cannot be turned into a mailing tool, the emails go out with limits — both on the number of emails to one address and on the total; we do not write to an address to which our emails have recently bounced or been rejected. The message still reaches the moderator. If the page has been hidden from the site by the time the form is sent, no emails are sent at all. There may be no email with the outcome if the first email did not arrive or the address turned out to be invalid, if the message is not about the information on the page, or if the email limit has been reached; we answer a photo request with a separate email from the info@medaro.am mailbox.
  • Emails to a doctor about a verification application: the account email address at the time of the event, the language of the email, which email it is (application received, profile published, application rejected), when it was queued and when it went out, and, if it was not sent or bounced, why (for example, “the address is not confirmed” or “the address does not exist”). We do not keep the reason for a rejection in these records: it stays in the log of moderator actions, in the notes to the documents and in the email itself. For each application a moderator receives a notice at info@medaro.am — the doctor’s name, specialties, clinic, the number of documents under review and what happened to the email to the doctor, without the documents themselves.
  • Service logs: the consent log and the log of moderator and administrator actions (who changed what). It exists so that decisions on reviews and verification can be audited.
  • Server request log: the time, IP address and country, browser and device type, the full address of the page opened, the response code, the site protection’s service mark; for file uploads, also the account and the file. Why we keep it and who sees it is described under “Server request log”. The ru.medaro.am mirror keeps its own request log (see “Mirror for visitors from Russia”). Separately from it, we keep the service records of the site’s protection against abuse, including IP addresses (see “Server request log”).
  • Site-search statistics — anonymously: the query text, the section, the language, the day, how many times it was searched for and how much was found; the table itself holds nothing that links a query to you. See the statistics section for details.
  • Letters to clinics: the address we wrote to, the organisation, the date of sending, and the marks that the letter was opened and which links in it were clicked. This is data from business correspondence with an organisation, not with a patient.
  • Letters you send to info@medaro.am — in our mailbox (see “Who we share data with” about email and about how we review letters); the same mailbox holds copies of our emails about “Spotted an error?” messages and about doctors’ applications, notices to moderators about applications and non-delivery notices.
  • A subscription to notifications about new articles — only if you turned them on: the delivery address your browser issued, the two encryption keys that go with it, the notification language, the topic, the delivery service, the version of this document, the date you subscribed and the dates of the latest delivery attempts. The subscription holds no IP address, no information about your device and no link to an account. See “Notifications about new articles” for details.
  • Backups. So as not to lose data in a failure, we regularly copy the database and the file storage; the copies contain everything listed above. The copies are kept by us and, encrypted, in the Google Drive cloud storage (see “Who we share data with”): only we hold the encryption key, so Google cannot see the contents. Daily copies are kept for 30 days, and copies taken on the first day of the month for up to 3 months. No backup is kept longer than 3 months, so deleted data disappears from the backups for good within 3 months at most.
  • The camera, your location and notifications are switched on only with your permission: the camera for the visit QR-code scanner in the review form, the location for the “Near me” button on the map, notifications for new blog articles. The camera image and your coordinates are not sent to our server; only the visit code that was read is sent.

The cookies we set

There are no advertising networks on the pages of the portal. There are no tracking pixels on medaro.am either — the one pixel we use sits in the letters we send to clinics, described below. Two external traffic counters run on medaro.am — Google Analytics and Cloudflare Web Analytics; the second one sets no cookies and stores nothing in the browser (see “Who we share data with”). On the ru.medaro.am mirror, Google Analytics and Yandex Metrica run (see “Mirror for visitors from Russia”). The portal also keeps its own internal statistics, described in the section below. So the cookies come in three kinds — four technical ones of ours (portal staff also get service ones, for the admin area; ordinary visitors and users do not get them), two of Google Analytics and — on the mirror only — the cookies of Yandex Metrica.

  • sb-medaro-auth — the sign-in session: appears after you log in and is deleted when you log out; if you do not log out, the browser keeps it for up to 400 days. Without it signing in is impossible. If it holds a lot of data, the browser splits it into parts (sb-medaro-auth.0, sb-medaro-auth.1) — it is still the same cookie.
  • sb-medaro-auth-code-verifier — a one-off service cookie for the time of email confirmation and password recovery; once you are signed in it is no longer needed.
  • NEXT_LOCALE — the selected interface language: set only when you switch language or open medaro.am without a language in the address, and lives until you close the browser.
  • medaro_vid — a random identifier with no meaning of its own. It is set only when you open the page of a doctor who has verified their profile on the portal, lives for 48 hours and is needed for exactly one thing: so that the same visitor is not counted twice in one day.
  • _ga — a cookie of the Google Analytics counter: a random number for your browser, by which the counter tells a first visit from a repeat one. It holds no name, no email address and nothing from your profile. It lives for up to two years; the browser may shorten that (Chrome to 400 days, Safari to 7 days).
  • _ga_JQZD411NCY — the second cookie of the same counter: it holds the state of the current visit — when it began and how many pages have been opened. It lives for up to two years; the browser may shorten that in the same way.
  • _ym_uid, _ym_d and the service cookies of Yandex Metrica — on the ru.medaro.am mirror only. _ym_uid is a random number for your browser by which Metrica tells visitors apart, _ym_d is the date of the first visit; both live for a year. _ym_isad notes whether the browser has an ad blocker and lives for 20 hours; the service cookies _ym_metrika_enabled, _ym_hostIndex, _ym_fa and gdpr live from an hour to two years. Metrica sets these cookies on the medaro.am domain, so the browser also sends them to medaro.am, where nobody reads them. Metrica also keeps the visitor number and service marks about its own requests in the browser storage of ru.medaro.am. And when talking to Yandex servers, the browser — if it allows third-party cookies — receives and sends cookies of Yandex domains (yandexuid, yuidss, i, ymex, usst, yabs-sid, is_gdpr and others), by which Yandex recognises the browser on other sites and on its own services; they live for up to a year, is_gdpr for up to two years.
  • If your browser sends the “Do Not Track” (DNT) or Global Privacy Control signal, our doctor-page statistics do not count you and do not set the medaro_vid cookie, and your site searches do not enter the search statistics. Google Analytics and Yandex Metrica ignore this signal — you can switch them off with the Google and Yandex add-ons or a blocker (see “Who we share data with”).

A few more details for completeness — these are not cookies but notes and permissions the browser keeps on its side. After the registration form is sent, the browser in which it was filled in keeps, for one day, a local note that the boxes were ticked for the new account. Usually the consent is written to the log at the moment you confirm your email, whichever device you open the email on. If it could not be written then, the site adds it from this note when you sign in to that account in the same browser; nothing is written from it for any other account. The note is removed at that sign-in or, if there was none, the first time the site is opened in this browser after the day has passed. If you close the notice about an updated policy, the browser remembers that with a similar local note so as not to show it again; on another device or after clearing the browser the notice will appear once more. While the tab is open, the browser also remembers that your consent to the current version has already been checked, so as not to ask the server about it on every page. Likewise, while the tab is open, the browser remembers that you pressed “Later” under the request to confirm your consent. If you turned on notifications about new articles, the browser keeps your permission for medaro.am; a small service script that displays an incoming notification and opens the article when you tap it (it stores no pages and no data, and is removed when you turn notifications off on the site); and a note with a short fingerprint of the delivery address — not the address itself — plus the notification language and the version of this document: from it the site can tell that the subscription has not changed and does not contact the server on every visit. If you pressed “Not now” under the offer to turn notifications on, the browser remembers the date, and we do not offer them again for 90 days. On the devices of portal staff, the browser also keeps service notes — for the admin area, for test notifications, and so that visits from these devices are not counted in our site-search statistics and either do not reach the traffic counters or reach them marked as internal. Ordinary visitors and users do not have them; they can be removed by clearing the site’s data in the browser. These notes are never sent to the server.

Our own statistics: doctor pages, site search and letters to clinics

The portal counts how many times during a day the page of a doctor who has verified their profile was opened and how many times the “Call” button on it was pressed. The doctor sees these two numbers in their dashboard and uses them to judge how the profile performs.

Only the daily total is stored: the doctor, the date, the kind of event and the number. No IP address, no user agent, no page URL and no exact event time are kept, so an individual person cannot be reconstructed from this table.

The identifier from the medaro_vid cookie never reaches the database: before writing it is turned into an irreversible hash together with a server-side secret. The table that tells us this visitor has already been counted today is cleared automatically after two days.

The statistics are tied neither to your account nor to your profile: the daily total contains no user identifier and no visitor identifier.

One honest caveat: at the moment of a request our server sees both the technical cookie and — if you are signed in — your session, because they arrive together in the same request. They are not linked in storage, but it would be untrue to claim that such a link is technically impossible.

Since version v3 the portal also counts what people search for on the site — to see which doctors, clinics, tests and services the catalogue is missing. This covers the search for doctors, clinics, laboratories and conditions, the search on the map and, on organisation pages, the search in the price list and in services under state health insurance. Until now, the text you typed into the search for clinics, tests, conditions, the map or a price list never left your browser; now, when you stop typing or leave the page, the result of the search goes to our server: the query itself, the site section, the page language and the number of results found. Intermediate variants while you type are not sent. The query text does not go to Google: it is cut out of the page addresses the Google Analytics counter sees, and the counter’s “Site search” feature is switched off. For Yandex Metrica on the ru.medaro.am mirror it is likewise cut out of the addresses our code passes on and dropped by the counter’s settings in its reports. But in three kinds of service requests — occasional reports on loading speed, reports on failures of the Metrica script itself and the matching of identifiers with Yandex partners — the script takes the address from the address bar itself, and if the search text is in the page address (the doctor, pharmacy and medicine searches), it does reach Yandex with these requests (when and how often is described under “Who we share data with”, the “Yandex Metrica” paragraph).

Only the daily total is stored: the query, the section, the language, the date, how many times it was searched for, how many times the search found nothing and how many results the latest search found. The query is reduced to a plain form (lower case, no extra spaces or punctuation) and cut to 64 characters. Queries that look like an email address, a website address, a phone number or a document number (five or more digits in a row, or six or more digits in total) are dropped entirely — already in the browser and again on the server. With the “Do Not Track” or Global Privacy Control signal on, the query is not counted. The IP address is not written to the statistics table: the server keeps it only in memory — so that one person is not counted many times a day and to guard against inflated counts; a repeat of the same query from the same IP address within a day is counted once. There is no cookie, device, account or exact time in this table either, so this table alone cannot tell who searched for what. But the very fact that a search result was sent enters the server request log as an ordinary request — with the IP address and the time, without the query text. And the doctor search changes the page address, and the log records such an address in full, together with the search text (see “Server request log”). Only portal administrators see the totals.

An honest caveat here too: if someone types a person’s name into the search, it is stored as query text — with no link to whoever searched, but it is stored. If such a query needs to be removed, write to info@medaro.am — we will delete it from the statistics, and it will leave the backups within 3 months at most. So that it is not counted again, the query text itself stays only in a closed exclusion list — with no counts and no search dates; only administrators see that list.

Letters to clinics are a separate story. We write to the management of clinics, pharmacies and laboratories at the addresses they have published on their own websites: we tell them about the portal and link to their page in the catalogue. This is business correspondence with an organisation; we never use patients’ addresses for such letters.

In such a letter we see two things: that it was opened — through a transparent one-pixel image that the mail program loads from our server — and which links in it were clicked: “Open the clinic page”, the video about the portal, or simply the site address. The links run through our own domain, and where each of them leads is fixed on our server behind a short keyword: an outside site cannot be slipped into such a link. We count this for one purpose only — to understand whether the mailing is of any use and whether it is worth writing again.

What is stored: the address the letter went to, the organisation, the date it was sent, the marks that it was opened and which links were clicked, and the line by which the mail program or browser introduces itself. The last one is needed to tell a live opening from a preload by a mail service. We do not store the IP address in the mailing tables: what matters to us is the response, not where you connected from. Loading the images of a letter and following its links are ordinary requests to our server: they enter the request log with the full IP address and the full address of the link, including the letter’s code, so the log shows which organisation the letter was sent to. Marks about openings and clicks are kept for 6 months, the record of the letter itself for 12 months from the day it was sent.

Opting out is simple: reply with a single word — “no”, “stop”, “unsubscribe”, any of them will do — and we strike the address off the list; there will be no second letter. No explanation is needed. The same reply can be sent to info@medaro.am. A request not to write again we remember even after the remaining records about the letter are deleted — otherwise we would forget it and write again.

One honest caveat here too: “the letter was opened” is an estimate, not a fact. Apple and Google mail apps often load the images in a letter by themselves, before the person has even seen it — the opening is counted although nobody started reading. So we treat only a click on a link as a fact, and the number of openings as an approximate estimate.

Server request log

Since version v3 our server keeps a log of requests to the site. Its purpose is security, failure analysis and the investigation of abuse: to see attacks, break-ins, password guessing and abuse, and to know who uploaded what to the site; we also use it to see how search engines crawl the site.

For each request the log records: the date and time; the IP address in full and the country derived from it; the line by which the browser introduces itself (user agent) and the device type derived from it — phone, tablet or computer; the request method; the full page address, including the parameters after “?”; the response code, its size and how long it took to prepare; the site you came from — its domain only; and the site protection’s service mark (described below).

The page address is recorded in full. It shows which page you opened — for example, the page of a particular doctor, clinic, laboratory or condition — which filters you chose and what you searched for, if the search text was in the address. The IP address is recorded in full for every address, including the service addresses of our statistics and the images and links in letters to clinics. There is one exception: the values of sign-in parameters — one-time codes and keys from email-confirmation and password-recovery letters and the like — are replaced with the mark “[скрыто]” (Russian for “hidden”), so that the log cannot give access to other people’s accounts. The part of the address after “#” is never sent to the server by the browser at all.

What the log does not contain: what you send in the body of a request — form contents (except what the browser itself puts into the page address, such as the doctor search text) — passwords, cookies, the text of reviews and messages, or the account you are signed in with. The exception is uploading files to the site (currently, documents for doctor verification): uploads go to a separate upload log — the time, IP address, country, browser, the account that uploaded the file, the file name and type, size and result. It also records when and from which IP address these documents were opened. The notification delivery address and its encryption keys are also sent in the body of the request and do not get into the log; turning a subscription on or off, or updating it, is recorded like any other request — with the IP address, browser and time. Sending the “Spotted an error?” form gets into the log like any other request — a line with the IP address, browser and time, without the message text or the email address. The message itself is stored in the database with the exact time it was sent, so a server administrator can match a message to an IP address by time. To protect against abuse, the server limits how often the form can be sent by IP address, which it keeps only in memory and does not write to the database.

Site protection. To keep the site from being downloaded wholesale or otherwise abused, requests to it are checked by our protection. Cloudflare also filters traffic (see “Who we share data with”). We do not publish how the protection works: the details would help to get around it. If the requests from an IP address look like abuse, access from it may be temporarily restricted — a short message with our email address and a code is shown instead of the page. If you see such a message but have done nothing of the kind, write to info@medaro.am and include the code: an administrator will lift the restriction. For its work, the protection keeps on our server, separately from the request log, service records: the IP address, time, reason, number of requests, country, browser strings and details of the requests — for example, which sections of the site were opened. Only portal administrators see them; retention periods are given under “How long we keep data”. Of the protection’s data, only its service mark for each request goes into the request log itself — for example, whether the request was restricted.

The technical logs of the software our server runs on may also contain IP addresses — for example, when a doctor’s photo is requested. These logs are limited in size and are overwritten as they fill up — at today’s traffic, after roughly 1–5 weeks.

The logs are kept only on our own server in Armenia (the log of the ru.medaro.am mirror is also kept on the mirror itself for the first 7 days, likewise in Armenia) and are not included in backups. Only server administrators have access to them. We pass them to no one and combine them with nothing — not with Google Analytics, not with Yandex Metrica, not with accounts; we may disclose records only on a lawful request from an authorised state body. The request log and the upload log are kept for 12 months, after which records are deleted automatically.

The log is kept regardless of the “Do Not Track” signal. We keep it to protect the site, not as traffic statistics: there is no regular summary of visits to medaro.am drawn from it. Occasionally, when we investigate failures or how people find the site through search engines, we count totals from it — for example, how many pages search engine robots and people arriving from search opened in a day; such counts contain only numbers, without IP addresses. The log of the ru.medaro.am mirror is different: a summary of visits is drawn from it every day (see “Mirror for visitors from Russia”). Records are tied to an IP address, not to a name. To find out what the log holds about your IP address, write to info@medaro.am stating the address and the approximate time.

Mirror for visitors from Russia

The portal has a mirror — ru.medaro.am. Some Russian internet providers cut connections to the Cloudflare network through which medaro.am runs, so the site does not always open for visitors from Russia. That is why Cloudflare determines the country from the visitor’s IP address (which it sees anyway, see “Who we share data with”) and redirects visitors from Russia to the same page address on ru.medaro.am — together with the parameters after “?”.

The mirror runs on a separate Medaro server in Armenia. The connection to it is encrypted. The mirror takes pages from the main site medaro.am and shows you the same pages. When requesting them, it passes the page address, language and browser details to the main site — and so also to Cloudflare, through which the main site runs — but not your IP address: the IP address stays in the mirror’s request log, which is copied to our main server (see below). If the main site is unavailable, the mirror shows a copy of the public pages — the same one described under “Who we share data with”.

On the mirror you cannot sign in, leave a review, send a “Spotted an error?” message or turn on notifications about new articles — these buttons are hidden there or do not work; for that, open medaro.am or write to info@medaro.am. No doctor-page or site-search statistics are kept from the mirror, and Cloudflare Web Analytics does not work on it. Of its own cookies, the site on the mirror sets only NEXT_LOCALE — in the same cases as on medaro.am: when you switch language or open an address without a language (see “The cookies we set”); the counters’ cookies are covered below. The map base layer is loaded from the OpenStreetMap servers just as on medaro.am.

Two external traffic counters run on the mirror — Google Analytics and Yandex Metrica. Google Analytics is the same counter as on medaro.am, with the same rules; in its reports the mirror is told apart by the site name. Yandex Metrica, a service of YANDEX LLC (Russia), runs only on ru.medaro.am; there is none on medaro.am. It sees the address of the page opened and its title, the page you came from, whether you stayed on the page longer than 15 seconds, clicks on links to other sites and file downloads, your IP address and details of your browser and device. Our code passes page views to Metrica without the part of the address after “#”, without sign-in codes and without search text; the page address and the address of the page you came from are cleaned in the same way in the request with which the Metrica script fetches the counter settings each time a page loads. Metrica receives clicks on links only from pages whose address contains neither search text nor a part after “#”; it receives no taps on phone numbers or email addresses and no clicks at all on the emergency help page. But in three kinds of service requests the Metrica script takes the page address from the address bar itself — with the search text (the doctor, pharmacy and medicine searches put it there) and the part after “#”, if they are present: in occasional reports on loading speed (from no more than about one page load in 250), in reports on failures of the script itself (when such a failure happens) and when matching identifiers with Yandex partners, which Yandex turns on for some visitors under its own settings (no more than once per page load; the address of the page you came from is sent with it too). Details are under “Who we share data with”. Sign-in codes are never there, because the counters are not loaded while a code is in the address. In our counter’s reports the search-text parameter and the part after “#” are dropped by its settings. Recording of actions on the page (Webvisor), click and scroll maps, form analytics and Metrica’s automatic goals are switched off. Neither counter is loaded in “My account”, the doctor’s dashboard or the administration area, for automated checks, or while a sign-in code is in the address; on portal staff devices with a service note Yandex Metrica is not loaded at all. They ignore the “Do Not Track” signal. What exactly goes where, how long it is kept and how to opt out is described under “Who we share data with”, and the cookies under “The cookies we set”.

The mirror keeps the same request log as our main server (see “Server request log”): the time, the IP address in full, the browser string and device type, the request method, the full page address including the parameters after “?”, the response code, its size and how long it took to prepare, and the domain of the site you came from; the values of sign-in service parameters are replaced with the mark “[скрыто]”. There is no country in this log. The purposes are the same — security and the investigation of failures and abuse; in addition, a summary of visits to the mirror is drawn from this log every day (see below). Throughout the day the log is regularly copied to our main server in Armenia and kept there for 12 months, like the medaro.am log — also outside the backups; only server administrators have access to it. To protect against overload and abuse, the mirror limits requests from one IP address; for that, the address is held only in memory and forgotten shortly afterwards.

Summary of visits to the mirror. Once a day our main server counts totals for the previous day from the mirror’s log: how many visitors there were (different IP addresses of people; search engine robots are counted separately) and how many page views, which sections were opened and in which languages, which sites people came from (the site’s domain only), from which devices — computer, phone or tablet — and at what hours, how many requests search engine robots made, how many errors there were and how fast the mirror responded; for comparison, the same numbers for the day before and totals for 7 days. The totals are emailed to the portal administrators. The email contains only numbers, site domains and robot names — no IP addresses, page addresses, parameters or browser strings; the program holds IP addresses only in memory while it counts. The “Do Not Track” signal does not affect the summary: the log does not record it. Summary emails are kept in the administrators’ mailboxes like the rest of the correspondence.

On the mirror itself the log is kept for 7 days — with a margin, so that it reaches the main server even after a break in the connection — and is then deleted automatically. Only portal administrators have access to the mirror.

Notifications about new articles

From version v4 you can receive notifications about new articles in the Medaro blog — on your phone or computer, even when the site is closed. They never switch themselves on and never pop up by themselves: you need to press the consent button — at the end of an article or in the bell window in the site header — and then allow notifications in the browser’s prompt. Until you do, the site registers nothing in your browser and asks for no permissions. There is one topic — new blog articles. There are no topics about diseases or specialties and there will be none: choosing such a topic would in itself be information about health.

When you turn notifications on, the browser issues a delivery address — a long random link to the server of a delivery service that knows which browser on which device should receive the message — and two keys used to encrypt the notification text. We store them together with the notification language (the language of the page where you turned them on), the topic, the name of the delivery service (Google, Apple, Mozilla or Microsoft — we work it out from the address), the version of this document, the date you subscribed — without the time — the dates of the last successful and the last failed delivery, and the number of failed attempts in a row. Subscriptions of portal staff may also carry a service mark for test notifications.

What the subscription does not hold: an IP address, the browser string, the device model or any other information about the device, a link to an account — even if you are signed in — your history of visits to the site, or any record of which notification was shown to you and whether you opened it. We deliberately do not keep the time you subscribed: with the exact time, a subscription could be matched with an entry in the server request log. To guard against abuse, the server limits how often subscriptions can be turned on and off by an irreversible hash of the IP address, which it keeps only in memory and never writes to the database. If your browser’s delivery service is unknown to us, no subscription is created: we only note the name of that service’s server and how many times someone tried to subscribe through it — for 12 months, to decide whether it is worth supporting. The site’s admin area shows only totals: how many subscriptions there are, in which languages and with which services, how many people subscribed and unsubscribed per day; there are no subscription addresses there.

The notification is prepared by our server — usually the title and first sentence of a new article with its cover image — in the language of your subscription, and it links only to pages of medaro.am. It is delivered not by our server but by the delivery service your browser chose: Google, Apple, Mozilla or Microsoft, all of them in the United States (see “Who we share data with”). The notification text is encrypted with your browser’s keys, so the delivery service cannot read it. A notification is visible on the device screen, including a locked one, so for articles on sensitive topics it arrives with a neutral title and no image.

Your device loads the notification icon and image from our addresses medaro.am and api.medaro.am, like any image on the site. The link in a notification carries the parameters utm_source=push and utm_medium=web_push and the name of the mailing — the same for every recipient: from them Google Analytics counts how many visits a mailing brought, and the server request log records the address as it is. There is nothing in the link that points to your subscription or device. We count only how many notifications the delivery services accepted; we do not track whether a notification appeared on screen or who opened it.

You can turn notifications off at any moment with one tap: in the bell window in the site header, with the “Turn off notifications” button. The browser drops the subscription, the record in our database is deleted at once, and the notification service script is unregistered. You can also block notifications for medaro.am in your browser settings, and on an iPhone or iPad remove the site from the Home Screen: the delivery service will then tell us at the next sending that the subscription no longer exists, and we delete the record. A subscription to which five notifications in a row could not be delivered, or which has had no successful delivery for more than 60 days while its latest attempt also failed, we delete during the daily clean-up. Retention periods are listed under “How long we keep data”.

To be honest about it: the delivery address is a pseudonym, not a name, but the delivery service knows which browser on which device it belongs to — and often which Google, Apple, Mozilla or Microsoft account is signed in to that browser. We do not know that, but the request to subscribe is recorded in the server request log together with the IP address. That is why we treat a subscription as personal data and handle it like the rest: it is kept on our server in Armenia and, like everything else, goes into the backups.

Who we share data with

We sell data to no one and pass it to no one for advertising. Your records — the account, reviews, documents, notification subscriptions, the request log, search statistics — sit on our own server in Armenia; the request log of the ru.medaro.am mirror is also kept on the mirror itself for the first 7 days, likewise in Armenia. The portal uses no ad network and no CRM. Eight outside services are involved in running the site: the data of visitors and users passes through them or is stored with them, and we name all of them. Six apply to everyone: Cloudflare (together with its Cloudflare Web Analytics counter), Google Analytics, OpenStreetMap, Zoho Mail, Google Drive and PowerDMARC. The seventh — Yandex Metrica — runs only on the ru.medaro.am mirror. The eighth — your browser’s notification delivery service — is added only if you have turned on notifications about new articles. We use three more services to translate and parse open texts, and one of them, Anthropic, also to review applications, letters and messages — see below. We keep working tables with open information about organizations and doctors in the GitHub service — see below as well.

Cloudflare. The site runs through the network of Cloudflare, Inc. (USA): it filters traffic and protects the site against attacks, speeds up loading and connects visitors to our server. Every request to medaro.am and api.medaro.am passes through its nodes, so Cloudflare sees your IP address, page addresses, browser details and whatever you send to the site, including form contents — such a service cannot work without that. Cloudflare keeps information about requests under its own terms (cloudflare.com/privacypolicy). If a connection fails, the browser may send Cloudflare a technical error report: the page address and the type of failure. From the IP address Cloudflare also determines the visitor’s country: it redirects visitors from Russia to the ru.medaro.am mirror (see “Mirror for visitors from Russia”).

Copy of the public pages at Cloudflare and on the mirror. So that the portal stays available during failures, we keep at Cloudflare and on the ru.medaro.am mirror a copy of the public pages — only what everyone can see anyway: the catalogue, doctor cards and photos, organisation pages, published reviews, articles. Accounts, email addresses, unpublished reviews, documents, the request log and statistics are not in the copy; while the copy is shown, sign-in, forms and text search do not work. The copy is refreshed every day; if a refresh fails, the previous copy stays until the next successful one. Anything removed from the site disappears from the copy with the next successful refresh, and a doctor’s photo that it has been decided to remove on request disappears the same day, both at Cloudflare and on the mirror.

Cloudflare Web Analytics. The pages of medaro.am also run a second counter — Cloudflare Web Analytics, a service of the same company Cloudflare, Inc. (USA); the data is processed on its servers, including outside Armenia. Its script is inserted into the page by the Cloudflare network itself, and the browser loads it from the server static.cloudflareinsights.com. We need it to see where the site is slow for real visitors and how many pages are viewed. The counter sends Cloudflare the page address — without the parameters after “?” — the address of the page you came from, the loading time and speed measures: how fast the content appeared, how the page responds to taps and clicks and how much the layout shifts, together with which page element was the largest or shifted. Cloudflare works out the country, device type, browser and operating system from the request itself. This counter sets no cookies and stores nothing in the browser; according to Cloudflare, it does not fingerprint the browser and does not track individual people across sites. It runs on every page of medaro.am — unlike Google Analytics, also in “My account”, the doctor’s dashboard and the administration area — but it does not send what you type into forms or the contents of these pages. If you are served by a Cloudflare data centre in a country of the European Union or the European Economic Area, in the United Kingdom or in Switzerland, Cloudflare does not process this data — that is how we switched the counter on. Cloudflare keeps the detailed data for 7 days and after that in aggregated form; in the dashboard we can see totals for the last 6 months. The counter does not work on the ru.medaro.am mirror. You can switch it off by ordinary blocking of tracking scripts in the browser.

Google Analytics. The pages of the portal — on medaro.am and on the ru.medaro.am mirror — run the Google Analytics traffic counter — a service of Google LLC (USA). The data is processed on Google servers in the USA and other countries, that is, it is transferred outside Armenia. The counter sees: the address of the page opened — without the part after “#”, without sign-in codes and without search text — and its title; which page you came from; how long you stayed and how far you scrolled; clicks on links to other sites and file downloads; the start and submission of forms — without what you typed into them; since version v3, clicks on phone numbers and “Call” buttons (except short and emergency numbers) and on links to Google Maps, Yandex Maps and 2GIS, including in the “Get directions” block: what was clicked, in which part of the page and on the page of which organisation or doctor, without the phone number and without your location; as well as your IP address, device, browser, language and approximate location down to the city. We pass it no name, no email address, no phone number and nothing from your profile. In “My account”, the doctor’s dashboard and the administration area there is no such counter at all, and on portal administrators’ devices it is not loaded on the other pages of medaro.am either. The mirror runs the same counter; in its reports the mirror is told apart by the site name. The counter sets the _ga and _ga_JQZD411NCY cookies on the medaro.am domain, so they are shared by medaro.am and the mirror, and visits from one browser to both addresses look to it like one visitor. The counter’s advertising features are switched off: Google signals, ad personalisation, links to Google advertising accounts. Google Analytics keeps detailed visit data for 14 months; if you come back to the site, the period for data linked to your _ga cookie starts again. We need the counter for two things: to know how many people come and which sections they read, and to see whether the portal helps people call a clinic and get there. You can opt out — the official Google add-on (tools.google.com/dlpage/gaoptout) switches this counter off on every site at once; ordinary blocking of tracking scripts in the browser works too.

Yandex Metrica. On the ru.medaro.am mirror — and only there — the Yandex Metrica traffic counter also runs: a service of YANDEX LLC (Russia). Under the service terms Yandex processes this data on our behalf; it is processed on Yandex servers, including in Russia, that is, it is transferred outside Armenia. The browser loads the counter script from the mc.yandex.ru server and sends the data there. Yandex sees: the address of the page opened and its title; which page you came from; whether you stayed on the page longer than 15 seconds; clicks on links to other sites and file downloads, with the link address; your IP address; the browser, operating system, device type, screen size, language and other technical details of the browser and device by which Metrica tells visitors apart. Our code passes page views without the part of the address after “#”, without sign-in codes and without search text; we pass the script the page address and the address of the page you came from, cleaned in the same way, for the request with which it fetches the counter settings each time a page loads; clicks on links are passed only for links to websites and only from pages whose address contains neither search text nor a part after “#”; taps on phone numbers and email addresses and any clicks on the emergency help page do not go to Metrica. But the Metrica script sends three kinds of service requests on its own, and the page address in them is the one in the address bar — with the search text (the doctor, pharmacy and medicine searches put it there) and the part after “#”, if they are present: a technical report on loading speed — occasionally, from no more than about one page load in 250, when you have stayed on the page longer than 15 seconds; a report on a failure of the Metrica script itself — only if such a failure has happened; the matching of identifiers with Yandex partners (see below) — Yandex turns it on for some visitors under its own settings, no more than once per page load, and it also sends the address of the page you came from: if, for example, you opened the page from search results on our site in a new tab, that address contains the search text. These requests go to Yandex’s own service counters, not to ours, and our counter’s settings do not apply to them; sign-in codes are never in them, because the counters are not loaded while a code is in the address. Our counter’s settings drop the search-text parameter and the part after “#” in its reports. Yandex works out the visitor’s region, gender and age itself, from its own data. The script also exchanges identifiers with other Yandex addresses (for example, mc.yandex.md and mc.yandex.com.am), and the browser then sends cookies of Yandex domains if it has them: this way Yandex can recognise a browser it knows from other sites and its own services and match identifiers under its own rules. Depending on its settings, the Metrica script may also contact Yandex partners — telecom operators, for example — to match identifiers; they then see your IP address and browser. This is controlled by Yandex, not by us. Recording of actions on the page (Webvisor), click and scroll maps, form analytics, e-commerce and automatic goals are switched off; we pass the counter no name, no email address and no phone number. Where Metrica is not loaded is described under “Mirror for visitors from Russia”. We need it to know how many people use the mirror, which sections they need and whether they get through to clinic websites, maps and medaro.am. Yandex keeps the counter data for as long as the counter exists: Yandex sets no retention period for it, and we can delete it as a whole. You can opt out with the official Yandex Metrica opt-out add-on for Chrome and Firefox (yandex.ru/support/metrica/general/opt-out.html); ordinary blocking of tracking scripts in the browser works too.

Notifications. If you turned on notifications about new articles, we send them through the delivery service chosen by your browser, not by us: Google (Chrome, browsers on Android and most Chrome-based browsers), Apple (Safari on iPhone, iPad and Mac), Mozilla (Firefox) or Microsoft (Edge). All four are US companies, so the delivery address and the encrypted notifications are transferred outside Armenia. The service cannot read a notification: it is encrypted with your browser’s keys. What it sees is that medaro.am sent a message to this address, when, and how large it was. Your browser is connected to this service regardless of us — that is how it receives notifications from any site; how the service handles that data is described by the maker of your browser.

Maps. On the “Map” page and in the mini-maps on the pages of clinics, pharmacies, laboratories and pharmacy and laboratory chains, the base layer is loaded from the OpenStreetMap servers (tile.openstreetmap.org; OpenStreetMap Foundation, United Kingdom). Your browser talks to them directly: they see your IP address, your browser, the fact that you came from medaro.am (the address of the particular page is not passed) and which part of the map is shown — in a mini-map, the area around the organisation you are viewing. If you press “Near me” on the map, the map servers receive the areas around your location; the coordinates themselves are sent neither to us nor to OpenStreetMap. Fonts and images are served from our own domain; apart from the services named in this section and the addresses their scripts contact (see “Yandex Metrica”), the browser talks to no one.

Links to Google Maps, Yandex Maps, 2GIS and to clinics’ websites lead to other people’s sites: nothing is passed to them until you click, and after that their own rules apply.

Email. The portal’s email runs on Zoho Mail (Zoho Corporation; our mailbox is hosted in a Zoho data centre in the USA). Registration confirmations and password recovery emails, moderators’ emails to account addresses (for example, to the author of a rejected review — why it was rejected and how to correct it), letters to clinics, emails to people who sent a “Spotted an error?” message — the confirmation of receipt, the outcome of the check and the moderator’s replies — emails to doctors about the progress of a verification application and notices to moderators about applications go out through Zoho. Copies of these emails remain in the “Sent” folder of the info@medaro.am mailbox; if an email is not delivered, a non-delivery notice with the address the email did not reach arrives in this mailbox. Our program reads such notices without changing anything in the mailbox, to mark on the message or on the email to the doctor that the email bounced. Before sending a form email or an email to a doctor it checks through the Domain Name System (DNS) whether the domain of the address accepts mail — only the domain is looked up, not the address itself. The info@medaro.am mailbox also holds the letters you send us — including requests about your data and opt-outs from the mailing. Zoho sees the addresses, subject and text of the letters. The portal has no mail server of its own.

Google Drive. Encrypted backups of the database and files are stored in Google Drive, a cloud storage service of Google LLC (USA), on Google servers outside Armenia, which means they are transferred out of Armenia. Only we hold the encryption key, so Google sees encrypted files, not their contents.

DMARC reports. So that no one can send letters in the name of medaro.am, mail services that receive letters with our address as the sender send reports about them. These reports go to the PowerDMARC service of MENAINFOSEC, Inc. (USA, State of Delaware; the service’s data is hosted on Amazon Web Services servers), which means they are transferred outside Armenia. The reports contain technical data about letters sent in the name of medaro.am: which mail server sent them, how many, and whether they passed authentication. Detailed reports about letters that failed authentication may contain recipients’ addresses — yours, for example, if our letter to you failed the check — and letter headers: sender, recipient, subject, date. We need the reports for one thing: to notice forgery of our address in time and protect recipients from it. PowerDMARC keeps them under its own terms (powerdmarc.com/privacy-policy): as long as needed to run the service and as required by law, and after that only in anonymised form.

Translation and parsing of open texts. To translate open information about organizations and doctors into other languages and to parse the pages of their websites, we send these public texts, including doctors’ names, to OpenRouter (USA), Google (USA) and Anthropic (USA). Data about visitors, accounts, applications and reviews is not part of this work.

Review of applications, letters and messages. When administrators review doctors’ applications together with the documents sent, letters to info@medaro.am and “Spotted an error?” messages, they also use the Claude service of the same company, Anthropic PBC (USA). Their texts and files, and their authors’ names and email addresses, are thereby transferred outside Armenia. Anthropic keeps and uses them under its own terms (anthropic.com/legal/privacy): among other things, it may use them to train and improve its models and keep them for this purpose for up to 5 years, and whatever has already gone into trained models stays in them. The decision on each of them is made by an administrator. We do not use Claude for reviews, letters about reviews and disputes over them, or documents confirming a visit.

Working tables. The tables in which we collect and check open information about organizations and doctors (names, addresses and phone numbers of organizations; names, specialties, places of work and education of doctors; the addresses of the pages the information was taken from) are stored, together with the history of edits, in a private repository of the GitHub service by GitHub, Inc. (USA). We do not put doctors’ documents, account data, reviews or the server request log there.

Apart from the services named here, we hand over data only on a lawful request from an authorised state body. We have no other grounds for disclosure.

How long we keep data

The retention periods in force today.

  • Account, reviews and doctor profile — for as long as you use the portal. Verification documents and the record of the check — for another 3 years after the account is deleted or consent is withdrawn.
  • Sign-in sessions on the server — until you log out; the sign-in service event log — 12 months; records of attempts to enter the second-step sign-in code and an unfinished app attachment — about a day; information about an attached app — for as long as it stays attached.
  • Rejected verification documents — 90 days, after which the file is deleted from storage.
  • Daily statistics for a doctor — 400 days.
  • The table that records “this visitor has already been counted today” — 2 days.
  • Site-search statistics (anonymous daily totals) — 24 months; queries that have only ever been searched for once — 90 days.
  • The server request log and the file upload log — 12 months.
  • The request log of the ru.medaro.am mirror — 7 days on the mirror itself and 12 months on the main server.
  • Records of the site’s protection against abuse — no longer than 90 days; the list of restricted addresses — for as long as the restriction lasts (it is lifted automatically when it expires); service notes about individual IP addresses of visitors and users — no longer than a year. The protection’s service mark in a line of the request log is kept together with the log — 12 months.
  • Technical logs of the server’s services — roughly 1–5 weeks at today’s traffic: they are limited in size and overwrite themselves.
  • Visit data in Google Analytics (medaro.am and the mirror) — 14 months.
  • Cloudflare Web Analytics data — detailed for 7 days, then in aggregated form; totals are available to us for 6 months (the periods are set by Cloudflare).
  • Information about requests to the site held by Cloudflare — under its own terms (the periods are set by Cloudflare).
  • Yandex Metrica data (the ru.medaro.am mirror only) — for as long as the counter exists: Yandex sets no retention period, and we can delete the data as a whole.
  • DMARC reports at PowerDMARC — under that service’s terms: as long as they are needed for it to work and as required by law.
  • Doctors’ applications, letters to info@medaro.am and “Spotted an error?” messages that administrators reviewed with the help of Claude — at Anthropic, under its terms: to train and improve its models, it may keep them for up to 5 years, and whatever has gone into already trained models stays in them.
  • Working tables with open information about organizations and doctors in GitHub — for as long as we need them to check information; earlier versions remain in the history of edits.
  • Notification subscription — until you turn it off. If the delivery service replies that the subscription no longer exists (you blocked notifications or removed the browser), we delete it at once; if five notifications in a row could not be delivered, or there has been no successful delivery for more than 60 days and the latest attempt also failed, it is deleted in the daily clean-up. Totals on subscriptions and mailings, with no addresses, and the texts of sent notifications — 24 months. The “Not now” note in the browser is in effect for 90 days.
  • Cookies: sb-medaro-auth until you log out, but no longer than 400 days; sb-medaro-auth-code-verifier until sign-in is complete; NEXT_LOCALE until you close the browser; medaro_vid for 48 hours; service cookies on portal staff devices for no longer than 30 days; _ga and _ga_JQZD411NCY for up to two years (the period is set by Google Analytics, and the browser may shorten it); on the mirror, _ym_uid, _ym_d and _ym_fa for a year, _ym_isad for 20 hours and the other Yandex Metrica cookies from an hour to two years (the periods are set by Yandex). Any of them can be deleted in your browser settings at any moment.
  • The consent log and the moderator action log are kept for as long as we need them to demonstrate that processing was lawful and that decisions on reviews were justified.
  • “Spotted an error?” messages and the records of emails — until the message has been dealt with and for 12 months after that. In a message that has not been dealt with, we keep the email address for no longer than 12 months from receipt: after that we delete it and the message stays without an address; earlier — at your request (see “Your rights”). Copies of our emails and non-delivery notices in the info@medaro.am mailbox are kept like the rest of the correspondence — see the item on that mailbox below.
  • Records of emails to a doctor about an application — 12 months from the day the email was queued, or, if the account is deleted, they are removed at once. Copies of the emails themselves and non-delivery notices in the info@medaro.am mailbox are kept like the rest of the correspondence.
  • Letters to clinics: marks about openings and clicks — 6 months; the record of the letter itself — 12 months.
  • Letters in the info@medaro.am mailbox — with no time limit: this is our correspondence with you and with organisations, including your requests about your data, copies of our emails about “Spotted an error?” messages and about doctors’ applications, notices to moderators about applications and non-delivery notices. The exception is emails with a document confirming a visit that the author of a review sends during a dispute: we delete them after the check.
  • Backups of the database and files: daily ones for 30 days, those taken on the first day of the month for up to 3 months; no backup is kept longer than 3 months. The copy of the public pages at Cloudflare and on the ru.medaro.am mirror is refreshed every day (if a refresh fails — at the next successful one), replacing the previous one.

Your rights

You have the right to obtain a copy of your data, to correct it, to delete your account and to withdraw consent.

Some of this is not yet available as a button: the “My account” section shows your reviews and their status, but there is no self-service account deletion on the site yet. Write to info@medaro.am from the address the account is registered to and we will carry out the request and reply by email. We will delete the email address from a “Spotted an error?” message before the deadline if you reply to our email or write to info@medaro.am; the message itself stays without the address, and copies of emails already sent remain in the info@medaro.am mailbox like the rest of the correspondence. Copies of applications, letters and messages that administrators reviewed with the help of Claude are kept by Anthropic under its terms, and deleting data on our side does not extend to them (see “Who we share data with”).

Notifications about new articles are turned off without writing to us — in the bell window in the site header or in your browser settings (see “Notifications about new articles”). A subscription is linked neither to an account nor to an email address, so we cannot find it by your name or email: it can be turned off only on the device where it was turned on.

About reviews specifically: when an account is deleted the reviews do not disappear from doctors’ pages — they lose the link to you and stay anonymous. Otherwise ratings would lose scores retroactively and the picture other patients see would be distorted. If you want the text of your own review taken down, say so in the message.

About doctor cards specifically: if a doctor deletes their account or withdraws consent, we remove from their page the “Credentials verified” mark, the details under it and the first-100 mark. A card we compiled from open sources stays on the site as an ordinary card, while a card created only from the doctor’s application is taken off the site. We keep the documents sent to us and the record of the check closed for another 3 years, so that we can show on what basis the doctor was verified: at Medaro, only administrators see them.

Medical confidentiality

A doctor’s reply to a review is public text: every visitor to the page can read it.

For that reason a doctor’s reply must not disclose information about the patient: the diagnosis, treatment and test results, the date and circumstances of the visit, or the name. A reply containing such details is not published.

Every doctor’s reply is moderated before publication — a doctor cannot publish text directly. A doctor also does not moderate reviews about themselves and cannot delete them: the only tools available are a public reply and a report to a moderator.

What changed in version v10

Compared with version v9 of 13 November 2026.

  • The site’s protection against abuse is now described in general terms: we do not publish how it works, so that it is harder to get around. What data it keeps, who sees it and how long it is kept is stated as before (sections “What we store”, “Server request log” and “How long we keep data”).
  • It is stated that Cloudflare also filters traffic and that it keeps information about requests under its own terms (sections “Server request log”, “Who we share data with” and “How long we keep data”).
  • Service cookies and notes on portal staff devices are described in general terms (sections “The cookies we set” and “How long we keep data”).
  • It is specified that the ru.medaro.am mirror limits requests from one IP address to protect not only against overload but also against abuse; the address is held for this only in memory (section “Mirror for visitors from Russia”).
  • This changes the introduction and the sections “What we store”, “The cookies we set”, “Our own statistics: doctor pages, site search and letters to clinics”, “Server request log”, “Mirror for visitors from Russia”, “Who we share data with” and “How long we keep data”; everything else is as in version v9.

Version v10 of 16 November 2026; the previous one is v9 of 13 November 2026. The document describes how the portal actually handles data. A new version is published on this same page with a new number and date and a list of what changed.