Privacy Policy · Context Move

Context Move is local-first. Your conversations, summaries and search indexes are stored on your own machine — in the desktop application’s database, or inside your browser when you use the extension. There is no Context Move server holding your data, and nothing is uploaded anywhere unless you explicitly turn a feature on.

This policy covers the Context Move desktop application and the Context Move browser extension. Both are published by Context Move (“we”, “us”).

The short version

We do not operate a server that receives your conversations. We cannot read your data, because it never reaches us. Context Move runs no AI models and sends your conversations to no one, not to us, and not to any model provider. The only features that touch a third party are Google sign-in, Google Drive backup, the update check, and opt-in crash reporting, each described individually below. Signing in tells us who you are; it carries none of your conversations with it.

01What the desktop app stores, and where

Everything the app captures is written to a local SQLite database on your computer. On macOS and Linux this lives in the standard per-user application data directory; on Windows it lives in the application’s own program directory. It contains:

Conversation transcripts you choose to capture
Summaries, titles and continuation prompts derived from them
Search and retrieval indexes built over that content
Files and attachments that accompanied a captured conversation
Your local settings and preferences

We have no access to this database. It is not synchronised, mirrored or backed up by us. If you delete it, it is gone.

Credentials

Account-level secrets, principally your Google Drive refresh token, are held in your operating system’s credential store (Windows Credential Manager, macOS Keychain, or the Linux Secret Service) wherever one is available. On a system that provides no credential store, the application falls back to storing them in its local configuration file under a clearly marked key. In either case the secret stays on your machine and is never transmitted to us.

What we never collect

No password: signing in goes through Google, and we never see or store one (see Signing in with Google)
No advertising identifiers, tracking pixels or analytics SDKs
No browsing history, and no page content outside the AI chat sites you explicitly capture from
No selling, renting or sharing of personal data with third parties: we hold none to sell

02The browser extension

The Context Move extension captures a conversation you are looking at on a supported AI chat site, together with the files attached to it, and keeps it so you can search it later and carry it into another AI.

Where the data goes

It stays in your browser. The extension keeps your conversations, their summaries, their search indexes and their attached files in its own private storage inside the browser, on your computer. It does not contact any Context Move server, because none exists, and it contains no analytics, telemetry or tracking code of any kind.

Two optional features send data anywhere at all, and only where you send it: Google sign-in (section 03) and Google Drive backup (section 04), each to Google, under your own account.

Earlier versions of the extension instead forwarded captures to the Context Move desktop application over http://localhost, and the current version can still read from that application once, if you ask it to bring an existing vault across.

Removing the extension deletes your vault

Because the data lives inside the browser, uninstalling the extension removes it, as does clearing the browser’s site data for it. That is a deliberate consequence of keeping nothing on a server. Use Settings → Backup & Move to download a backup file, or connect Google Drive, before you remove it.

What it reads, and why each permission is needed

Permission	Why it is needed
Chat site access	To read the conversation you have chosen to capture from ChatGPT, Claude, Gemini, Grok, DeepSeek, Perplexity, Copilot, Lovable and Replit, and to paste a carried-over conversation into a new chat on those sites. The extension activates only on these sites.
Provider file domains	Attachments in a conversation are hosted on the provider’s own file and CDN domains. Access is required to download the files belonging to the conversation you are capturing, so they can be saved alongside it. Requests are restricted to those domains and to the chat site you are on.
`localhost`	To import an existing vault from the Context Move desktop application running on your own machine, when you choose to.
`googleapis.com`	To upload and download your backups in your own Google Drive, if you connect it.
`identity`	To sign in with Google (section 03).
`storage`, `unlimitedStorage`	To keep your saved conversations, their files and your preferences in the browser.
`offscreen`	To run the local database that holds them.
`notifications`	To tell you a capture succeeded, and to warn you when a chat site says you are near its usage limit.
`alarms`	To schedule the daily Google Drive backup, if you connect it.
`clipboardWrite`	To copy a generated continuation prompt when you ask for it.

Conversation content is read only when you trigger a capture. The extension does not run in the background collecting your chats.

Context Move asks you to sign in with Google once, so that an account exists to attach a purchase to. Sign-in identifies you; it does not give us your conversations, and it is not a place your data is stored.

