From af9a0bc57fd0f0c8b09c55e6d6f7632435ddb649 Mon Sep 17 00:00:00 2001 From: DJ Satoda Date: Wed, 11 Jun 2025 15:49:34 -0400 Subject: [PATCH 1/2] Creating custom retention windows changelog post; still needs image --- .../2025-06-11-custom-retention-windows.mdx | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 pages/changelogs/2025-06-11-custom-retention-windows.mdx diff --git a/pages/changelogs/2025-06-11-custom-retention-windows.mdx b/pages/changelogs/2025-06-11-custom-retention-windows.mdx new file mode 100644 index 0000000000..912ae2c5a8 --- /dev/null +++ b/pages/changelogs/2025-06-11-custom-retention-windows.mdx @@ -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 +--- + + + +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. + +Longer replay retention helps teams practicing digital continuous innovation by preserving rich observational data for longer. In doing so, teams can reflect on past initiatives-months after launch—and more effectively determine what bets paid off and why, helping fuel their next round of improvement + +For more information, please reach out to your Account Manager. + +Learn more in our [help docs](/docs/session-replay#how-long-are-replays-stored) From ef40a4583ed3719e5b11f5714e680b5225989d1d Mon Sep 17 00:00:00 2001 From: DJ Satoda Date: Wed, 11 Jun 2025 15:57:47 -0400 Subject: [PATCH 2/2] Simplifying oada ref --- pages/changelogs/2025-06-11-custom-retention-windows.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/changelogs/2025-06-11-custom-retention-windows.mdx b/pages/changelogs/2025-06-11-custom-retention-windows.mdx index 912ae2c5a8..567a690936 100644 --- a/pages/changelogs/2025-06-11-custom-retention-windows.mdx +++ b/pages/changelogs/2025-06-11-custom-retention-windows.mdx @@ -18,7 +18,7 @@ Enterprise customers can now define their own replay retention period—from **7 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. -Longer replay retention helps teams practicing digital continuous innovation by preserving rich observational data for longer. In doing so, teams can reflect on past initiatives-months after launch—and more effectively determine what bets paid off and why, helping fuel their next round of improvement +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.