Data retention
How long executions, change records, metrics, audit logs and API request logs are kept per plan, the organization retention setting, and what is swept.
Retention has a plan cap and an organization setting; the effective window is the smaller of the two. Sweeps run continuously in the background, so nothing older than the window is kept.
Per plan
| Plan | Execution & change history | Audit & API request logs |
|---|---|---|
| Free | 3 days | 3 days |
| Team | 30 days | 7 days |
| Pro | 365 days | 90 days |
| Enterprise | 365 days | Unlimited |
Organization setting
Organization → Security → Retention offers 7, 30, 90, 180 or 365 days, or a custom value from 1 to 3650 days. A setting above the plan cap is honoured only up to the cap; a shorter setting is honoured as-is, which is the right choice when your own policy says to keep less.
What is kept and swept
- Monitor executions (each check's result, timing, assertions and, for HTTP, the response excerpt) and fingerprints and change records (the External Intelligence history) are swept to the effective window.
- Current status per monitor is one row and is never swept.
- Time-series metrics (response times used for charts and anomaly baselines) are kept in the metrics store with a platform-wide retention that is longer than any plan window.
- Audit logs and the API request log follow the audit retention; MCP audit rows are kept for 365 days and MCP approval requests for 30 days after expiry.
- Downgrading shortens the window: history older than the new plan's cap is swept on the next pass.
Secrets in the credential vault and environment secrets are encrypted at rest and are deleted immediately when you delete the credential or environment; they are not subject to retention windows.