Legal information
Cookies and local storage policy
Information about local storage of user settings and consent-first use of Yandex Metrica on the website of ООО «АЛЬТРАДА ИМПОРТ».
Version dated 21 August 2026
1. General provisions
This Policy describes the use of cookies, browser local storage and similar technologies on the website of ООО «АЛЬТРАДА ИМПОРТ».
It applies alongside the Personal Data Processing Policy available at /en/privacy/.
This Policy does not itself constitute consent to personal data processing or replace the separate consent provided when submitting the form.
2. Current website configuration
As at the date of this version:
- Yandex Metrica is connected only after explicit permission for analytics;
- Session Replay, e-commerce, advertising and retargeting pixels are not connected in the website code;
- selecting ‘Necessary only’ prevents tag.js and the Yandex Metrica counter from loading;
- form data is not stored in cookies or localStorage;
- form content and enquiry identifiers are not sent to Yandex Metrica.
Standard hosting, web server or reverse proxy technical logs are separate from page cookies or localStorage and are described in the Personal Data Processing Policy.
3. Local storage
Analytics permission lasts only for this site document, separately for Russian and English. Reloading or returning requires a new explicit choice. Navigation within the site preserves the choice.
Legacy keys ali-analytics-choice-v2 and ali-en-analytics-choice-v1 do not grant permission. On refusal they signal other tabs; delivery of that signal cannot be guaranteed.
The previous key, ali-analytics-choice-v1, is not migrated automatically and cannot activate Yandex Metrica without a new informed choice.
3.1. Local setting contents
The ali-analytics-choice-v2 key may contain only accepted or necessary and must not contain:
- name;
- email;
- telephone numbers;
- company name;
- enquiry content;
- request identifier;
- IP addresses;
- UTM parameters;
- other form data.
The localStorage value remains in the browser until the user deletes it, clears website data or the choice mechanism's version changes.
A stored accepted value does not permit analytics to load. Refusal disables analytics in both languages of the current document. Before a new permission, inherited UTM context must be confirmed removed; if this fails analytics remains off.
4. Cookies
Before analytics is permitted, the website does not load Yandex Metrica or initiate its analytics cookies or network requests.
After permission is given, Yandex Metrica may use its own storage technologies as part of the service; the precise production list and retention periods require a separate check by the project owner.
Hosting, reverse proxy or infrastructure security facilities may, where necessary, use strictly technical mechanisms for connections, security, load balancing or abuse prevention.
The use of specific infrastructure cookies is not asserted until confirmed by the actual production configuration.
4.1. Information when cookies are introduced
If such cookies are introduced, the Policy must be updated before they are enabled to specify:
- name;
- purpose;
- provider;
- duration;
- category;
- basis for use.
5. Technical logs
When the website is accessed, the hosting service, web server or reverse proxy may process technical information, including:
- IP addresses;
- access date and time;
- requested URL;
- response code;
- user-agent;
- network error information;
- technical abuse-prevention identifiers.
This information is not stored in page cookies and is processed for website operation and security in accordance with /en/privacy/.
The specific log retention period is not considered configured until confirmed by the production configuration. The requirement to set and document this period remains in the release checklist.
6. User choice
The settings interface allows the user to:
- decline optional analytics;
- allow optional analytics;
- change the choice by clearing website data or using the provided settings interface;
- continue using the website's core functions while declining optional analytics.
Declining optional analytics does not prevent access to the website or submission of the form.
7. Browser settings
The user can delete cookies and localStorage through browser settings.
After reloading, opening a new tab or returning to the site, preferences are requested again if the analytics interface is enabled. Earlier permission is never automatically restored.
8. Changes to analytics
Before enabling Session Replay, an advertising pixel or another new optional technology, the Controller must:
- check the data processed and its purposes;
- check form field recording and the risk of transferring identifying data;
- check storage location and possible cross-border transfers;
- check the agreement with the relevant processor;
- update /en/privacy/ and /en/cookies/ where necessary;
- maintain the prohibition on data transfers before the required choice is obtained;
- update the Roskomnadzor notification if the declared processing information changes.
9. Contacts
For general questions about the website:
For personal data processing matters, users should use the contacts specified in /en/privacy/.
