Data Retention and Cleanup Policies
Set how long Organization content is kept, preview what a retention change would delete, and monitor irreversible cleanup.
Open Governance → Policies → Data retention to review retention policy. Owner, Admin, and Security Admin can change policy and run cleanup. Auditor can review policy and cleanup history.
Retention removes eligible content. Enabling enforcement or shortening an enforced retention period can start cleanup immediately when you save. Export anything you need before confirming; turning enforcement off afterward does not restore removed content.
Choose retention periods
The policy has separate horizons for these categories:
| Category | What cleanup affects |
|---|---|
| Conversations | Eligible message content and associated attachment content |
| Execution history | Eligible execution details and stored tool or processing content |
| Files | Eligible workspace files and their stored bytes |
| Browser artifacts | Eligible browser task artifacts and related stored content |
| Security activity | Eligible Organization security audit events, subject to a minimum 365-day period |
File eligibility uses creation time, not the last time someone opened or used a file. A long-lived reference document can therefore become eligible even if an agent still needs it. Inspect the impact preview and your active workflows before choosing a short file horizon.
Cleanup preserves necessary operational identifiers, and statuses rather than deleting the Organization or every agent. It does not revoke provider credentials or remove data already copied to external services. Agent Audit View has its own metadata and evidence policy.
Preview, save, and verify
- Adjust the proposed horizons and wait for the impact preview to finish recalculating.
- Review the eligible counts for each category. If preview fails, resolve that failure before saving.
- Obtain an Organization agent export if you need portable copies of eligible content. Export authority is separate: a Security Admin may need an Owner, Admin, or Agent Admin to prepare it.
- Choose whether to Enforce retention policy, then save and read the cleanup confirmation.
- Review cleanup history for completion and errors. Run cleanup now starts an eligible run; an already-running cleanup is reported instead of starting another one.
Once enforced, cleanup also runs on the daily maintenance schedule. Your installation operator must run the scheduler and workers. If immediate dispatch fails after saving, the policy can still be saved; inspect the warning and fix dispatch rather than assuming nothing changed.
Disabling enforcement prevents future policy-driven cleanup. Do not assume it cancels work already underway; inspect the active run. Archives, downloaded exports, and backups each have their own lifetime. Define how your Organization handles those copies separately.