Nothing here needs to remember you

A cookie is useful when a site has to remember something about you from one page to the next: that you are logged in, what is in your basket, what you ticked last time. Here you are not logged in, there is no basket, and nothing is sold.

The pages are static. They download from the server, they display, and that is the end of it. Nothing is left behind in your browser: no cookies, no local storage, no identifiers.

The shade key, the one you change the page colour with, is built from radio buttons and CSS. It writes nothing anywhere, which is why your choice is lost when you reload. I preferred it that way, even though it is less convenient.

I would still like to know whether anyone reads these pages, and which ones. The measurement is done through Cloudflare Web Analytics, which counts visits without cookies, without browser fingerprinting and without a persistent identifier.

What I see is a number: how many times a page was opened, from which country, on what kind of device. I cannot see who you are, I cannot follow you from one visit to the next, and I cannot find you again on another site.

There is no Google Analytics, no Facebook pixel and no social buttons, because each of those would bring foreign code into the page and make you traceable somewhere else.

If at some point the site genuinely needs a cookie, for an embedded map or a video, then the consent window appears with it, with the options separated and refusing as easy as accepting.

Until then there is no point asking you something I have no intention of doing. A cookie banner on a site without cookies is theatre, and that particular theatre has worn everybody out.

Blocking cookies in your browser settings breaks nothing here, because there is nothing for it to break.