Privacy Policy.

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

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 account registration, email address or password
• 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 exists for one purpose: to send a conversation you are looking at, and the files attached to it, from a supported AI chat site to the Context Move application running on your own computer.

Where the data goes

The extension transmits captured conversations to http://localhost on ports 8000–8009: your own machine, over the loopback interface. It does not contact any Context Move server, because none exists. It contains no analytics, telemetry or tracking code of any kind. If the desktop application is not running, the capture simply fails.

What it reads, and why each permission is needed

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

03Google Drive backup (optional)

Context Move can back up your saved conversations to your own Google Drive so that you can move it to another machine. This feature is off until you connect it, and can be disconnected at any time.

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.

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.

04AI 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.

05Software 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.

06Crash 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.

07Folder sharing

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.

08Retention and deletion

Because we hold no copy of your data, deletion is entirely in your hands: delete individual conversations in the app, delete the local database to remove everything, uninstall the application, and delete the “ContextMove Backups” folder in your Google Drive if you used backup. Nothing survives on our side, because nothing was ever there.

09Children

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

10Changes 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.

11Contact

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