Back to ContxtFlow
Privacy

Privacy Policy

Last updated: February 26, 2026

ContxtFlow is built on a simple principle: your data stays on your device. This policy explains what little data the extension interacts with, and how.

1

What Data We Collect

ContxtFlow is designed with a privacy-first architecture. We collect no personal data on our servers. The extension operates locally in your browser.

Data stored locally in your browser only:

  • OpenRouter API Key — stored exclusively in your browser's local storage or Chrome extension storage. It never leaves your device via ContxtFlow.
  • Extension preferences — settings such as keyboard shortcut configuration, stored locally in Chrome extension storage.

Webpage content — when you activate ContxtFlow on a page, the extension reads the visible text content of that page to build your AI prompt. This content is sent directly from your browser to OpenRouter and is never transmitted to ContxtFlow servers.

We do not collect, store, or process:

  • Your name, email address, or any account information
  • Browsing history or visited URLs
  • AI conversation content or prompts
  • Any analytics tied to individual users
2

How We Use Your Data

Because ContxtFlow does not collect personal data, there is no user data for us to use, sell, share, or analyze.

The webpage context extracted by the extension is used solely to fulfill your real-time request — constructing an AI prompt and sending it directly to OpenRouter on your behalf. This happens entirely within your browser session and is not retained by ContxtFlow.

We do not use any data for advertising, profiling, or behavioral tracking.

3

Data Storage & Security

All data associated with the ContxtFlow extension is stored locally on your device using Chrome's built-in extension storage APIs (chrome.storage.local). This data is sandboxed to the extension and is not accessible to websites or other extensions.

ContxtFlow maintains no databases, user accounts, or backend infrastructure that stores personal information.

To remove all locally stored data, you can uninstall the extension from Chrome, which will delete all associated storage.

4

Your API Key

ContxtFlow requires an OpenRouter API key to function. This key is:

  • Stored only in your browser's local Chrome extension storage
  • Never transmitted to ContxtFlow's servers
  • Sent directly from your browser to OpenRouter's API endpoints when you make a request

You are responsible for keeping your API key secure. If you believe your key has been compromised, revoke it immediately in your OpenRouter account dashboard.

5

Third-Party Services

OpenRouter

ContxtFlow uses OpenRouter as its AI inference provider. When you submit a prompt, your browser sends the request — including the extracted webpage context and your message — directly to OpenRouter's API. OpenRouter's privacy practices are governed by their own Privacy Policy. We encourage you to review it.

Simple Analytics

Our website (contxtflow.co) uses Simple Analytics, a privacy-friendly analytics provider that does not use cookies and does not collect personal data. This applies only to our marketing website, not to the Chrome extension itself.

6

Your Controls & Rights

You have full control over all data associated with ContxtFlow:

  • Delete your API key — clear it at any time from the extension settings panel.
  • Remove all data — uninstalling the extension from Chrome permanently deletes all locally stored data.
  • Revoke OpenRouter access — delete or rotate your API key in your OpenRouter account to stop all AI requests.

Since we store no personal data on our end, there is no account to delete or data to request from us.

7

Chrome Extension Permissions

ContxtFlow requests only the permissions necessary to function:

  • activeTab / scripting — to read the content of the currently active tab when you explicitly activate the extension via keyboard shortcut or toolbar button. The extension does not run in the background or monitor pages without your action.
  • storage — to save your API key and preferences locally in Chrome extension storage.

The extension does not request permissions to access all browser history, cookies, passwords, or background network activity.

8

Changes to This Policy

We may update this privacy policy as the extension evolves. Material changes will be noted in the extension's Chrome Web Store listing changelog. The "Last updated" date at the top of this page reflects the most recent revision.

Continued use of the extension after a policy update constitutes acceptance of the revised terms.

9

Contact Us

If you have any questions or concerns about this privacy policy or how ContxtFlow handles data, please contact us:

[email protected]

ContxtFlow · [email protected]