Your script stays yours.

Last updated · 13 October 2026

The short version: when you upload a screenplay, its text is sent — encrypted in transit — to our AI providers to produce your breakdown. If they can't complete it, a local parser in your browser builds the breakdown instead. When you're signed in, your productions, including the script text, are saved to your account so they sync across your devices. We never use your script to train AI models. Your script stays your property, always.

1. Who we are

Lumen is a product of MindMade® (“MindMade”, “we”, “our”). This Privacy Policy explains what personal information we collect when you use lumen.film (the “Service”), how we use it, and the rights you have over it.

2. What we collect

We collect only the minimum needed to operate the Service and stay in touch with you about it:

Waitlist email — when you join the waitlist, we store the email address you provided and the role you selected (director, producer, etc.) so we can send you access invitations and product updates.
Account details — when you create an account, our authentication provider stores the details needed to sign you in (your email address, your name and profile image if you provide them, and a hashed password or the identity from the social sign-in provider you choose). We keep your email, name, profile image, plan, and subscription status in our own database to run your account.
Production data — the productions you create: script text, breakdowns, schedules, budgets, locations, notes, and the cast and crew names and contact details you enter. Lumen keeps a working copy in your browser on each device you use (removed from that device when you sign out, except changes that haven't reached your account yet, which stay until you next sign in there); when you're signed in it is also saved to our database so it syncs to your account, along with the account preferences and IRIS memory notes you save.
Messages you send and replies — when you send call sheets or updates, we record delivery receipts (recipient name, channel, and when the message was sent, viewed, or confirmed), and we store replies recipients send back by SMS or WhatsApp.
Voice — when you start a live call with IRIS, your microphone audio is streamed to our voice provider (see section 5) for the duration of the call.
Usage and diagnostics — product analytics events (pages viewed and interface interactions) and error reports, as described in sections 5 and 6.
Billing information — for paid subscriptions, payment processing is handled by our payment provider. We receive confirmation of payment and a last-four-digits reference; we never receive or store your full card details.
Technical logs — standard server access logs (IP, user agent, timestamps) kept for 30 days for security and abuse prevention.

3. How we handle your script

When you upload or paste a screenplay, its text is extracted in your browser. If in-browser PDF extraction fails, the PDF file is uploaded to our server so the text can be extracted there; the file is not stored.

The extracted script text is then sent to our server and forwarded to a third-party AI provider to produce the deep breakdown — scenes, characters, elements, and the derived schedule. We use xAI (“Grok”) first; if it is unavailable, the same request goes to Groq or Google (Gemini) instead. If none of them can complete the analysis, a local parser in your browser builds a simpler breakdown instead. Rebuilding a schedule and chatting with IRIS send the relevant production details (such as scenes, cast, locations, and the schedule) to the same providers. A live voice call with IRIS sends your microphone audio, a compact summary of the production, and the details IRIS looks up during the call to OpenAI.

Script text is encrypted in transit (TLS). We send it to these providers only to return the result you asked for; they handle it under their own API terms, which may include keeping it for a limited period, for example for abuse monitoring. We do not use your script to train any model — ours or anyone else's. We do not keep analytics on the content of what you upload, and the screenplay remains your intellectual property at all times.

When you're signed in, your production — including the script text and everything derived from it — is saved to our database so it syncs to your account. If you use Lumen without signing in, it stays in your browser's storage on that device. Documents you generate (such as call-sheet PDFs) are kept in your browser on that device and are cleared when you sign out, so download any versions you want to keep.

4. How we use what we collect

To invite you from the waitlist and send product announcements.
To operate your account, authenticate you, and remember your preferences (including your light/dark theme choice).
To fulfil billing, provide receipts, and manage your subscription.
To understand how the product is used and to find and fix errors (product analytics and error monitoring).
To investigate abuse, bugs, and security incidents.
To comply with applicable law.

We do not sell your data. We do not share it with advertisers. We do not use it to build advertising profiles.

5. Third-party services

Lumen uses these third-party services to run:

Vercel — hosting and delivery of the web app, and Vercel Web Analytics for aggregate, cookie-free page-view statistics.
xAI (Grok) — our primary AI provider. It receives screenplay text to generate breakdowns, and production details when you rebuild a schedule or chat with IRIS.
Groq and Google (Gemini API) — fallback AI providers. When xAI is unavailable they receive the same content, for the same purpose.
OpenAI — live voice calls with IRIS. It receives your microphone audio, a compact summary of the production, and the production details IRIS looks up during the call.
Neon — Postgres database for product-update sign-ups, account records, saved IRIS memory, message receipts and replies, and cloud production sync, including script text.
Clerk — authentication provider.
Stripe — payment processing for paid subscriptions. Stripe collects and processes your card details directly; we receive only confirmation of payment and a last-four-digits reference, never your full card number.
Resend — email delivery: transactional emails and the call sheets, calendar invites, or updates you explicitly send by email.
ClickSend — delivery of SMS messages that you choose to send to your cast and crew from within Lumen, and of their replies.
Meta WhatsApp Business Platform — delivery of WhatsApp messages that you choose to send to your cast and crew from within Lumen, and of their replies, when WhatsApp is enabled.
Telnyx — phone numbers, calls, and text messages for the Producer phone feature, only when it is enabled for your account. Calls on that line, and replies drafted to texts on it, also use OpenAI.
PostHog (EU hosting) — product analytics: pages viewed and interface interactions, linked to a random identifier stored in your browser (see section 6).
Sentry (EU hosting) — error monitoring. Error reports include your IP address, browser and device details, and request information. For some errors, Sentry also captures a replay of the page leading up to the error, with on-screen text and form inputs masked.
Open-Meteo — weather forecasts on call sheets. It receives the shoot location's name or coordinates only.
Google Fonts — the site's typefaces are loaded from Google's font servers, which receive your IP address and browser details.

Each of these is used only for the purpose listed, and each has its own privacy practices. Script content goes only to our database (Neon) and to the AI providers above (xAI, Groq, Google, and, for live voice, OpenAI), as described in section 3 — plus whatever production details you choose to include in documents and messages you send.

When you use Lumen to send messages — call sheets, schedules, or updates — to your cast and crew, the recipient contact details you enter (names, email addresses, phone numbers) are shared with the relevant delivery provider above for the sole purpose of delivering the specific messages you send. You are responsible for ensuring you have a lawful basis to contact those recipients. We do not use your cast and crew contact details for our own marketing.

6. Cookies and local storage

We use cookies and browser storage for session authentication, to remember preferences such as your theme choice, and to keep your productions and generated documents on your device. Our product analytics (PostHog) also sets a first-party cookie and a local-storage entry holding a random identifier, so it can count visits and sessions. We do not use advertising pixels, advertising cookies, or cross-site profiling.

7. Data retention

Script text and production data: when you're signed in, stored in our database for as long as the production exists in your account; deleting a production removes it, including its script text, from our database. Without an account, kept in your browser on that device until you delete it or clear your browser data.
Generated documents: kept in your browser on that device and cleared when you sign out.
AI providers: script text and production details are sent per request; any retention on their side is governed by their API terms, as described in section 3.
Message delivery receipts and replies: stored in our database until you ask us to delete them.
Waitlist emails: until you ask us to remove them or the waitlist is retired.
Account data: for the lifetime of the account, plus 30 days after deletion for backup rotation.
Server access logs: 30 days.
Billing records: seven years, or as required by applicable tax law.

8. Your rights

Depending on where you live, you may have the right to access, correct, or delete your personal data; to object to or restrict its processing; to data portability; and to lodge a complaint with a supervisory authority. To exercise any of these rights, email us at the address below and we will respond within 30 days.

9. Security

We use TLS in transit, encryption at rest for database contents, and principle-of-least-privilege access for staff. No system is perfect — if we learn of a material security incident affecting your personal data, we will notify you without undue delay.

10. Changes to this policy

We'll update the “last updated” date at the top of this page whenever we revise the policy, and we'll highlight material changes in-app before they take effect.

11. Contact

Questions, requests, or complaints: write to privacy@mindmade.co.