Privacy first

Privacy policy.

Last updated: April 2026

The short version. Your text stays on your device by default. No analytics, no telemetry, no tracking. The only network calls are to cloud AI providers you configure, plus a once-per-30-minutes subscription check if you're on Pro.

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, 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.

Data collection

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 accounts, ClipAction generates a random anonymous device identifier — a UUID with no personally identifiable information — stored locally on your device.

If you upgrade to Pro, this device identifier is sent to our subscription service (hosted on Supabase) 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 personal information, browsing data, or text content is ever included in these requests.

Payment processing is handled entirely by Stripe. ClipAction does not store or have access to your payment card details. Stripe's privacy policy applies to payment data.

Permissions

ClipAction requests only the minimum permissions needed to function:

activeTab
Read your selected text on the current page when you invoke the palette. No access to other tabs, history, or bookmarks.
contextMenus
Power the right-click menu so you can run actions without the shortcut.
storage
Save your preferences, custom prompts, site profiles, and subscription cache locally — nothing is synced.
scripting
Inject the command palette into the page you're on when you trigger it.
declarativeNetRequest
Set CORS headers so a local Ollama server can accept requests from the extension, if you choose to use Ollama.
http://localhost:11434/*
Optional host permission, requested only if you enable Ollama. Never granted by default.

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 encrypted local storage, never transmitted to us)
  • Custom prompts, 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

ClipAction connects to external services only in these cases:

  • Subscription verification — anonymous device ID sent to Supabase to check Pro status, cached for 30 minutes.
  • Payment processing — handled by Stripe when you choose to upgrade.
  • Cloud AI providers — OpenAI, Anthropic, Google Gemini, Groq, Mistral, xAI, Together, or OpenRouter — only if you explicitly add an API key. Your text is sent directly from your browser to that provider.
  • Ollama — if you run Ollama locally on localhost:11434, your text is sent to it over loopback. Nothing leaves your machine unless the Ollama model itself is configured to call out.

We do not share, sell, or otherwise transmit your data to any party not listed above.

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.