Privacy policy
Updated:
The Russian version of this document is the authoritative one.
Short version: this site uses strictly necessary cookies only, the ones that make signing in work. There are no analytics counters, no advertising trackers and no forms, and visitors’ IP addresses are not recorded. The rest of this page is the same statement in detail, one source of data at a time.
Who owns this site
Roman Polyansky, a private individual. This is a personal page: the site carries on no commercial activity, sells nothing, takes no payments and accepts no orders.
Contact: me@roman-polyansky.ru
Cookie
Only strictly necessary cookies are used here. They exist to sign you in to the account area and to protect forms against forged requests. There are no analytical or advertising cookies: no traffic counters, no advertising pixels, and no third party sets a cookie on this site.
One point worth being precise about, because it is easy to get wrong. This page issues no cookies itself. They are issued by the account area on subdomains of roman-polyansky.ru, and they are scoped to the whole domain, so your browser sends them when you open this page too, even if you came only to read.
Which cookies are used
| Purpose | Type | Lifetime | Set by |
|---|---|---|---|
| Sign in session: ties the browser to your session. Signing in does not work without it | Strictly necessary | Until the session ends | First party |
| Stay signed in: keeps you signed in after the browser closes. Created only if you tick that box yourself when signing in | Strictly necessary for a feature you chose | Up to 30 days | First party |
| Protection against cross site request forgery in forms | Strictly necessary | Until the session ends | First party |
There are no third party cookies in this table, and none will be added without saying so first.
Why the notice informs rather than asks
Strictly necessary cookies do not require consent, because without them signing in and form protection simply do not work. A “Decline” button next to a cookie you cannot decline without breaking the login would be untrue. So the notice at the bottom of the page tells you, rather than asking permission.
If analytical or advertising cookies are ever added, that changes. The notice becomes a real consent request with equally weighted accept and decline buttons, and nothing loads until you have answered rather than after.
How to refuse or delete them
Cookies can be deleted and blocked in your browser settings, in the section about site data, where they can also be blocked for one domain only.
You can read this site with cookies blocked without losing anything: on the pages you are looking at now they do nothing. Blocking strictly necessary cookies only makes signing in to the account area impossible.
Browser local storage
Besides cookies, the site writes two entries to your browser’s local storage.
The first is your chosen theme, light or dark, under the key theme, written
only after you press the theme switch in the header yourself. The second records
that the cookie notice was dismissed, under the key cookie-notice, so it does
not reappear on every visit.
Both entries stay in your browser. They are not sent to the server, not shared with anyone, and cannot identify you. You can remove them by clearing site data in your browser settings.
The dismissal record stores the date of this policy’s version. If the policy changes, the notice appears again.
Web server logs
The web server keeps a technical request log. IP addresses are not written to it: the log format was changed specifically so that the address is not stored.
What the log does keep is the date and time, the address of the page or file requested, the response code, the response size, the referring page and the browser’s User-Agent string. These records serve one purpose: noticing that a page or a file has stopped loading.
The logs are capped by size and overwritten in rotation. No separate archive is kept and no extracts are shared with anyone.
Fonts, images and icons
Everything the page loads is hosted on the same server as the site itself. There are no requests to Google Fonts, to content delivery networks or to any other outside source, so opening a page does not make your browser contact a third party.
Outbound links and QR codes
The contact page carries links and QR codes to Telegram, MAX and email, and the projects page links to external sites. Following any of them takes you to a third party service with its own rules for handling data.
The QR codes are static images. They contain the destination directly, do not route through an intermediate link and do not record scans.
Forms
There are no contact, subscription or enquiry forms on these pages. You can only write to me through a messenger or by email, which happens outside this site and under the rules of whichever service carries it.
Where the site is hosted
The site runs on servers located in Russia.
Your rights
The pages you are reading now collect nothing about you: no forms, no counters, no IP addresses in the logs.
If you have signed in to the account area, that session has an identifier, and for that part you have the right to ask what is held about you, to have it corrected or deleted, and to withdraw consent where consent was given. Write to me@roman-polyansky.ru and I will answer.
Changes
If counters, forms or anything else that collects data is ever added, this document will be updated before that happens rather than after, and the cookie notice will appear again. The date at the top of the page is when it was last changed.