Privacy Policy — Grok Automate

Last updated: July 23, 2026 Hosted version: https://grokautomate.com/privacy

Grok Automate ("we", "us", "the extension", "the Service") is an unofficial, third-party browser extension that helps you queue prompts and download generated assets on grok.com. We are not affiliated with, endorsed by, or sponsored by xAI Corp. or any of its products.

Grok Automate is free to use — it processes no payments and collects no payment data, and there is no active billing integration. An optional account sign-in (handled on our website, grokautomate.com) syncs your plan tier for higher automation limits; it is free through 2026 and never asks for payment.

This document explains what data the extension handles, where it goes, and how to delete it. Sections 1–4 and 6 cover everything that is always true. Section 5 applies only if you choose to create an account and sign in.


1. TL;DR

If you use the extension without signing in (the default):

  • We do not collect, transmit, sell, share, rent, lease, or log any of your personal information.
  • All data the extension produces (prompts, queue state, downloaded images and videos, settings) stays in your own browser and your own downloads folder.

If you create an account and sign in (optional):

  • Authentication is handled by Google Firebase on our website. We store a small account record in Google Cloud Firestore — your name, email, and plan tier — so the extension can display your correct plan.
  • There is no payment processing of any kind. We never collect a card number, bank details, or any payment information, because the extension is free.
  • We do not sell your account data, and we do not share it with advertising or analytics third parties.

Separately, our website (grokautomate.com) uses Google Analytics and Google AdSense, which set cookies in your browser. The extension itself ships neither. See Section 5.5.

You can verify every claim above by reading the source code linked from the Chrome Web Store listing.


2. Data the extension stores locally (with or without an account)

The following data is stored only in your browser using the standard Chrome storage APIs. None of it is transmitted to servers we operate.

DataWhere it livesWhy
Your prompts and prompt historychrome.storage.localSo your queue survives a browser restart.
Uploaded reference images for image-to-videoIndexedDB (grok-auto database)Re-uses the image across queue items; deleted after the item succeeds.
Queue state (pending / running / failed items)chrome.storage.localLets the queue resume after the browser was closed.
Generation parameters (resolution, duration, aspect ratio, picker action)chrome.storage.sessionPer-session preferences.
Daily prompt counter (dailyStats.used)chrome.storage.localDrives the "X / 25" progress bar in the popup. Tracked locally only — never synced to our servers.
Your settings (download folder, retry config)chrome.storage.localHonored on every run.
A cached copy of your account (name, email, plan) — only if you sign inchrome.storage.local under userProfileSo the popup can show your plan without an async round-trip.
Diagnostic logs (Logs tab)chrome.storage.local (last 200 entries)Shown in the Logs tab so you can see queue activity. Cleared with the Clear button or on uninstall.

You can clear all of it at any time from chrome://extensions/ → Grok Automate → Site settingsClear data, or by uninstalling the extension.


3. Network traffic the extension causes

