Personal Data Processing Policy
Version of 8 October 2026.
This is an English translation of the Russian-language policy published at serjfedik.com/politika. If the two texts differ, the Russian text prevails.
This is the personal website of one person. The public part of the site has no registration, forms, subscriptions, chat or payments: there is nothing to enter here. The site does not store or send the ticks in the self-check boxes on the home page; see section 3. The only thing collected about visitors is visit statistics gathered by the Yandex Metrica counter, and only with their consent. Separately, the site counts how many times each blog article was opened and how far it was read: these are totals per article per day, and they cannot tell who read it (section 3). Below is what exactly it collects, why, who sees it and how to limit collection.
1. Who collects the data
Site owner: Sergey Sergeevich Fedik, individual entrepreneur.
Website: serjfedik.com.
Contact email: info@atlaspanel.ru.
Nothing is sold, advertised or provided as a service through the site.
2. What counts as personal data here
The law defines personal data as any information relating directly or indirectly to a person (Federal Law No. 152-FZ “On Personal Data”, Article 3(1)). The counter does not know your first name, last name, phone number or email and has no way to learn them: there is nowhere to enter them. It knows your network address, your browser and a random number it writes into your browser. That number distinguishes your visits from other people’s, so this information is treated here as personal data, and how it is handled is described below.
3. What is collected and on which page
The counter is installed on four pages: the home page, the English version (/en), and the CV in both languages (/cv and /en/cv). It is not installed on any other page of the site: not on the policy, not on the consent text, not on the easter egg pages, not in the closed part.
The counter loads only after your consent: the “Accept” button in the bar at the bottom of the page (“Принять” on the Russian pages), “Accept all” in the cookie settings (“Принять все”), or “Analytics” (“Аналитика”) switched on followed by “Save choice” (“Сохранить выбор”). Until you consent, and after you refuse, the Metrica code is not loaded onto the page and collects none of the items below. The consent text is a separate page: Consent to personal data processing.
Counter: Yandex Metrica, number 112844629.
It collects:
- the visit and the full address of the page;
- the address of the page you came from;
- clicks on the page: they are assembled into a map showing what people touch and what they don’t;
- clicks on links;
- whether the visit counts as a bounce, that is, whether the person left right away;
- network address, browser, operating system, screen size and city by network address. Yandex collects these itself on its side.
All of the above is done by the Metrica code loaded from mc.yandex.ru. The site itself writes to your browser only your statistics choice and the easter egg records: the choice when you press a button in the consent bar or in the cookie settings, the easter egg records only after you open an easter egg (section 7). It does not read your network address: its code makes no calls to x-forwarded-for, x-real-ip, user-agent or geolocation.
Self-check on the home page. In the self-check block on the home page you can tick boxes. The answer below them is worked out by the page in your browser. The site does not store the ticks, does not send them anywhere and does not write them to your browser: once you close or reload the page, they are gone. If you have allowed statistics, Metrica sees a click on a box just as it sees any click on the page (the list above); whether a box is ticked or not, the site does not tell it.
Blog article read counter. On article pages under /blog the site itself records that an article was opened, read to a quarter, to a half, to three quarters and to the end, and the number of the subheading where the reader left. The site database keeps only the totals of these marks per article per day. The counter sets and reads no cookies and neither reads nor stores the network address or browser data, so the numbers cannot be linked to a person, and no consent is asked for it. A mark that another site tries to send through the reader's browser is not counted. With scripts disabled the counter does not work.
Your session is not recorded. Metrica has such a feature, called Session Replay (Webvisor), which records cursor movement and scrolling like a video. Here it is switched off in two places at once: the counter code contains webvisor:false, and the switch is turned off in the Metrica settings themselves. The Session Replay addresses have been removed from the site’s permissions.
If scripts are disabled in the browser, there is no counter at all: without scripts consent cannot be asked, and without consent the site does not count.
4. Why the owner needs this
Three purposes, and no others:
- to count how many people visit;
- to see where they come from;
- to see how long they stay on the page and what they click. The home page consists of several sections one after another, and clicks in the lower ones show whether a visitor gets there. How far the page is scrolled Metrica does not see without Session Replay: the scroll map is switched on by the same setting as Session Replay.
There is no advertising on the site and no mailings. The site owner does not build advertising segments and does not sell or transfer the counter data to anyone except Yandex, as stated in section 6. How Yandex handles the data collected on its side is set out in its own documents, and the site owner has no influence over that.
5. Legal basis
The visitor’s consent: Federal Law No. 152-FZ, Article 6(1)(1) and Article 9. It is given with the “Accept” button in the bar at the bottom of the page (“Принять” on the Russian pages), “Accept all” in the cookie settings (“Принять все”), or with “Analytics” (“Аналитика”) switched on and the “Save choice” button (“Сохранить выбор”). The consent text is set out separately from this policy, as Article 9(1) requires: Consent to personal data processing.
Transferring data to Yandex is an instruction to process data on the operator’s behalf. Article 6(3) permits it with the person’s consent, and the consent text names Yandex directly.
6. Who receives the data
Yandex. In full: YANDEX LLC, 16 Lva Tolstogo St., Moscow, 119021, Russia.
Under the Yandex Metrica terms of use (clause 5.4), the site owner is the personal data operator, and Yandex is the person acting on the operator’s instructions. Under clause 5.1 of the same terms, the collected statistics are used both by the site owner and by Yandex.
What Yandex does with data from its services is set out in its privacy policy. The full Metrica terms: yandex.ru/legal/metrica_termsofuse.
The data goes nowhere else. The site has no other counters, apart from the article read counter in section 3 (it sends nothing outside the site), and no chats, embedded maps, advertising networks, social media buttons or external fonts.
7. Cookies and browser storage
On the four pages with the counter the site itself does not set a single cookie. Everything listed below, except the site’s own records at the end of this section, is set by the Metrica code, and only after your consent. Yandex defines this list and changes it without notice; it is given here as of 21 September 2026, and the primary source with retention periods is the Metrica help page on cookies.
On the serjfedik.com domain:
| Name | Lifetime | Purpose |
|---|---|---|
_ym_uid | 1 year | distinguishes visitors from one another |
_ym_d | 1 year | date of the first visit to the site |
_ym_fa | 1 year | technical, works together with _ym_uid |
_ym_isad | 20 hours | whether the visitor has an ad blocker |
_ym_metrika_enabled | 60 minutes | checks that the others are set correctly |
_ym_hostIndex | 1 day | limits the number of requests |
gdpr | up to 2 years | identifies visitors from the area where GDPR applies |
What does not appear here: _ym_visorc_* is the Session Replay cookie, and Session Replay is switched off; _ym_debug and _ym_sup_debug: debug mode is switched off; _ym_ucs: server-side cookie re-setting is not configured.
Some records Metrica makes in browser storage. In localStorage: _ym<counter number>_lastHit, _ym<counter number>_lsid, _ym<counter number>_reqNum, _ym_hide_phones, _ym_retryReqs, _ym_uid, zz. In sessionStorage: _ym_debugger_state, _ym_turbo_uid.
On its own domains Yandex sets its own cookies, and the site owner does not control them; their list is in the Metrica help at the link above.
The site's own records are your statistics choice and the easter egg records. The choice is recorded when you press a button in the consent bar or in the cookie settings. Easter egg records appear on the home page and on addresses such as /wp-admin, and only after you open an easter egg yourself. These records never leave your browser: neither the site nor Metrica receives them, and only the page in your browser reads them.
| Name | Where | Lifetime | Purpose |
|---|---|---|---|
soglasie-statistika | localStorage | until you clear the site's data in your browser | your choice: whether Yandex Metrica statistics are allowed; with it the bar does not ask again, and the counter decides whether to load |
paskhalki-seans | localStorage | until you clear the site's data in your browser | date and time the terminal was last opened, hours and minutes, so the terminal can say "welcome back. last session: 14:05"; and a random page-load number, so the terminal can tell reopening without reloading the page from a new visit; the number is not linked to you, and the site never sends it anywhere |
paskhalki-sudo | sessionStorage | until the tab is closed | how many times the sudo command has been typed in the terminal |
paskhalki-dveri | sessionStorage | until the tab is closed | which addresses such as /wp-admin and /.env you have already opened, for the "doors checked: 3 of 7" count |
Separately, about the closed part of the site: there the site sets its own technical sign-in cookie, and it exists only for the owner. It is never set for a visitor of the public part.
8. How to limit collection
“Necessary only” in the bar (“Только необходимые” on the Russian pages) or “Cookie settings” at the bottom of the page (“Настройки cookie”) switch collection off on this site. The counter does not load, and Metrica’s records for this site in your browser are erased. Changed your mind after consenting? Open “Cookie settings”, switch “Analytics” off and press “Save choice”.
The “Yandex Metrica Blocker” extension switches collection off. It is made by Yandex itself. Once it is installed, the counter stops writing files to your browser and sending data, on every site where Metrica is installed. Links for Chrome and Firefox: Yandex page about the blocker.
After consent, blocking cookies for this site in your browser settings does NOT switch collection off. The counter stops linking your visits together, but the visit is still counted, and Yandex still receives your network address, browser and referral source.
The extension is mentioned here because the Metrica terms require the site owner to tell visitors about it (clause 5.8).
9. How long it is stored
The retention period for counter data is set by Yandex on its side, and the site owner does not control it. The exact period cannot be confirmed from Yandex’s public documents, so this line stands here instead of a plausible number.
What is known for certain: no Session Replay records exist at all, because it is switched off. The site has no database of its own with visitor data. The site database holds only the daily totals of the article read counter (section 3): they contain nothing that identifies a person, so they are kept without a time limit.
10. Information on the implemented personal data protection requirements
- There is no database of visitor data of its own. Not a single table about visitors has been created on the site.
- The site is served only over an encrypted connection. The browser will not let you reach it over an unencrypted protocol: the
Strict-Transport-Securityheader is set. - Camera, microphone and geolocation are prohibited by the
Permissions-Policyresponse header. The site cannot request them. - The page loads code only from its own address, and Yandex Metrica code only after your consent. Embedding the page in another site is prohibited for everyone except Metrica, which needs it to show the owner the click map.
- The closed part of the site lives on a separate subdomain and is protected by a password and a one-time code.
- There are no passwords or keys in the site’s code: they are set in the hosting control panel.
11. Your rights
Article 14 of Federal Law No. 152-FZ gives you the right to find out whether your data is being processed and by whom. It also gives you the right to demand that data be clarified, blocked or deleted if it is incomplete, outdated, inaccurate, unlawfully obtained or not necessary for the stated purpose. You can withdraw your consent to statistics at any time (Article 9(2)): “Cookie settings” at the bottom of the page (“Настройки cookie” on the Russian pages) or by email to info@atlaspanel.ru.
How this works in practice. The counter statistics contain neither names nor email addresses, so it is impossible to find you specifically in them from a letter. What can actually be done:
- switch collection off using the method in section 8, and new visits will not reach the statistics;
- write to info@atlaspanel.ru; the owner reads these letters personally;
- contact Yandex about the data on its side through its policy.
12. The closed part of the site
The site has a closed part on a separate subdomain. Only one person, the owner, signs in there, with a password and a one-time code. There is no visitor data in any table there, and there is no Metrica counter on any screen there.
13. Changes
The version date is at the top of the page. If collection changes, this page changes, and the date with it.