ContextMover operates on a zero-knowledge privacy model for your conversation data. Your AI conversations are captured and stored exclusively in your browser extension's local IndexedDB. They never travel through ContextMover servers.
Conversation content never stored on ContextMover servers
Optional sync to YOUR personal Supabase — ContextMover has zero access
AES-256-GCM encrypted vault credentials, keys never leave your device
You own all your data — export or delete at any time
ContextMover is built on the principle of minimal data collection. Here is a precise breakdown:
When you install the ContextMover browser extension, your AI conversations are captured and stored in your browser's IndexedDB — a local database accessible only to the extension on your own machine. This data never leaves your device unless you explicitly connect a personal Supabase vault.
If you choose to connect your own Supabase project as a “personal vault,” your session data syncs to your Supabase project — not ContextMover's. The vault URL and anon key are stored with AES-256-GCM encryption in your local browser storage, with the decryption key derived from your account credentials via PBKDF2. The encrypted credentials are never transmitted to ContextMover servers.
You may disconnect or delete your vault data at any time from Settings → Personal Vault. Disconnecting does not delete local or vault data — you retain full control.
We use Supabase Auth to manage user accounts. Authentication state is stored in cookies and localStorage strictly for session management. We do not use tracking cookies, advertising pixels, or third-party analytics.
We do not sell, rent, or share your personal information with third parties, except: (a) Supabase Inc., our database and authentication provider; (b) Stripe, our payment processor, for subscription billing only; (c) as required by applicable law.
You have the right to access, export, correct, or delete any personal data we hold about you. To exercise these rights, contact us at privacy@contextmover.app.
Because your AI conversation data is stored locally and/or in your personal vault, ContextMover cannot access it — requests for conversation data must be handled directly by you in your browser extension or Supabase dashboard.
We employ industry-standard security measures including TLS in transit, encrypted database storage (Supabase), and AES-256-GCM for vault credential encryption. Our zero-knowledge architecture means that even in the event of a ContextMover server breach, your conversation content cannot be compromised because it was never there.
We will post any changes to this policy on this page with an updated date. Continued use of ContextMover after changes constitutes acceptance of the revised policy. For material changes, we will notify you via email.
Questions about this policy? privacy@contextmover.app