The extension operates on grok.com and, when you generate something, fetches the resulting asset from imagine-public.x.ai (xAI's own CDN). It does not ship any analytics, telemetry, crash reporter, error tracker, ad SDK, A/B-test framework, fingerprinting code, or remote configuration endpoint.

The two grok.com / xAI interactions are:

  1. Requests Grok.com makes itself. The extension does not initiate these. It only watches outgoing /rest/app-chat/conversations/new requests and, when Grok's own UI loses the prompt you typed, rewrites the in-flight request body to re-insert that prompt. The destination, headers, cookies, and authentication of the request are entirely controlled by Grok.com — we never add, remove, or forward anything to a third party.
  2. Asset downloads. When generation finishes, the extension downloads the resulting image/video directly from xAI's public CDN (https://imagine-public.x.ai/...) using Chrome's built-in chrome.downloads API. The file goes straight to your local Downloads folder.

If you have signed in, the extension additionally reads your plan tier from Google Cloud Firestore (see Section 5). There is no billing service and no payment traffic.


4. Permissions and why we ask for them

Chrome will prompt you to approve these on install. We ask for the minimum needed for the features you see in the UI.

PermissionWhy it's needed
storageTo remember your queue, settings, daily counter, cached account profile and reference images across browser restarts. Stored locally.
downloadsTo save the generated images and videos to your Downloads folder when each generation completes.
tabsTo find the grok.com tab the queue is running in, refresh it between items, and post each prompt to the right tab.
scriptingTo clear stale Grok client-side state (localStorage, IndexedDB, cache) between queue items so prompt N doesn't get contaminated by prompt N-1.
alarmsTo keep the service worker alive briefly and schedule the next queue item while a queue is running, and to reset the local daily counter at UTC midnight.
debuggerThe reason for the yellow "Grok Automate started debugging this browser" bar at the top of grok.com while the extension is running. Grok's TipTap/ProseMirror editor and React form-state only accept trusted keyboard input — synthetic events fired by a normal content script are ignored, which leaves the queue stuck. The Chrome DevTools Protocol is the only way to type prompts and press Enter in a way Grok's React state actually sees. We attach the debugger only to grok.com tabs, only while a queue item is processing, and detach automatically (35 s timeout) after each item. We never use it on any other site.
Host permission https://grok.com/*Required so the content scripts can run on grok.com — inject the side panel, type into the editor, observe completion, and capture generated image URLs.
Host permissions https://grokautomate.com/* and https://www.grokautomate.com/*Used only by a small content script on our own site (apex and www) that reads your optional sign-in state (name, email, plan) from a hidden page element and caches it locally, so the popup shows your correct plan. It reads no other page content and writes nothing to the site.

The extension has no other host permissions. It cannot read, write, modify, or inject anything on any site other than grok.com and our own grokautomate.com (apex and www).


5. Optional account data (only if you sign in)

This section applies only to users who choose to create an account and sign in. Everyone else skips it entirely — they never trigger any of the behaviour described below. There is no paid tier and no billing; the optional account only carries a plan tier for higher automation limits, free through 2026.

5.1 Authentication (Google Firebase, on our website)

Creating an account and signing in happens on our website (grokautomate.com), because Firebase Authentication cannot run from a chrome-extension:// origin. We support:

  • Email + password
  • Sign in with Google (OAuth)

Firebase Authentication (a Google service, governed by Google's Privacy Policy at https://policies.google.com/privacy) receives and stores standard authentication data about you:

FieldSourcePurpose
Email addressYou typed it / your Google account provided itAccount identifier, recovery
Hashed password (email sign-up only)You typed it; Firebase hashes it before storage — we never see plaintextAuthentication
Firebase user IDGenerated by FirebaseInternal account key
Sign-in timestampsGenerated by FirebaseSecurity and abuse prevention
IP address of the sign-in requestFirebase serverAbuse prevention (rate limit, geo block)

The extension itself never handles your password. It reads only the resulting profile (name, email, plan) — either from our website via the grokautomate.com content script, or by looking up your email in Firestore — and caches it locally.

5.2 Account record (Cloud Firestore)

On sign-up we create one document per user at users/{uid} in Cloud Firestore, containing only this:

{
  "firstName": "Jane",
  "lastName":  "Doe",
  "email":     "you@example.com",
  "role":      "user",
  "plan":      "free" | "pro",
  "createdAt": <server timestamp>,
  "updatedAt": <server timestamp>
}

We do NOT store: your password (that lives only in Firebase Auth, not in this record), any payment or card data (there is none), address, phone number, profile picture, country, currency, IP address, browser fingerprint, the contents of your prompts, or the contents of your generated images.

Your daily usage counter is tracked locally in your browser (chrome.storage), not in this record — it is never synced to our servers. A subset (name, email, plan) is cached in chrome.storage.local.userProfile so the popup can show your plan without an async round-trip.

5.3 Operational processing

The extension reads your plan tier from Google Cloud Firestore directly (client-side reads). We do not operate a separate application backend that stores the contents of your prompts or generations. Google's own infrastructure keeps standard operational logs for Firebase/Firestore governed by Google's policies. We never log the contents of your prompts, your generated images, or your password.

5.4 What we DO NOT do with account data

We do not, and never will:

  • Sell your name, email, or prompt history to anyone, ever.
  • Use your data to train an AI model.
  • Send you marketing email unless you separately opt in.
  • Share your account data (name, email, plan tier) with advertising or analytics third parties. Website ad and analytics cookies are a separate matter and are disclosed in Section 5.5 — they are never joined to your account record.
  • Use your data for credit scoring or lending decisions.

5.5 Website analytics and advertising (grokautomate.com only)

This section applies to our website only. The browser extension contains no analytics, no ad SDK, and no tracking code of any kind — see Section 3.

When you visit grokautomate.com, we use:

ServiceWhat it doesData involved
Google Analytics 4Measures pageviews and which pages and tools people use, so we know what to improve.Cookies, IP address (truncated by Google), pages viewed, approximate location, device/browser.
Google AdSenseServes the ads that keep the site free.Advertising cookies and device identifiers.

Specifically, as required by Google's policies:

  • Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites.
  • Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to our site and/or other sites on the internet.
  • You can opt out of personalised advertising by visiting Google Ads Settings. You can also opt out of third-party vendor cookies at aboutads.info/choices.
  • You can opt out of Google Analytics entirely with the Google Analytics Opt-out Browser Add-on, or by blocking cookies in your browser.

We do not send your prompts, generated images, account email, or any data from the extension to Google Analytics or AdSense. Website analytics and advertising are never linked back to your Grok Automate account.

If you are in the EEA, UK, or Switzerland, Google's advertising is governed by Google's EU User Consent Policy. Where that policy requires it, a consent message is presented before personalised ads are served, and you can change or withdraw your choice at any time through that message or through Google Ads Settings.


6. Sensitive data we explicitly do NOT touch (with or without an account)

  • Payment cards, banking info, ID documents, health data, location, contacts, calendars — the extension never reads or writes any of these. The extension processes no payments and collects no payment data.
  • The password for your Grok Automate account is handled exclusively by Firebase Authentication on our website; the extension never sees it.
  • Your Grok / xAI / X account credentials and cookies. We never read, copy, export, or transmit them. We rely on whatever authenticated session is already in your browser, exactly like a normal visit to grok.com would.
  • Browsing history outside of grok.com and grokautomate.com. The extension cannot see it because it has no host permission for any other domain.

7. Children

The extension is intended for adults using Grok's commercial services under xAI's own age requirements. We do not knowingly collect any information from anyone under 13 (or 16 in jurisdictions where that is the GDPR-K threshold). If you believe a minor has created an account, email us and we will delete the account.


8. Your rights

If you have not signed in

There is no server data to access, correct, or delete — everything is in your own browser. Clearing the extension's storage or uninstalling it deletes everything.

If you have an account

You can, at any time:

  • Access the data we hold about you by emailing privacy@grokautomate.com; we will send a plain-language summary of your Firestore document within 30 days.
  • Correct your details through your account settings or by contacting privacy@grokautomate.com.
  • Export your account record as JSON by emailing privacy@grokautomate.com (we respond within 30 days).
  • Delete your account by emailing privacy@grokautomate.com with the subject line "Delete my account". Account deletion:
    1. Deletes your Firestore users/{uid} document immediately.
    2. Deletes the Firebase Authentication record (email, hashed password) immediately.

We comply with GDPR data-subject requests, CCPA right-to-know / right-to-delete requests, and the equivalent rights in other jurisdictions.

Contact

privacy@grokautomate.com

We respond to privacy enquiries within 30 days.


9. Compliance with Chrome Web Store policies

We declare, for the Chrome Web Store review:

  • The extension's single purpose is: queueing prompts on grok.com/imagine and saving the resulting images/videos to disk.
  • The extension does not sell user data to third parties.
  • The extension does not use or transfer user data for purposes unrelated to its single purpose. (Optional account data is used only to display the correct plan tier and enforce automation limits. It is never re-purposed for marketing, advertising, or analytics.)
  • The extension does not use or transfer user data to determine creditworthiness or for lending purposes.
  • All data handling is consistent with this Privacy Policy, posted at https://grokautomate.com/privacy.

10. Changes to this policy

If we ever change the data-handling behaviour (for example, if we add a new optional integration), we will update this document, raise the version number of the extension, and the Chrome Web Store update prompt will surface the change before you upgrade.

You can always see the diff at the project's source repository linked from the Chrome Web Store listing.