What we receive

Your Google account’s email address, display name and profile picture URL
An account identifier issued by our authentication provider

That is the whole of it. We receive no password, no contacts, no calendar, no files and no conversation content.

Where it is held

Accounts are handled by Supabase, acting as our processor, which records the email address and sign-in dates. The session itself is kept on your own device: in your operating system’s credential store for the desktop application, and in the extension’s private browser storage for the extension, where the sites you visit cannot read it.

Signing out, in the extension’s Settings → Profile, removes the session from your device. Your conversations stay where they are.

04Google Drive backup (optional)

Context Move can back up your saved conversations, and the files attached to them, to your own Google Drive so that you can move them to another machine or recover them later. This applies to both the desktop application and the extension. The feature is off until you connect it, and can be disconnected at any time. In the extension it then refreshes about once a day while your browser is open, which you can turn off in Settings → Backup & Move.

The scope we request

Context Move requests exactly one Google scope: drive.file. This grants access only to files the application itself creates. Context Move cannot see, read or list any other file in your Google Drive, not because we promise not to look, but because Google does not give us the ability.

What is stored, and who owns it

Backups are written to a visible folder named “ContextMove Backups” in your Google Drive, under your Google account. They are your files. You can inspect them, download them or delete them at any time without involving us. We never receive a copy; the transfer is directly between your computer and Google.

Limited Use disclosure

Context Move’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically: data obtained through Google APIs is used solely to provide the backup and restore feature described above. It is not transferred to any third party, is not used for advertising, is not sold, and is not read by humans.

Revoking access

Disconnect Drive inside Context Move, or revoke the application entirely at myaccount.google.com/permissions. Revoking access does not delete backups already in your Drive: those remain yours to keep or delete.

05AI models and inference

Context Move runs no AI models and performs no inference. Summaries, titles and continuation prompts are produced deterministically, by selecting text out of the conversation itself rather than generating prose about it. Search is a local keyword index built on your machine. The installer downloads no models, and the application contacts no model, local or remote.

There is therefore no API key to supply and no AI provider to configure. The text of your conversations is never sent to any model provider, because the application never calls one. A consequence worth stating plainly: nothing you capture can end up in anyone’s training data by way of Context Move.

If a future version introduces a hosted inference feature, it will be opt-in, described clearly at the point of use, and this policy will be updated before that version ships.

06Software update checks

Context Move checks for new versions by making an anonymous request to the public GitHub releases API for its distribution repository. The request carries no account, no identifier and no information about your saved conversations; as with any web request, GitHub sees the connecting IP address and receives it under their own privacy statement. This is the only channel by which a shipped bug can reach you as a fix.

07Crash reporting (opt-in)

Crash reporting is off until you enable it. You are asked once during onboarding; declining, or never answering, counts as no. You can change the setting at any time in Settings → Tools → Privacy.

When enabled, a crash report contains the exception, the stack trace through Context Move’s own code, the application version, and the operating system. Before transmission:

Stack-frame local variables are dropped entirely
Your home directory path is collapsed to ~ and your username is removed
Strings shaped like credentials (API keys, OAuth secrets, access tokens) are redacted

Conversations, summaries, titles, searches and keys are never included. Reports are processed by Sentry acting as our processor.

Exporting a folder produces a .cvpack file on your disk. It leaves your machine only if you send it to someone. Note that a pack contains full conversation transcripts, not just summaries: treat it as you would the conversations themselves.

09Retention and deletion

Because we hold no copy of your conversations, deleting them is entirely in your hands: delete individual conversations, empty the recycle bin, uninstall the desktop application or remove the extension (which deletes everything it stored in the browser), and delete the “ContextMove Backups” folder in your Google Drive if you used backup. Nothing survives on our side, because nothing was ever there.

The one record we do hold is your account: an email address and sign-in dates, kept by our authentication provider. To have it deleted, write to contact@contextmove.com and it will be removed within 30 days.

10Children

Context Move is not directed to children under 13, and we do not knowingly collect information from them.

11Changes to this policy

If this policy changes materially, we will update the effective date above and note the change on this page. Continued use after an update constitutes acceptance of the revised policy.

12Contact

Questions about this policy, or about data handling in Context Move, can be sent to contact@contextmove.com.