Privacy

Who is responsible

Kybernetes is run by Dominik Vošček as a personal publication. There is no company behind it. For anything on this page — including a request to see or delete whatever is held about you — write to contact@kybernetes.app.

Reading the site

There are no reader accounts. There is nothing to sign up for and nothing to sign in to. Every article, every simulation and the search work for an anonymous visitor, and no profile of you is built anywhere.

One cookie is set for a visitor, and only one. lang remembers whether you prefer English or Slovak, so that the bare address of the site sends you to the right half of it. It is written when you land on / and the site works out which language to serve; it holds two letters, en or sk, and expires after a year. Deleting it costs you one redirect and nothing else.

What your browser remembers

Your light-or-dark preference is kept in localStorage under the key mode, written by the theme toggle and read back by a small script before the page paints so the wrong palette never flashes at you.

It stays in your browser. It is never sent to the server, never attached to a request, and this site never learns which mode you chose. Clearing your site data removes it, and the page falls back to whatever your operating system says about prefers-color-scheme.

Why there is no cookie banner

Because there is nothing to consent to. The one cookie above is strictly functional, which is the category that does not require consent. There is no advertising here, no tag manager, no social widgets, and no cross-site tracking of any kind.

The fonts are served from this domain rather than from Google Fonts, so reading a page does not hand your IP address to a third party. Every stylesheet and image comes from this origin too. One script does not, and it is the subject of the next paragraph.

Visits are counted with Cloudflare Web Analytics. It sets no cookie, records no identifier for you, and cannot follow you to another site, which is why it needs no banner. It is not invisible, though, and it would be dishonest to describe it that way: Cloudflare adds a small script to each page as it leaves the network, and your browser fetches that script, beacon.min.js, from static.cloudflareinsights.com. That one request does leave this origin. What it measures — page load timings, the address of the page, the page that referred you, and coarse details such as country and device type — is then sent back to this domain, not to a third-party address. Anything that would require a banner will not be added.

Logs and abuse prevention

This site runs on Cloudflare, which handles every request on its network and keeps short-lived operational logs — the ordinary server-log fields: IP address, time, the address requested, the browser's user agent, the response status. They exist so that outages and attacks can be diagnosed. Cloudflare acts as a processor on behalf of this site.

The one place an IP address is used deliberately is the administrator login endpoint, which is rate-limited: the address serves as a counting key so that a single origin cannot start an unlimited number of sign-in attempts per minute. The counter lives a couple of minutes and is then discarded. It is never linked to anything else and never written to the database.

The administrator's sign-in

One person can sign in to this site: its author, in order to write and publish. That is the only thing the __Host-session cookie is for. It holds an opaque random token — the server keeps only a hash of it, never your identity — and it is issued at the end of an administrator sign-in through Google. As a reader you will never be given one.

Three further cookies (oauth_state, oauth_verifier, oauth_next) exist for the ten minutes an administrator sign-in is in flight, to protect it against request forgery, and are deleted the moment it completes.

Google is the identity provider for that sign-in and learns that the author was here. That exchange is governed by Google's own privacy policy rather than this one, and it involves you not at all.

How long things are kept

• The lang cookie — one year, renewed each time the site works out a language for you.
• The theme preference — in your browser until you clear its storage. This site never has a copy.
• Rate-limiting counters — a couple of minutes, then discarded automatically.
• Cloudflare edge request logs — only as long as Cloudflare keeps them, under its own retention rules.
• Administrator sessions — 30 days from last use, then automatically discarded.
• Database backups — written nightly to Cloudflare R2 and deleted after 30 days, so anything that leaves the live database is gone everywhere within a month.
• Web Analytics measurements — kept by Cloudflare under its own retention rules. They carry no identifier that could be traced back to you.

Your rights

Under the GDPR you can ask for access to what is held about you, correction of it, erasure of it, a portable copy of it, or restriction of how it is used. In practice there is next to nothing to ask about — no account, no email address, no comment history — but requests go to the address above and are answered within a month.

You also have the right to complain to a data-protection authority if you think this site has handled your data badly.

Changes

The date at the top is the last time this text changed in a way that mattered. Material changes to what is collected will be announced on the site rather than made quietly.