Update data retention periods

[coolguyzone]

DESCRIBE YOUR PR

Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• Urgent deadline (GA date, etc.):
• Other deadline:
• None: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
  Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sentry-docs	Ready	Preview	Aug 13, 2026 9:42pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ignored	Preview	Aug 13, 2026 9:42pm

[sentry]

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.