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..567a690936 --- /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. + +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)