Privacy Policy
Privacy Policy
Draft for review — not yet the final policy our counsel will review before public launch.
Your script is read in memory for a single analysis and deleted the moment that read finishes. We never store the raw pages, and we never use them to train anything. If you create an account, the generated read can sync to that account.
Your script and material.
When you upload a file, your material is held in memory only for the length of one read. It is not written to a database, saved to disk, or kept in our logs — those logs record only metadata (which endpoint, status, timing), never your pages. Uploaded files are used only to extract text for that one read; when the read finishes, or fails, the material and the file are discarded.
The AI that performs the read.
To produce your read, we send your material to a third-party AI provider, which processes it and returns the analysis. We send it only to run the read, retain nothing afterward, and never use your work to train any model. The specific provider will be named in the final policy.
What we keep.
We keep our read of your work — not your work itself. In the platform preview, a few things may be stored so they can sync across sign-ins: your generated reads, notes, and verdicts; your project titles and account email; and a billing reference (your pass history and Stripe customer).
A read may include short excerpts or references that the read itself shows you, but we do not store the submitted script, treatment, uploaded file, or extracted source text as a separate asset.
Access and accounts.
The platform preview uses Firebase Authentication for individual accounts, including email/password and Google sign-in. We use Stripe for payment and credit purchases. We store only the account and billing metadata needed to provide the service.
Cookies and local storage.
We use Firebase sign-in state and browser storage to keep the app working across reloads. We use Google Analytics only for sanitized product events such as sign-in method, checkout status, read started/completed, and broad material type. We do not send your email, project title, filename, logline, notes, or submitted material to analytics.
What we don't do.
- We don't sell or rent your material or your reads, and we don't share them with anyone except the providers needed to run the service: the AI provider that performs your read, Firebase for authentication/data storage, Stripe for payments, and sanitized analytics.
- We don't use your script — or anyone's — to train models.
- We don't keep a library of submitted scripts on a server.
Your choices.
You can delete synced projects and reads in the app, and you can clear local browser storage for device-only history. Because we don't retain your pages, there's no separate raw script file on our side to delete. For any privacy question, reach us at the address below.
Changes and contact.
We'll update this policy as the product grows — notably when accounts and stored reads arrive — and we'll note the date at the top. Questions about privacy or your material: team@thereadbefore.com.