Privacy Policy

Privacy Policy

๐Ÿ“ฆ CreatorFlow โ€“ Tools for Grok, VEO & AI Creators ๐Ÿ“… Last Updated: May 2026 โœ‰ nguyendinhdungqd@gmail.com
โœ… Core Privacy Commitment

CreatorFlow does not collect, store, sell, or transmit any personal data to external servers.

All extension functionality runs entirely locally within your browser. No browsing history, prompts, images, videos, account credentials, or any personal information is ever transmitted to the developer or any third party.

โš  CreatorFlow is not affiliated with, endorsed by, or connected to Google, xAI (Grok), Meta, CapCut, ByteDance, or any third-party AI platform. This is an independent productivity tool. All product names and trademarks belong to their respective owners.

Summary
At a Glance โ€” What We Do and Don't Do
Personal Data Collected
โœ… None
Data Sent to Servers
โœ… None
Analytics / Tracking
โœ… None
Third-Party APIs Used
โœ… None
Data Sold to Third Parties
โœ… Never
Local Storage Used
โš™ Settings only
Section 1
What Data the Extension Reads

CreatorFlow reads only the minimum data required to provide its features. Specifically:

  • Active tab URL โ€” read once when the side panel opens, solely to detect which supported AI site is active and auto-switch the panel tab. The URL is never stored or transmitted.
  • DOM elements on supported AI sites โ€” the extension interacts with UI elements (buttons, text inputs, image upload areas) on the AI platform pages you are actively using. This interaction is performed locally in your browser. No DOM content, text, or images are extracted, stored, or sent anywhere.
  • Download file metadata โ€” when auto-saving generated media, the extension reads the filename and URL of the file being downloaded. This is used only to rename and organize files in your local Downloads folder. No file content is transmitted.
The extension does not read: your account credentials, session tokens, cookies, personal profile data, chat history, prompt history, or any content outside the supported AI sites.
Section 2
What Data Is Stored Locally

User settings and preferences are stored locally on your device using Chrome's built-in chrome.storage.local API. This data never leaves your device. The only data stored is:

  • Last active tool tab (VEO, Grok, Seedance, or Meta)
  • Download folder name and file prefix you have configured
  • Workflow settings you have set (e.g. number of concurrent prompts, delay between prompts)
  • UI language preference
  • Auto-download quality preference

This data is stored solely to restore your preferences between sessions. It is never read by the developer and never transmitted anywhere.

No prompts, images, videos, or AI-generated content are ever stored by the extension.
Section 3
Data Sent to External Servers

No data is sent to any external server by this extension.

All extension logic, UI, and configuration are bundled locally within the extension package. The extension makes no outbound network requests of its own. The only network activity that occurs is the normal browser traffic between your browser and the AI platforms you are using โ€” this traffic is entirely outside the extension's control and is governed by those platforms' own privacy policies.

The extension operates fully offline after installation. No telemetry, crash reports, usage statistics, or any other data is transmitted to the developer.
Section 4
Analytics, Tracking, and Crash Reporting

CreatorFlow contains no analytics libraries, tracking pixels, telemetry systems, crash reporting tools, or usage monitoring of any kind.

The developer has zero visibility into:

  • How often or when you use the extension
  • Which features or modes you use
  • What prompts or content you generate
  • Any errors or crashes that occur on your device
  • Your geographic location or device information
Section 5
Third-Party APIs and Services

CreatorFlow does not use any third-party APIs, SDKs, or external services.

The extension does not integrate with:

  • Advertising networks or ad SDKs
  • Analytics platforms (e.g. Google Analytics, Mixpanel, Amplitude)
  • Crash reporting services (e.g. Sentry, Bugsnag)
  • Data brokers or identity resolution services
  • Any developer-controlled backend API

The AI platforms themselves (Google Flow, Grok, Dreamina, Meta AI) are accessed directly by your browser as you normally would โ€” the extension only assists with UI interactions on those pages.

Section 6
Data Not Sold to Third Parties

