Legal
Privacy Policy
Last updated 19 August 2026
You are handing us an unproduced screenplay. We know exactly what that is worth, and this page is a plain account of what happens to it. ScriptSift is operated by GCC Grow, LLC.
The short version. Your screenplay is stored privately, is never published or shared with other users, is never used to train AI models, and is never written into our logs. Scene text is sent to Anthropic to perform the analysis and is not retained by them for training. Delete a project and the file and its text are deleted with it.
What we collect
- Account details: your name, email address, and a securely hashed password. We never store your password in readable form.
- Your screenplay: the file you upload, the text extracted from it, the scenes we detect, and the breakdown elements produced from them.
- Project details: titles and notes you type.
- Processing records: which model ran, when, how many tokens it used, and whether it succeeded. These records never contain your screenplay text.
- Payment records: a ledger of credits bought and spent, plus the Stripe identifiers for each purchase. We never receive or store your card number.
Who else touches your screenplay
Only these, and only to make the product work:
- Anthropic — receives the text of each scene to identify production elements. Anthropic does not use data submitted through its API to train its models.
- Neon — hosts the database holding your account, scenes, and breakdown.
- Vercel — hosts the application and stores your uploaded file in private storage.
- Stripe — processes payments and handles card data. We do not see it.
We do not sell your data, and we do not share it with advertisers or data brokers.
How your screenplay is protected
- Private storage. Uploaded files are stored with private access. There is no public URL for your screenplay — anyone requesting the file without authorisation is refused.
- Database isolation. Every table holding your content is protected by row-level security enforced by the database itself, using a connection role that cannot override it. One account cannot read another account's screenplays even if the application has a bug.
- No screenplay text in logs. Error messages are stripped before being recorded, and processing records store only metadata. This is deliberate: logs are the easiest place for confidential text to leak, so script content never enters them.
- No analytics on your content. Screenplay text is never included in any analytics or error-reporting payload.
How long we keep it
- Your screenplay, scenes, and breakdown are kept until you delete the project or your account. Deleting a project deletes the stored file along with its scenes and elements.
- Payment ledger entries are kept after a project is deleted. They record that a purchase happened, never what the screenplay was — we are required to keep accurate financial records.
Your choices
- Delete anything, any time. Deleting a project removes its file and all its content.
- Get a copy. Your breakdown exports to Excel whenever you want it.
- Close your account. Email us and we will delete your account and its content.
- Depending on where you live, you may have additional rights to access, correct, or delete your personal data. Email us and we will honour them.
Cookies
We use a single signed cookie to keep you logged in. There are no advertising cookies and no third-party trackers.
Children
ScriptSift is not intended for anyone under 18 and we do not knowingly collect their data.
Changes
If we change how we handle your data in a way that matters, we will tell you before it takes effect — not quietly edit this page.
Contact
Privacy questions, data requests, deletion: jason@nyonic.com