Cookie and Technical Data Policy
Revision dated 13.10.2026. Identifier: 2026-10-13-analytics-prepared-1.
1. Scope
1.1. This document describes the technical arrangements of the website https://sql.moscow/. The Controller is Individual Entrepreneur Andrei Viktorovich Svirin, INN 772872317733, OGRNIP 322774600176722; address: 117647, Moscow, P.O. Box 15. Contact: request@sql.moscow.
2. Current technical tools
2.1. Cookies are small browser records that may be transmitted to a website with subsequent requests. localStorage is storage on the device, without automatic transmission of each entry to the server and without a built-in deletion deadline.
2.2. The Website provides static pages and email inquiries. Its own choice interface for Yandex Metrica is ready; the counter is currently disabled. There is no inquiry form or advertising subscription. The banner lets visitors separately allow analytics or refuse them, while the permanent “Analytics settings” button lets them change their choice. New consent will be requested upon actual activation.
2.3. The “Write an email” button hands control to your email application. On the consent page, the text of a separate email may be prefilled, but it is not sent automatically. The operation of your chosen email application and its own cookies are governed by its terms; this does not remove the Controller's obligations after receiving the data.
3. Technical data without cookies
3.1. To deliver a page, the server receives the IP address, request time and address, necessary browser information and the result of processing the request. This information may be contained in security logs.
3.2. The purpose is the operation and protection of the Website; the basis is paragraph 7 of part 1 of Article 6 of Federal Law No. 152-FZ, subject to respect for the data subject's rights and freedoms. Ordinary logs are retained for no more than 30 calendar days. Information about a specific incident is retained for longer only on an independent basis, to the extent and for the period necessary.
3.3. Such logs are not used on that basis for optional behavioral analytics or advertising. The absence of cookies does not exclude the processing of the IP address and other connection information.
4. Managing data
4.1. In your browser settings, you can view and delete data for a specific website, block cookies and clear local storage. Menu item names vary. Clearing only cookies may not delete localStorage.
4.2. Deleting browser data does not delete emails, server logs or previously transmitted analytics information. To refuse analytics, use “Analytics settings”; send requests concerning other data using the contact details in the Personal Data Processing Policy. After refusal, no new Metrica requests are sent.
5. Changes to the technical arrangements
5.1. Before introducing counters, external widgets or other additional tools, the Controller determines the actual data, record names, purpose, recipients, periods and basis for processing, and updates the documents. If consent is required, the relevant processing begins only after the visitor makes a separate choice.
5.2. Continuing to browse pages, closing the message and submitting an inquiry do not constitute consent to future analytics. Changing the document does not change the scope of consent already given.
6. Choice records and future analytics
6.1. site_analytics_choice_v2 is a necessary cookie containing the server-signed choice, HttpOnly, Secure, SameSite=Lax; its lifetime is 180 days. site-analytics-choice-v2 is the corresponding localStorage entry containing the choice, revision, expiry and technical identifier. Upon expiry, the local entry is cleared at the next visit or check on an open page. If the Website is closed, it may remain until the next check or deletion by the user.
6.2. The minimal choice log on the server contains a random identifier, choice, date and time, revision, consent address and deletion deadline. Contact details, full IP addresses, User-Agent, messages and files are not included. Where there is an independent basis for confirming the lawfulness of processing or protecting rights, the retention period is up to three years; unnecessary information is deleted earlier.
6.3. Metrica analytics cookies are currently not created. If analytics are enabled after new consent, the main records are: _ym_uid and _ym_d — up to one year; _ym_isad — 20 hours; _ym_metrika_enabled — 60 minutes; _ym_visorc_* — 30 minutes with Webvisor. The names and purposes of additional cookies and localStorage entries are listed in the service documentation. Webvisor is currently disabled.
6.4. Upon refusal, first-party cookies and local entries with the _ym prefix are cleared. Necessary choice records remain to enforce the refusal. Website code cannot delete cookies on Yandex domains or data previously sent to the service. Requests concerning such data should be sent using the Controller's contact details.
6.5. The maximum retention period for analytics data attributable to a visitor or browser is up to three years from collection where actually necessary; early termination applies upon achievement of the purpose or withdrawal. Browser record lifetimes do not determine server retention periods. Activation is permitted only after the established retention limit has been ensured and an active revision published.