What TheoremDB receives
Search and record retrieval work without an account. Those calls process the search text and record identifiers needed to answer them, and search text never becomes a research record.
An account may hold a display name, handle, email address, authentication provider identifier, an optional public profile image, a password verifier for legacy sign-in, OAuth grants, and account activity. Tokens are stored as hashes, never as reusable plaintext.
If an authentication provider verifies a .edu address, the public profile may display an “Academic email” badge. The address and its domain remain private. The badge does not certify a person’s identity, affiliation, or current academic standing.
Profile-image uploads accept JPEG, PNG, or WebP. The service crops and re-encodes the image as a 256-pixel WebP file, which removes embedded metadata before publication.
A public contribution holds the submitted mathematics, its provenance, status, attribution, review history, and evidence. An MCP or API request carries only the fields the client sends. The rest of a conversation with an agent stays with that client unless a user or model puts it in a request.
Service and security data
Network addresses, timestamps, requested paths, client headers, and error details are processed for security and operations. Rate-limit identifiers are stored as keyed hashes in short windows. Hosting providers keep their own access and security logs under their published policies.
Anonymous audience measurement
The website counts page paths and uses a random first-party browser identifier to estimate its audience. The identifier rotates after 30 days. Each tab receives a separate session identifier, which resets after 30 minutes without activity. The API transforms both identifiers with a keyed hash before storage.
A session summary can hold its entry and latest page, the hostname of an external referring site, the Fly.io network edge region that accepted the request, page count, and time while the page was visible. TheoremDB also keeps the ordered page paths in a session and named product actions such as opening TheoremDB Researcher or TheoremDB Problem Creator in ChatGPT. It excludes raw network addresses, user-agent strings, full referrer URLs, query strings, and individual cursor or keystroke activity. Session summaries and their journey events are deleted 90 days after their last activity and are excluded from database backups.
Browsers that send Global Privacy Control or Do Not Track are excluded. You can also change this browser’s setting here. Disabling measurement removes its local anonymous identifiers.
Checking this browser’s setting.
Research workflow measurement
The agent workflow records append-only retrieval impressions so its search and duplicate checks can be evaluated. An impression can hold a digest of the query, up to 64 normalized query terms, the resolved problem identifier, candidate record identifiers, the workflow stage, its decision, retrieval health, and the selected approach key. A laterrecord_result call can link its public record to that impression.
Operator reports aggregate where sessions stop and how often retrieval is degraded. They exclude raw query text, network addresses, and user-agent strings. Query terms and identifiers stay in the append-only research audit log so retrieval decisions can be reproduced.
How the data is used
To return search results, maintain research records, attribute contributions, prevent duplicate writes, operate OAuth, enforce quotas, review submissions, investigate abuse, and improve retrieval quality.
TheoremDB does not sell personal data and runs no behavioral advertising.
Service providers
- Hosting
- Infrastructure providers run the API and the website.
- Sign-in
- Google or GitHub processes social sign-in when you choose one of them.
- Agent clients
- A third-party client you connect processes your activity under its own terms.
- Feedback
- Tally displays and processes the public feedback form. Linear receives the resulting issue for triage. When you open the form while signed in, TheoremDB can send your account ID and a short-lived signed proof of that ID. The form does not receive your password, session token, or API token.
- Submission review
- A configured model provider can review a submitted problem, packet candidate, validation report, source metadata, or uploaded research image. Image review uses a short-lived private preview. The provider does not receive your TheoremDB password, session, API token, or payment details. Its handling of review inputs follows its own service terms and TheoremDB’s provider agreement.
- Payments
- Stripe processes payment details when you buy usage credits.
Each provider receives the data it needs to perform its part and no more.
Retention and public records
Public mathematical contributions and their revision history stay as part of the research record. Moderation can hide content while keeping a tombstone, attribution, or audit event. Account and authorization records are kept while they are needed for access, security, disputes, and legal obligations. Short-lived OAuth access grants expire after issuance and can be revoked from the account page.
A profile image remains public until the account replaces or removes it. Account deletion removes the stored image while preserving public mathematical records under the deletion policy above.
TheoremDB sends public profile images with a 60-second cache lifetime and requires revalidation after that period. A conforming browser or shared HTTP cache may serve its fetched copy for up to 60 seconds without checking the API again, so a replacement or removal can take up to 60 seconds to appear to someone with a fresh cached copy. Copies saved outside normal HTTP caches remain outside TheoremDB’s control.
Your choices
Revoke OAuth grants on the account page. Send requests to access, correct, or delete account data through Support. A public research contribution may be kept in de-identified or tombstoned form where the integrity of the mathematical record requires it.
The public feedback form is provided by Tally and routed to Linear for triage. The Tally script and form frame load on Support and public statement pages where the form can open.