Flow AutomatorPrivacy Policy
Last updated 4 September 2026. Applies to Flow Automator 3.60.0 and later.
Flow Automator is a Chrome extension that queues prompts on Google Flow, captures the clips Flow renders, and saves them as one zip. It is built so that your prompts, your clips and your settings stay on your own computer unless you deliberately switch on one of the three optional features described below. This page says exactly what is stored, what can leave your device, and what each browser permission is for.
The short version
- The extension only runs on labs.google/fx pages. It does nothing on any other site.
- Everything it keeps lives in your browser profile: the queue, the settings, the captured clips and the activity log.
- It contains no analytics, no advertising and no third-party tracking of any kind.
- Nothing is sent to us by default. The one service we operate, persistent memory, is off until you turn it on and enter a key.
- The other two optional features, the local MCP bridge and cloud storage, talk only to endpoints you control: a program on your own computer, or a storage bucket you configure.
- We never sell, rent or share your data, and we never use it for advertising or to train anything.
What stays on your device
All of the following is stored with Chrome's extension storage and IndexedDB, inside your browser profile, and is removed when you uninstall the extension or clear it from the Library tab:
- The prompt queue: prompt text, reference image choices, output settings and per-prompt status.
- The library: the clips and stills the extension captured, with the project, prompt and Flow identifiers they came from.
- Your settings, including the light or dark theme and the run options.
- The activity log, which records what the extension did on the Flow page and why.
- Any tokens you enter for the optional features. They are stored locally and shown masked once saved.
What leaves your device, and when
Google Flow
The extension operates the Flow page you are already signed in to. Your prompts, reference images and project names therefore reach Google exactly as they would if you typed them yourself, and Google handles them under its own privacy policy. When the extension captures a clip, it fetches the file from Google's media servers or saves it through Chrome's download manager. We do not see any of this traffic.
The MCP bridge (off by default)
Flow Automator can be driven by an AI coding agent such as Claude Code, Codex or Cursor through a small server that runs on your own computer. When you enable the bridge, the extension opens a WebSocket to 127.0.0.1 only, guarded by a token minted in the setup guide. Nothing crosses the network: the connection cannot reach another machine, and a client that presents the wrong token is refused before it can send anything. What the agent then does with prompts and clips is governed by that agent's own policy, not by this one.
Cloud storage (off by default)
You can have every captured clip mirrored to an object storage bucket. To do that you enter the address of a signing service and a token in Settings. The extension then asks that service for a single signed upload or download URL per file and sends the clip bytes to the bucket the service points at. The signing service and the bucket are yours: we ship the open source code for the signer so you can deploy it on your own account, and the extension never contacts any storage we operate. Turn the feature off and no further uploads happen; the clips already in your bucket remain under your control.
Persistent memory (off by default)
This is the only feature that talks to a server we run. It exists so that a reinstall or a second computer does not have to re-learn identifiers that are slow to recover from the Flow page. It stays off until you enable it and enter an account key in Settings; minting a key needs a bootstrap secret we issue on request, so it is not something a fresh install can do by accident. When it is on, the extension stores the following against that key:
- Project identifiers and the names Flow shows for them.
- For each captured clip: its Flow identifier, which project and prompt it came from, and where its mirror lives if cloud storage is on.
- The mapping between the two identifiers Flow uses for the same asset.
- Observations about the Flow page layout, used to find buttons and fields when Flow changes.
The account key is generated on request and shown once; it is the only thing that links a record to you. We do not receive your name, your email address, your Google account, your reference images or any clip bytes. There is no way for us to tell who a key belongs to. To erase everything held under a key, use the flow_memory_forget tool over the bridge, or write to us quoting the key; records are deleted at once. Traffic to the memory service is protected with TLS, and the server keeps only ordinary access logs, which its hosting provider, Cloudflare, also processes in order to serve requests.
Nothing above is required. Queueing, capturing and zipping work with all three optional features switched off, and they are switched off on a fresh install.
What each permission is for
Chrome shows a warning for some of these when you install. This is why each one is there:
| Permission | Used for |
|---|---|
| storage, unlimitedStorage | Keeping the queue, settings and captured clips in your profile. Video batches are large, so the default quota is lifted. |
| tabs, scripting | Finding the open Flow tab and re-attaching the extension's page script after Flow navigates or the extension updates. |
| sidePanel | The extension's interface is a Chrome side panel. |
| offscreen | Zipping a batch and fetching clip bytes happen in a hidden extension page, because the background worker cannot hold large files. |
| downloads | Saving the finished zip, and saving individual clips that Flow only exposes as downloads. |
| contentSettings | Allowing the extension to save several files in a row without Chrome asking you to confirm each one. It is applied only to the extension's own origin and to labs.google. |
| debugger | Flow ignores clicks and typing that come from a script. To press its Generate button and fill its prompt field the extension sends trusted input events through Chrome's debugging protocol, attached only to the Flow tab and only while a run is active. It never reads page data through this channel. |
| alarms | Waking the background worker to keep a run going and to keep the optional bridge connected. |
| Host: labs.google | The page the extension works on. |
| Host: googleusercontent.com, storage.googleapis.com | Where Flow serves the clip files the extension captures. |
| Host: memory service | The optional persistent memory service described above. |
Chrome Web Store User Data Policy
Our use of information received from Google APIs and from the Flow page complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only to provide the extension's single purpose, which is automating prompt queueing, clip capture and batch download on Google Flow.
Children
Flow Automator is a production tool for people who already use Google Flow and is not directed at children. We collect no personal information and offer no accounts, so we do not knowingly hold data about anyone, including children.
Your rights
Regulations such as the GDPR and the CCPA give you rights to access, correct and delete personal data held about you. Everything the extension keeps on your device is yours to inspect in the Library and Settings tabs and to delete with one action. The memory service holds records only against your account key, and the forget tool removes them. If you believe we hold something about you that you cannot remove yourself, write to us and we will help.
Changes
If this policy changes in a way that affects what happens to your data, we will update the date at the top, describe the change here, and note it in the extension's changelog.
Contact
Questions about privacy go to the support email shown on the extension's Chrome Web Store listing.
Google, Google Flow and Veo are trademarks of Google LLC. Flow Automator is an independent project and is not affiliated with, endorsed by or sponsored by Google.