Privacy & Data Ethics

Privacy Policy

Last Updated: October 2026 • Verified against Extension Source v1.0.0

Operator Review Notice:This privacy policy accurately reflects an audit of the actual Flowmator Chrome Extension source code. Any business entity publishing Flowmator to commercial app stores should review legal entity details, governing jurisdictions, and contact endpoints before commercial distribution.

1. Core Architecture: Zero Telemetry & Local Operation

Flowmator is built on a strict "Local-First" privacy model. The extension operates entirely within your browser environment. Flowmator does not maintain external tracking servers, telemetry services, behavioral analytics, or third-party advertising SDKs.

2. What Information Flowmator Processes

Flowmator processes the following data exclusively on your local device:

Prompt Texts & Queue Order: Stored locally in your browser's chrome.storage.local database to remember your queue between browser sessions.
Extension Preferences: Your selected mode (Safe Sequence vs Turbo), minimum/maximum intervals, retry counts, and neumorphic UI theme preferences.
DOM Canvas References: The extension temporarily inspects image media IDs (data-media-id) and error tiles on the active Google Flow tab to verify generation status. This visual metadata is never logged, stored persistently, or transmitted off your machine.

3. Third-Party Interactions (Google Flow)

Flowmator automates actions within Google Flow (flow.google.com and labs.google). Any prompt submitted through Flowmator is processed directly by Google pursuant to your existing Google Terms of Service and Privacy Policy. Flowmator does not proxy, intercept, or reroute your network requests to Google.

4. Data Retention & Deletion

All queue data remains in your local browser profile until you choose to delete it. You can completely erase all stored prompts, completed histories, and settings at any moment by clicking the "Clear All" button in the Flowmator side panel or by uninstalling the extension from chrome://extensions.

5. Chrome Extension Permissions Justification

Flowmator requests the following permissions strictly for functionality:

sidePanel: To render the automation dashboard docked alongside Google Flow.
debugger: To dispatch authentic keystroke and mouse click events into the ProseMirror rich text editor.
scripting: To execute client-side canvas verification in Google Flow's main page context.
storage: To persist your queue and configuration locally.
downloads: To automatically save generated image tiles to your local disk when user-enabled.

6. Contact & Support Inquiries

For privacy-related questions or source code verification audits, submit an inquiry through our Support Center.