Overflow is a free Chrome extension that automates bulk prompt submission on Google Flow™. This policy explains what data Overflow accesses, how it's used, and what is (and isn't) collected.
In short: Overflow runs entirely inside your own browser, on your own Google Flow account. It does not have a server, does not transmit your prompts, images, or activity anywhere, and does not sell or share data with anyone.
What Overflow accesses
To do its job — queueing and submitting prompts on your behalf — Overflow reads and interacts with the content of the Google Flow page (labs.google/fx) that you have open. Specifically, it:
Reads the state of Flow's prompt composer, so it knows when a prompt has finished generating and it's safe to submit the next one.
Types queued prompts into the composer and submits them on your behalf.
Reads generated results (images/video) so they can be downloaded, if you've enabled Auto Download.
Matches uploaded reference images to prompts by filename, for the Consistent Character feature.
This is the only site Overflow interacts with. It does not read, monitor, or collect data from any other tab or website you visit.
What Overflow does not collect
Overflow does not collect, transmit, or have any means of accessing:
Personally identifiable information (name, email, address, etc.)
Authentication credentials or passwords
Health, financial, or payment information
Your browsing history or activity outside of the Google Flow tab
Location data
Where your data lives
Overflow stores the following locally in your browser only, using Chrome's built-in storage APIs. This data never leaves your device:
Your prompt queue and queue settings (delay range, download folder name, auto-download toggle)
Uploaded character reference images, for matching against queued prompts
Overflow has no backend server. There is nowhere for this data to be sent, because no such destination exists.
Permissions Overflow uses, and why
Host permission (labs.google/fx): required to read and interact with Flow's prompt composer — this is the extension's core function.
debugger: used narrowly to send a single trusted click to Flow's Generate button when submitting a queued prompt, since Flow's composer does not respond to standard synthetic click events. It is only active on the current Flow tab, only while a queue is running, and is not used for anything else.
downloads: used only when you enable Auto Download, to save your own generated results to a folder you choose.
storage: used to save your queue settings and reference images locally, as described above.
sidePanel: used to display the queue controls in Chrome's side panel, so you can monitor and control a running queue.
Sharing and selling of data
Overflow does not sell, rent, or transfer any user data to third parties. It does not use data for advertising, profiling, or any purpose unrelated to running your own prompt queue on your own Google Flow account.
Children's privacy
Overflow is not directed at, or knowingly used by, children. It is a developer/creator productivity tool intended for adult use in connection with a Google Flow account.
Changes to this policy
If this policy changes, the updated version will be posted at this same URL with a revised effective date. Material changes affecting how your data is handled will also be reflected in Overflow's Chrome Web Store listing.
Contact
Questions about this policy or how Overflow handles data can be sent to: [YOUR CONTACT EMAIL HERE]