Retention Policies
DATA LIFECYCLE0POLICIES
0ACTIVE
0DISABLED
0RECORDS LAST RUN
● HOW RETENTION WORKS
Retention policies are applied server-side on a schedule. Actions are irreversible — a DELETE removes the run from storage, REDACT removes payload content but preserves the chain hashes, and ARCHIVE marks runs as cold. Configure policies via the API or SDK; manage scheduling with POST /v1/admin/retention/run.
▣
No retention policies configured
Add policies via POST /v1/admin/retention to manage the data lifecycle.
Example: auto-delete runs older than 90 days for a given model pattern
Retention actions are cryptographically logged. Deletion does not alter historical chain integrity proofs — once anchored, the Merkle root remains valid.