Privacy-First Architecture

Continu Privacy Policy

Effective Date: September 10, 2026

Core Promise: Continu does not track you, does not log your browsing habits, does not inject advertisements, and never sells user data. All conversation contexts are protected by client-side End-to-End Encryption (AES-256-GCM).

1. Single Purpose Overview

Continu is a universal cross-platform AI context manager and prompt optimizer. Its sole purpose is to allow users to capture conversation contexts, store them locally, optionally synchronize them across their devices, and insert or arm contexts when interacting with web-based AI chat assistants.

2. Data Collection and Usage

Conversation Contexts: When you click "Extract & Save" or drop contexts, Continu generates structured summaries (e.g., goals, decisions, constraints). This data is stored locally in your browser using chrome.storage.local.
Zero Plaintext Cloud Access: If you sign in to sync contexts across devices, your contexts are encrypted locally on your device using AES-256-GCM with PBKDF2 key derivation before being transmitted to our secure cloud database (Supabase). The encryption key is derived on your device; our servers receive only ciphertext and cannot read your conversations.
User Authentication: We support optional sign-in via Google OAuth (using Chrome's secure identity.launchWebAuthFlow). We receive your public user ID and email address solely to associate your encrypted vault with your account.
AI Provider API Keys: If you configure an AI API key for prompt cooking (e.g., OpenAI, Claude, Gemini, Groq, or OpenRouter), your API key is stored strictly on your local device in chrome.storage.local. API calls are sent directly from your browser to the designated AI provider's official API endpoint over HTTPS. Your API keys are never sent to our servers.
Zero Tracking & Zero Telemetry: We do not use third-party analytics, behavioral tracking cookies, or advertising SDKs.

3. Chrome Extension Permissions Justification

Continu requests only the minimum permissions required to perform its functions:

storage & unlimitedStorage: Used to store your saved contexts, themes, and configuration locally on your machine.
activeTab: Used to detect the active AI chat composer, read conversation turns on demand when requested by the user, and insert prompts into the composer.
tabs: Used to identify page titles and URL transitions on AI chat web applications to properly name saved contexts.
identity: Used to securely handle Google OAuth sign-in without embedding web login credentials.
host_permissions (<all_urls> & https://*.supabase.co/*): Required to communicate with your Supabase database for encrypted backup and to support universal AI chat applications across all domains (including major providers like ChatGPT, Claude, Gemini, Perplexity, DeepSeek, and custom or self-hosted AI chat apps such as Open WebUI, Ollama, and LibreChat).

4. Data Retention and Deletion

You have complete control over your data:

Local Deletion: You can delete any saved context at any time by clicking "Delete" in the extension interface or by clearing extension storage.
Cloud Deletion: Deleting a context locally immediately propagates the deletion to the cloud database.
Account Deletion: Signing out or requesting account deletion removes your encryption vault and associated records permanently.

5. Third-Party Services

Supabase: Cloud database infrastructure for storing encrypted ciphertext. Protected by Row-Level Security (RLS).
AI Model Providers (User-Configured): When using prompt cooking, your prompt text is processed according to the privacy policy of the specific provider you chose (e.g., OpenAI, Anthropic, Google, Groq, OpenRouter).

6. Contact Us

If you have any questions or security inquiries regarding this policy, please contact:

Developer: Chirag Damani
Email: damanichiru38@gmail.com
Project Repository: github.com/CHIRAG-DAMANI-08/Continu