Version 2.0. Prepared on 24 August 2026 and effective from the date of publication on the website.
Language note. This English-language version is provided for convenience and mirrors the Russian-language document. In case of any discrepancy, the Russian-language version published at /ru/cookies prevails.
1. General provisions
This Policy explains the use of cookies and similar browser technologies on eaglis.ru. It applies together with the Personal Data Processing Policy.
The website Operator is Individual Entrepreneur Anna Arefovna Evstratova, Tax ID (INN) 616810901920, Primary State Registration No. (OGRNIP) 325619600176478. Questions may be sent to contact@eaglis.ru.
2. What cookies and similar technologies are
Cookies are small pieces of data that a website or connected service may store in the user's browser. Similar technologies include localStorage and sessionStorage, which can store technical settings, identifiers or state on the user's device.
3. Strictly necessary technology
The website stores the user's analytics choice in localStorage. The Russian version uses eaglis.analytics-consent.ru; the English version uses the separate key eaglis.analytics-consent.en.
The saved value contains the selected status, the identifier of the current terms and the decision date. The choice remains valid for 180 days. If it is missing, corrupted, belongs to another version or has expired, analytics is treated as not allowed and the website asks for a new choice.
Storing the choice itself is necessary so the website can apply the requested setting. It is not used for advertising profiling or hidden analytics.
4. Yandex Metrica
The website is prepared to use Yandex Metrica tag 111908478 to measure traffic, traffic sources and page views. Metrica code loads only after the user explicitly allows analytics for the current language version of the website.
Before permission, after refusal or withdrawal, or after the saved choice expires, the website does not load tag.js, does not use a noscript pixel and does not send analytics page views. The integration also uses disableYaCounter111908478 as an additional safeguard.
Session Replay, click map and e-commerce are disabled in the current integration. Contact-form data — name, email address and message text — is not sent to Metrica. Automatic goals based on entering contact details are not used.
5. Analytics data that may be stored in the browser
After analytics is allowed, Metrica may create first-party cookies and browser-storage values. The exact set depends on the service version, browser and tag settings.
According to Yandex Metrica documentation, such cookies include, among others, _ym_metrika_enabled for up to 60 minutes, _ym_isad for up to 20 hours, _ym_uid for up to one year, and related service values such as _ym_fa, _ym_d and other _ym_* cookies required for the service.
In localStorage, Metrica may use values such as _ym111908478_lastHit, _ym111908478_lsid, _ym111908478_reqNum, as well as _ym_retryReqs, _ym_uid and zz. Not every listed value necessarily appears for every user.
Yandex publishes the current list and purpose of these technologies in its documentation. This Policy should be updated if the actual website configuration or the technologies materially change.
6. How the user makes a choice
Before the first decision for the current terms, the website shows a choice interface. The user can either keep only necessary technology or separately allow analytics. Continuing to browse, silence or consent to contact-form data processing is not treated as consent to analytics.
The Russian and English versions use separate terms identifiers. A choice made for one language version does not automatically allow analytics on the other.
The choice can be changed at any time using Cookie settings in the website footer.
7. Refusal, withdrawal and browser-data deletion
If analytics is refused or permission is withdrawn for the current language version, the tag stops sending analytics events on that version of the website. The Russian and English permissions are independent, while both use the same Metrica tag and first-party identifiers shared on the domain.
If analytics is still allowed for the other language version, the website does not remove shared _ym_* cookies or related browser-storage values, because those identifiers and the session remain in use under that still-valid permission. When no valid analytics permission remains for either language version, the website attempts to remove Metrica-related first-party cookies and localStorage/sessionStorage values that are accessible to the website.
A browser does not allow a website to remove data set on another domain. If such values exist in a particular service configuration, they can be managed through browser controls or tools provided by Yandex. The user may also delete the website's saved choice; a new choice will then be requested on the next visit.
8. Contact form and analytics
Consent to personal data processing for the contact form is not consent to analytics. These decisions are not combined in one checkbox and are governed separately.
The terms for processing contact-form data are published in the Consent to Personal Data Processing.
9. Changes to this Policy
This Policy is updated when the analytics provider, tag number or settings, categories of cookies or browser storage, purposes, events, retention periods or user-choice logic materially change. A new version takes effect from publication unless it states otherwise.