Privacy policy

1. Scope

This policy covers the VideoFlow Studio website, its account system, hosted generation, and the command-line tool ("the CLI") that drives it. It does not cover any third-party site your own submissions point at, the privacy practices of the third-party providers we rely on to operate (listed in Section 5), or any other product, including any separately branded "VideoFlow" product or open-source project that is not this Service. If you reach this Service through a link on another site, that site's own policy governs your visit there, not this one.

2. What we collect

We collect the following categories of information in the ordinary course of operating the Service:

• Account information. An email address. There is no password; sign-in happens by emailing a short-lived link and code to that address. We also store your plan, your subscription status and Stripe customer references, and your AI credit balance. Card details are handled by Stripe and are not stored by us.
• Projects. For each project: the URL and brief you gave, the selected agent and model, the film document (its layers and revisions), planning files, the assets the film uses (images, video, audio, fonts), rendered cuts, and checkpoints. With the CLI, these are synced from your machine to our servers when you publish a project, so that it can be opened in the browser editor and continued from another machine.
• Content gathered from your URL. For hosted generation, our headless browser visits the public pages at the URL you submit and gathers screenshots, images, logos, page text, and layout and styling information, and may download media from that site. Our automated browser is restricted from reaching internal or private network addresses. We do not access anything behind a login unless you explicitly give us the means to. In CLI runs, this gathering happens on your machine.
• Run records. For hosted generation: the job's steps, the agents' conversation transcripts, logs and error messages, kept so you can follow and steer the film and so we can debug failures.
• Usage and billing records. Counts of CLI renders and edits per month, and a ledger of AI credit movements (grants, reservations, charges, expirations, purchases), plus your storage use.
• CLI error reports. If the CLI hits an error it may send a report to us without signing in: a session identifier, CLI version, the agent provider and model, the step that failed, the error message and stack trace (truncated), your operating system platform and Node version, and your IP address. Reports are stored in a log file used for debugging and are size-capped.
• Usage telemetry. The website uses Google Analytics (pageviews and clicks). For CLI activity, our servers send some events (for example opening a project, a render finishing) to Google Analytics, identified by an account or project identifier.
• Communications. If you contact us, we keep that correspondence for as long as is reasonably necessary to address it.
• Technical and log data. Standard web request information (such as IP address, browser or client identification, and timestamps), retained for security, abuse-prevention and operational purposes. Sign-in pages may show an approximate location (city) derived from your IP address using a local database, so you can recognise your own session.

We do not intentionally collect information from anyone we know to be under the age of 16, and the Service is not directed at children. If you believe a child has provided us information, contact us and we will take reasonable steps to remove it.

3. How we use it

We use the information above to:

• Provide, operate, and maintain the Service, including producing and storing the videos you request;
• Authenticate you, secure accounts, and enforce plan limits and fair use;
• Process payments, manage subscriptions and meter AI credits;
• Send you service-related communications, such as email verification, security notices, and, where you have not opted out and it is permitted, occasional product updates;
• Diagnose problems, improve reliability, and understand how the Service is used in aggregate;
• Detect, investigate, and prevent fraud, abuse, security incidents, and violations of our Terms of use; and
• Comply with legal obligations and enforce our agreements.

We do not use the content of what you submit to train any general-purpose model that we control, and we do not sell personal information. Where a request is processed by a third-party AI provider as part of generating your video (see Section 5), that provider's own handling of the request is governed by their terms and policies, not this one.

4. Two ways to make videos, and what that means for your data

CLI. The coding agent that plans and builds your video is your own Claude Code or Codex, running on your machine under your own subscription. The content of your submission and the reasoning behind your film pass through your agent provider under your account, and their policies apply. We relay the instructions and skill library the agent needs, and receive back the project files (the film, assets, plan, renders, logs) that you publish to your account. We do not control your relationship with your agent provider. If you request AI voice, images or video, those requests are made through our account with the provider (Fal.ai) and billed in credits.

Hosted generation. Our agents, powered by Anthropic's Claude, run on our infrastructure with your URL, brief and the content our browser gathers from your site, and write the results directly to your project. Optional AI voice, images, video and word timestamp alignment are sent to Fal.ai. Anthropic and Fal.ai process this content under their own terms.

5. Who we share information with

We disclose information only in the following circumstances:

• Service providers. These process data on our behalf, only as needed to perform their function:
  • Anthropic: Claude models for hosted generation.
  • Fal.ai: AI voice (text to speech), images, video and word-timestamp alignment.
  • Stripe: subscriptions, credit packs and billing portal.
  • Cloudflare: R2 object storage for your files, CDN and secure tunnelling.
  • MongoDB Atlas: our database.
  • Mailgun: sign-in emails.
  • Google Analytics: website and CLI usage measurement.
