Cookies

Short version: we set one cookie, it exists so forms are safe to submit, and we do not measure you.

The cookie we set

It is called session. It is set when you open a page that has a form — today that is the beta application — so on arrival, not when you press send. That is the distinction a cookie notice exists to draw.

• What it holds: a one-time key tying the form to your browser, so that nobody else can make your browser submit the form in your name.
• How long: until you close the browser. It has no expiry date and is not there on your next visit.
• Who can read it: only our server. It is marked HttpOnly, so the page's own JavaScript cannot reach it, and SameSite=Lax, so it does not travel along when another site links to us.

Why there is no consent banner

Because the cookie is necessary for something you asked for. Cookies like that need no consent — and we set no others. If we ever set one that is not necessary, a consent banner is the first thing you will see.

What we do not do

• No web analytics. We have not chosen an analytics tool, and there are no measurement scripts on the site.
• No advertising or tracking cookies, and nothing that follows you on to other sites.
• No third-party requests at all. The typefaces are hosted by us rather than by a font vendor, so your browser fetches nothing from anyone else while you read this page. Nobody else learns you were here.

If you want rid of it

Every browser can block or delete cookies, per site or in general — look for cookies or site data in the settings. Block ours and the pages still read normally, but forms cannot be submitted: without the key, the server cannot tell your form from a forged one.

If this page changes

We update this page before a new cookie starts being set, not afterwards. The whole picture of how we handle personal data is in the privacy policy.