Skip to content

Creating custom retention windows changelog post; still needs image #1898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Creating custom retention windows changelog post; still needs image #1898

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
af9a0bc
Creating custom retention windows changelog post; still needs image
djmixpanel Jun 11, 2025
ef40a45
Simplifying oada ref
djmixpanel Jun 11, 2025
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
25 changes: 25 additions & 0 deletions pages/changelogs/2025-06-11-custom-retention-windows.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
title: "Custom Retention Windows for Session Replay"
slug: "changelog-2025-06-11-custom-retention-windows"
hidden: false
createdAt: "2025-06-11T19:59:02.165Z"
updatedAt: "2025-06-11T19:59:02.165Z"
date: "2025-06-11"
description: "Customers on our Enterprise plan can now customize how long their session replays are retained (anywhere from 7 days to one year) to better fit their compliance, support, or analysis needs."
isAnnouncement: false
---

<ChangelogPostHeader
date="2025-06-11"
title="Custom Retention Windows for Session Replay"
/>

Enterprise customers can now define their own replay retention period—from **7 days up to 1 year**—to match their organization's compliance policies, data sensitivity, or long-term analysis needs.

Until now, Session Replay data was only retained for 30 days. This rigid default didn’t work for everyone—some teams needed shorter retention for regulatory reasons, while others needed longer retention for support escalations or long-term product decision making. This release provides the flexibility customers need to align replay retention with their unique goals.

Extended replay retention fuels digital continuous innovation by preserving rich observational data for longer — letting teams revisit past releases, see what worked, and sharpen future bets.

For more information, please reach out to your Account Manager.

Learn more in our [help docs](/docs/session-replay#how-long-are-replays-stored)