Legal
Draft. Not reviewed by a lawyer. Do not show this to a customer.
All three of the documents below, without exception.
This was written by the engineer who built the software, by reading the code. It has not been reviewed by anybody qualified to review it. It is published here so that it can be read, checked and corrected — not so that it can be relied on. Nothing in it is an offer, a contract or legal advice, and it must not be linked from a signup flow or signed by anybody until a lawyer has read it.
Three documents. All three were written by the engineer who built the software, by reading the database and the code that writes to it, which makes them accurate about this specific product and no substitute for a lawyer having read them.
- Terms of Service — What you are licensing, what you are responsible for, and what we will not do. 10 unfilled
- Privacy Policy — Every table in the database, whose data is in it, who can see it, and how long it is kept. 17 unfilled
- Data Processing Agreement — The processor terms a buyer's legal team will ask for, including the sub-processor list. 15 unfilled
The count beside each one is how many [NEEDS ZACH: ...] markers
it still carries. Each marker is a fact only Zach can supply — the legal
entity name, the registered address, the governing jurisdiction, the address
for data requests, the insurance position. While any of them is still
showing, that document is unfinished, and the count is read from the file on
every page load rather than from a build, so it is always the truth about
what is on disk.
Why these are published at all, unfinished
Because a privacy policy copied from a template is worse than none: it is a promise nobody checked. These were written from the models — table by table, what is collected, who can see it, how long it is kept — so that the thing a lawyer is reviewing is a true description of the software rather than a generic one they have to reconcile with it afterwards. Publishing them here is how they get read.