Draft · prelaunch · not legal advice
Privacy draft
This page describes the ClaimComb prototype as it behaves in this repository today. It is not a finished policy. Creating an account does not record agreement to this draft. A legal entity, postal address, contact email, retention period, and training rule have not been chosen.
What you can do without an account
The opening page is a temporary demo on this device. Choosing files records their names and sizes in the page only. The prototype does not read those file bytes and does not send them to a server. The public sample about The Dalles agreements is pre-written. It is not an analysis of your files, and it is not saved to an account.
Accounts
Sign-in uses email and a password, an email sign-in link, or a password-reset link. The account service is the existing Supabase project (ref nptgmwyelncwqjfqyfbv, display name ClaimComb). The page stores the session with that service’s browser client. Guest or anonymous Auth users are not created. This draft does not promise how long an account lasts, and the page does not yet offer account deletion.
What is stored when you are signed in
- A saved analysis: a title and a JSON document of the on-screen sample state, in the existing
saved_analysestable, tied to your user id. - Appearance: light, dark, or system, in
user_settingsand also in this browser under the existing keynp-theme. - Private files: the page can store a supported file for a signed-in email account only after a reviewed migration is applied. That switch is off. Until then, nothing is uploaded. A stored file would be metadata plus an object in a private bucket under your user id, opened with a short-lived link. Storing a file would not analyze it.
Signing out removes saved analyses and any short-lived file link from this page. Forgetting the link does not cancel it. A link already issued can keep working until it expires or the file is deleted. Signing out does not delete stored files. The inspected database still has no document bucket. While storage is switched off, the page does not upload and does not report a successful upload. Deleting a saved analysis deletes that row. Clearing a local file selection does not contact a server.
What this prototype does not do
It does not run the evidence engine on your documents. It does not call a model to analyze uploads. No analytics or advertising tag was added. A future hosted analysis, if one is built, is not described here and would need its own review.
Limits
Owner-only row policies were inspected for the two existing tables. That inspection was not a two-account login test. Database roles still have broad grants, including truncate, which row policies do not cover. Whether a browser can use those grants was not established. The publishable client key is in the page source; it is not a service-role key. A service-role key is not shipped here and can bypass row policies, so it must not be used to store a guest catalog.
Still undecided
- Who operates ClaimComb, and how to reach them.
- How long accounts, saved analyses, and server logs are kept.
- Whether file bytes will ever be stored, and in which private bucket.
- Any rule about model training. None is stated, because no model is called.
- Any compliance certification. None is claimed.