Privacy
ScriptFix handles screenplay text only long enough to preview or render the output for the current request, unless you keep a draft locally in your own browser through autosave or the save shortcut.
No accounts, no analytics, and no server-side storage for screenplay drafts. A short-lived download cookie may be set only so the browser can re-enable export buttons after a file starts downloading. Basic infrastructure services may still record request metadata needed to keep the app online and observable.
Policy Details
The points below cover the screenplay content you paste or upload, plus the small amount of infrastructure metadata needed to operate the service.
Your screenplay text is processed in memory on the server long enough to extract elements and render the PDF. Nothing is written to disk. When the request returns, the text is released. ScriptFix keeps no copy of the draft, the rendered PDF, the filename, or any metadata about it.
The editor can autosave the current draft in your browser storage on that device, and Cmd/Ctrl+S refreshes that local copy too. Those local copies never go to the server. The latest saved draft restores automatically when you reopen the formatter on the same device.
The hosting provider (Vercel) may record the timestamp, IP address, and path of each HTTP request for infrastructure operations. ScriptFix does not add application logs that include screenplay content.
If an exception occurs, an error report may be sent to a monitoring service (Sentry) with the stack trace and request path. Screenplay text is never attached to error reports.
ScriptFix does not send screenplay text to AI models, LLM APIs, or training pipelines. Formatting and export logic run inside this app only.
No tracking cookies, analytics pixels, or ad tech. When an export starts, ScriptFix may set a short-lived download_ready cookie so the page can stop showing its loading state. It expires quickly and is not used to identify you.