Privacy Policy — Flow Connector

Last updated: 2026-09-03

Flow Connector ("the extension") automates image and video generation on flow.google.com (formerly labs.google/fx/tools/flow) using the Google session you are already signed into. This policy describes every piece of data the extension touches.

This is a different product from Grok Imagine Connector, which is free and contacts no server of ours. Do not read that policy for this extension.

Short version

The extension runs on your computer. It has no accounts, no analytics and no telemetry, and we cannot see what you generate. Two things do leave your machine, both described in full below: a licence check if you sign in, and a bug report if you choose to send one.

There are no ads, no ad network, no tracking pixels, and no third-party code of any kind inside the extension.

What is stored, and where

All of the following lives locally in your browser (chrome.storage) and never leaves your machine:

Generated images and videos are saved to your own Downloads folder by Chrome's download manager. We never see them.

Your Google account

The extension uses the Google session you are already signed into. It never asks for, stores, or transmits your Google username, password, cookies or tokens. It drives the Flow interface the same way you would by hand.

Your prompts go to Google, because Google is what generates the media. They are subject to Google's own privacy policy. They never come to us.

Network activity

The extension makes only these kinds of requests:

1. Google Flow (flow.google.com, and labs.google which still redirects there) — the same server your browser already contacts when you use Flow, to submit prompts and retrieve results.

2. A licence check, to our own server, only if you have signed in. It sends exactly two things: the email address you typed into the extension, and a random installation id. The email address is how a paid plan is recognised — it is the address you paid with, and it is stored on our server alongside your plan and its end date, nothing else. It is never used to contact you, never sold, never shared and never given to any advertiser or analytics service. The installation id is generated once by your browser, is not derived from your hardware, your Google account or anything about you, and exists solely so one subscription can be limited to one device at a time. The response is your plan and how long it is valid for. This happens about once an hour while the browser is running. If you never sign in, this request never happens and we hold no record of you at all.

3. A configuration file, from the same server. Flow changes its interface frequently, which breaks automation; this small file lets those breakages be fixed without waiting for a store update. It also carries the free tier's daily limits. The request downloads configuration only — it sends no prompts, no identifiers and no personal data. It is an ordinary file download, and we cannot distinguish one user's request from another's beyond the IP address that any web request necessarily carries.

4. A status check, to the same server, when you open the Help tab. It asks one question — is the service up — so the tab can tell you whether a problem is yours or ours. It sends no identifiers and no personal data, and happens only while that tab is open.

5. An optional local bridge on 127.0.0.1 (loopback — your own machine), used when you drive the extension from the command line or an AI coding agent. It is reachable only by programs already running on your computer, rejects requests from web pages, and sends nothing to the internet.

We keep no per-user logs of requests 2, 3 and 4.

Bug reports

Help → Report a problem prepares a report containing the extension version, your browser's user-agent string, your plan, and the tail of the local debug log, then opens a public GitHub issue with that text filled in.

Nothing is sent when you press the button. The report opens in your browser for you to read, edit or abandon; it becomes public only if you submit it there. The report includes a reminder to read it first. If you would rather not use GitHub, the same button offers to copy the report to your clipboard instead.

Payments

Payment is taken by Razorpay on their own hosted page. Your card, UPI and bank details go to them and never to us — the extension never sees them, and nothing about a payment passes through the extension at all. We receive only the email address you paid with and whether that address has an active plan. Razorpay's privacy policy governs the payment itself.

Pro is sold as a one-time package. Nothing auto-renews, so there is no stored payment method and nothing to cancel.

Permissions

Each permission exists solely to deliver the extension's single purpose.

What the extension does NOT do

Limited Use

Our use of information received from Google APIs and Google services adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data from the extension is never sold, never transferred except as described above, and never used for advertising.

Changes

Any change affecting data handling will be published here before it ships. If a future version ever collects anything more, it will be disclosed here and in the Chrome Web Store data-usage section first.

Contact

Questions, bug reports, or privacy concerns: https://github.com/srijan-kaiwart/flow-connector/issues

Disclaimer

Flow Connector is an independent tool, not affiliated with, endorsed by or sponsored by Google LLC. Google product names are used only to say what this tool works with, and remain the property of their owner. Automating a website may be subject to that site's terms of service; use responsibly.