Skip to content

Privacy and security

KoNiMa Claude Sync syncs through your own git repository, not through our servers: KoNiMa receives neither your configuration nor your memories.

Your data doesn’t pass through KoNiMa’s servers

Configuration, memories, plugins and sessions travel only through the git repository you own and control. The only KoNiMa service the extension contacts is the license service, to verify your license.

No telemetry

The extension sends no usage statistics and no tracking. When you request a trial, an anonymous machine identifier is sent along with the form details: it can’t be traced back to you and only serves to prevent the trial from being requested more than once from the same computer.

Credentials stay on your machine

The git repository token and the license code are kept in VS Code’s protected storage, that is, in the operating system keychain. To sync even when VS Code is closed, Claude Sync keeps an encrypted copy of them that can only be used on this machine. Credentials are never written in plain text and never end up in the repository.

MCP servers: the structure travels, the secrets don’t

Before sending, the credentials (tokens, keys, passwords) in MCP server environment variables and headers are blanked: the repository receives the server definition, without its secrets. On a new machine you enter the credentials once; later syncs leave them where they are.

The choices stay yours

  • Before applying a change that arrives from your other machines, Claude Sync saves a local copy of what was there.
  • One machine doesn’t overwrite another’s work. When the same file changes in two places at once, the choice is yours: see Waiting for your decision in Troubleshooting.
  • Your edits to team items stay on your machine and, if the team publishes a new version, yours is kept until you choose which one to keep. See The dashboard.

A way back with every update

When you install a new version of the extension, Claude Sync keeps the previous state before the new version writes to your repository. In the same way, compacting the history leaves a recovery copy before reducing it.

Sessions travel encrypted

If you use session sync, each conversation is encrypted before it leaves the machine. Sessions are visible only to you and go out only when you ask with /sync-session.

Works offline too

Changes made without a network connection go out at the next sync that can run. The license, kept encrypted on the machine, keeps working offline for up to seven days after the last successful check.

Machine registry privacy

Machine activity dates in the repository are recorded by day, by design: no fine-grained activity tracking.