Security and data privacy

This page only describes what the app and its infrastructure actually do today. It is a status summary, not a promise.

In short

• Your script is not used to train models. ProductionEngine does not train models on customer content.
• AI is optional. If you don't add your own key, or you turn AI off, your content never goes to an AI provider.
• Data in the EU. The database and files live in Supabase's European Union region (Ireland).
• Access enforced in the database. A project's data is visible only to that project's members, and only as far as their role allows.

Hosting

The app runs on Vercel. The database, authentication and uploaded files are hosted on Supabase in the European Union region (Ireland, eu-west-1). Project files sit in a storage bucket that is not public and is opened only to project members.

Encryption in transit

Every connection to the site and the app is encrypted with HTTPS. The server sends an HSTS header (including subdomains, two years), so browsers never fall back to an unencrypted connection. A content security policy (CSP) limits what a page can load, and our pages cannot be framed inside other sites.

Who can access what

• Project roles: every member is an admin, an editor or a viewer. Admins manage the team and roles; viewers can only read.
• Access profiles: an admin can limit a member module by module (for example, no budget at all), and narrow the budget to sections and the breakdown to departments.
• Enforced in the database: these rules are not only in the interface; they are applied in the database with Postgres row level security (RLS) policies. Someone who is not a member of a project cannot read its data.
• Sign-in: authentication is handled by Supabase Auth; you sign in with a link or a one-time code sent to your email address.
• Secrets: secrets such as AI keys are stored encrypted, in tables that cannot be read from the browser at all.

Share links

Call sheet, sides, document and visual plan links exist so that crew without an account can open them too. That is why it matters how they work:

• Signed: links are signed by our server; nobody else can create a fake call sheet link in ProductionEngine's name.
• Personal links: recipient-specific links expire after 30 days. Attachments, the personal call time and the viewed/confirmed record only open on these links.
• One-click revoke: a project admin can invalidate every personal link already sent, instantly, with the Revoke personal share links button in team settings. Later sends create new links.
• General copy links: a link that is not personal, the kind you copy and share yourself, carries its content in the address itself and cannot be revoked. Send sensitive information with personal links.

AI: your key, your call

• Your own key: AI features run on your own API key from an Anthropic (Claude), OpenAI or Google Gemini account. The key is tied to your account, stored encrypted with AES-256-GCM on the server and never sent back to the browser. Requests are billed directly to your provider account; we have no credits or coins.
• When content is sent: only when you start an AI action: AI breakdown, enriching the breakdown, reviewing the schedule with AI, asking the script a question, asking the AI in the assistant, and the AI budget estimate. No AI action runs on its own in the background.
• What is sent: the content that action needs; for example the script text or the relevant part of it for a breakdown, the scene list and shooting plan for a schedule review. The request goes from our server, with your key, directly to the provider you chose.
• Works without a key: if you don't add a key, or you turn AI off in account settings, the breakdown and the automatic schedule run in the rule-based mechanical mode and no content is sent to any AI provider. Text recognition for scanned PDFs also runs in your own browser.

Model training

ProductionEngine does not use your script, your breakdown or any other project content to train models, and does not hand it to anyone as training data.

How a request is handled once it reaches a provider is governed by that provider's API terms. As of October 2026, according to their own documents, Anthropic and OpenAI do not use API content for model training by default; Google states that it may use content sent on the Gemini API's unpaid tier to improve its products, and does not on the paid tier. For a confidential project, use a key from a paid account and check the terms yourself.

Exporting and deleting your data

• Export: you can download the script as FDX (.fdx) and Fountain; reports (breakdown summary, element list, DOOD, schedule), the shot list, contacts and tasks as Excel (.xlsx); the budget as Excel (.xlsx) and JSON; the calendar as .ics; and call sheets, sides and the daily production report as PDF. Selected shooting days also download as one ZIP set package that opens without internet.
• Full copy: to request a copy of all your data, write to info@productionengine.app.
• Account deletion: you can delete your account yourself in the app's account settings; what is deleted right away and what stays is listed step by step in the privacy policy.
• Backups: nightly database backups are taken and kept for up to 30 days; deleted data drops out of the backups at the end of that period.

GDPR, KVKK and certifications

Which personal data we process and why is set out in the privacy policy; the service terms are in the terms of use.

Services we use to process data: Supabase (database, sign-in, files; EU), Vercel (hosting the app), Resend (sign-in, invitation and call sheet emails), Apple and Google notification services (push notifications), Open-Meteo and OpenStreetMap Nominatim (weather and maps; only an address or city is sent), and, only if you turn it on with your own key, the AI provider you choose.

A KVKK (Turkish data protection) notice and a data processing agreement (DPA) for business customers are being prepared; if you need them, write to info@productionengine.app.

We do not hold a certification such as SOC 2 or ISO 27001. Our infrastructure providers' certifications cover their services, not ProductionEngine.

Reporting a vulnerability

If you think you have found a vulnerability, write to info@productionengine.app. Please give us time to fix it before making details public.