Legal
Privacy Policy
Last updated 22 October 2026
Draft for owner and legal review. This page describes how the product actually behaves today, but it is not legal advice and has not been reviewed. Replace the bracketed placeholders and remove this notice before launch.
This policy describes the data OpenWeightModels actually collects in the product today, where it goes, and how long it stays. It is written for the current build, not for an aspirational future one. The operator is [legal entity name], contactable at [contact email].
What we collect
| Data | Why | Who can see it |
|---|---|---|
| Email address | To send a single-use sign-in link and to contact you about your account | You and the operator only. Never shown publicly. |
| Handle, account id, member-since date, role (member or Admin), suspension status | Public identity and access control | Handle is public on everything you publish. The rest is internal. |
| Sign-in session: a session token, its expiry, IP address and browser user agent; a hashed magic-link token with its expiry | Keep you signed in, prevent link replay, and secure the service | The operator only. |
| Comparison content: title, Prompt, Categories, Effort, the Base output you upload, and generated Challenger Responses with model, token count, latency and provider-reported cost | To run and display the Comparison | Published Comparisons are public. Drafts, Jobs and unpublished work are visible only to you (and silently hidden from everyone else). |
| Discussion and Annotations: comments, annotation kind, the highlighted quote and range, thread messages, votes | To display the conversation and rank by activity | Public on a published Comparison; vote totals are public but individual votes are not shown. |
| Notifications and their read state | Tell you when a Job is ready | You only. |
| Reports you file, and moderation records | Review harmful content and keep actions attributable | Admins only; never published. |
| Public activity ticker lines, such as “@handle published …” | Live Board activity and reconnect replay | Public. |
We do not use analytics, advertising trackers or third-party cookies. Server logs may record requests and errors; they are used for security and debugging and are kept by the hosting platform’s log service.
Who processes it
- Email delivery. Amazon SES sends sign-in links in the documented production setup. Local development uses a local Mailpit inbox and sends nothing externally.
- Model providers. When a Challenger Response is generated, the Comparison’s Prompt and the fixed generation parameters are sent to the configured OpenAI-compatible provider (OpenRouter is the first adapter). The Base output you uploaded is not sent to the provider.
- Hosting. The documented production target is AWS: web and worker containers, a relational database, a Redis queue and logs in CloudWatch. Locally, data stays on the operator’s machine.
We do not sell personal data.
How long we keep it
| Data | Retention |
|---|---|
| Email and handle | Until you delete your account; both are erased and released then. |
| Anonymised account row (id, role, join date, deleted_at; no email, handle, name or avatar) | Retained after deletion solely to attribute published Comparisons to “[deleted]” and keep them readable. |
| Magic-link token | 15 minutes, single use; reused or expired tokens are rejected. |
| Session | Up to 7 days, or until you sign out or delete the account. |
| Unpublished Comparisons (Drafts, generating and ready work) | Until you delete the Comparison or your account. Deleting the account removes them, their uploaded Base outputs and their generated Responses. |
| Published Comparisons and generated Responses | While the Comparison exists. Deleting your account keeps published Comparisons on the Board under an anonymous attribution. If you need a published Comparison removed after deleting your account, write to [contact email]. |
| Discussion comments, Annotations and thread messages | While the Comparison exists. Deleting a Discussion comment leaves a tombstone with an empty body so replies keep their place. Deleting an Annotation removes its highlight and thread. Deleting your account applies the same rules to everything you wrote. |
| Votes, notifications and reports you filed | Until you delete your account. |
| Public activity ticker lines | Kept for the live Board and reconnect replay. Lines for content or an account that is removed are deleted. There is no scheduled pruning job yet; the retained window is the database’s full history. |
| Moderation and Admin audit records | Retained after an account is deleted for accountability. They record the action, target and reason, never an email address. |
Your choices
- Export. Account has a download that returns your profile, Comparisons, comments, Annotations, votes and notifications as JSON. Other people’s emails and words are excluded.
- Delete. Account deletion erases your email, handle, sessions, votes and notifications and deletes unpublished work. Published Comparisons stay under [deleted]; your Discussion comments become tombstones so replies stay readable, and your Annotations are removed with their threads. Your handle and email are released for reuse. The action is immediate and cannot be undone.
- Corrections and questions. Write to [contact email]. Depending on where you live, you may also have rights to access, correct, restrict or object to processing, and to complain to a data protection authority.
Security
Sessions are cookie-based and HTTP-only. Sign-in links are single use and stored only as a hash. Email addresses are never rendered on public pages, raw HTML in uploads is escaped, and provider API keys live in environment variables or a secrets manager rather than the database.
Changes
Material changes to this policy will be announced on the service before they take effect, with an updated date at the top. See also the Terms of Service.