Privacy
Prereasoner analyzes the spreadsheet data and questions you submit so it can compute an answer and show the steps used to reach it. The reference service at chat.prereasoner.com is operated by MailRecipe LLC.
What we process
- Files and Google Sheets you choose, including table names, columns, and cell values.
- Your questions, conversation history, generated SQL, results, and reasoning traces.
- Account and session identifiers supplied through Google and Firebase Authentication.
- Operational data needed to secure, debug, and operate the service.
How answers are produced
The core engine builds and executes inspectable SQL against your data. It uses a frozen model as an encoder for intent and schema signals; that model does not decode SQL or invent the numerical answer.
Assistant processing. The hosted assistant currently uses Anthropic. Assistant requests can include your messages, conversation history, attached table contents, table and column names, generated SQL, limited query results, and trimmed tool output. This processing is used to present results, handle ambiguity, orchestrate tools, and fill reference cells you explicitly request.
Anthropic receives those requests through the service's API account. Its handling is governed by the operator's agreement and is also described in the Anthropic Privacy Policy and Privacy Center. Prereasoner is working toward operating this assistant layer locally once a local model meets the required quality, latency, security, and cost standards. The calculation and verification path remains deterministic.
Service providers
- Google Cloud and Firebase: hosting, authentication, databases, and reasoning-trace delivery. See Firebase privacy and security.
- Anthropic: language processing for the hosted assistant features described above.
Why we process data
We process this data to provide the analysis you request, maintain your account and saved work, secure and debug the service, and meet legal obligations. Depending on the law that applies, the bases are performance of the service contract, legitimate interests in operating and protecting the service, and compliance with legal obligations. We do not treat a protocol field or a popup click as blanket permission for unrelated uses.
Sharing and international processing
We do not sell customer spreadsheet data or use it for targeted advertising. We share data with the providers above only to operate the service, and may disclose information when required by law or needed to protect the service and its users. Those providers can process data in the United States and other locations where they operate. We use the applicable contractual safeguards when data-protection law requires them.
Storage and retention
Uploaded tables are stored in a conversation-scoped PostgreSQL schema. Conversation state and named workbook revisions are stored in application tables with verified user ownership. Conversations expire after 90 days without activity by default. The service also limits each account to 100 stored conversations, 256 MiB of serialized source and workbook state, and 1 MiB per saved snapshot. Reasoning traces stored in Firebase Realtime Database expire after seven days by default. A daily retention job applies both policies.
Operational logs contain operation names, sizes, and error classes. They do not contain raw request bodies, questions, conversation history, generated SQL, credentials, spreadsheet rows, or full error messages.
Deletion
Deleting a conversation removes its owned PostgreSQL data and the reasoning traces indexed to that conversation. The delete-all action removes every conversation owned by the signed-in user and the user's complete reasoning-trace subtree. Deleting only the Firebase identity does not currently erase every PostgreSQL or trace record. For complete account-linked deletion, email mani.doraisamy@gmail.com.
Training and public data
Customer spreadsheet rows are not included in Prereasoner's released training corpora. Public reference facts come from documented sources such as Wikidata and publisher datasets, under their respective terms.
Your choices and rights
You can delete conversations in the product and request access, correction, export, restriction, objection, or deletion where applicable by emailing the address below. Do not upload regulated health, payment-card, or similarly sensitive data unless your deployment has a specific agreement and controls for it.
Children
The reference service is not directed to children under 18. Contact us if you believe a child has submitted personal data so we can investigate and remove it where appropriate.
Contact
MailRecipe LLC
340 S Lemon Ave #9974, Walnut, CA 91789, United States
Privacy and data-rights requests: mani.doraisamy@gmail.com.
Security reports: see the security policy.