Short version: the site's own code still sets no cookies, but two services do. Google measurement — Google Analytics and the Google Ads tag — loads for every visitor at once and sets its cookies straight away; "Only essential" in the notice switches it off. Yandex Metrica starts only after you press "Allow". What follows is the exact picture.
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. Every cookie you find in your browser belongs to the services below — Google and Yandex. Google's appear as soon as a page opens, unless you have already chosen "only essential"; Yandex's appear only after you press "Allow".
What we store without asking
From the site itself, 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, and so that after "only essential" the Google tags stay off on the pages you open next. Google measurement itself does not wait for your answer — see the next section.
What loads for every visitor
Google measurement. It comes through Google Tag Manager (container GTM-TVZLJCNM) — not a counter but a container, whose contents are set up in Google's panel rather than in this site's code. It loads as soon as a page opens, without waiting for your answer, and holds two tags:
- Google Analytics: visit statistics — how many people come and which pages they read.
- Google Ads tag: shows which ads bring requests.
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.
What starts when you press "Allow"
One more thing, loaded at that moment and not a second earlier:
- Yandex Metrica: visit statistics, running with Webvisor and a click map. 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.
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 googletagmanager.com and mc.yandex.ru and the data goes to Google and Yandex. Google's appear as soon as a page opens, Yandex's only after "Allow". The terms below are not quoted from documentation — they were read out of a real browser; the exception is _gcl_aw and _gcl_gb, which appear only after a click on a Google ad:
_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 ad brought the request._gcl_aw,_gcl_gb: the Google Ads tag again, only if you arrived by clicking a Google ad — they hold the identifier of that click for up to 90 days.
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 requests rather than clicks. The numbers printed on the pages are ours and stay ours; nothing swaps them for tracking numbers. The site sends the counters its own events: a tap on the phone number and a tap on WhatsApp, only as the bare fact of the tap; Google also gets the fact that a request form was sent, with our request number. The rest the counters read themselves: the page address, where you arrived from, browser language, screen size and an anonymous identifier of your browser.
Your name is not sent to Google. The phone number from the form is, but only as a one-way SHA-256 hash made in your browser before sending, and only to match the request with an ad click; Google calls this enhanced conversions. The request itself — name, phone, page and the ad labels from the link (utm tags, gclid and the like) — goes to our CRM (Bitrix24).
Saying no
Press "only essential" and Google measurement switches off: the site stops sending its own events to Google straight away, and on the next pages the Google tags are not loaded at all. Yandex Metrica stays off. Ignoring the notice keeps Yandex Metrica off — for it, silence counts as refusal — but not Google measurement: that runs until you press "only essential".
Changing your answer later
and choose "only essential" — it works whether you allowed earlier or never answered. Precisely what changes: the site stops sending its own events straight away, and on the next page you open neither the Google tags nor Yandex Metrica start at all. The tags already loaded into the page you are reading cannot be unloaded — they go 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: on your next visit Google measurement runs again and the notice asks again — answer "only essential" and it stops.
Third-party services
Apart from the measurement above, every page — typefaces, styles, images and the branches map included — loads from this site's own server; the typefaces are self-hosted since 08.2026. 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.
