Data Retention Policy
Learn about Sentry's data retention periods for different data types and plan tiers.
Sentry retains different types of data for varying periods based on your plan tier and the specific data type. This policy outlines the retention periods for all data types across our Developer, Team, and Business plans.
| Data Type | Developer | Team | Business |
|---|---|---|---|
| Errors | 30 days | 90 days | 90 days |
| Logs | 30 days | 30 days | 30 days |
| Spans/Transactions | 30 days | 90 days | 90 days + 13 months sampled |
| Session Replays | 30 days | 90 days | 90 days |
| Profiles | 30 days | 30 days | 30 days |
| Crons | 30 days | 30 days | 30 days |
| Uptime | 30 days | 90 days | 90 days |
| Attachments | 30 days | 90 days | 90 days |
Starting November 2025, Team and Business plans will move from the current 90 day retention period for spans and transactions, to 30 days. If you are on a Team or Business plan that uses transaction-based billing, retention will stay at 90 days.
Business plan customers receive extended retention for spans data through our sampled retention feature. This provides:
- Full fidelity data: 90 days of complete span data
- Sampled data: 13 months of downsampled span data (starting August 26, 2025)
The 13-month sampled retention period allows for year-over-year comparisons and trend analysis while maintaining reasonable storage costs. Sampled retention is currently only available for spans data.
Retention periods are applied at the time data is ingested, based on the then-current plan. This means plan upgrades or downgrades affect retention for new data only; existing data retains its original retention period.
When data reaches the end of its retention period, it can no longer be accessed. If you need to retain data beyond the standard retention period, consider:
- Upgrading to a plan with longer retention
- Contacting support for enterprise retention options
Reference our security policy for information about data deletion.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").