26. Privacy and telemetry
[!ref] Full details in the User Manual, "Security and privacy".
26.1 Defaults
| Item | Default | Description |
|---|---|---|
| Behavioural analytics | Off | Not reported |
| Crash stack | Ask | On crash, asks whether to report |
| Model conversation | Your chosen Provider | Provider's privacy terms apply |
| Decompilation byte range | Sent when called | You explicitly trigger it; goes to the 澜砥 model chosen by routing, or only the session's model in local mode (§6.8.1) |
| Code Q&A snippets | Sent when called | Code snippets retrieved by code.ask; same destination as above |
| Sample bytes | Not uploaded as a whole | Local analysis; the exception is sec.decompile, which sends the requested byte range on demand (a small sample may go out in full) |
26.2 Encrypted storage
The following live encrypted on the local machine:
- Sign-in credential
- Model provider API key
- External tool service bearer token / credential
- Channel (WeChat iLink) session state
All of the above are encrypted at rest with ShangMi SM4-GCM + HKDF (SM3) (bound to the machine ID, with a random salt); the encrypted .zbk backup uses SM4-GCM + PBKDF2-SM3, and legacy AES-256-GCM backups remain decryptable.
26.3 Conversation content
Conversation content is persisted locally only; the corresponding messages go out only when you actively call the model, following the Provider's protocol.