Privacy
Nothing about you is collected, and nothing is kept
No personal data of any kind is collected or stored by this site.
That is a statement about how the site is built, not a promise about how carefully we behave. What follows is the whole of it.
- no cookies
- None are set, of any kind — not technical, not analytical, not from anybody else. There is no cookie banner because there is nothing to ask you about, and a banner asking consent for things that do not happen would be theatre. The only thing this site ever writes to your device is your light-or-dark choice, if you make one; it holds one word, it never leaves your browser, and clearing your site data removes it.
- no analytics, and no measurement of you
- No analytics script, no pixel, no tag manager, no heatmap, no session replay, no fingerprinting. Not one line of anybody else's JavaScript runs on this site.
- no access logs
- The web server is configured with logging off. We do not know who reads a page, who opens the checker, or who downloads the skill — and we have arranged not to be able to find out. A tool about disclosure that counted the people checking it would be refuting itself.
- nothing loaded from anywhere else
- Fonts, styles and scripts are served from this domain only. No CDN, no font service, no embed. This matters more than it sounds: a page that loads a font from a third party hands that third party your IP address, your browser and the address of the page you are reading — without asking you, and without you being able to refuse.
- nothing to fill in
- There is no form, no sign-up, no newsletter, no account, no email address to collect. There is nothing here you could give us even if you wanted to.
- the checker never uploads anything
- The file you drop on the checker is read in your own browser and goes nowhere. It works with the network off, which is the plainest proof of it: turn it off and try.
If you think something on this site collects anything, that is a defect and it is worth reportinggithub.com.
The skill
What the skill does on your machine
The skill runs where you run it.
- files on your disk
- The case folder, the register, your drafts, the annotation and the measurement are files on your disk, and none of them is sent anywhere. There is no account, no telemetry, no deposit service and no hosted copy — the method has no address to offer.
- one hash at the seal
- One thing leaves your machine, and only when you seal.
seal.shsends a SHA-256 digest to a timestamp authority —timestamp.digicert.comby default, changeable withCOLOPHON_TSA— to obtain an RFC 3161 token. What travels is a hash of the manifest, never the text: the authority cannot read what it timestamps. If OpenTimestamps is installed, the same digest is also anchored on Bitcoin. Both are third parties with policies of their own. - only the public half travels
- The private key never leaves. It is read from
~/.ssh/colophon, used locally to sign, and stays there. Only its public half is copied into the bundle, because a reader needs it to check the signature offline — which is the whole point of it being there.