Cookie policy
Two groups of cookies can appear here: security and — once enabled — analytics. All of them come from third parties, not from us.
What a cookie is, briefly
A cookie is a small file a site asks your browser to store. It can keep you signed in, remember a preference, or help a third party recognise the same browser across visits. Some are essential for a site to work; most are not.
This site has no login, no cart and no settings, so it has nothing of its own to remember about you. Every cookie you may receive here is set by Cloudflare or by Google Analytics — and the latter only once a measurement ID is configured.
Scroll the plate sideways to see all of it.
Necessary cookies
Cloudflare, which serves this site and filters abusive traffic, sets cookies to tell a real browser from a bot and to keep a security challenge from repeating on every request. They contain no profile of you. Blocking them can make a page loop on a challenge.
Analytics cookies
When analytics is enabled, Google Analytics 4 sets a client identifier cookie so it can tell a new reader from a returning one, plus one or more cookies scoped to this property. The configuration used here switches on IP anonymisation and fires only on the production hostname, so preview and local builds send nothing. While analytics is disabled, the loader script is not printed and these cookies are never created.
| Group | Set by | Examples | Purpose | Lifetime |
|---|---|---|---|---|
| Security | Cloudflare | __cf_bm, cf_clearance | Distinguish browsers from bots; keep a passed challenge from repeating | Roughly 30 minutes to a few hours; set by the host |
| Analytics | Google Analytics 4 | _ga, _ga_<id> | Count visits and attribute them to a source; only when analytics is enabled | Up to about two years for _ga |
Scroll the table sideways to see every column.
Consent, stated plainly
This site does not run its own consent banner and does not store a consent choice. Analytics, when it is enabled, is loaded for measurement only. The controls below are the reliable way to decide what your browser accepts.
If you are somewhere that requires consent before non-essential cookies are set, treat them as not consented unless you have given it, and block them using the steps below. Saying that openly is better than claiming a consent flow we cannot show you.
The short version
There is no sign-up and no profile. Block all third-party cookies in your browser and the site still reads perfectly. Details on data handling are in the privacy policy.
How to manage them
Every major browser lets you block or delete cookies per site. In Chrome, use Settings, then Privacy and security, then Third-party cookies. In Safari, use Settings, then Privacy. In Firefox, use Settings, then Privacy and Security, where Total Cookie Protection blocks cross-site tracking by default. In Edge, use Settings, then Cookies and site permissions.
For measurement, Google publishes an Analytics opt-out browser add-on. Using a private window, a container tab or a tracker-blocking extension also stops most of these cookies without changing your browser permanently.
If you block them
Nothing on this site stops working. Pages are static, there are no logins and no features depend on a cookie. The visible effect is that Cloudflare may ask your browser to prove it is not a bot more often.
Do Not Track and Global Privacy Control
Browsers can send a Do Not Track or Global Privacy Control signal. This site has no server-side application of its own to read those signals, so they are not separately honoured by anything we control. Third-party scripts decide for themselves. The dependable route remains blocking the cookies at the browser.
Changes and contact
If a new processor or analytics tool is added, this page and the privacy policy change before the tool goes live, and the date at the foot of the page moves. Questions go to [email protected]; the contact page explains what that mailbox handles.
Last updated 2026-11-16. This page is written and maintained by the site editors. Email us to request a correction.