Data retention defines how long request and prompt data is kept and how it is removed afterward. Shorter retention reduces exposure but limits debugging and audits; the right policy depends on your compliance obligations. Infere supports workspace-scoped retention and export controls on the request ledger.

Why it matters

Longer retention means more exposure and more compliance obligation; shorter retention means less ability to debug and audit. The policy is a deliberate trade-off.

How it works

Retention defines how long prompts and request data are stored and how they are deleted. Infere supports workspace-scoped retention and export controls on the request ledger.

Example

Keep full request bodies for 30 days for debugging, then store only aggregate cost and latency metrics after that.

← Back to the full glossary

Put the platform behind the terms

Route, evaluate, and monitor every AI request from one OpenAI-compatible platform.

Start Free → Explore the Features