Privacy Policy

Zero Page (“the Studio”) is an AI pre-production studio: it turns ideas, scripts and reference photography into scene prompts, keyframes and AI-generated video. It is operated by Michael Massaad, trading as Zero Page Films, from the United States. Anyone can sign up; a new workspace starts with a small one-time grant of trial credits, and everything beyond that is paid for through the plans on the pricing page.

Signing in uses Supabase Auth, either by email and password or through Google or Discord. Zero Page never sees or stores your password with those providers. When you sign in with Google or Discord, the Studio receives only your basic profile: your email address, display name and profile picture. They are used to create and identify your account and for nothing else. Zero Page's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

A session is kept in a single signed, HTTP-only cookie on your device, valid for 30 days; signing out clears it. One further cookie remembers which workspace you had open, and your browser's own storage keeps an unsent draft so it survives a reload. Zero Page sets no advertising or tracking cookies and loads no analytics scripts.

• Account — email address, display name, profile picture, an account identifier, and which workspaces you belong to.
• Production material — the photos, reference images, audio and video you upload; the characters, props and places you add; and the ideas, scene prompts, keyframes, rendered clips and cuts produced from them. A web link you paste into the Guide is fetched once, by the Studio, to read that page's own preview image.
• Billing — your plan, your credit balance and a ledger of what each render and still cost. Card details are entered on Stripe's pages and held by Stripe; the Studio stores a Stripe customer identifier and the email on it, never a card number.
• Connected model accounts — optionally, your own ChatGPT or Claude sign-in, if you connect one to write with. The signed-in session those providers issue is kept on the Studio's server, scoped to your account, used only when you ask that model to work, and removed when you press Disconnect.
• Chat app connections — if you connect a chat app to the Studio, the name that app gave, the site it sent you back to, when you allowed it and when it was last used. See “Connecting a chat app” below.
• Usage — basic operational data (timestamps, error logs, model-call counts and their cost) used to keep the pipeline running, meter spend and grade output quality.

The Studio relies on a small set of providers to function, each under its own privacy policy:

• Supabase — authentication and database storage. The sign-in step may be served under a zeropage.studio address or a supabase.co one; both are this project.
• Google (Gemini API) — writing and judging scenes, describing the photos you upload, and drawing keyframes and reference sheets from them.
• fal.ai — video rendering. When you approve a render, the shot's prompt and its reference images are sent to fal.ai, which runs the model you picked (from Kling, ByteDance, Lightricks, Alibaba or Google). When you index footage in the editor, a clip's speech is transcribed there too.
• Serper — the web image search behind the Guide's reference suggestions. It receives the search text only, never your material.
• Stripe — payments and subscriptions.
• Cloudflare R2 — storage for reference images and rendered media.
• OpenAI and Anthropic — only if you connect your own ChatGPT or Claude account to write with, and only for the work you send to it; or if you connect their chat app to the Studio, in which case they receive what the connector answers (see “Connecting a chat app”).
• Vercel and Fly.io — application hosting.

The Studio's research scout also reads public feeds and the operator's own connected Instagram, Pinterest and YouTube accounts for visual reference. It never reads a member's social accounts: the Studio asks for no access to them. None of the providers above receive more than what is needed to perform their function, and Zero Page does not authorize any of them to use Studio data for advertising.

The Studio has a connector: an address you can give to a chat app such as Claude or ChatGPT so that it can work in your workspace. Nothing is connected until you add that address in the chat app yourself, sign in to the Studio, and press Allow on a page that names the app that is asking. The chat app is then issued an access token by Supabase Auth. The Studio checks that token on every request and does not keep it, and it never sees the password of your chat account.

What the chat app can do. While it is connected it can read your projects (their briefs and looks, their scenes, the reference photos those scenes used, and the conversation saved with a project), your elements and their photos, your scenes with the stills and clips made for them, and your credit balance when it asks a price. It can start a project, add a picture as an element, and save a scene it wrote. On the address that renders, it can also draw a still, draw a scene's keyframes or render a scene, which spend credits. The connector gives the chat app a price for each and instructs it to show you that price and wait for your answer; the Studio cannot see whether it did. It reaches your own workspace and no one else's.

What leaves the Studio. Whatever the connector answers is sent to the chat app, and so to the company that runs it: Anthropic for Claude, OpenAI for ChatGPT. That includes text from your projects and scenes, and links to your images and clips. From there it is handled under that company's privacy policy, not this one. Connect a chat app only if you are content for it to see that material.

What the Studio receives. Only what the chat app hands to a tool: a project's name, brief and look; a scene's text and the photos chosen for it; an element's name and notes; and the web address of a picture you asked it to keep. The connector has no tool that takes the conversation itself. A picture added by its address is fetched once by the Studio from that address, stored with your elements, and described by the Gemini API like any photo you upload.

What is recorded. That a connection was allowed: the name the app gave, the site it sent you back to, when you allowed it and when it was last used. Requests are counted for a short time to limit their rate. Projects, elements, scenes, stills and clips made through the connector are kept like any others in your workspace.

Zero Page does not sell data, run ads, train models on your material, or share your media, images or account details with data brokers or marketers. Nothing is posted anywhere on your behalf: every render lands in your own Library, and publishing is an explicit action a person takes.

Production material and account data are kept for as long as your account is active. Deleting a render in the Studio removes it from your library at once; the file itself is kept until your account is deleted, so a scene that used it keeps playing. You can disconnect a connected model account at any time from its settings. To disconnect a chat app, remove the connector in that app (in Claude: Customize, then Connectors): the Studio is not told when you do, cannot disconnect it for you, and keeps its record that the connection was made until you ask for it to be removed. You can ask for your account and all of its data to be deleted — see contact below.

Zero Page is a professional production tool and is not directed at or knowingly used by children under 13.

If this policy changes materially, the effective date above will be updated. Continued use of the Studio after a change means you accept the revised policy.

Questions about this policy or your data can be sent to mikemassaad@gmail.com.