Legal

Cookie Policy

Cookie Policy

Controller: Individual Entrepreneur Ruslan Alikovich Beriev

Effective date: 4 August 2026

Published at: https://alania-drive.ru/en/cookies

1. General provisions

1.1. This Cookie Policy explains which cookies and similar technologies may be used on https://alania-drive.ru, why they are used and how users can manage their preferences.

1.2. The website is operated by:

Individual Entrepreneur Ruslan Alikovich Beriev

Russian Taxpayer Identification Number, INN: 151500962010

Primary State Registration Number, OGRNIP: 321151300017276

Registered and postal address: 9 Borodinskaya Street, Vladikavkaz, Republic of North Ossetia–Alania, Russian Federation

Telephone: +7 (928) 480-29-99

Privacy email: — hello@alania-drive.ru

1.3. This Policy should be read together with the Personal Data Processing Policy:

https://alania-drive.ru/en/privacy

1.4. Essential cookies may be used where required for website operation. Non-essential cookies and similar technologies are used only in accordance with the user’s choice.

2. What cookies are

2.1. A cookie is a small piece of data sent by a website to a user’s browser and stored on the user’s device.

2.2. Cookies may allow the website to:

  • remember the selected language;
  • save user preferences;
  • support website functions;
  • maintain security;
  • save the user’s cookie choices;
  • receive technical information about website operation;
  • analyse website usage where consent has been provided.

2.3. The website may also use similar technologies, including:

  • localStorage;
  • sessionStorage;
  • technical identifiers;
  • server request logs;
  • pixels and analytics scripts, only where actually implemented and permitted by the user.

2.4. Certain technical information, when combined with an IP address, browser identifier or other information, may constitute personal data. Such processing is governed by the Personal Data Processing Policy.

3. Cookie categories

3.1. Essential cookies

Essential cookies support the website’s basic operation and cannot be disabled through the website’s non-essential cookie settings.

They may be used to:

  • save the selected website language;
  • ensure correct navigation;
  • maintain a technical session;
  • protect forms and infrastructure;
  • prevent abuse;
  • retain the user’s cookie choice;
  • maintain website availability and stability.

The website may use the technical `ad_locale` cookie to remember the selected interface language.

Separate cookies or browser local-storage records may be used to retain the user’s cookie preference.

Blocking essential cookies through browser settings may prevent certain website functions from operating correctly.

3.2. Functional cookies

Functional cookies help retain additional preferences and improve convenience.

They may be used to:

  • remember interface preferences;
  • retain previously selected parameters;
  • restore the state of certain website components;
  • support additional functionality.

Where a functional cookie is not essential, it is used only after the user has made the corresponding choice.

3.3. Analytics cookies

Analytics cookies may be used to obtain aggregated information concerning:

  • visit numbers;
  • popular pages;
  • traffic sources;
  • device and browser types;
  • technical errors;
  • navigation paths;
  • the effectiveness of interface improvements.

Analytics cookies must not be activated before the user has made the relevant choice through the cookie interface.

As of the effective date of this Policy, an analytics provider should be listed in the website interface only where it is actually integrated.

If Yandex Metrica, Google Analytics or another analytics service is integrated later, the Controller must:

  • identify it in this Policy;
  • disclose its purpose and retention period;
  • verify the location of data processing;
  • ensure that it is activated only after consent where required;
  • update regulatory notifications and internal documents as necessary.

3.4. Marketing cookies

Marketing cookies may be used to:

  • assess advertising campaigns;
  • identify advertising sources;
  • create audiences;
  • limit ad frequency;
  • display more relevant advertising;
  • analyse advertising conversions.

These technologies are not essential and are activated only after the user has made a separate choice.

Where advertising systems, retargeting tools or marketing pixels are not actually integrated, no marketing cookies are set by the website.

3.5. Third-party cookies

Third-party cookies may be set by external services embedded into the website, including:

  • mapping services;
  • video platforms;
  • analytics systems;
  • communication widgets;
  • social networks;
  • advertising platforms.

Links to Telegram and WhatsApp may take the user to third-party websites or applications. After the user leaves the website, personal data may also be processed by the relevant third-party provider under its own terms.

The Controller does not control cookies set by a third-party service after the user accesses that service’s website or application.

4. Technical information that may be processed

Cookies and similar technologies may involve processing of:

  • IP address;
  • date and time of access;
  • requested page;
  • referrer;
  • browser type and version;
  • device type;
  • operating system;
  • user-agent;
  • selected language;
  • technical identifiers;
  • cookie preference information;
  • traffic source;
  • UTM parameters;
  • error information;
  • website interactions, only where permitted analytics is used;
  • the date, time and version of the user’s choice.

The Controller does not intentionally use cookies to obtain sensitive or biometric personal data.

5. Purposes of use

