Privacy policy

1. Scope

This policy applies to visitors of radaev.dev, including its Russian and English versions.

It describes processing by this website only. Once a visitor opens an external resource, that service’s own rules apply.

2. Operator

The operator of this website is Ilya Aleksandrovich Radaev, a natural person.

The operator organises the processing personally and responds to privacy enquiries. He can be contacted in Telegram: https://t.me/radaev_dev.

3. Data processed

When a page is opened, the server may receive the IP address, a User-Agent describing the browser and device, request date and time, requested URL, referrer if supplied by the browser, response status and technical error details.

After consent, Yandex Metrica may receive the page URL and title, referrer, browser, operating system, device, screen, language, time zone, cookie availability, visit duration and depth, outbound clicks and downloads. Reports may include approximate geography and aggregated audience characteristics.

The data subjects are website visitors. The website does not request special-category or biometric personal data.

4. What the website does not have

There is no request form, registration or personal account. The website does not ask for a name, phone number, email address or message text.

Google Analytics, advertising pixels and advertising cookies are not connected. Yandex Metrica is configured without Webvisor, click maps, form analytics, Advanced Matching or CRM data transfer.

5. Purposes and basis

Technical data is needed to deliver the requested page, keep the website available, diagnose errors, maintain security and prevent abuse.

Server logs are processed on the basis of the operator’s legitimate interest in stable and secure website operation, provided that the visitor’s rights and freedoms are not infringed.

Yandex Metrica is used only with separate consent to measure traffic, sources, devices and general page performance. The website does not use the data for mailing lists or individual advertising.

6. Processing and retention

Processing is automated when a browser contacts the server. Possible operations include receiving, recording, storing, using for the stated purposes, restricting access, deleting and destroying.

Technical logs are stored for no longer than 30 calendar days from recording and are then deleted automatically by log rotation. A record connected with a confirmed incident may be retained until the investigation and protection of legal rights are complete.

The operator can access Metrica statistics while the counter remains active or until data is deleted through the service tools. Retention by Yandex is governed by the Yandex Metrica documents and settings.

7. Storage location and transfers

Technical logs are collected, recorded and stored on a server and in log files located in the Russian Federation.

The website does not transfer server logs outside the Russian Federation. After consent, the browser separately sends analytics data to YANDEX LLC (16 Leo Tolstoy Street, Moscow). Under the service terms, Yandex acts on the operator’s instructions.

Yandex Metrica terms: https://yandex.ru/legal/metrica_termsofuse/en/. Yandex privacy policy: https://yandex.ru/legal/confidential/. The geography of further processing by Yandex is governed by its documents; no such transfer from the website occurs without visitor consent.

8. Cookies and browser storage

To remember the choice, the website sets the necessary radaev_analytics_consent cookie with an accepted or declined value for 180 days. It contains no visitor identifier.

After consent, Metrica may set cookies and browser-storage entries. These include _ym_uid for up to one year, _ym_isad for about 20 hours, _ym_metrika_enabled for about 60 minutes and Yandex technical identifiers. The current list and periods are available at https://yandex.ru/support/metrica/ru/general/cookie-usage.

9. Choice and withdrawal

The Yandex Metrica code is not loaded before “Allow analytics” is selected. A visitor may continue without analytics; only the necessary refusal cookie is then stored.

The choice can be changed using the button at the bottom of this page. Declining stops future Metrica loading and removes first-party Metrica cookies available to this site. Cookies on Yandex domains are removed through browser controls or according to Yandex retention periods.

10. Access to data

Server logs can be accessed by the operator and only those technical specialists who need access for administration, security and fault resolution. Metrica statistics can be accessed by the operator and people explicitly granted access in the counter interface.

Yandex processes data within the service terms. The operator does not sell the data or disclose it for third-party mailing lists.

11. Telegram and visitor rights

The website opens Telegram only after the visitor chooses the https://t.me/radaev_dev link. The website sends no visitor data to Telegram before that action.

A visitor may request information about processing, ask for relevant data to be corrected, restricted or deleted, and report a suspected violation.

Contact the operator in Telegram: https://t.me/radaev_dev. The request should include enough information to verify the requester and locate the related record.

12. Security and policy updates

The operator restricts access to logs and applies organisational and technical safeguards against unlawful access, alteration, disclosure and destruction.

If the analytics scope, cookies, recipients or processing procedure changes, this policy will be updated. The current revision date is shown above.