Below is what happens when you load a page here: what we do, what we refuse to do, and the parts we do not control. Where a claim is a vendor's, it is quoted and linked so you can check it against us.
None of the following exists on any page of this site. This is not a promise about intent; it is a description of the files that get served.
The fonts are worth naming specifically, because until 5 September 2026 they were the exception. The three typefaces here (Fraunces, Public Sans, JetBrains Mono) were loaded from Google's font servers, which meant every reader's browser announced its address to Google before a word of this site was read. They are now served from this domain. All three are licensed under the SIL Open Font License 1.1, and the font files and their licenses sit in the repository next to the pages.
This site is served through Cloudflare. There is no version of delivering a web page in which the network in front of it does not see the request, and Cloudflare is that network. It sees your IP address, because that is the address it sends the page back to.
Cloudflare's own privacy policy (effective 4 November 2025) describes what it processes for people who visit a customer's site: information that may include but is not limited to IP addresses, traffic routing data, system configuration information, and other information about traffic to and from Customers' websites, devices, applications, and/or networks.
Read it at cloudflare.com/privacypolicy.
Cloudflare does not publish a fixed retention period for that data. Its policy states only that information is kept for a period of time that is consistent with the business purposes set forth in Section 3 of this policy or as long as needed to fulfill and comply with legal obligations.
That is Cloudflare's answer, not ours; we cannot improve on it and we will not pretend to know a number it does not publish.
What the Committee can see through Cloudflare is aggregate: request counts, bandwidth, a unique-visitor figure, and the countries requests came from. Cloudflare's zone analytics documentation also records that those analytics can be filtered by dimensions including source IP address. We do not do that, and nothing on this site would let us tie an address to a person if we did.
On cookies: we checked the live response headers for this domain on 5 September 2026 and no cookie was set. Cloudflare documents the cookies it can set on a domain behind it. The two a reader here could plausibly meet are __cf_bm, used for bot detection, which Cloudflare says expires after 30 minutes of continuous inactivity by the end user
, and cf_clearance, which records that a challenge was passed. Both come from Cloudflare, not from us; we do not read them and could not.
Cloudflare attaches two headers to every response from this site: nel and report-to. They instruct your browser that if a request to this site fails at the network level, it should send an error report to a.nel.cloudflare.com. This is Cloudflare's Network Error Logging, and we are disclosing it because it is the only remaining case of a page here causing a browser to contact any host but this one.
The header served on this domain reads {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}. The success_fraction of 0.0 is the part that matters: successful requests are never reported. A report is generated only when a connection breaks.
Cloudflare's documentation for the feature lists what a report carries: the requested URL, the error type and phase, the protocol, elapsed time, status code, and server address. On the reader's own address it states that Cloudflare does not log the client IP address anywhere in the Network Error Logging pipeline
and that Reports do not contain personally identifiable information (PII)
. We did not add this, we do not receive the reports, and it is a setting Cloudflare documents as switchable at the domain level. As of 5 September 2026 it is on. It is the next thing to go.
There is no application server here and no database. The pages are files. Nothing of ours runs when you read one.
The single exception is a small Worker that answers /health, which exists so that a deploy can be verified by asking the live site which commit it is serving. The configuration routes only that path through code; every other path is served straight from Cloudflare's asset store.
Cloudflare's Workers Logs is switched on for that Worker. Cloudflare describes what it captures as invocation logs, custom logs, errors, and uncaught exceptions
, and says each invocation log is enriched with information available to Cloudflare in the context of the invocation
. In practice: whatever reaches the Worker is recorded, at minimum the method and the URL. Retention is Cloudflare's and it is short. Its limits give three days on the free Workers plan and seven on the paid one, against a stated Maximum log retention period
of seven days.
We keep no copy of any of it. Nothing in this project's configuration exports request logs anywhere, and there is nowhere for them to go.
No intake channel is open yet. The Signal number, the Telegram handle, and the encrypted-email key listed on the front page are marked pending because they are pending: there is nothing to send to today. The rules below are the rules for when they exist, published in advance so that nobody has to take them on trust after the fact.
This policy changes by published, dated revision and in no other way. There is no silent edit, no continued use constitutes acceptance
, and no version that exists only in a vendor's archive. The date below is the date of the text you are reading; when the text changes, that date changes with it, and the previous wording stays in the repository's history where anyone can diff it.
Last changed: