What this site collects, and what it does not.

This site is a set of static files and server-side functions running on Cloudflare. It collects as little as it can get away with.

What we do not do

No third-party analytics, advertising or tracking scripts.
No tracking cookies. No cookie banner, because there is nothing to consent to.
No embedded social widgets, comment systems or remote fonts that would see your visit.
We do not sell, rent or share personal data with anyone.

Request logs. Cloudflare, as the network provider, processes IP addresses and user-agent strings to serve pages and block abuse. This is standard for any website and is retained on their side.
Visit counts. We count how many times each page is read, so we know which articles are worth writing. This is measured on our own infrastructure and stored only as daily totals: number of views, page path, the hostname of the referring site, the country the request came from, and coarse device categories (desktop, phone, tablet) along with the operating system and browser family. There is no cookie, no identifier, and no per-visitor record — we cannot tell one reader from another, and no third party is involved. The browser's user-agent string is read to derive those categories and is then discarded; it is never stored. Automated traffic (search engine and AI crawlers, uptime monitors, scripts) is excluded. Browsers sending DNT: 1 are not counted.
Newsletter. If you subscribe, your email address is stored in our own Cloudflare key-value store. It is used for one thing only: sending you an email when a new article is published. Ask us to delete it and it is deleted.
Editor session. If you log into the editorial admin, a password is kept in your browser's session storage and a preview cookie may be set. Neither applies to ordinary readers.

To have a newsletter address removed, or to ask what is held, write to the address on the about page.