Privacy policy
What this site measures, what it refuses to store, and why nothing here asks you to click a box.
Last reviewed 30 July 2026
The short version
One measurement tool runs here, it writes nothing to your device, and nothing else runs at all. There is no advertising pixel, no remarketing tag, no session recorder, no heatmap, no chat widget and no social embed. Nobody is profiled, nothing is sold, and no attempt is made to work out who any individual reader is. The one commercial link on the site is declared separately under advertising disclosure.
Analytics
The site runs Google Analytics 4 on property G-MDQQRBTV9R. It records which pages
are opened, roughly where in the world the request came from, which browser and device class made
it, whether a link out was clicked, and which site or search sent the visit. Addresses are
truncated by Google before storage, so the location it reports is coarse — a country, sometimes
a region, never a street.
Advertising features are switched off on the property, and all four advertising consent signals are set to denied before the tag loads, so no audience is built from this traffic and none is shared for targeting elsewhere — a position that follows from what the site is for, described under about. Google processes the data as a service provider and its own terms apply on top of this page.
Cookies, and why there are none
None are written. The tag loads under Google's consent mode with storage denied by default, and because this site never asks you to grant it, that denial stands for every visit. In that state Google Analytics may not write to your device at all: no identifier, no session record, nothing that survives the tab closing.
Two cookies would exist without the setting — _ga, which tells one browser from
another, and _ga_MDQQRBTV9R, which holds session state for the property. Neither is
created here. Open your browser's developer tools, read the storage tab, and the absence is
verifiable in fifteen seconds, which beats trusting this paragraph.
The trade is deliberate. Measurement drops to cookieless pings, so a returning reader counts as a new one and Google fills the gaps by modelling. Weaker numbers were preferred to a consent box interrupting a page nobody arrived here to click through.
No banner, and why not
Consent boxes exist because a site wants the storage and needs permission first. This one does not want it. Denying storage before the tag loads arrives at the same lawful position from the opposite end, with nothing to dismiss and nothing remembered about you between visits.
Should that ever change — should a cookie turn out to be worth having — permission will be asked for properly, and this page will say so before anything is written.
Opting out
- Install Google's analytics opt-out add-on, which blocks the tag across every site that uses it.
- Block third-party scripts with a content blocker, or use a browser that blocks trackers by default — the tag simply fails to load and the site works unchanged.
- Browse privately and clear cookies on exit, which resets the identifier every session.
None of these degrades anything, and each is a belt to braces already fastened. The site has no logged-in state, no personalisation and no feature that depends on recognising you — the comparison renders identically whether the tag loaded or not.
Typefaces and other third parties
Fonts are served from this domain out of /assets/fonts. Nothing is requested from
Google's font hosts, so no request carrying your address reaches them when a page renders — a
third party that European regulators have repeatedly treated as a problem when embedded without
permission. Aside from the analytics tag, the browser contacts no other domain to display these
pages.
Server logs and retention
The hosting platform keeps standard access logs — address, timestamp, requested path, user agent — as every web server does, and nobody, including the writer, reads them for anything else. They exist for security and fault-finding, are not joined to analytics data, and are not used to build any profile.
Event-level analytics data is held for the window configured on the property, which cannot exceed fourteen months under Google's own limits; aggregated reporting outlives the underlying events, and with storage denied no identifier ties any of them to a device in the first place. Correspondence sent to the addresses on the contact page is kept only as long as the exchange needs.
Your rights
Readers in the EU, the UK and comparable regimes may ask what is held, ask for deletion, or object to processing. In practice there is little to hand over: with no stored identifier, nothing on the analytics side attaches to a person, and requests are answered on that basis. Send them to [email protected].
Changes
Material changes advance the stamp above, on the same discipline the methodology page applies to figures. Nothing described here is altered retroactively — a new tool means a new paragraph, not a quiet edit to an old one. Your rights under this policy sit alongside the terms of use, which govern everything else about reading these pages.