Privacy

This site uses Google Analytics in Consent Mode: Google's tag loads on every page but sets no cookies unless you accept, and until you choose it receives only cookieless counts, which include your IP address and the page you are on. It carries no advertising, no social widgets and no external fonts, does not ask for or store personal information, and has no account to create.

The short version

This site uses Google Analytics to count visits and see which pages are read, in what Google calls Consent Mode. Google’s tag loads on every page, but before it does we tell it that analytics cookies are denied. Until you press Accept it sets no cookie. It does still send Google a cookieless ping for each page view, which includes your IP address, the page you are on, the page you came from and your browser’s user agent, and Google may use those pings to model aggregate visit counts. If you press Accept, it also sets cookies. If you press Decline, it keeps to the cookieless pings and removes any Google Analytics cookies already in your browser. See cookies and consent below.

This site used to load nothing from Google until you accepted. It no longer does, so a visit now reaches Google before you choose; the choice governs cookies and identifiers, not whether the cookieless ping is sent. If that is not acceptable to you, a tracker blocker or Google’s browser opt-out add-on stops the pings entirely.

Beyond that there is no advertising, no social widgets, no fingerprinting and no external fonts — the fonts are served from this domain. Google Analytics is the only third-party script the site loads, and a content security policy blocks every other origin at the browser level.

There is no account to create, no newsletter that requires an address, and no form that collects personal information.

What is collected

Google Analytics 4. If you accept, it sets cookies (_ga and a property-specific _ga_*) that persist in your browser and give you an identifier Google uses to recognise a returning visitor. If you have not accepted, it sets none, and Google receives cookieless pings as described above. What we see is aggregate: page paths, referrers, approximate location, device and browser categories, and how people move between pages. With consent denied, Google may fill gaps with modelled figures; they are estimates, not a record of individuals.

We have configured it to collect less than it does by default:

• Advertising signals (ad_storage, ad_user_data, ad_personalization) are denied permanently, and ads data redaction is on.
• IP anonymisation is the default in Google Analytics 4: it does not store full IP addresses.
• Google signals are off, so your visits here are not joined to your signed-in Google activity across other sites.
• Advertising personalisation is off, so nothing collected here feeds ad targeting.

What we cannot change is that the data goes to Google and is handled under Google’s privacy policy. If you would rather not be counted, Google publishes a browser opt-out add-on, and ordinary tracker blocking works too — nothing on this site depends on analytics running, and blocking it changes nothing about what you can read.

Cloudflare Web Analytics, if it is enabled on this deployment. It is privacy-preserving by design: it uses no client-side state, sets no cookie, does not fingerprint the browser, and does not track visitors across sites or sessions.

Server logs, kept by Cloudflare as the host. These record the ordinary technical facts of serving a page — IP address, timestamp, requested path, user agent — and are retained by Cloudflare under its own policy. They are used for delivering the site and for security, not for building profiles.

That is the complete list.

What is not collected

• No advertising identifiers, and no personalisation signals sent to ad systems.
• No fingerprinting, and no social-network widgets.
• No email addresses, except where you choose to email us directly.
• No account data, because there are no accounts.
• Nothing you type: there is no form on this site that submits anything.

Cookies and consent

Google’s analytics tag loads on every page, and a banner on your first visit asks whether it may use cookies. The tag is configured under Google Consent Mode v2 with every signal set to denied before it runs: until you accept, no analytics cookie is written, but cookieless pings are sent (see above). Accepting grants analytics storage only. It never grants advertising storage, because the site carries no advertising.

This is the arrangement Google calls “advanced” Consent Mode. It is less strict than loading nothing until you accept, and it reaches Google before you have chosen, which some privacy regulators treat as needing consent in its own right. We have chosen it so that Google can model the visits it cannot count; if you would rather not be in those pings, block the tag.

Accept and Decline are the same size and carry the same weight, because a decline that is harder to find than an accept is not a choice. Your choice is stored as a single flag in your browser’s local storage so we do not ask again; it sets no cookie. Declining, or reopening the choice below, withdraws consent and removes Google Analytics cookies from this site’s domain. Nothing on this site depends on analytics running.

You can change your mind at any time:

That button needs JavaScript to work. If yours is off, Google’s tag does not run and nothing is sent.

Email you send us

If you email a correction or a question, we have your message and your address, because that is how email works. We use it to reply and to record the correction. We do not add it to any list, and we do not share it.

External links

Pages link extensively to regulator websites, primary legal texts and court filings. Those sites have their own privacy practices, which we neither control nor endorse. Links to third-party documents carry rel="nofollow noopener".

Data requests

Because the site holds essentially no personal data about visitors, there is usually nothing to disclose, correct or delete. If you believe we hold information about you and want to know what, email [email protected].

Note that pages about individuals named in public enforcement filings contain information drawn from those public filings. The editorial policy sets out what such a page may contain and what it may not, and the corrections process covers requests to correct or update one.

Changes

If this changes, this page changes, and the date at the top records when.

Last updated October 5, 2026.