• AI providers for your own CLI agent. When you use the CLI, your chosen provider (Anthropic or OpenAI) receives your work under your own account and its own terms, not through us.
• Sites you submit. Our browser makes requests to the URL you submit, and to the media that site references, as you instructed.
• Legal and safety reasons. We may disclose information if we reasonably believe it is necessary to comply with a legal obligation, protect the rights, property, or safety of ourselves, our users, or the public, investigate fraud or security issues, or enforce our Terms of use.
• Business transfers. If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to standard confidentiality arrangements.
• With your direction. Where you explicitly direct us to share something — for example, by making a link public or exporting your own content.

We do not sell personal information, and we do not share what you submit with unrelated third parties for their own marketing purposes.

6. Internal access

A limited number of people involved in operating this Service can access session, account, and run data through an internal administrative interface, gated separately from the public product, to provide support, investigate abuse, debug failures, and maintain the Service. Access is limited to what is reasonably necessary for those purposes, and we take reasonable steps to log and restrict it.

7. How long we keep information

• Sign-in sessions last 14 days since you last used them, then expire and are removed. A pending sign-in expires after 15 minutes.
• Projects, films, assets and renders are kept while your account is active, until you delete the project. Each plan has a storage allowance.
• Deleting a project (a button in the project) removes its files from storage, its film, revisions, checkpoints, jobs, agent transcripts and assets, and the project record. It is refused while something is still building it.
• The AI credit ledger is kept when a project is deleted, as the account's billing history.
• CLI error reports are kept in a size-capped log; once the cap is reached new reports are dropped.
• Account data is kept while the account is active and for a reasonable period afterward for billing, legal, accounting, security and abuse-prevention purposes. Backups and logs may persist for a limited additional period after deletion, then age out.

To have your account and associated data deleted, contact us. We will act on that request within a reasonable time, subject to anything we are required or permitted to retain by law, for dispute resolution, or to enforce our agreements. Account deletion is not currently self-service.

8. Security

We use reasonable safeguards: traffic is encrypted in transit (TLS); sessions use HttpOnly, Secure cookies; sign-in and public endpoints are rate-limited; hosted browsing is restricted from reaching private network addresses; and internal access is limited as described above. We also encrypt the skill library and prompts we send to the CLI. That encryption protects our own material from casual copying, and is not a protection for your content. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. You are responsible for keeping your account inbox confidential and for the security of the machine you run the CLI on, including any coding-agent credentials it uses.

9. Cookies and similar technology

• vf_user: keeps you signed in (HttpOnly, Secure, up to 14 days, renewed when you use the site).
• vf_pending: tracks a sign-in you have started but not yet confirmed (15 minutes).
• A separate cookie that gates our internal administrative view (staff only).
• Google Analytics (gtag.js) sets its own cookies on the website to measure usage. We do not use advertising or cross-site tracking cookies of our own.

Your browser lets you block or delete cookies; blocking the sign-in cookies will sign you out, and you can block analytics cookies without affecting the Service.

10. International use

The Service, and the providers listed above, may operate infrastructure in one or more countries other than your own, including the United States. By using the Service, you understand that your information may be transferred to, stored in, and processed in a country that may have data protection laws different from those of your own jurisdiction. Where required by applicable law, we take steps intended to provide an adequate level of protection for such transfers.

11. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, export, or obtain a copy of the personal information we hold about you, to object to or restrict certain processing, or to withdraw consent where processing is based on it. You can delete your own projects in the app, and the project files are yours to download from the editor. To exercise any other right, contact us as described below. We will respond within a reasonable time and may need to verify your identity before acting on a request. We will not discriminate against you for exercising a privacy right available to you under applicable law.

You may opt out of non-essential email communications at any time using the unsubscribe mechanism included in those messages; you will still receive essential service and account-related messages, such as security notices and billing receipts.

12. Third-party links

The Service may link to third-party websites, including sites you submit for the Service to visit and comparison pages we maintain about other products. We are not responsible for the content, security, or privacy practices of any third-party site, and this policy does not apply to them.

13. Changes to this policy

We may update this policy from time to time as the Service, our providers, or applicable law change. If we make a change we consider material, we will provide reasonably prominent notice, such as a notice on this page or, where appropriate, by email, and update the date at the top. Continued use of the Service after a change becomes effective constitutes acceptance of the revised policy to the fullest extent permitted by law.

14. Contact

Questions about this policy, or a request concerning your data: reach us through videoflow.dev. Please include enough detail (such as the account email or session identifier involved) for us to locate the relevant records; we may not be able to act on a request we cannot verify.