ContxtFlow consists of two parts: a Chrome extension and a web application. Each handles data differently.
Chrome extension (stored locally):
Website & web application (server-side):
We use the data we collect for the following purposes:
We do not use your data for advertising, profiling, or behavioral tracking. We do not sell your data to third parties.
Extension data 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.
Server-side data (accounts, sessions, usage logs, and saved conversations) is stored in a PostgreSQL database hosted in the EU. All connections to our servers are encrypted via TLS. We apply the principle of least privilege to database access and regularly review our security practices.
To remove extension data, uninstall the extension from Chrome. To remove server-side data, delete your account from the account settings page — this permanently deletes all associated data.
When you send a message through ContxtFlow, the request flows through our servers:
Your prompts and page context pass through our servers but are not stored after the request completes (except when you explicitly save a conversation, or in aggregate usage logs that record model, token count, and cost without prompt content).
OpenRouter
ContxtFlow uses OpenRouter as its AI inference provider. When you submit a prompt, the request — including the extracted webpage context and your message — is sent from ContxtFlow servers to OpenRouter's API. OpenRouter may route requests to underlying model providers (such as Google, Anthropic, or OpenAI). OpenRouter's privacy practices are governed by their own Privacy Policy.
Google OAuth
We use Google OAuth for account authentication. When you sign in with Google, we receive your name, email address, and profile image. We do not access any other Google account data. See Google's Privacy Policy.
Simple Analytics
Our website 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.
You have full control over your data:
ContxtFlow requests only the permissions necessary to function:
The extension does not access your browser history, cookies, passwords, or any data beyond the content of the page you explicitly activate it on.
We may update this privacy policy as the service evolves. Material changes will be communicated via a prominent notice on the Service.
Continued use of the Service after a policy update constitutes acceptance of the revised terms.
If you have any questions or concerns about this privacy policy or how ContxtFlow handles data, please contact us:
[email protected]Under the General Data Protection Regulation (GDPR), we process your personal data on the following legal bases:
If you are in the European Economic Area (EEA), you have the following rights under the GDPR:
You also have the right to lodge a complaint with your local data protection authority if you believe your rights have been violated.
If you are a California resident, the California Consumer Privacy Act (CCPA) grants you additional rights regarding your personal information.
Categories of personal information we collect:
We do not sell your personal information. We do not share your personal information for cross-context behavioral advertising.
You have the right to know what data we collect, request deletion, and opt out of any future sale of personal information. To exercise these rights, contact us at [email protected] or use the data export and account deletion features in your account settings.
Your data may be processed by third-party service providers located outside the European Economic Area, including in the United States. Where such transfers occur, they are protected by appropriate safeguards:
We ensure that any international transfer of your data is subject to adequate protection measures in compliance with the GDPR.
We use the following third-party subprocessors to deliver the Service:
We will update this list when we add or change subprocessors and will notify you of material changes.