Privacy Policy

Every page view writes one row: the page you opened, the site you arrived from, any campaign tags in the link, the domain you came in on, your IP address, your browser's User-Agent string, and a country and region derived from that IP. A second row records how long the page stayed open and which labelled elements you clicked — the label only, never text you type.

Calls to the public API record one row too: which endpoint, the calling address, and the same automated-or-not verdict. Nothing about a page and nothing about a person — the API needs no identity and asks for none.

This exists to answer two questions: which pages people actually read, and which visits are automated. It is not used to build a profile of you, and it is never matched against anything outside this site.

Two of our own. One holds a random visitor id — sixteen hex characters, meaningless anywhere else — so repeat visits can be counted without knowing who you are; it cannot be read by scripts and expires after 180 days. The other remembers the language you picked, for a year. Google Analytics sets its own on top of these.

Umami runs on our own server. It sets no cookies, does not fingerprint, and its data never leaves our infrastructure.

Google Analytics is a Google product. It sets its own cookies and sends the visit to Google, which may process it outside the country you are in.

The newsletter stores your email address and language. The contact form stores what you type into it: email, name, optional company, message. Coding-plan feedback stores which plan and whether you hit its limit, tied to the random visitor id and nothing else.

The cost calculator is different. What you type there never leaves your browser, except inside a share link you choose to create.

There are no accounts and no passwords, so there is nothing of that kind to lose. No payment details, because nothing here is paid for. No advertising networks and no data brokers. Nothing collected here is sold or traded to anyone.

Plainly: there is no automatic deletion today. Visit records accumulate, and we would rather say so than publish a retention period the code does not implement. If you want the rows tied to your visitor id or your email address removed, ask and they will be.

Google, for the Analytics visits described above. Our mail providers see the address you subscribed or wrote in with, and nothing else. Nobody else receives any of it.

Block the trackers — nothing on this site depends on them. Clear the cookies whenever you like; the site will mint a fresh anonymous id and carry on. Or write to us and have your data removed.

This page is updated when what the site does changes, and the effective date above moves with it. It describes the current behaviour of the code, not an intention.

Anything here unclear, or want your data removed? Get in touch.

Terms of Service