Cookies
There is no cookie banner on this site because there is nothing to consent to: Google Analytics 4 runs cookielessly, no advertising script loads, and nothing is written to or read from your device — including by the one third-party script the CDN inserts.
There is no cookie banner because there is nothing to consent to
What this site stores on your device
Nothing. No cookies, no local storage, no session storage, no device fingerprinting. The pages are static files; there is no server-side session to keep.
Third-party scripts
We load one: Google Analytics 4 (GA4), Google’s measurement script, from googletagmanager.com. It runs in cookieless mode — it writes no analytics cookie and stores no identifier on your device. Instead it sends Google cookieless, aggregated pings that carry the page URL, the referrer, an approximate location derived from your IP address, and basic device and browser characteristics. Google is a third-party processor of that data, and it may be handled outside Ireland. No advertising script is loaded, and fonts are self-hosted, so no font request leaves for a third-party host.
There is one more script, and it is not ours. While this site sits on its preview address, the network that serves it — Cloudflare — inserts its own visit-counting script into the response, loaded from static.cloudflareinsights.com(Cloudflare Web Analytics). It is in none of the files we build: it is added to the output after our server has produced it, and nothing in this repository can call it or remove it — only the account holder can switch it off in Cloudflare’s own settings. We measured a page load in a real browser: that script sets no cookie, and the browser finishes the load with zero cookies.
Why there is still no banner
The consent defaults in the page head are set to denied and nothing on this site ever flips them. GA4 runs cookieless, so it never asks them to. Because nothing about you is stored on your device on an ordinary visit, no consent requirement under the ePrivacy Regulations arises — that is why there is no banner, not an oversight. A read does take place on every page view, and it is named rather than passed over: the internal-visit flag described below, which is a single switch and not an identifier, and which exists in a browser only if the reader put it there.
Excluding our own visits
One exception, named here rather than passed over in silence: on every page view the measurement code checks whether the gr_int flag is present in your browser. That is our own exclusion for internal visits, so that our test traffic does not end up in the figures. It is written only when a page is opened with ?internal=1 appended — as a cookie with a lifetime of one year, and additionally in local storage. Without that, nothing is written, and nothing on this site links to it. It holds a single flag and nothing about you. You delete it by clearing this site’s data in your browser.
Changes
Last updated 10 August 2026.