Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/security-legal-pii/security/data-retention-periods.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -15,26 +15,26 @@ By default, new account trials have Team plan retention. If you are trialing fro
| Data Type | Developer | Team | Business / Enterprise |
|-----------|-----------|------|----------|
| Errors | 30 days | 90 days | 90 days |
| Logs | 30 days | 30 days | 30 days |
| Logs | 30 days | 30 days | 30 days + 13 months sampled |
Comment thread
sentry[bot] marked this conversation as resolved.
| Spans/Transactions | 30 days | 30 days* | 30 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 |
| Size Analysis | 30 days | 30 days | 13 months |
| Application Metrics | 30 days | 30 days | 30 days |
| Application Metrics | 30 days | 30 days | 30 days + 13 months sampled |

**Exception\*:** If you are on a [Team or Business plan](https://sentry.io/settings/billing/overview/) that uses [transaction-based billing](https://docs.sentry.io/pricing/), transactions retention will be 90 days and sampled retention of spans data will not apply.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The documentation inconsistently uses an asterisk for an exception on Spans/Transactions but not on Logs or Application Metrics, creating ambiguity about retention policies for transaction-based plans.
Severity: LOW

Suggested Fix

To resolve the ambiguity, either add asterisks to the Logs and Application Metrics rows if the exception applies to them, or update the exception footnote to explicitly clarify whether it applies only to Spans or also to Logs and Application Metrics.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: docs/security-legal-pii/security/data-retention-periods.mdx#L28

Potential issue: The documentation for data retention periods is inconsistent. The table
marks the `Spans/Transactions` row with an asterisk to indicate an exception for
transaction-based billing plans, but fails to do so for the `Logs` and `Application
Metrics` rows, which also now list sampled retention. The exception footnote itself only
mentions "spans data". This creates ambiguity for customers on transaction-based plans,
as they will not know if the exception (which removes sampled retention) also applies to
their logs and application metrics.


## Sampled Retention for Business and Enterprise Plans

Business and Enterprise plan customers receive extended retention for spans data through our sampled retention feature. This provides up to:
Business and Enterprise plan customers receive extended retention for spans, logs, and application metrics through our sampled retention feature. This provides up to:

- **Full fidelity data**: 30 days of complete span data
- **Sampled data**: 13 months of downsampled span data
- **Full fidelity data**: 30 days of complete data
- **Sampled data**: 13 months of downsampled data

13 month downsampled data is a percentage of span data. Sampled retention is currently only available for span data.
13 month downsampled data is a percentage of your ingested data. Sampled retention is currently available for span, log, and application metrics data.

## Data Retention Details

Expand Down
Loading