Legal
Our documents, published while they are still drafts.
Five documents govern what we do: what we agree to, what we collect, what our checks technically touch, what changes when you authorise more, and what this site stores in your browser. They are published so you can read and challenge them. None has been through counsel yet, and every page says so.
01 The documents
What each one is for
-
tos.draft-0
Terms of Service
What you and we each agree to, for the free snapshot and for paid work.
-
privacy.draft-0
Privacy Policy
What we collect, why we are allowed to, how long we keep it and how to get it back.
-
dpn.draft-0
How the snapshot collects, and what it never touches
The technical note for whoever is asked “is it safe to let them do this?”
-
auth.draft-0
Acceptable use and written authorisation
The written permission that has to exist before anything connects to your systems.
-
cookie.draft-0
Cookies, browser storage and consent
Short, because there is one item of browser storage and no cookies at all.
02 Why they are here early
When the review finishes, the draft banner disappears from every page at once — one
constant in src/config/legal.ts governs the banner, the indexing rule and the
sitemap together.
A draft you can read beats a promise that one exists
Publishing an unreviewed legal document is unusual, so here is the reasoning. These documents describe a service that already exists, in language we wrote and have to stand behind. Counsel's job is to correct the law in them, not to invent what we do. Holding them back would mean asking a hospital to trust us on the strength of a sentence saying our terms are being drafted.
What that costs you as a reader: passages marked [COUNSEL: …] are open
questions, some numbers are not settled, and nothing in them is in force. What it gets you:
an exact account of what we intend to collect, keep, promise and refuse — early enough that
you can tell us it is wrong.
The published version strings matter beyond this website. The exact wording you agreed to is stored against your consent record, so a version string is never reused for different text.