Privacy and content logging

Profile → Privacy controls stored inference content across your API keys and playground requests. Content logging is on by default, with 30-day retention. Choose 1–30 days; a server-wide cap can shorten this further. Turning logging off deletes existing request bodies and disables response caching. In-flight requests cannot restore deleted content.

Retention

Shorter retention applies to existing requests immediately. Increasing retention never extends existing requests or restores deleted content. Expired bodies are hidden immediately; physical cleanup runs on startup and at least hourly. Request statistics, timings, token usage, error codes and financial transactions are preserved.

Manage privacy through the API

Use GET /api/privacy to read your settings and PATCH /api/privacy with { "log_content": true, "retention_days": 7 } to update them. DELETE /api/privacy/content removes stored request and response bodies without changing logging for future requests. These endpoints require a signed-in session; inference keys cannot change them.

Content availability and caching

Usage detail includes content_logging.state: available, disabled, deleted, expired or not_captured, plus expires_at. Credentials are redacted before captured bodies are stored or truncated. Response caches are isolated by account/key, workspace and privacy version; earlier cached replies cannot be served after settings change or deletion. Deleted content is no longer available through your account.

Other stored data

Uploaded files, temporary OCR job results and saved playground conversations are separate from request-body logs. Delete them using their own controls. Other records follow the retention periods described in our privacy policy. Your provider’s own retention policy may also apply.