Informational English translation of the Cartelta cookie policy, including cookie categories, analytics consent, settings, and the cookie table.
This English page is provided for information only. The Russian version remains authoritative where that position applies to the company.
Cartelta uses technical cookies and similar technologies to operate the site and account area, protect sessions, store user settings, measure traffic, and analyze service stability.
Required cookies are needed for the site to work, to protect the form from abuse, and to remember cookie settings. A user may delete them through browser settings, but the site will then ask for a new choice.
Yandex Metrica and Google Analytics are not loaded before consent. If the user rejects optional cookies, the site stores that rejection and does not load analytics scripts.
Current configuration status: Yandex Metrica is disabled, Google Analytics is disabled. Public counter IDs are also required before those integrations can operate.
| Cookie / storage key | Provider | Category | Purpose | Data | Retention | Domain | Before consent | Can be disabled | Status |
|---|---|---|---|---|---|---|---|---|---|
| cartelta_cookie_consent_v1 | Cartelta | Required | Stores the user's cookie choice, consent version, consent date, domain, and consent page. | Consent categories, date and time of choice, domain, page, and technical consent ID. | Until the user changes settings, clears browser data, or the consent version changes. | Current site domain | Yes | No, otherwise the site cannot remember the user's choice | Implemented on the site |
| _ga | Google Analytics | Analytics | Traffic analytics and differentiation between users and sessions. | Cookie identifier plus technical visit, page, device, and browser data. | Usually up to 2 years; the exact period depends on GA4 settings. | Current site domain | No | Yes | Supported in the codebase, currently disabled by configuration |
| _ga_* | Google Analytics | Analytics | Stores GA4 session state and parameters. | Session identifiers and technical visit parameters. | Usually up to 2 years; the exact period depends on GA4 settings. | Current site domain | No | Yes | Supported in the codebase, currently disabled by configuration |
| _gid | Google Analytics | Analytics | Traffic analytics when the corresponding Google Analytics mode is used. | Cookie identifier and technical visit data. | Usually up to 24 hours; the exact period depends on Google Analytics settings. | Current site domain | No | Yes | May be set depending on Google Analytics settings |
| _ym_uid | Yandex Metrica | Analytics | Traffic analytics and visitor differentiation. | Cookie identifier and technical browser, device, visit, and page data. | According to Yandex Metrica settings and the applicable service configuration. | Current site domain | No | Yes | Supported in the codebase, currently disabled by configuration |
| _ym_d | Yandex Metrica | Analytics | Stores the first visit date for analytics. | Technical identifier or visit date. | According to Yandex Metrica settings and the applicable service configuration. | Current site domain | No | Yes | Supported in the codebase, currently disabled by configuration |
| _ym_isad | Yandex Metrica | Analytics | Detects ad blocker presence and supports analytics quality checks. | Technical browser flag. | According to Yandex Metrica settings and the applicable service configuration. | Current site domain | No | Yes | Supported in the codebase, currently disabled by configuration |
| _ym_visorc | Yandex Metrica | Analytics | May be used by Webvisor. Webvisor requires separate legal and product review. | Technical session data; the exact scope depends on Webvisor settings. | According to Yandex Metrica settings if Webvisor is enabled after separate review. | Current site domain | No | Yes | Webvisor is disabled in the codebase; do not enable it without separate review |
The actual list of cookies, their purpose, and retention periods are clarified based on the deployed technology stack and updated in this section when the set of technologies changes.
The user can open cookie settings at any time through the footer or the button below.
Cookies can be deleted in browser settings. This is usually under privacy, security, cookies, or site data. After deletion, the site will show the cookie banner again.
Open cookie settings and choose to reject optional cookies, or disable analytics cookies and save the settings. The site will update the consent state and try to remove known analytics cookies for the current domain.
Yandex Metrica is used for visit analytics only after consent. Google Analytics may involve processing or transferring technical data outside the Russian Federation and requires separate legal review.
See the Privacy Policy for more detail.
Version: 2026-05-09.1. Revision date: 2026-05-09.
© 2026 Cartelta. All rights reserved.
Send request