Current version · Cookie and browser storage policy
Necessary cookies, functional storage, and optional analytics
Strictly necessary data is always active. The interface language is retained between visits only after consent to functional storage. Yandex Metrica remains disabled and is not loaded until separate explicit analytics consent; refusal does not affect site functions.
- Version
- 2026-08-16-metrica-2
- Effective from
- August 16, 2026
- SHA-256
- e0566eea5511620dac3d82db9fdce6e51724e31fbde13e6c21853ead7f226188
Provider and company details: view company details
Authentication cookie — up to 30 days
A session cookie confirms sign-in to the client portal and lasts no longer than 30 days under the security settings. You can end it by signing out or clearing this site's data.
Cookie choice — one year
A versioned consent cookie retains one of Necessary only, Functional, or Analytics + functional for up to one year. It is strictly necessary so the site does not ask for the same choice every time it opens. Retaining the choice itself does not enable analytics unless the separate third option was selected. The analytics value includes this published legal release ID, so a later release does not reactivate the earlier choice.
Language — only with permission, up to one year
After Functional is selected, a cookie and localStorage retain the chosen interface language for up to one year. Without that permission, language switching still works in the current URL but is not written to the cookie or localStorage.
Current-tab state
sessionStorage is used only for temporary state in the current tab and is removed when the tab closes. It is not used for cross-site tracking.
Yandex Metrica — only after separate consent
Before Accept analytics + functional is selected, Yandex Metrica code is not loaded, no network request is made to its provider, and analytics cookies are not created. After consent, the browser may create technical analytics-storage identifiers and sends the provider the request's technical IP address, time, browser and device characteristics, a sanitized page path, and only two fixed events: successful registration and the start of a purchase.
Data minimization and disabled features
The query string, hash fragment, and dynamic identifiers are removed from the path, and an empty referrer is supplied. Names, email addresses, phone numbers, INN, raw user IDs, account, order, or payment IDs, proxy credentials, UTM tags, and form or page contents are not sent to analytics. Webvisor, session and form recording, click maps, link tracking, ecommerce, content analytics, tag manager, user parameters, and account mapping for cross-device tracking are disabled.
Purposes, ground, and retention
Analytics is used only for aggregate measurement of visits and routes, successful-registration and purchase-start conversions, and interface improvement. The ground is separate voluntary consent. Technical identifier periods follow Yandex's current documentation: most analytics identifiers last up to one year, certain technical cookies last up to two years, and yandexuid may last longer than one year in some countries. The counter interface provides no single operator-controlled retention period for all provider data. Advertising and marketing profiling are not performed.
Provider, route, and transfer
Technical analytics data is received by YANDEX LLC (16 Leo Tolstoy Street, Moscow) under the then-current Yandex Metrica terms. The site does not independently send analytics data to any other foreign recipient. If the contractual recipient, the actual processing arrangement, or applicable requirements change so that a cross-border-transfer notice or another mandatory procedure is required, new transmissions are suspended until the requirement is satisfied and updated information is published.
Change or withdraw the choice
The Cookie settings button reopens all three choices. Switching to Necessary only stops future transmissions, destroys the in-browser counter instance, and removes first-party _ym-prefixed cookies and storage accessible to the site, as well as the language cookie and localStorage entry. Data already sent to the provider is processed and deleted under Yandex's then-current terms and documentation, or earlier when an applicable verified request requires it.