Privacy, Security, and Data Controls
Retention controls, zero-retention mode, training opt-in, data purge, and enterprise-safe defaults.
Retention controls, zero-retention mode, training opt-in, data purge, and enterprise-safe defaults.
- Pick default retention and privacy mode.
- Set webhook secrets and verify signatures.
- Limit key scope and rotate periodically.
- Run access and data-deletion checks quarterly.
Control matrix
| Control | Default | Effect |
|---|---|---|
| Training opt-in | Off | No training on prompts/responses unless explicit opt-in |
| Zero-retention mode | Off | Retention paths disabled or purged when enabled |
| Semantic memory | Feature on | Cross-session recall when retention policy allows |
| BYOK | Optional | Provider-billed traffic when key is active |
Retention impact
- Usage logs retained
- Optional semantic memory
- No training unless opt-in
- Prompt/response text redacted
- Memory entries unavailable
- Training opt-in forced off
Managing privacy settings
Toggle controls via PUT /api/v1/settings/privacy:
{
"zero_retention_mode": true,
"data_training_opt_in": false,
"purge_existing_data": true
}
zero_retention_mode— when enabled, all new requests skip prompt/response storage and semantic memorydata_training_opt_in— explicit consent for training data collection (auto-disabled when zero-retention is on)purge_existing_data— when enabling zero-retention, purge previously stored data
Check current settings with GET /api/v1/settings/privacy.
Data purge
When you enable zero-retention mode with purge_existing_data: true, the following data is permanently removed:
- Semantic memories — all vector embeddings deleted
- Training samples — all opted-in training data deleted
- Request logs — prompt and response text redacted (metadata preserved for billing)
- Conversations — titles scrubbed
The API returns a count of affected records so you can verify the purge was complete.
Enterprise baseline checklist
- Enable zero-retention for regulated workloads.
- Keep training opt-in disabled by default.
- Rotate API and webhook secrets on a schedule.
- Use BYOK when customer contract requires provider-direct billing.
- Verify purge counts after enabling zero-retention.
LLMWise does not train on user prompts/responses by default. If teams enable opt-in, scope and consent should be explicit and auditable.
ChatKit-style guided help
Product-scoped assistant for LLMWise docs and API usage. It does not answer unrelated topics.
Sign in to ask implementation questions and get runnable snippets.
Sign in to use assistant