Privacy and security
KoNiMa Claude Sync is built around a simple principle: your data stays yours. Syncing happens through your own git repository, not through our servers.
Your data doesn’t pass through KoNiMa’s servers
Configuration, memories, and the plugin inventory travel exclusively through the git repository that you own and control. The only KoNiMa endpoint the extension contacts is the license API, and only to validate the license.
No telemetry
The extension sends no analytics or tracking. The only outbound call is the license validation; when you request a trial, an anonymized machine identifier (a salted, one-way hash) is sent solely to prevent abuse — the raw identifier never leaves your computer.
Credentials stay in the keychain
Your git repository token and the license code are kept in the VS Code secret store (the operating system keychain). They’re never written to files or to the log channel.
MCP server credentials are scrubbed
Before export, the values of keys matching the patterns token, secret, key, password,
auth, bearer, and credential are blanked. The repository receives the MCP server’s
structure — URL, name, arguments — but never its secrets. After pulling on a new machine, re-enter
the credentials once: they go back into the keychain.
Your changes always win
- No blind overwrite. A pull never deletes local work: a three-way reconciliation is performed against a per-machine baseline, and before anything is applied a local backup snapshot is saved.
- Never force-push. Conflicts are shown in the dashboard and never resolved behind the scenes.
- Idempotent operations. Every operation is declarative and can be re-run without harm.
Works offline
Pushes that fail due to no network are queued locally and retried. The license, stored encrypted at rest, keeps working offline within a grace period from the last successful validation.
Machine registry privacy
The activity dates of machines in the repository are recorded at day granularity, by design: no fine-grained activity tracking.