Privacy Policy

Last updated: September 8, 2026  ·  Version 1.0.14

Veo Automation ("the Extension", "we", "our") is a Chrome browser extension that automates batch video and image generation on Google Flow (flow.google.com, and the legacy address labs.google/fx/tools/flow). This Privacy Policy explains what data the Extension accesses, how it is used, and your rights. 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, transmit, or store any of the following:

• Your Google account credentials or authentication tokens
• Your prompts, generated videos, or images
• Browsing history, cookies, or any data from websites other than Google Flow
• Personal identification information (name, email, address, phone)
• Payment information
• Usage analytics, telemetry, or crash reports
• IP addresses or device identifiers
• Any data via the Chrome Debugger API (see Section 4)

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 stores the following data exclusively in your browser's local storage (chrome.storage.local) — this data never leaves your device:

• User preferences — your chosen generation mode, aspect ratio, model, download quality, folder name, and delay settings.
• Selector configuration — CSS selectors used to locate UI elements on Google Flow. These may be loaded from a remote configuration URL you provide (see Section 3).
• Uploaded images — images you attach for Frame to Video, Ingredients to Video, or Image to Image modes are held temporarily in memory during automation and are never written to disk by the Extension.

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. Remote Configuration (Optional)

If you choose to load a remote configuration via the Settings tab (by supplying a URL), the Extension will fetch a JSON file from that URL. This fetch is initiated by you and only you. We do not control, log, or process that request. The downloaded configuration is cached in chrome.storage.local on your device. 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

The Extension uses the chrome.debugger API for a narrow, well-defined purpose: to dispatch trusted mouse-click events inside Google Flow. This is technically necessary because Google Flow's interface only responds to browser-trusted events (events with isTrusted: true). Standard DOM dispatchEvent() calls produce untrusted events that the interface ignores.

Scope of debugger use:

• The debugger is attached only to the Google Flow tab (flow.google.com or labs.google) and only while an automation run is active.
• It is used exclusively to send Input.dispatchMouseEvent CDP commands (simulating a physical mouse click).
• It is detached immediately after each click operation completes.
• No data is read from the page via the debugger protocol. No screenshots, DOM snapshots, network data, or JavaScript evaluation is performed through it.
• The debugger is never used on any website other than Google Flow (flow.google.com / labs.google).

5. Permissions Used and Why

The following table explains every permission the Extension requests and exactly why it needs it:

Permission	Why it's needed
storage	Save your preferences and selector configuration locally.
tabs	Detect whether the active tab is Google Flow; send automation messages to the correct tab.
sidePanel	Display the extension's control panel alongside Google Flow.
activeTab	Access the currently focused tab to send automation instructions.
downloads	Save generated videos and images to your Downloads folder or a sub-folder you specify.
scripting	Execute text-input helpers in the Google Flow page context to type prompts reliably.
debugger	Send trusted click events to Google Flow's interface (see Section 4).
windows	Create a detached pop-out window for the control panel.

6. Host Permissions

The Extension requests access only to *://flow.google.com/* and *://labs.google/* (Google Flow's current and legacy addresses). It does not access any other website or domain, including your personal accounts, social media, banking, or search history. The Extension is completely inactive on all other domains.

7. No Third-Party Sharing

We do not sell, rent, or share any user data with third parties. The Extension contains no analytics, tracking pixels, advertising SDKs, 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 policy when the Extension's functionality changes. The "Last updated" date at the top of this page will reflect any revision. We recommend reviewing this page when you install a new version of the Extension. Continued use of the Extension after an update constitutes acceptance of the revised policy.

10. Contact

Questions about this Privacy Policy? Email us at veosupport@devoveagency.com or visit veoautomation.com/contact.