Privacy
Written against what the application does, clause by clause. Where a clause depends on a decision the operator has not made, it says so rather than guessing.
1. What is collected
An account holds an email address, a display name if one is given, a password hash, and whichever second factors have been enrolled — a passkey, an authenticator secret, or a phone number for SMS. Sessions record the time, an IP address, and a user agent, which is what makes it possible to see and revoke a session you do not recognise. Records you create in the workspace hold whatever you put in them.
2. What is not collected
No advertising or cross-site tracking, and no third-party analytics that follow a reader between sites. Errors are reported to an error tracker so that a crash can be fixed; that report carries a stack trace and the route, not the contents of your records.
3. Why it is held
To authenticate you, to keep an account from being taken over, to show you your own data, and to keep the service working. Nothing here is sold, and nothing is used to build a profile of you for anyone else.
4. Who else processes it
No subprocessor list is published. The vendors this deployment actually relies on have not been enumerated.
5. How long it is kept
You can delete your account from account settings. That deletion is real: the account and the records attached to it are removed rather than flagged.
Retention after deletion is not documented. Deletion itself is implemented; how long backups keep a copy is not settled.
6. What you can do
Export and deletion are both in account settings. Export currently answers that it is not built yet rather than producing a partial file, which is a deliberate choice — a truthful refusal beats a button that appears to work. Deletion is complete and available now.
7. Who to ask
No contact address is published yet. An address that does not receive mail is worse than none.
8. Who is responsible
No legal entity is named yet. Which entity offers this application is not settled.