Your screenplay is an asset
You worked too hard on the screenplay to toss it into a mystery box. Here is the plain-English version of what happens to your pages: where records live, who can access them, when an AI provider processes them, and how deletion works.
New accounts receive 1 free credit—enough for one Quick Analysis.
Screenplay content and analysis records are stored in the application database and associated with your user ID. Supabase authentication identifies you, and row-level security policies are intended to restrict screenplay and analysis access to the owning user. Authorized system and support operations use separate server-side credentials when required.
When you run a report, server-side application code sends the screenplay and report instructions to the language-model provider configured for that analysis type. Provider handling is also governed by that provider’s current API terms and data policies.
The deletion flow checks both the screenplay ID and your user ID before removing the selected screenplay record. Full-account deletion is not currently self-service; contact support and an administrator will handle the request.
AI Script Coverage Pro runs on enterprise-level cloud and database infrastructure built for secure, reliable applications. The “bank-level security” promise is supported by authenticated account access, row-level database controls, server-side credentials, and ownership checks that help keep each writer’s screenplay records tied to the correct account.
Yes. Screenplay and analysis records are stored so authenticated users can access them from the dashboard.
The database uses user ownership checks and row-level security policies intended to restrict records to their owner. Administrative server operations may use privileged credentials for authorized support or system tasks.
Yes. The screenplay deletion logic verifies ownership and deletes the selected screenplay record. Full-account deletion currently requires administrator assistance.
Yes, when an analysis is requested, the screenplay content is sent server-side to the configured language-model provider to generate that report.