roose-flow

Privacy Policy — Roose Flow

Last updated: 23 October 2026

Roose Flow does not collect, transmit, or sell any personal data.

The extension has no backend. It makes no network requests to any server operated by the developer, and contains no analytics, tracking, advertising, or third-party SDKs.

What the extension stores

Your prompts are held in Chrome’s session storage while the side panel is open. They are never written to disk and never leave your computer. They are discarded when you close the side panel, and again when you close Chrome.

Earlier images from the same run. To reuse the look of a place that was already generated, the extension remembers, for the current run only, which prompt each image belongs to and the web address of that image on Flow. This is held in the same session storage, is never written to disk or sent anywhere, and is discarded together with your prompts. The extension does not copy or upload the images themselves; it only finds the image again on the Flow page and uses Flow’s own “Add to prompt” option.

Your settings — auto-download on/off, download folder, serial numbering, character consistency, the character names you save, and the delay range between generations — are saved in Chrome’s local storage on your own machine so they persist between sessions. They are never transmitted anywhere.

Generated images and videos are saved to your computer, either through Chrome’s downloads API or, if you pick an output folder with the Browse button, directly into that folder. Choosing a folder grants the extension access to that folder alone — nothing outside it is read or written, and the grant can be revoked at any time from Chrome’s site settings. The extension does not upload your renders, copy them, or retain them anywhere else.

What the extension accesses

On flow.google.com, the extension reads and writes the page in order to type your prompt into the prompt box, submit it, and detect when a render has finished. It does not read your account details, cookies, or credentials, and it does not operate on any other site.

Permissions and why they are needed

• storage — save your settings, and hold the prompt queue in memory.
• downloads — save finished renders to the folder you pick.
• sidePanel — display the extension’s interface in Chrome’s side panel.
• debugger — used for one thing: sending a real mouse click on Flow’s send button. Flow ignores clicks generated by a page script, so a genuine click has to be delivered through Chrome’s debugger protocol. It is attached only to the Flow tab, only while a batch is running, and detached when the batch stops; Chrome shows a “debugging this browser” banner for as long as it is attached. Nothing is read from the page through it.
• host permission for https://flow.google.com/* — the only site the extension operates on; required to enter prompts and detect finished renders.

The extension requests no other permissions.

Data sharing

None. No data is collected, so none is shared, sold, or transferred to third parties, and none is used for creditworthiness or lending purposes.

Changes

Any future change to this policy will be published at this address alongside a new version of the extension.

Contact

Questions about this policy can be sent through the support tab of the extension’s Chrome Web Store listing.