This Privacy Policy explains how Veo Automation ("the Extension", "we", "our") handles your information. The short answer: we don't collect any of it. The Extension operates entirely on your local machine and has no server, no analytics, and no external data transmission of any kind.
1. Data We Do NOT Collect
Veo Automation does not collect, store, transmit, or sell any of the following:
- Your name, email address, or any other personal identifier
- Your text prompts or image uploads
- The videos or images generated by Google Flow
- Browsing history, visited URLs, or page content from any website
- Usage analytics, telemetry, or crash reports
- IP addresses or device identifiers
There is no account system, no sign-up form, and no login. You are completely anonymous to us — because we have no way of knowing you exist.
2. Data Stored Locally on Your Device
The Extension uses chrome.storage.local (or the Firefox equivalent) to save your preferences between sessions. This data never leaves your browser. It includes:
- Selected generation mode — e.g. "Text to Video"
- Selected model — e.g. "Veo 3.1 Quality"
- Download quality setting — e.g. "4K Upscaled"
- Delay range, max retries, concurrent prompts
- Folder name and auto-rename preference
- Language preference — stored under the key
language - UI panel state — open/collapsed sections
You can clear this data at any time by removing the Extension from your browser or using your browser's built-in extension storage management tools.
3. Optional Remote Configuration
The Extension may periodically fetch a small remote configuration file to receive updated UI selector definitions when Google Flow updates its interface. This request:
- Contains no personal data
- Is a plain HTTP GET request with no authentication
- Returns only CSS selector strings and version metadata
- Is served over HTTPS
This mechanism exists solely to keep the Extension working after Google Flow UI changes, without requiring you to install a new version.
4. Chrome Debugger API Usage
Veo Automation uses the Chrome Debugger API (chrome.debugger) to interact with Google Flow. This is a technically necessary design choice, explained here in plain language.
Google Flow is built with React. React's synthetic event system only responds to "trusted" browser events — those that originate from genuine user interactions, not from JavaScript code. Standard DOM methods like element.click() are treated as untrusted and ignored by React's input handlers.
The only way to programmatically send a trusted click event is through the Chrome DevTools Protocol (CDP) via the Debugger API. Veo Automation attaches the debugger, sends a single Input.dispatchMouseEvent command to simulate a click at a target element's coordinates, then immediately detaches.
The debugger is used only to click buttons and inputs on labs.google. It never reads page content, DOM data, network requests, cookies, or any other information from the page.
5. Permissions Table
The following table explains every permission the Extension requests and exactly why it needs it:
| Permission | Why it's needed |
|---|---|
| storage | Save your settings (model, quality, delay, language, etc.) in chrome.storage.local so they persist between sessions. |
| tabs | Detect when you are on the labs.google/fx/tools/flow page so the side panel can activate automatically. |
| sidePanel | Display the Veo Automation control panel as a browser side panel alongside Google Flow. |
| activeTab | Interact with the currently active Google Flow tab when you trigger an action from the side panel. |
| downloads | Automatically save generated videos and images to your Downloads folder at your chosen quality level. |
| scripting | Inject the content script into the Google Flow tab to monitor generation progress and detect UI state changes. |
| debugger | Simulate trusted mouse click events on React components in Google Flow. Required because React's synthetic event system ignores untrusted DOM events. |
| windows | Support the detachable pop-out panel feature — open the control panel in a separate floating window. |
6. Host Permissions
The Extension requests access only to: *://labs.google/*
It has no access to any other website, including your personal accounts, social media, banking, search history, or any other page you visit. The Extension is completely inactive on all other domains.
7. No Third-Party Sharing
Because we collect no data, there is nothing to share with third parties. Veo Automation does not include advertising SDKs, analytics libraries, crash reporters, A/B testing tools, or any third-party code that could collect information about you.
8. Children's Privacy
Veo Automation is not directed at children under 13 years of age. We do not knowingly collect personal information from children. If you believe a child under 13 has used the Extension, please note that the Extension collects no personal data from anyone, regardless of age.
9. Changes to This Policy
We may update this Privacy Policy when the Extension's functionality changes in a way that affects data handling. When we do, we will update the "Last updated" date at the top of this page. We recommend reviewing this page when you install a new version of the Extension. Continued use of the Extension after a change constitutes acceptance of the updated policy.
10. Contact
Questions about this Privacy Policy? Email us at veosupport@devoveagency.com or visit veoautomation.com/contact.