Screenplay Advisor Privacy Policy

Effective date: May 30, 2026

This Privacy Policy explains how Screenplay Advisor handles data in the mobile app, the Studio web app at /studio, the restricted Admin site at /admin, and related websites. In this policy, "we," "us," and "our" refer to the app and website provider.

1. Summary

The Screenplay Advisor mobile app sends screenplay production analysis requests directly to a third-party cloud AI service for cloud processing. The mobile app does not include an on-device LLM model, does not require an account, does not include advertising, and does not include analytics tracking. We do not receive your prompts, model responses, or completed analyses through the mobile app.

Studio is an account-based web service. If you use Studio, we may collect and store account, authentication, prompt, package, saved-use-case, feature-usage, credit, support, and security records as described below.

Studio users can create account-free shared package links. A shared link displays a snapshot of the selected package to anyone who has the URL, whether or not that viewer has a Screenplay Advisor account.

The Admin site is a restricted operational tool. Authorized administrators can view and manage user accounts, Studio usage metadata, credit requests, policy memory rules, LLM token and cost metrics, and audit logs. Routine Admin usage reports show operational metadata and do not expose package prompt text or generated-output details. Admin actions, notes, reasons, and policy-rule changes may be stored for account integrity, safety, and operational review.

We do not sell personal information and we do not use Studio or Admin records for third-party advertising.

2. Information processed by the app

The app may process scene briefs, character descriptions, settings, dialogue constraints, director-style preferences, storyboard requests, or other text you type into the app; model responses generated by the cloud AI service; and basic app state needed to display the current package.

This information is used to provide the app's core function: generating screenplay production packages through the ScriptCraft / Cinematic Matrix framework.

3. Information collected by us through the app

We do not intentionally collect personal information through the app. The app does not require registration, login, email entry, payment entry, contacts access, location access, camera access, microphone access, SMS access, call log access, or advertising identifiers for its core operation.

The app does not transmit your prompts or analysis results to our servers. Prompts are sent directly from the app to a third-party cloud AI service and are governed by that provider's applicable terms and privacy policies.

4. Information collected through Studio

If you use Studio or account features on the Screenplay Advisor website, we may collect and store:

• Account information, such as email address, display name, role, account status, created and updated timestamps, and password hashes.
• Authentication and security records, such as session token hashes, session timestamps, password reset token hashes, pending signup token hashes, WebAuthn/passkey credential IDs, public keys, sign counters, authenticator metadata, passkey names, challenge records, CSRF tokens, cookies, browser/device information, IP address, request metadata, and server logs.
• Package content, such as the scene brief, prompt, character or setting description, Studio context fields, displayed brief, generated response, classification, rubric metadata, source type, created timestamp, and related model usage metadata such as runtime, model, token counts, latency, and estimated direct model cost when available.
• Saved scripts, including the saved name, brief text, generated response, Studio context, and created or updated timestamps.
• Shared package records, including a share token, the shared name, brief text, generated response, classification, package description, created and updated timestamps, and revocation status.
• Feature usage records for custom packages, Continuity Notes, and Rewrite Pass, including the submitted brief, completed package or report used for the feature, generated output, credit cost, source type, and related history entry.
• Credit account records, including current balance, ledger entries, credit debits and adjustments, request amounts, user notes, admin notes, decision status, decision timestamps, and related admin or history references.
• Local browser data, such as the current conversation saved in local storage, the Studio history collapsed or expanded setting, service worker cache data, and first-party cookies used for sessions and package history.

Do not enter confidential, regulated, or sensitive personal information into Studio unless you are authorized to use it and comfortable with it being processed and stored for the service.

5. Shared package links

If you create a shared package link in Studio, the shared page may include user-submitted brief text, Studio context, saved-package names, generated package text, classifications, scores, and other output included in the snapshot. The link is intended for read-only viewing, but anyone with the URL can view, copy, screenshot, print, download, or further distribute what they can see.

Shared package links are not intended to be indexed by search engines, and shared pages are served with no-store caching headers, but we cannot guarantee that recipients, browsers, search engines, network intermediaries, or other third parties will not retain copies or records. If you revoke a shared link, the old URL should stop opening the shared page through our service, but revocation does not delete copies already made by viewers.

Viewing a shared package without logging in may still create ordinary server logs, such as IP address, user agent, request path, referring page, timestamp, and security metadata. Do not create shared links for packages containing confidential, regulated, sensitive personal, or third-party information unless you are authorized to share that information with anyone who receives the URL.

6. Information collected through Admin

The Admin site is available only to authorized admin and super-admin accounts. It may display Studio account, usage, credit, project-rule, audit, director-style, and LLM usage metadata so administrators can operate the service. This includes feature type, timestamps, credit activity, token counts, model, latency, estimated direct model cost, and aggregate per-user totals. The Admin dashboard is designed not to show prompt text, saved-script text, generated package responses, or raw package JSON in routine usage and cost reporting.

Admin actions may create or update records such as credit adjustments, credit request decisions, user disable or enable reasons, role changes, session-clearing events, project rules, trigger terms, guidance text, director-style status, admin notes, audit metadata, and timestamps. These records may identify the administrator who performed the action and the account or object affected.

7. How we use information

We use the information described in this policy to provide packages and Studio features; authenticate users; save and retrieve package history and saved scripts; create, display, refresh, and revoke shared package links; operate credit balances, credit requests, and usage ledgers; distinguish custom packages from Continuity Notes and Rewrite Pass usage; apply project rules; administer accounts; protect the service; investigate abuse or errors; measure model usage and cost; respond to support or privacy requests; comply with legal obligations; and improve reliability and product quality.

8. Third-party services

The mobile app communicates directly with a third-party cloud AI service to generate responses. Studio and related web features may send prompts, Studio context, completed package reports, policy-rule guidance, and generated outputs to a third-party cloud AI service for processing. The provider may process that information under its own terms and privacy policy.

If you install the mobile app through Google Play, Google Play may process information needed to provide installation, updates, app integrity, crash reporting, purchase infrastructure, and device compatibility. Those activities are controlled by Google and are governed by Google's terms and privacy policy.

9. Cookies, local storage, and deletion

Your current prompt and response may be kept in memory while the app is running so the app can display the analysis. The app does not store an on-device LLM model.

You can clear the current analysis by using the app's reset or "Try another case?" control. You can remove locally stored app data by using your device's app storage controls or by uninstalling the app.

Studio uses first-party cookies for authentication sessions and package history, and it uses local storage to keep the current conversation and interface preferences on your device. Logout attempts to clear cookies, storage, and cache where supported by the browser. You can also clear browser storage through your browser settings.

You can delete saved scripts in Studio and revoke shared package links. Other account, package history, shared-package audit records, credit, admin audit, and security records may be retained while your account is active and as needed for service operation, security, accounting, dispute resolution, legal compliance, and abuse prevention. To request access, correction, deletion, or other privacy help, use the contact method below.

10. Voluntary contact

If you contact us for support, legal, or privacy questions, we may use the information you voluntarily provide, such as your name, email address, device details, screenshots, or message content, to respond to your request, troubleshoot issues, improve the app, protect users, or comply with legal obligations.

We do not sell personal information.

11. Security

We use technical and organizational measures intended to protect the information we keep, including password hashing, session token hashing, CSRF protections, restricted Admin access, and audit logging. No method of transmission or storage is completely secure.

The app and Studio use cloud processing, so you should avoid entering information that you are not authorized to use or that would create unacceptable risk if sent to a cloud AI service, stored in your account, included in restricted support or admin workflows, or viewed on your device.

12. Children

The app is intended for users who can evaluate creative and production outputs responsibly. It is not directed to children under 13, and we do not knowingly collect personal information from children through the app.

13. International users

If you contact us or use related websites, information you voluntarily provide may be processed in the United States or other countries where we or our service providers operate.

14. Changes to this policy

We may update this Privacy Policy from time to time. The effective date above indicates when this version became effective. Continued use of the app after an update means you acknowledge the updated policy.

15. Contact

For privacy inquiries, use the developer contact mechanism listed in the Google Play Store listing for Screenplay Advisor or the contact mechanism available through the Screenplay Advisor website.