Last updated: August 7, 2026
Flow Batch Prompter is an independent browser extension and is not affiliated with or endorsed by Google.
The extension stores prompts, recorded Google Flow control selectors, settings, progress, license status, and a randomly generated device identifier in Chrome's local extension storage. Prompts and generated media are not sent to the Flow Batch Prompter license server.
When a user activates or periodically verifies a paid license, the extension sends the Gumroad license key and random device identifier over HTTPS to the Flow Batch Prompter license server. The server sends the key to Gumroad solely to confirm the purchase and its status.
The license database stores one-way SHA-256 hashes of the license key and device identifier, the plan, and activation/verification timestamps. It does not store the raw key or the customer's Gumroad email address.
Free users sign in with Google so the 100-image allowance can be enforced across reinstalls and devices. Google provides a stable account identifier and verified email address. The server stores a one-way hash of the Google account identifier, the email address, usage count, sign-in timestamps, and marketing preference. Google passwords and authentication cookies are never collected.
Product news, offers, and discounts are sent only when a user separately opts in. Marketing consent is optional, is not required to use the extension, and can be withdrawn in the Account tab or through an unsubscribe link.
License-validation information is shared with Gumroad only as necessary to verify a software purchase. Google processes sign-in authentication. The service is hosted on Cloudflare, which processes requests as the infrastructure provider. Flow Batch Prompter does not sell personal information.
The extension interacts with Google Flow in the tab selected by the user. Google processes prompts, account information, credits, and generated media under Google's own terms and privacy policies. The extension does not collect Google passwords or authentication cookies.
Local extension data can be deleted by clearing the extension's storage or uninstalling it. A user can remove a device activation with the Deactivate button. Hashed activation records remain while needed to enforce the device limit and may be removed following a support request.
The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Questions or deletion requests: biotech.shahid@gmail.com