Cookies.

01 · The claim

The whole policy

This site sets no cookies of any kind, including the ones called "strictly necessary". It writes nothing to local storage and nothing to session storage. It keeps no session and holds no identifier for a reader. It loads nothing from any origin but its own.

That is why there is no consent banner. There is nothing to consent to, and a banner asking anyway would be this page's first lie. A reader who arrives, reads every route on the site and leaves again is unrecorded, and the site is built so that stays true by default.

02 · The two that would

What would set one

Two cookies are foreseeable and neither exists today. A session cookie arrives the day accounts do, to keep a signed-in reader signed in across a page load. A preference cookie arrives the day a reader can save a view, to remember which view it was.

Neither is a tracking cookie and neither is set today. Neither would carry an identifier that leaves this origin. This page changes on the same day either one lands: its name, what it holds, when it is set, when it dies. By dated revision, before the code ships.

03 · The evidence

Checking it yourself

The claim is checkable from outside this site, with the tools already in the browser. Four checks, and none of them needs us:

• The response headers. Request any page here and read the Content-Security-Policy header. It declares default-src 'self', so this page is not permitted to load a script, a font, a style or an image from another host.
• The Set-Cookie header. No response from this origin carries one, on any route, before or after a form is submitted. A cookie the browser was never sent is a cookie the browser never stores.
• The storage panel. Open the browser's own storage view for this domain. Every store it lists is empty for this origin, and stays empty for as long as you read.
• The origins on a page load. Count the hosts in the network panel. The fonts are served from this origin and every figure is read by this site's own server before the page is sent, so a page load speaks to this host and to no other.

The one cross-origin request in the whole site is the launch notice form, and it happens only when a reader submits it. It posts to the EU server that holds the launch notice list, which is described on the privacy page.

04 · The date

Last verified against the shipped headers

2026-08-10