Your script is never attached to who you are.
Writers are careful about who reads an unfinished script. Only the systems needed to produce your report process your screenplay, none of it is kept for training, and the script is deleted as soon as the analysis has run. Here is what happens to your pages, in plain terms and technical ones.
Anonymous sessions
There is no account to create. You upload, get your report and leave. The only link between you and your script is a random token in your browser.
- A session token
- A cookie in your browser
- Tied to: Your upload, your report and any credits. Never a name or an email address.
- Your script and report
- Our datastore, for a limited time
- Tied to: The session token, and nothing else.
- Payment details
- Lemon Squeezy, the merchant of record
- Tied to: Your purchase. They are never connected to your script.
Technical detail: Sessions are random tokens made with nanoid, and the service keeps no user records to attach them to. Payment, tax and anti-fraud records stay with the payment provider for as long as the law requires; see the privacy notice.
Encrypted in transit and at rest
- A PDF
- Converted to text in your browser. The PDF file itself never leaves your computer.
- Technical: Parsed client-side; only the extracted screenplay text is uploaded.
- On the way to us
- Sent over an encrypted connection, the same standard your bank uses.
- Technical: HTTPS (TLS).
- While it waits
- Encrypted before it is stored, so a look inside the database shows nothing readable.
- Technical: AES-256-GCM. Keys live in the server environment, never in code or logs.
- During the analysis
- Decrypted and sent to the analysis model, which reads it to write your report.
- Technical: Sent over TLS to the model provider through OpenRouter, in several requests for a long script.
Your writing never trains an AI
Your pages go to the analysis model to produce your report, and to nothing else.
The request can only go to a model provider that neither trains on it nor keeps it. Nothing from your script is kept to train or fine-tune a model, ours or anyone else's, so nothing you upload can surface in someone else's results.
Technical detail: Every analysis request sets OpenRouter's provider routing to data_collection: deny and zdr: true, so it can only reach an endpoint that does not train on prompts or retain them. If no such endpoint is available, the analysis fails instead of going elsewhere.
It deletes itself
Your script is deleted as soon as the analysis has run, or after an hour if it doesn't run. The report is deleted 24 hours after it is made. The datastore expires the data itself, whether or not you come back.
- When you uploadYour script is stored, encrypted, while you choose instruments and pay. If the analysis doesn’t run, it is deleted after an hour.
- When the analysis has runYour script is deleted. The report is stored, along with the analysis it was built from.
- 24 hours after the report is madeThe report is deleted. You can delete it sooner from the report page, and it goes at once.
Technical detail: Every stored key carries an expiry the datastore enforces. An uploaded script has one hour, restarted when you go to checkout and again when payment is confirmed, and it is deleted as soon as the report is stored. A report and the analysis behind it have 24 hours from when the report is written.