Where your productions live

Application data lives in a managed Postgres database on Supabase in the EU (eu-west-1, Ireland). Uploaded media lives in Supabase Storage in the same region. The application itself runs on Vercel.

Every production-scoped table is protected by Postgres row-level security: a signed-in user can only read or write rows for productions they own, are a member of, or are linked crew on. The user directory is scoped the same way: you can only see people you share a production with. Public call-sheet pages authenticate by unguessable token, are scoped to a single day or crew member, and are revocable at any time.

TLS everywhere in transit (HSTS enabled). Storage and database encrypted at rest by the platform. Bring-your-own AI keys are encrypted with AES-256-GCM before they touch the database and are only ever decrypted server-side; they are never sent to the browser. Card details never touch our servers: payment runs entirely on Stripe.

Passwords are handled by Supabase Auth (bcrypt), with self-serve reset. Deleting your account removes your profile, your uploaded files and every production only you own; shared productions transfer to a remaining member so a team never loses work.

Shot lists export to CSV and calendars to ICS today; a full per-production export bundle is on the near-term roadmap. If the service were ever discontinued, accounts would get a minimum 60-day window and help exporting.

Email ben@producedbyben.co.uk with details. You'll get a response within two business days, and a fix or mitigation plan before any public disclosure.