Reference
Privacy and telemetry
Privacy and telemetry describe where workspace data goes and which optional usage events are collected. Local storage does not mean every connected feature operates without network requests.
Updated
By Kition Docs
Verified against Kition 0.1.41 (d3e1b931) on 2026-08-29
Review data flow before using a connected feature
Separate the material stored in the workspace from the information a selected operation sends to another service. The Agent context, a reference image, an imported message, and diagnostic output can have different destinations. Read the version-specific behavior below before relying on a particular control.
- Identify the operation and the account or provider that will receive its request.
- Review the selected context and remove material that is unnecessary for the task.
- Check the anonymous usage analytics setting separately from model-provider requests.
- Inspect diagnostics before sharing them and redact private content.
- Use the documented provider and local-data controls for the specific information you want to remove.
| Surface | Review |
|---|---|
| Workspace files | Local storage, backups, and file sharing |
| Connected AI request | Selected context and the configured recipient service |
| Optional usage analytics | The documented preference and event schema |
| Logs and diagnostics | Sensitive details before sharing |
Anonymous product analytics are opt-in
Share anonymous usage data is off by default. You can enable or disable it in Settings → General.
When enabled, Kition accepts only a fixed, coarse event schema: event name and time, app version/build identity and platform, an analytics-specific anonymous installation ID, and bounded result, provider, account, subscription, or update states.
Sensitive fields are rejected
The event validator rejects unsupported fields and sensitive-looking strings, including file paths, URLs, email addresses, keys, tokens, prompts, document contents, and browser history. Product analytics are not a general log-upload channel.
The local analytics queue is bounded to 200 events. A configured remote endpoint must use HTTPS, except that loopback HTTP is allowed for local development.
What disabling analytics does
Disabling the setting clears the queued events, one-time event markers, and the anonymous analytics ID, and aborts an in-flight analytics delivery. It does not delete workspaces, application logs, account data held by remote services, or data already sent while the setting was enabled.
Features that can contact external services
Local-first workspace storage does not make these optional network actions local. Review the destination service and its terms before connecting it.
- Kition Cloud account, billing, and hosted AI
- External AI providers that you configure
- Websites opened in the embedded browser
- Email providers and synchronization connections
- Feedback or support submissions that you choose to send
- Application update checks and downloads
Heads up
Provider and proxy credentials are plaintext application-data secrets in Kition 0.1.41. Use least-privilege keys, protect local backups, and revoke credentials remotely when access must be terminated.
Implementation sources
Related pages
Settings reference
Kition settings configure device behavior, accounts, model providers, email connections, and diagnostics. This reference identifies the version-specific sections and the scope of each choice.
Protect provider credentials
Understand how Kition 0.1.41 stores provider secrets and reduce the impact of device or key compromise.
Uninstall Kition and remove app data
Uninstall the application separately from its workspaces, settings, credentials, caches, and logs.