Personal data policy

1. Who processes the data

The operator is V. I. Abdullaev, sole proprietor (TIN 770378901630, OGRNIP 323774600672350), the owner of abdullaev.vladimir.ru. Anything in this policy can be taken up by email at abdullaev.vladimir@ya.ru.

The policy is published under article 18.1 of Russian Federal Law No. 152-FZ of 27 July 2006 “On Personal Data” and covers every page of abdullaev.vladimir.ru.

2. What is collected

The site collects requests in exactly one place: the contact form. Everything that goes in:

• the name you typed into the form;
• the way to reach you that you picked, and the contact for it: a phone number, an email address or a Telegram handle — whichever you filled in;
• the comment, if you wrote one — the field is optional, and what goes in it is up to you;
• the date and time the request was sent;
• the IP address the request came from and how long the form took to fill in — the server sees both and uses them against automated submissions only.

No other data is collected. The visitor counter does record the session, but the contents of the form fields are not in that recording — clause 8 explains how. I do not ask for special categories of data (health, beliefs, criminal record and the like) or for biometrics; please do not put them into free text either.

3. Why it is needed

Data from the form has a single purpose: to get back to you about your request and talk the work through. It is not used for mailing lists, advertising or profiling, is not passed to third parties commercially, and is not sold.

The counter serves a different purpose: to see how many people reach the site, which pages they arrive from, where they stumble and whether anyone gets as far as the form. I watch session recordings for that and for nothing else — not for advertising, not for profiling. The legal basis for them is my legitimate interest in a site that makes sense to use (article 6, part 1, clause 7 of 152-FZ); if you would rather stay out of them altogether, clause 8 explains how.

The legal basis is your consent, given by the checkbox in the form (article 6, part 1, clause 1 of 152-FZ). Without it the form does not send and the server does not accept the request.

4. What happens to it next

The request is never written to a site database: the server forwards it straight to me as a Telegram message and as an email, and keeps nothing of its own. Two channels, because either one can fail and a request should not go missing. From there it lives in my correspondence — the same place an email sent to me directly would live.

The captcha response is checked by Yandex SmartCaptcha and is not stored anywhere afterwards.

Server technical records, the IP address among them, are kept for no longer than 90 days and serve only to fend off automated submissions and to investigate failures.

5. Who else receives it

For the request to arrive, for the form not to be filled in by robots, and for the use of the site to be visible at all, the data passes through outside services:

• Telegram Messenger Inc. — delivery of the request to my personal chat. Its servers sit outside Russia, which makes this a cross-border transfer; sending the form is consent to that transfer as well.
• Yandex LLC — delivery of the same request as an email to my Yandex Mail inbox. The email carries the same data as the chat message.
• Yandex.Cloud LLC — the SmartCaptcha check that keeps robots out of the form. It receives the captcha response and the IP address, not the contents of the fields.
• Yandex LLC — the Yandex.Metrica visitor counter, session recording included. It sees data about the visit, the IP address among it, and what happens on the page. It does not receive the contents of the form fields — the name, the phone number, the email, the handle, the comment: those are wiped in the browser before anything is sent. A request travels to my server past the counter.

Nobody else receives it, save where the law requires it.

6. How long it is kept

Correspondence about a request is kept while we are discussing the work, and for no more than a year after the last message — or until you ask for it to be deleted.

Consent can be withdrawn at any moment by email to abdullaev.vladimir@ya.ru. After that I delete the correspondence and stop using the contact; it takes no more than 30 days.

7. Your rights

Under articles 14–17 of 152-FZ you are entitled:

• to learn what data about you I hold and where it came from;
• to have inaccurate data corrected;
• to have the data deleted or your consent withdrawn;
• to complain about my actions to Roskomnadzor or in court.

All of it takes one email to abdullaev.vladimir@ya.ru. I answer within 30 days, usually sooner.

8. The visitor counter, cookies and browser storage

The site runs Yandex.Metrica, a visitor counter. It collects data about the visit: the page you opened, where you arrived from, the kind of device, the browser, the screen size, a rough region derived from the IP address, and what happens on the page — clicks, scrolling and cursor movement.

The counter has Webvisor enabled: it records the session in a form that can later be replayed like video, showing where you clicked and how far you read. I watch it to find out where people stumble on the site.

The contents of the form fields are not in that recording. Every field carries two markers: one replaces whatever is typed with asterisks, the other blanks out whatever the field holds — for the case where your browser autofilled it rather than you typing it. Both happen inside your own browser, before the recording is sent to Yandex. So the name, phone number, email, handle and comment are not merely hidden from view on their side: they are never sent at all. You do not have to take my word for it — open the page source and look for the ym-disable-keys and ym-hide-content classes on the fields.

Metrica sets its own cookies to tell a repeat visit from a new one. What it gathers is handled by Yandex LLC under its own policy, published at yandex.ru/legal/confidential, which also sets how long recordings are kept. You can opt out of the counter entirely with a blocker; the site keeps working either way, and so does the form.

The browser storage of the site itself holds exactly two values: the theme you picked, light or dark, and the site colour. Neither leaves your device, neither reaches me, and neither is personal data.

There are no advertising pixels and no ad-network cookies on this site.

9. How the data is protected

The site runs over HTTPS, the form is guarded by a captcha and by a limit on how many requests one address may send. Requests land in a chat only I can open.

Nobody can guarantee that data sent across the internet is safe, and I will not pretend otherwise: I take reasonable measures, but the risk of the transfer itself remains.

10. Changes to this policy

The policy may be revised: if the site ever starts collecting something else, a new version with a new date will appear here. Requests already sent are handled under the version that was in force when they were sent.