Short version: the site itself still sets no cookies, but since 08.2026 two statistics services do — and only after you press "Allow" in the notice. What follows is the exact picture: the cookies and the terms below were read out of a real browser, not copied from a template.
Cookies of our own
None. No session cookie and no cookie of ours at all, because the site has no accounts and nothing to keep you signed in to. Everything you find in your browser after you allow statistics belongs to the services below — Yandex and Google — and none of it appears before that.
What we store without asking
One thing: your answer to the notice, written into your browser's local storage under the key wr-consent. That is not a cookie — it never leaves your device and is not sent with requests. It exists so the notice does not ask you the same question on every page. Until you answer, and for as long as your answer stays "only essential", this record is the single trace the site leaves in your browser.
What starts when you press "Allow"
Two things load at that moment, not a second earlier:
- Yandex Metrica: visit statistics, running with Webvisor on. Besides counting visits it records how the page was used — mouse movement, scrolling, clicks, the order pages were opened in — and plays that back to us as a session recording. We watch those to find where people get stuck: a button nobody notices, a step of a form nobody finishes.
- Google Tag Manager: not a counter but a container, and what sits inside it is set up in Google's panel rather than in this site's code. Measured in 08.2026 it holds two tags — Google Analytics, the same kind of visit statistics, and the Google Ads tag, which reports which advertising campaign ended in a call.
A container can be refilled without a single line of the site changing, so we cannot promise its contents will stay these two. What the site does fix is how far they may reach: its security policy lets a page talk to Yandex and Google and to nobody else. Advertising pixels of other networks are configured in that container as well, and the browser blocks them — measured in 08.2026, they load nothing and receive nothing.
Which cookies appear, and for how long
They are all kept in your browser under this site's address, although the scripts that set them come from mc.yandex.ru and googletagmanager.com and the data goes to Yandex and Google. The terms below are not quoted from documentation — they were read out of the browser right after pressing "Allow":
_ym_uid,_ym_d: Metrica's anonymous browser identifier and the date of your first visit — a year each._ym_isad,mdd: Metrica's housekeeping — a day._ym_visorc: the Webvisor recording — minutes; it goes with the session._ga,_ga_…: Google Analytics — 400 days, the longest a browser will keep a cookie set by a script._gcl_au: the Google Ads tag — 90 days. This one is an advertising cookie, and it is the price of knowing which campaign brought the call.
Metrica also sets several cookies on its own domain, yandex.ru, through a matching frame. Those live outside this site's address: a general clearing of cookies removes them, and a browser that blocks third-party cookies never lets them appear.
What it is for
Two things: seeing how many people come and which pages they actually read, and telling which advertising brings calls rather than clicks. None of this is personal data — no name, no phone number, nothing you type into a form. The numbers printed on the pages are ours and stay ours; nothing swaps them for tracking numbers. The site sends the counters two events of its own, a tap on the phone number and a tap on WhatsApp, and only as the bare fact of the tap. The rest they read themselves: the page address, where you arrived from, browser language, screen size and an anonymous identifier of your browser.
Saying no
Press "only essential" and nothing loads: no counter, not one request. Ignoring the notice has the same effect — silence counts as refusal here. No tag pointing at Yandex or Google sits in the page waiting to fire; the scripts are created after your answer, so before it there is nothing to switch off. Measured on the English, Russian and Arabic home pages: zero requests to mc.yandex.ru and googletagmanager.com until the answer is given.
Taking it back after you allowed
and choose "only essential". Precisely what changes: the site stops sending its own two events straight away, and on the next page you open the counters do not start at all. The counter already loaded into the page you are reading cannot be unloaded — it goes when the page does, at your next click or reload.
The cookies already set stay until their term runs out, and this page has no way to delete them for you. To be rid of them now, clear this site's data in your browser — the setting is usually under Privacy, and cookies can be cleared one site at a time; the few Yandex cookies mentioned above sit under yandex.ru and go with a general clearing. That also wipes the wr-consent record, so the notice will ask again on your next visit; answer "only essential" and the counters will not come back.
Third-party services
Apart from the statistics above, every page — typefaces, styles, images and the branches map included — loads from this site's own server. Since 08.2026 the typefaces are self-hosted, so opening a page sends nothing to Google or anyone else. The one exception is the podcast player: if you choose to play an episode, the video loads from YouTube (youtube-nocookie.com, the privacy-enhanced embed) — only after your click, never on page load — and YouTube may set its cookies at that point.
If you want to avoid even that, simply don't start the videos.
Blocking cookies in general
Every browser can refuse or delete cookies in its settings — usually under Privacy. Blocking them does not break this site: nothing here depends on a cookie, and the counters simply lose the ability to tell one visit from another.
