This site is static. It has no accounts, no login and no server-side database. What follows is a complete account of what it stores, what it sends elsewhere, and what it deliberately does not do.
What this site collects directly
Nothing. There is no account system, no newsletter, no contact form that posts to a server, and no cookie set by this site.
Site search runs entirely in your browser against an index downloaded with the page. What you type into the search box is not transmitted anywhere and is not logged.
Checklist progress stays on your device
Procedure pages let you tick steps off as you work. That progress is written to your browser's local storage — a small store on your own device, similar to a cookie but never sent with a request. It is not transmitted anywhere, this site cannot read it, and it is not shared between your devices.
What is stored is only the page address, the version of the procedure, which step numbers you marked, and when. It holds nothing about you.
Three things worth knowing:
- Clear progress on any procedure page erases that page's entry immediately. Clearing site data in your browser erases all of them.
- When a procedure is revised, saved progress for it is discarded rather than restored. Replaying "step 7 done" against a renumbered step 7 would be a silent and potentially dangerous mistake, so the page tells you it was cleared and asks you to start again.
- If your browser blocks storage, or you are in a private window, the checklist still works for the session. It simply does not remember.
Hosting
The site is served as static files by a hosting provider and delivered through a content delivery network. Like any web server, that provider processes the technical information needed to deliver a page — your IP address, the page requested, the time, your user agent and the referring page. That processing is the hosting provider's, under their own policy, and it is what makes serving a web page possible at all.
Comments
Comments are provided by Giscus, which stores each thread as a GitHub Discussion in this project's repository. Comments deliberately do not live inside this site: a static site redeploys constantly, and anything stored in the page itself would be destroyed on the next deploy.
This means three things worth being explicit about:
- To post a comment you sign in with a GitHub account. That is an interaction with GitHub, under GitHub's privacy policy, not this site's.
- Comments are public, and they are hosted by GitHub rather than here.
- The comment widget loads from giscus.app, so your browser makes a request to that domain when the section renders.
Comments are never edited and never deleted by this site. Spam and abuse are hidden, which leaves the original record intact.
Analytics
Analytics are currently switched off. No analytics script is loaded and no analytics identifier is set.
If analytics are added later, this page will name the provider before the script is served. The build refuses to emit an analytics tag that is not disclosed here — that is enforced in code, not by good intentions.
Requests to other domains
Pages are self-contained: the stylesheet is inlined, the fonts are the ones already on your device, and there are no third-party images, tracking pixels or embedded videos. The only request to another domain from a normal page is the comment widget described above. Links to source documents are ordinary links; nothing is fetched from them until you click.
Children
This site is not directed at children and does not knowingly collect information from anyone.
Changes and contact
Material changes to this policy will be recorded in the public corrections log with a date, in the same way as a change to a procedure. Questions about privacy can go to the contact address on the contact page.