Session Replay: Data, Retention & Pricing

Note: Session Replay is in Beta / Preview. The details below describe the current direction — exact retention windows and pricing are still being finalized and will be announced before general availability.

Where data is stored

Captured (already-masked) frames are stored in Cloudflare R2, the same edge-native storage layer used across ScryWatch. Because masking happens on-device before upload, R2 only ever holds the redacted frames — never an unmasked copy.

Storage location is expected to be region-pinnable per project, so you’ll be able to keep replay data in a specific jurisdiction to match your data residency requirements. Region selection is not yet exposed in the dashboard.

Retention

Retention for session replay data is planned to be configurable per project, similar to how you can already choose retention windows for other event data in ScryWatch. Default and maximum retention windows are still being determined during the Beta.

Pricing

Session Replay is expected to be metered per plan — likely based on captured sessions or storage volume, consistent with how other ScryWatch features are priced. Specific pricing and plan limits are coming soon and will be published here and on the Billing page ahead of general availability.

Tip: If you’re evaluating Session Replay for a production rollout and need firm numbers on retention or pricing sooner, reach out — we’re happy to talk through the Beta roadmap directly.

Related docs

• Overview — what Session Replay is and what it’s for
• Masking & Privacy — why only masked frames ever leave the device
• Billing — how ScryWatch plans and usage work today