Privacy Policy
Last updated: 1 August 2026 · Applies to the Reelforge browser extension.
Reelforge keeps everything on your own computer. It has no user accounts, no analytics, and no tracking. Nothing you type, generate, or download is sent to us, because there is nowhere for it to be sent.
What Reelforge stores
All of the following is saved in your browser's own extension storage, on your device. None of it is transmitted anywhere.
| What | Why |
|---|---|
| Your prompt list and uploaded prompt files | So your work is still there when you reopen the panel |
| Settings — mode, aspect ratio, model, output count, download folder, filename options | So you don't reconfigure every session |
| Interface language | To show the panel in your chosen language |
| A daily count of prompts submitted | Shown in the panel as a usage figure |
| Upscaler options and queue state | To resume and report progress during a run |
| An email address, if you choose to enter one | Stored locally only. It is not sent to any server in this version |
Removing the extension deletes all of it. You can also clear it at any time from your browser's extension settings.
What Reelforge sends over the network
One request, and it carries none of your information: the extension fetches a configuration file describing where the buttons and menus are on the Google Flow page. Google changes that page from time to time, and this lets the extension keep working without an update.
That request sends no prompts, no filenames, no email address, and no identifier for you or your device. If it fails, the extension falls back to a copy bundled inside the package and carries on working offline.
There is no analytics, no telemetry, no crash reporting, and no advertising.
What Reelforge never does
- It does not read, collect, or transmit your Google account details or password.
- It does not send your prompts or generated media anywhere. Files download straight from Google to your own Downloads folder.
- It does not sell, rent, share, or broker any data. There is no third party involved.
- It does not run on any website other than
labs.google.
Permissions, and why each one is needed
| Permission | Reason |
|---|---|
debugger | Google Flow ignores clicks made by scripts. This permission lets Reelforge produce real mouse and keyboard input so the page responds normally. It is attached only to your Flow tab, only while a run is active, and is used purely for input — never to read page data or network traffic. |
downloads | To save each generated video or image and give it a readable filename. |
cookies | To clear cached (non-login) site data for labs.google between batches, so the page reloads fresh results. Sign-in cookies are explicitly excluded and never touched. |
tabs, activeTab | To find your Google Flow tab and send instructions to it. |
scripting | To start the upscaler on a Flow tab that was already open before the extension loaded. |
storage | To save your settings and prompts on your device. |
sidePanel, background | To show the panel and keep a batch running while you work in other tabs. |
labs.google access | The only site Reelforge is allowed to touch. |
Children
Reelforge is not directed at children under 13 and does not knowingly collect information from them.
Changes
If a future version starts handling data differently — for example if optional accounts are added — this page will be updated before that version ships, and the date at the top will change.
Contact
Questions about this policy: nanku7525@gmail.com