We do not sell, rent, trade, or otherwise disclose any user data to third parties โ€” because we do not collect any user data in the first place.

This applies to all categories of personal information including but not limited to: identifiers, browsing history, usage data, content, geolocation, and inferences drawn from any of the above.

Section 7
Chrome Permissions Explained

CreatorFlow requests only the permissions strictly necessary for its features. Each permission is explained below:

PermissionPurpose & Scope
tabs Read the URL of the active tab only to detect which supported AI site is open and auto-switch the side panel. Also used to reload a tab after installation. No tab content, history, or URLs are stored or transmitted.
activeTab Interact with the currently open AI site tab when you initiate a workflow action. Used solely to assist with UI interactions on the active page at your request.
storage Save your local preferences (folder name, settings, last-used mode) in Chrome's local storage on your device. Data never leaves your device.
downloads Save AI-generated videos and images to your local device when generation completes. Files go directly to your Downloads folder. No file content is transmitted to any server.
sidePanel Display the CreatorFlow control panel in Chrome's built-in side panel UI.
debugger Purpose: Used exclusively to dispatch synthetic mouse input events on AI platform UI buttons that block standard programmatic DOM clicks.

Technical reason: Modern AI platforms (Google Flow, Grok, Dreamina, Meta AI) are built with React/Vue and intercept element.click() and dispatchEvent() calls, making them ineffective for UI interaction. The only reliable method is to use the Chrome DevTools Protocol (CDP) Input.dispatchMouseEvent command, which requires the debugger permission.

Exact CDP commands used:
  • Input.dispatchMouseEvent โ€” type: mouseMoved
  • Input.dispatchMouseEvent โ€” type: mousePressed
  • Input.dispatchMouseEvent โ€” type: mouseReleased

Strict scope โ€” what the debugger does NOT do:
  • Does not monitor network requests or responses
  • Does not read, capture, or extract any page content or DOM data
  • Does not intercept or inspect HTTP traffic
  • Does not take screenshots or record the screen
  • Does not access cookies, session tokens, or credentials
  • Does not transmit any data to external servers

Lifecycle: The debugger is attached to the active AI site tab only when you initiate a workflow action, used only to send the three mouse events above, and detached immediately after. No browsing history or unrelated website data is collected or transmitted.
Section 8
Host Permissions โ€” Supported Sites Only

The extension is active only on these specific websites as declared in the extension manifest:

  • labs.google โ€” Google Flow / VEO video and image generation
  • grok.com โ€” Grok / xAI image and video generation
  • dreamina.capcut.com and jimeng.jianying.com โ€” Seedance / Dreamina generation
  • meta.ai โ€” Meta AI image and video generation

The extension does not run on any other websites. It cannot access your general browsing activity, search history, or any sites outside this list.

Section 9
No Remote Code Execution

All extension logic, UI components, and configuration data are bundled locally within the extension package installed on your device. No JavaScript code, configuration files, or instructions are fetched from external servers at runtime.

This means the extension's behavior cannot be changed remotely without publishing a new version through the Chrome Web Store review process.

Section 10
Children's Privacy

This extension is not directed at children under the age of 13. We do not knowingly collect information from children. If you believe a child has used this extension and you have concerns, please contact us at the email below.

Section 11
Data Deletion Request

Since CreatorFlow does not collect or store any personal data on external servers, there is no user data held by the developer to delete.

The only data that exists is your local preferences stored in Chrome's local storage on your own device. You can delete this data at any time by:

  • Uninstalling the extension (Chrome will clear all associated local storage)
  • Going to chrome://extensions โ†’ CreatorFlow โ†’ "Clear data"

If you have any questions or requests regarding data, contact us at: nguyendinhdungqd@gmail.com

Section 12
Changes to This Policy

If this Privacy Policy is updated, the revised version will be published with the extension update on the Chrome Web Store. The "Last Updated" date at the top of this page will reflect any changes. Continued use of the extension after an update constitutes acceptance of the revised policy.