Single purpose
ClipAction has a single purpose: to let you run AI-powered actions (rewrite, summarize, translate, etc.) on text you select in any web page, routing the request either to an on-device model or to a cloud AI provider you have configured with your own API key. All data handling described below is in service of that single purpose.
What we collect (summary)
The table below lists every category of user data ClipAction handles, why it's handled, where it's stored, and who it is shared with. "We" / "ClipAction" refers to the developer of the extension.
Stored by ClipAction: No. Not logged, not cached on our servers, not transmitted to us under any circumstance.
Shared with: Only the AI provider you chose for that action, either the on-device Chrome Gemini Nano model (stays on your device), a local Ollama server you run (stays on your device), or a cloud provider you configured with your own API key (OpenAI, Anthropic, Google Gemini, Groq, Mistral, xAI, Together AI, OpenRouter). The request goes directly from your browser to that provider. ClipAction never receives, proxies, or stores it.
Stored by ClipAction: No. Treated identically to selected text, not logged, not transmitted to us.
Shared with: Same as selected text, only the AI provider you chose for that action.
chrome.tts API, which speaks it using a voice you select.Stored by ClipAction: No. Not logged, not cached, not transmitted to us.
Shared with: Depends on the voice you pick. Local OS voices (Microsoft, Apple, eSpeak) process the text entirely on your device. Google network voices send the text to Google's text-to-speech service over the network for synthesis. ClipAction does not see, proxy, or store the text in either case. The voice you select is shown in the popup so you can choose accordingly.
Stored by ClipAction: Only on your own device, via Chrome's
chrome.storage.local. Never transmitted to ClipAction servers.Shared with: Only the provider that key belongs to, and only when you trigger an action.
Stored by ClipAction: Only on your own device, via Chrome's
chrome.storage.local.Shared with: No one. Not synced, not uploaded.
Stored by ClipAction: On your device via
chrome.storage.sync, and on our subscription database (Supabase) linked to your subscription row.Shared with: Supabase (our database host). Not shared with anyone else.
Stored by ClipAction: On our subscription database (Supabase), linked to your subscription row. Only collected if you choose to upgrade to Pro.
Shared with: Stripe (payment processor) and Supabase (database host). Not shared with anyone else.
Stored by ClipAction: Never. Card details are entered directly into Stripe's payment form and are never visible to ClipAction.
Shared with: Stripe only.
Stored by ClipAction: No. ClipAction holds no permissions that would allow access to browsing history, bookmarks, or other tabs.
Shared with: No one.
Stored by ClipAction: No. ClipAction uses no analytics SDK, telemetry, or tracking pixel of any kind.
Shared with: No one.
Text processing
ClipAction's default mode uses Chrome's built-in Gemini Nano model, which runs entirely on your device. Your selected text is never sent to any external server when using on-device processing.
Every result in the extension is labelled with the processing path that produced it:
- ● On-device: processed locally via Gemini Nano or a self-hosted Ollama instance. Your text never leaves your machine.
- ● Cloud: if you configure a third-party AI provider (OpenAI, Anthropic, Google Gemini, Groq, Mistral, xAI, Together AI, OpenRouter), your selected text is sent directly from your browser to that provider using your own API key. ClipAction never sees, stores, or proxies this data. Each provider's own privacy policy applies.
Analytics & tracking
ClipAction does not use any analytics service. No Google Analytics, no Mixpanel, no Sentry, no PostHog, no Amplitude, no Plausible. There are no tracking pixels, no fingerprinting, no session recording, and no advertising. We have no way to see what you type, select, or transform, by design.
Subscription & payments
ClipAction offers a free tier and an optional paid Pro tier. To manage subscriptions without requiring a full account, ClipAction generates a random anonymous device identifier, a UUID with no personally identifiable information, stored locally on your device.
This identifier is stored using Chrome's chrome.storage.sync, which means if you are signed in to Chrome with sync enabled it will be replicated by Google to other Chrome installs under the same profile. We use sync so you can keep Pro working when you set up Chrome on a new machine. The UUID has no personal information attached. If you upgrade to Pro, this device identifier is sent to our subscription service (hosted on Supabase, a Postgres database provider) to verify your subscription status. This check runs when you open the extension and is cached locally for 30 minutes to minimize network requests. No browsing data or text content is ever included in these requests.
Payment processing is handled entirely by Stripe. ClipAction does not store, see, or have access to your payment card details, those are entered directly into Stripe's hosted checkout form. Stripe collects your email address at checkout so they can send you a receipt; we store a copy of that email address against your subscription row so that if you reinstall the extension or switch computers, you can re-link your subscription to your new device using the "Restore purchase" button. Stripe's privacy policy applies to all payment data.
Permissions
ClipAction requests only the minimum permissions needed to function:
activeTab
contextMenus
storage
scripting
clipboardRead
clipboardWrite
tts
content_scripts (http://*/*, https://*/*)
declarativeNetRequest
http://localhost:11434/*
Local storage
ClipAction stores the following on your device, using Chrome's chrome.storage.local API:
- Your preferences and default model routing
- API keys you entered (stored in Chrome's local storage, sandboxed to this extension, never transmitted to us)
- Custom actions, action chains, and site profiles
- Keyboard shortcut assignments
- Action history (if you keep it enabled)
- The anonymous device UUID used for subscription checks
This data is never synced or transmitted to our servers. Uninstalling the extension deletes all of it.
Third-party services & sharing
ClipAction only shares data with the parties listed below, only for the purpose stated, and only to the extent required to provide the feature you asked for. We have no advertising, affiliate, or data-broker relationships of any kind.
- Supabase (database / subscription backend), receives your anonymous device UUID, and, if you're a Pro subscriber, your email address and Stripe customer/subscription IDs. Used solely to verify your subscription status and let you restore Pro across devices. Supabase privacy policy.
- Stripe (payment processor), receives your payment card, billing details, and email when you choose to upgrade to Pro. Used solely to process the payment and send you receipts. Stripe privacy policy.
- Cloud AI providers you configure: OpenAI, Anthropic, Google Gemini, Groq, Mistral, xAI, Together AI, or OpenRouter. Each one only receives data when you explicitly add its API key and choose it as the model for an action. In that case, the text you selected plus your API key are sent directly from your browser to that provider. ClipAction never sees or proxies that request. Each provider's own privacy policy applies.
- Ollama (optional, local): if you run Ollama on
localhost:11434, your text is sent to it over the loopback interface. Nothing leaves your machine unless the Ollama model itself is configured to call out. - Vercel (website host), hosts clipaction.dev. Vercel receives standard web server request logs (IP, user-agent, URL) when you visit the marketing site, per Vercel's privacy policy. No personal data is collected by the site itself.
We do not share, transfer, or sell your data to any party not listed above. We do not use your data for advertising, profiling, or any purpose unrelated to providing the extension's features.
We do not sell your data
ClipAction does not sell, rent, trade, or otherwise transfer user data to third parties for money or other valuable consideration. We do not use user data to train any machine-learning model. We do not use user data to build advertising profiles, creditworthiness profiles, or any other kind of profile. We will not start doing so in future without first obtaining your explicit, opt-in consent.
Retention & deletion
On your device. All data stored by ClipAction on your device persists until you either clear it from the extension's settings, uninstall the extension, or clear Chrome's storage for the extension. Uninstalling the extension removes all locally stored data.
On our servers. If you upgrade to Pro, your subscription row (anonymous device UUID, Stripe IDs, email, period end) is retained for as long as your subscription is active, plus a retention window after cancellation to handle refund and billing disputes. Your email is only used for subscription management and receipts. You can request deletion of your subscription row at any time by emailing the address in the Contact section below, we will verify the request and process it within 30 days. Deletion of your subscription row will cancel your Pro entitlement.
Stripe. Stripe retains payment records independently under its own retention policy, which is subject to financial-services regulations we cannot override. See Stripe's privacy policy.
Your rights
Depending on where you live, you may have the right to access, correct, export, or delete personal data we hold about you, and to object to or restrict certain processing. To exercise any of these rights, email the address in the Contact section below. We will respond within 30 days. We will not discriminate against you for exercising any of these rights.
Children's privacy
ClipAction is not directed to children under 13, and we do not knowingly collect personal data from children under 13. If you believe a child has provided us with personal data, please contact us and we will delete it.
Limited use & Chrome Web Store compliance
ClipAction's use of information received from Google APIs, and information received from any Chrome Web Store user, adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Specifically:
- We only use user data to provide or improve the single user-facing features described in this policy, that is, running the AI actions you trigger and managing your Pro subscription.
- We do not transfer user data to third parties except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to users.
- We do not use or transfer user data for serving advertisements of any kind.
- We do not allow humans to read user data unless (a) you give us explicit affirmative consent, (b) it's necessary for security purposes such as investigating abuse, (c) it's needed to comply with applicable law, or (d) the data is aggregated and used for internal operations, and even then only after being anonymized.
Selected text may include personal communications
Because you can run ClipAction on any webpage, the text you select may include personal communications such as emails (e.g. Gmail, Outlook on the web), chat messages (e.g. Slack web, WhatsApp Web, Discord web), SMS mirrors, or draft messages. When you invoke an action on such text, that text is transmitted under the rules described above: on-device mode keeps it on your machine; cloud mode sends it to the provider whose API key you configured. ClipAction never reads, stores, or transmits the content of any page you have not explicitly selected text on and invoked an action against.
Secure transmission
All network traffic initiated by ClipAction uses TLS (HTTPS). This includes:
- Subscription checks to Supabase (HTTPS).
- Payment flows handed off to Stripe Checkout (HTTPS).
- Calls to every supported cloud AI provider (HTTPS, OpenAI, Anthropic, Google, Groq, Mistral, xAI, Together, OpenRouter).
The only non-HTTPS connection supported is an optional local Ollama server at http://localhost:11434, which never leaves your machine.
In-product disclosure
In addition to this policy, ClipAction surfaces data-handling disclosures inside the extension itself:
- A welcome page shown on install summarises what is collected and under what conditions.
- The Upgrade button in the popup is accompanied by a disclosure naming email, the anonymous device ID, and Stripe before you proceed to checkout.
- The cloud AI providers section in Settings carries a disclosure stating that adding an API key confirms you agree to send your selected text to that provider.
- Every result in the palette is tagged with an On-device or Cloud badge so you can see, per action, where processing happened.
Verifiability
You can verify every claim on this page yourself using Chrome DevTools. Right-click the extension icon → Inspect popup, open the Network tab, then use ClipAction:
- In on-device mode, you will see no outbound requests during text processing.
- Subscription checks go only to a Supabase endpoint and contain only the anonymous device UUID.
- Cloud mode shows requests going directly to the provider's domain you configured, never to a ClipAction server.
The extension source is delivered unminified in the Chrome Web Store package. You can audit it at chrome://extensions → Details → Inspect views: service worker.
Changes to this policy
If we change how ClipAction handles data, we update this page and bump the "last updated" date at the top. Material changes (new data collection, new third parties) will also be surfaced in the extension itself before they take effect.
Contact
Questions about this policy, or a specific request regarding your data? Email clipactionsupport@protonmail.com.