Privacy
What happens to data when you read this site. A registry about where other people's data goes owes you a precise answer about its own.
Controller
Viktar Patotski, contactable at [email protected]. Full provider details, including postal address, are on the legal notice. Mail to this address does not arrive yet — the domain publishes no mail record, and until it does a rights request has no route. This line goes when the route works. No data protection officer is appointed; the thresholds in Art. 37 GDPR are not met by a static site with no accounts.
What is processed when you read a page
| What | Why | Basis | Kept |
|---|---|---|---|
| Request log | IP address, time, page requested, user agent and referrer, recorded by the hosting provider to serve the page and to absorb abuse | Art. 6(1)(f) — operating and protecting the service | Provider's own retention; we hold no copy |
| Theme choice | One value in your browser's local storage (eucsoft-theme), written only if you press the light or dark button | Storage you asked for; it never leaves your browser and reaches no server | Until you clear site data |
| Email you send | Your address and whatever you write, so we can answer and, for a correction, record why an entry changed | Art. 6(1)(f) — answering a message you chose to send | Two years, then deleted |
There is no account, no newsletter, no form and no tracking pixel on this site, so there is nothing else to list. If that changes, this table changes with it and the change is dated like every other fact here.
Who else is involved
One processor: Cloudflare, which hosts the files and serves them from its network. Serving a page necessarily discloses your IP address to it. Cloudflare operates outside the EEA as well as inside it and relies on the EU Standard Contractual Clauses for transfers. That is the entire list — the same kind of list this site asks vendors to publish, which is why it is here rather than described in the abstract.
Personal data inside the registry itself
The registry records companies, not people. A few entries carry a role address a vendor publishes for security reports — security@ and the like. Those are business contact points the vendor chose to publish so they would be used, and they are reproduced for exactly that purpose. If you are named in an entry and would rather not be, write to us and it comes out; we do not need a human's name to record what a company disclosed.
Your rights
Access, rectification, erasure, restriction, portability, and objection to any processing based on legitimate interests — Arts. 15 to 21 GDPR. Write to [email protected]; we answer within a month. You may also complain to a supervisory authority in the country where you live or work.
Practically, for a reader who has sent us nothing, there is usually nothing to access: we cannot connect a request log held by the host to you, and we would have to collect more data than we hold in order to try.
Changes
This notice is versioned in the repository that builds the site, so what changed and when is visible in the same history as everything else here.