Skip to main content
Zero retention is a requirement about actual data handling across the full workflow. A single configuration flag cannot establish what every service, provider, or export stores.
platform_settings.privacy.zero_retention_mode is a saved boolean, default false. Threetone does not currently provide an implemented zero-retention guarantee. Setting it to true does not establish suppression of transcripts, audio, analysis, logs, or provider storage.
Use the field to record intent in a reviewed agent draft. Keep the requirement marked unverified until the relevant execution and storage paths support it.

​
Release checks to require

The current platform-managed backup order does not establish zero-retention filtering. A model’s appearance in a catalog is also not evidence of a retention commitment. Before using data with a strict no-storage requirement, obtain verified handling details for the released workflow. Configuration read-back can confirm the flag was saved; it cannot confirm those details.
No. Each model and fallback path needs its own verified handling policy and enforced selection rules.
No. It does not establish retroactive cleanup or removal of prior copies.