Cookies and similar technologies may be used to:

  • operate the website;
  • retain the selected language;
  • maintain security;
  • prevent abuse;
  • save user preferences;
  • retain the user’s cookie decision;
  • diagnose errors;
  • improve website quality and usability;
  • obtain statistics where consent has been given;
  • assess advertising where separate consent has been given;
  • demonstrate which preferences the user selected.

Data must not be used for purposes incompatible with those identified when it was collected.

6. Legal grounds

6.1. Essential technologies are used to the extent required for website operation, security and actions requested by the user.

6.2. Non-essential analytics, functional and marketing technologies are used according to the choice expressed by the user through the cookie interface.

6.3. Users may:

  • accept all categories;
  • reject non-essential categories;
  • select individual categories;
  • subsequently change or withdraw their choice.

6.4. Refusing non-essential cookies should not prevent users from viewing core public pages or submitting a request, except for functionality that objectively depends on the relevant technology.

7. Cookie preference interface

On the first visit, the website may display a notice offering:

  • “Accept all”;
  • “Reject non-essential”;
  • “Customise”.

The settings interface allows the user to permit or reject available categories separately.

Before the user makes a choice:

  • essential technologies may operate;
  • non-essential analytics must not be activated;
  • marketing technologies must not be activated;
  • optional third-party scripts must not load where they involve storing or transmitting data.

The choice is retained so that the notice does not appear on every page navigation.

8. Changing or withdrawing preferences

Users may change their decision at any time through the “Cookie settings” link in the website footer.

After withdrawal:

  • new non-essential cookies must no longer be set;
  • the relevant scripts must stop loading;
  • previously stored cookies may remain until deleted, expired or cleared by the browser.

Withdrawal does not affect the lawfulness of processing carried out before it was received.

9. Browser controls

Users may also:

  • view stored cookies;
  • delete individual or all cookies;
  • block new cookies;
  • restrict third-party cookies;
  • clear localStorage and sessionStorage;
  • use private browsing mode.

The relevant process depends on the browser and device.

Blocking all cookies may result in:

  • the website language not being remembered;
  • cookie preferences not being retained;
  • certain functionality operating incorrectly;
  • certain forms or security mechanisms becoming unavailable.

10. Retention periods

Retention depends on the purpose of the relevant technology.

The website may use:

  • session cookies, deleted when the browser or session is closed;
  • persistent cookies, retained until their specified expiry date;
  • local storage, retained until cleared by the user, deleted by the website or replaced following a settings change.

The language preference cookie may be retained for up to one year unless the technical configuration provides otherwise.

The user’s cookie preference may be retained for up to one year or until the policy version or category structure changes.

Retention periods for third-party cookies are determined by the relevant provider and must be disclosed in the settings interface where such services are integrated.

11. Disclosure to recipients

Information obtained through cookies may be disclosed to:

  • REG.RU, in connection with cloud-server and network infrastructure and technical request processing;
  • technical contractors maintaining the website;
  • analytics providers, only where actually integrated and legally permitted;
  • advertising platforms, only after the user has made a separate choice;
  • competent public authorities where required by law.

Only information necessary for the relevant purpose is disclosed.

The website’s principal infrastructure is hosted on a REG.RU cloud server in Moscow, Russian Federation. Backups are also stored within REG.RU infrastructure in Moscow.

12. Cross-border transfers

The principal database and server infrastructure are located within the Russian Federation.

The use of foreign analytics, advertising or embedded services may potentially result in cross-border transfer or access from outside the Russian Federation.

Before integrating such a service, the Controller must:

  • determine the processing route and location;
  • verify the lawful basis;
  • complete any required notification procedures;
  • update this Policy;
  • configure consent collection where required.

Where these conditions have not been met, the relevant third-party service must not be activated for the user.

13. Security

The Controller implements organisational and technical measures, including:

  • HTTPS;
  • access controls;
  • server infrastructure protection;
  • administrative account controls;
  • software updates;
  • logging of significant events;
  • backups;
  • activation of optional scripts only after the user’s choice;
  • minimisation of technical data;
  • deletion or anonymisation after lawful grounds expire.

14. Policy changes

14.1. This Policy may be updated where:

  • applicable law changes;
  • cookie categories change;
  • analytics is added or removed;
  • advertising systems are introduced;
  • the website structure changes;
  • infrastructure providers change;
  • retention periods change.

14.2. The current version is published at:

https://alania-drive.ru/en/cookies

14.3. The effective date and last-updated date are displayed on the relevant page.

14.4. Where categories or purposes materially change, the website may request the user’s choice again.

15. Contact information

Questions concerning cookies and related personal data may be submitted to:

Controller: Individual Entrepreneur Ruslan Alikovich Beriev

INN: 151500962010

OGRNIP: 321151300017276

Registered and postal address: 9 Borodinskaya Street, Vladikavkaz, Republic of North Ossetia–Alania, Russian Federation

Telephone: +7 (928) 480-29-99

Privacy email: — hello@alania-drive.ru