What we collect
- Encrypted data blobs. Opaque ciphertext we cannot decrypt. We do not see your files, file names, or folders.
- Opaque metadata needed to sync: content hashes, keyed path identifiers (not real paths), timestamps, data sizes, and per-device identifiers.
- Hashed access tokens for your devices (we store only a one-way hash).
- Transient IP address at the moment of a request, used only for rate-limiting/abuse prevention. It is held briefly in memory and not used to build a profile of you.
We do not require an account, email, or name to use the core sync. We do not run ads or sell data.
What we cannot access
Your file contents, file names, directory structure, and your encryption keys. These stay on your devices. The pairing code that links your machines carries your key and is generated and shared by you, out-of-band — we never receive it.
How we use what we hold
Only to operate the sync service: store and relay your encrypted blobs between your devices, enforce storage quotas, and keep the service reliable and abuse-free.
Data location & retention
Your encrypted data is stored on the relay server operated for the service. It persists until you delete a workspace or stop syncing. Because it is ciphertext, backups are also encrypted-at-source.
Your choices
- Stop syncing at any time; your local ~/.claude is always the source of truth and stays on your machine.
- Request deletion of a workspace's stored blobs by contacting us.
- Deleting a workspace removes its blobs from the relay.
Not for children
Continuum is a developer tool and is not directed to anyone under 18.
Changes
Material changes will be reflected by the "Last updated" date above.