Privacy Policy — Whisk Automator

Last updated: August 9, 2026

Whisk Automator ("the extension") is a browser extension that automates bulk AI image generation on Google Flow and optionally helps upload the results to the user's own Google Drive and Adobe Stock account. This page explains what data the extension handles, and — just as importantly — what it does not do.

In short: Whisk Automator does not run its own servers, does not sell or share your data, and does not use your data for advertising. Everything the extension stores lives in your own browser or your own Google Drive account.

1. What data the extension stores locally

The extension uses Chrome/Edge's built-in storage.local API to save the following, only on your own device:

This data is never transmitted to us. It stays in your browser's local storage unless you explicitly connect a service (see below), in which case it is sent only to that service, directly from your browser.

2. Google Drive (optional feature)

If you enable "Google Drive Auto-Upload" in Settings, the extension asks you to sign in with your own Google account (via standard OAuth) and requests the drive.file scope — which only allows access to files the extension itself creates, not your existing Drive files. Generated images and configuration files (such as config.json and prompts.json) are uploaded directly from your browser to your own Google Drive. We do not have access to this data — it never passes through any server we operate.

3. Adobe Stock FTP (optional feature)

FTP credentials you enter are stored locally and, if Drive upload is enabled, are also written (in a lightly obfuscated form, not strong encryption) to a config.json file in your own Google Drive so that your own separate Google Colab pipeline can read them. These credentials are used only to connect to Adobe's official SFTP server (sftp.contributor.adobestock.com) — never sent anywhere else.

4. License verification

If the extension requires a license key, that key is sent to a license-verification endpoint (hosted on Google Apps Script) solely to check whether the key is valid and unexpired. No other personal data is sent with this request.

5. Third-party AI providers (optional)

If you choose to use AI-generated metadata (Groq, Google Gemini, OpenRouter, Hugging Face, or a custom OpenAI-compatible endpoint) and provide your own API key, your prompts/images are sent directly from your browser to that provider's API to generate titles and keywords. This only happens if you actively choose that provider and supply your own key. We do not see or store this traffic.

6. What we do not do

7. Data retention & deletion

All locally stored data can be cleared at any time via the extension's Settings tab (History → Clear All) or by removing the extension entirely, which erases its local storage. Files placed in your own Google Drive or uploaded to Adobe Stock are governed by your Google and Adobe accounts respectively, and can be deleted by you at any time through those services.

8. Changes to this policy

If this policy changes, the "Last updated" date at the top of this page will be revised. Continued use of the extension after changes constitutes acceptance of the updated policy.

9. Contact

For questions about this privacy policy, please reach out via the contact details provided on the extension's store listing page.