Information we use
FilmWorx receives an account identifier, verified email address, and, when available, display name through its sign-in provider. Clerk supports the new member sign-in; ChatGPT sign-in remains available during the transition. We link these identifiers to preserve existing member work and use your email and approval date to manage Studio access. We do not receive your sign-in provider’s password or access to unrelated ChatGPT chats.
We store the projects, scripts, notes, prompts, scene plans, links, progress, images, and other files you save. Files may contain embedded metadata; the upload process does not automatically remove it. Remove sensitive metadata before uploading.
Generation records include submitted prompts, selected references, settings, job identifiers, timestamps, status, errors, saved images and videos, billing estimates and charges, credit quotes, and acceptance of the dated generation terms. Credit records include your account email, balance changes, payment or order identifiers, and support notes. The owner can view balances and job status to operate the service and resolve interrupted generations. The owner’s provider key is stored in encrypted form for server-side use.
Studio access purchases use Stan and its payment services. When purchase automation is enabled, Zapier forwards the buyer email, product identifier, order or event identifier, and payment status to FilmWorx to approve eligible access and prevent duplicate processing. Render credit purchases use Stripe Checkout. FilmWorx receives payment status, amount, credit quantity, order identifiers, and refund or dispute updates to manage your balance. FilmWorx’s site does not collect or store your full payment-card number.
Studio activity and browser storage
Our built-in analytics record member visits to studio sections, shared prompt opens and copies, prompt-pack use, tutorial starts and completions, and certain resource downloads. Records include event counts, dates, and first and last activity linked to your account email. They are not anonymous. The owner can view usage summaries and member activity dates.
These analytics do not collect the text of your private scripts or prompts. They help us understand which features are used and support the Studio. The current FilmWorx application does not install advertising pixels or use analytics cookies for this measurement.
Hosting, security, and Clerk or ChatGPT authentication may use cookies or similar technologies and process technical information such as IP address, browser, and request logs. Browser controls can restrict cookies, but doing so may affect sign-in. External websites have their own tracking practices.
What happens when you generate
Submitting a generation sends your prompt, settings, and selected references to the generation provider and applicable model provider. Nano Banana Pro images use Kie when connected by the owner; otherwise they use Pika. Video generation and extensions use Pika. Existing requests remain with their original provider. Selected files use temporary access links. For video extensions, FilmWorx prepares a short ending excerpt of your selected take and sends it as a video reference. The resulting image or video is saved in FilmWorx for preview and download.
Pika’s published privacy policy permits API inputs to be used for model improvement or training, subject to any separate agreement. Review Pika’s Privacy Policy for Pika processing. Kie’s terms permit use of submitted content to operate and improve its services. Review Kie’s Terms of Use and Privacy Policy for Kie processing. FilmWorx cannot promise that provider processing is confidential or training-free. Do not submit confidential client material or sensitive personal information unless you have permission and the processing terms meet your needs.
Processing may occur outside your country. External tools you open from Resources or Story Director are governed by their own privacy policies. FilmWorx does not operate its own AI training pipeline.
Storage and deletion
We keep saved content in active storage until you delete it or it is otherwise removed in service administration. Availability is not guaranteed. There is no automatic fixed-age deletion schedule. Account, approval, activity, billing, and security records may be retained for service operation, accounting, dispute resolution, and legal obligations.
Deleting a project removes its saved project content and associated uploads from active FilmWorx storage. Removing Studio access access alone does not delete saved work.
Deleting a settled take removes its saved private video and clears its prompt and settings from that take. Limited billing and duplicate-request records remain. Saved references are separate. Downloads, independently shared Prompt Vault copies, provider records, and any infrastructure backups are not erased by that action. Separate removal requests may be needed.
We use access controls and other safeguards, but cannot guarantee that any internet service is perfectly secure. Keep your own copies of important work.
Your requests and choices
You can edit or delete content where the Studio provides those controls. Contact FilmWorx to request access to, correction of, or deletion of other account information, or to ask about activity records. There is no self-service account-erasure button at present. We may need to verify your identity and retain information where required or permitted by law.
Privacy rights depend on where you live and which laws apply. Where applicable, these can include access, correction, deletion, portability, objection, and review of a denied request. You may also contact your local privacy regulator. We will not penalize a person for exercising applicable privacy rights.
FilmWorx is not intended for children under 13. The generator is restricted to adults. Contact us if a child’s personal information has been submitted so it can be reviewed for removal.
For Studio access, billing, privacy, or content questions, email hello@filmworxstudio.com. Include the relevant page or order reference and the email associated with your account. Never send your password, API key, or full payment-card details.