Back to Archground

Cookies

Effective date: 8 August 2026

This English text is a translation provided for convenience. The Russian version is the governing text: this service is operated under the law of the Russian Federation, and in case of any discrepancy the Russian wording prevails.

A cookie is a small record a site stores in your browser. Below is every cookie Archground may set. The list is complete: if a file is not in the table, we do not set it.

Today the site is a page describing the product plus an embedded, read-only demonstration of a synthetic model. There is no sign-in.

Which cookies are set

Name Set by Purpose Lifetime Essential
archground_locale Archground (first party) Remembers the language you chose 12 months Yes
ag_consent Archground (first party) Stores your answer about cookies — "necessary only" or "accept" — and the version number of the text you answered 12 months Yes
Yandex Metrica cookies Yandex (third party), loaded from mc.yandex.ru Web analytics: visit counting, click map, outbound link tracking, accurate bounce rate Set by Yandex No

We do not list the names of the Yandex Metrica cookies. Yandex sets them, and changing them is Yandex's business, not ours — a list we wrote down today could be wrong tomorrow.

Both of our cookies are first-party: only this site reads them. archground_locale is HttpOnly, because no script on the page reads it. ag_consent is deliberately not HttpOnly: the page has to read it to decide whether to show you the dialog at all.

Yandex Metrica

We use counter no. 111410802. It loads only after you press "Accept" — never before, and never after a refusal.

Enabled: click map, outbound link tracking, accurate bounce rate. Session replay (Webvisor) is off — your mouse movement, typing and screen contents are not recorded.

Once the counter is loaded, Yandex receives the ordinary web-analytics set: IP address, browser details (user agent), the addresses of the pages you view, the referring address, screen size, approximate location derived from the IP address, and its own identifiers stored in your browser. Yandex processes this as a separate operator under its own terms.

There is no <noscript> tracking pixel on the page. That is deliberate: such a pixel cannot read a consent cookie and would fire even for someone who refused.

We do not sell data, we show no advertising, and we do no profiling that produces legal effects for you.

Nothing non-essential loads before you choose

Most cookie notices are silent about this, so plainly: until you answer, Yandex Metrica is not loaded. Not "loaded but anonymised", not "loaded and waiting for permission" — it is simply not on the page.

Which means: if you never answer, you are never counted. Dismissing the dialog, leaving the page, or ignoring the question are all working options, not deferred consent.

How to refuse

Press "Necessary only" in the dialog. That is one click, it carries the same weight as "Accept", and it is not hidden behind extra screens.

A refusal is honoured: analytics will not load this time, and will not load on later visits while your answer stands. The essential cookies in the table above keep working either way — without them we cannot hold your language choice, or your refusal itself.

How to change a recorded choice

Delete the ag_consent cookie in your browser's settings for this site (or clear the site's cookies entirely). The dialog will appear again the next time you open the page, and you can answer afresh.

If we materially change the wording of the question, the version number in ag_consent changes and we ask everybody again. An answer given to different wording is consent to that wording, not to this one.

If your browser blocks cookies

A browser-level block applies here too: we will not be able to store anything. There are exactly two practical consequences. Your language choice will not persist between visits, so the page will work the language out again each time. And your cookie answer will not be stored, so the dialog will appear every time you open the page — analytics still will not load, because an answer we cannot read counts as no consent.

On blocking third-party cookies specifically: that already matches our default behaviour — before you consent there are no third-party cookies here.

What is not a cookie

The server keeps request logs: the address requested, the time, the IP address and the user agent. That is needed to run the site, it has nothing to do with cookies, and refusing cookies does not affect it. See the Privacy Policy for details.

Questions

The operator of personal data is Sergei Sergeevich Zobnin, a natural person. Questions about this notice, withdrawal of consent, and any request: sck.spb@yandex.ru.