Document 30-day retention for telemetry events

[ehfeng]

Summary

A customer asked how long Session telemetry data is persisted for. The answer (30 days, per the telemetry basin config) wasn't documented anywhere — the telemetry pages, privacy policy, and changelog were all silent on it.

This adds retention documentation in two places:

• Telemetry Overview — new "Retention" section stating captured events are retained for 30 days then expired, with a pointer to the streaming/archive flow and a note that ZDR orgs don't persist telemetry at all.
• Telemetry Categories — the "Data sensitivity" section already discusses data at rest; adds the 30-day window there so readers of either page get the answer.

---

Note

Low Risk
Documentation-only changes with no product or security behavior impact.

Overview
Documents that captured browser telemetry is retained for 30 days then expired, closing a gap where persistence duration wasn’t stated in the docs.

Adds a Retention section on the telemetry overview: events can be streamed or pulled within that window and are unavailable after 30 days. The categories Data sensitivity note now states the same retention window and links to overview#retention so readers of either page get a consistent answer about data at rest.

^{Reviewed by Cursor Bugbot for commit fd06c3f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Aug 19, 2026, 6:16 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[cursor]

Risk Assessment: Very Low

Decision: Keep existing approval (risk did not increase)

Re-evaluated after the latest push (fd06c3fc, applying a review suggestion). The PR still only edits two Mintlify documentation pages (browsers/telemetry/overview.mdx and browsers/telemetry/categories.mdx). Net change is 5 lines added and 1 line removed: a Retention section stating a 30-day event expiry window, plus a cross-link from the categories page.

The follow-up commit removed a Zero Data Retention sentence from that section. That is still documentation copy only and does not raise risk.

• Codepaths / blast radius: Docs copy only. No application code, APIs, config, CI, or infrastructure.
• Complexity: Trivial prose and internal doc links.
• Operational / security impact: None. Retention behavior is not implemented here; only described.
• User-facing surface: Public docs text. No runtime or auth/permission changes.
• CODEOWNERS: None required (no CODEOWNERS file).

This remains Very Low: documentation-only, no production logic or shared-system impact. Prior approval stands; not re-approving.

  

_{Sent by Cursor Automation: Assign PR reviewers}