AutoFlower - Veo Automation Privacy Policy
Effective date: June 22, 2026
AutoFlower - Veo Automation is a Chrome extension that helps users batch-run their own Google Flow image and video generation tasks from a Chrome side panel.
Data We Process
AutoFlower may process the following types of user data when you use the extension:
- Personally identifiable information: your email address, display name, and profile avatar if provided through Supabase or Google sign-in.
- Authentication information: authentication session data and tokens needed to keep you signed in.
- Website content: prompts, reference images, generated image or video result information, selected generation settings, and Google Flow page state needed to run the automation you start.
- Local extension data: extension settings, selected images, task queue state, download folder preferences, and recent runtime logs.
- Usage and quota data: daily prompt usage counters and account entitlement information used to enforce the extension's usage limits.
How We Use Data
We use this data only to provide the extension's single purpose:
- Sign you in and maintain your session.
- Verify your usage quota and account entitlement.
- Send your prompts, reference images, and selected settings to Google Flow when you start an automation task.
- Monitor task progress and display concise runtime status in the side panel.
- Save generated images or videos when you enable download options.
- Store local preferences so the extension works consistently between sessions.
Data Sharing
AutoFlower does not sell user data.
AutoFlower does not use or transfer user data for advertising, unrelated analytics, creditworthiness, lending, or any purpose unrelated to the extension's single purpose.
AutoFlower uses the following services only as needed to provide the extension:
- Supabase, for authentication, session handling, account entitlements, and usage quota checks.
- Google Flow, for the image and video generation tasks that you initiate.
Data sent to Google Flow is subject to Google's own terms and privacy policies. Data processed by Supabase is used for authentication and usage control for this extension.
Local Storage
AutoFlower stores settings, session data, selected images, task state, and recent runtime logs in Chrome extension local storage. This data remains on your device unless it is cleared by the extension, removed by you, or removed when the extension is uninstalled.
Remote Code
AutoFlower does not use remote code. All JavaScript, CSS, and extension logic are included in the submitted extension package. Network requests are used only for authentication, usage checks, and user-started Google Flow automation.
Data Retention
Local extension data remains on your device until you clear it, sign out where applicable, or uninstall the extension.
Authentication and usage quota records may be retained in Supabase as needed to provide account access, enforce usage limits, prevent abuse, and maintain the service.
User Choices
You can stop using the extension at any time. You can clear local extension data by using the extension's available clear controls or by removing the extension from Chrome.
You can sign out from the extension to remove the active authentication session from the extension.
Security
AutoFlower uses HTTPS for network requests to Supabase and Google Flow. Authentication is handled with public client credentials and user sessions. The extension does not include Supabase service role secrets.
Changes To This Policy
This privacy policy may be updated when the extension changes. The current version will be published on this page.
Contact
For privacy questions or requests, please contact the project through the GitHub repository: