Skip to content

Commit

Permalink
clarifcations around retention
Browse files Browse the repository at this point in the history
  • Loading branch information
markzegarelli committed Sep 11, 2024
1 parent 4a9abbe commit 53d5484
Show file tree
Hide file tree
Showing 4 changed files with 23 additions and 45 deletions.
22 changes: 1 addition & 21 deletions content/collections/session-replay/en/session-replay-plugin.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,6 @@ Amplitude built Session Replay to minimize impact on the performance of web page

Session Replay captures changes to a page's Document Object Model (DOM), including elements in the shadow DOM, then replays these changes to build a video-like replay. For example, at the start of a session, Session Replay captures a full snapshot of the page's DOM. As the user interacts with the page, Session Replay captures each change to the DOM as a diff. When you watch the replay of a session, Session Replay applies each diff back to the original DOM in sequential order, to construct the replay. Session replays have no maximum length.

{{partial:partials/session-replay/sr-retention}}

## Before you begin

Use the latest version of the Session Replay Plugin above version {{sdk_versions:session_replay_plugin}}. For more information, see the [change log](https://github.com/amplitude/Amplitude-TypeScript/blob/v1.x/packages/plugin-session-replay-browser/CHANGELOG.md) on GitHub.
Expand Down Expand Up @@ -233,25 +231,7 @@ if (nonEUCountryFlagEnabled) {
}
```



## Data retention

Session replay uses existing Amplitude tools and APIs to handle privacy and deletion requests.

{{partial:admonition type="note" heading="Consent management and Session Replay"}}
While privacy laws and regulations vary across states and countries, certain constants exist, including the requirements to disclose in a privacy notice the categories of personal information you are collecting, the purposes for its use, and the categories of third parties with which personal information is shared. When implementing a session replay tool, you should review your privacy notice to make sure your disclosures remain accurate and complete. And as a best practice, review your notice with legal counsel to make sure it complies with the constantly evolving privacy laws and requirements applicable to your business and personal information data practices.
{{/partial:admonition}}

### Retention period

If your Amplitude plan includes Session Replay, Amplitude retains raw replay data for 30 days from the date of ingestion.

If you purchase extra session volume, Amplitude retains raw replay data for 90 days from the date of ingestion. If you need a more strict policy, contact Amplitude support to set the value to 30 days.

Changes to the retention period impact replays ingested after the change. Sessions captured and ingested before a retention period change retain the previous retention period.

Replays that are outside of the retention period aren't viewable in Amplitude.
{{partial:partials/session-replay/sr-retention}}

### DSAR API

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,6 @@ Amplitude built Session Replay to minimize impact on the performance of web page

Session Replay captures changes to a page's Document Object Model (DOM), including elements in the shadow DOM, then replays these changes to build a video-like replay. For example, at the start of a session, Session Replay captures a full snapshot of the page's DOM. As the user interacts with the page, Session Replay captures each change to the DOM as a diff. When you watch the replay of a session, Session Replay applies each diff back to the original DOM in sequential order, to construct the replay. Session replays have no maximum length.

{{partial:partials/session-replay/sr-retention}}

## Before you begin

Use the latest version of the Session Replay standalone SDK above version {{sdk_versions:session_replay_standalone}}. For more information, see the [change log](https://github.com/amplitude/Amplitude-TypeScript/blob/v1.x/packages/session-replay-browser/CHANGELOG.md) on GitHub.
Expand Down Expand Up @@ -224,23 +222,7 @@ if (nonEUCountryFlagEnabled) {
}
```

## Data retention

Session replay uses existing Amplitude tools and APIs to handle privacy and deletion requests.

{{partial:admonition type="note" heading="Consent management and Session Replay"}}
While privacy laws and regulations vary across states and countries, certain constants exist, including the requirements to disclose in a privacy notice the categories of personal information you are collecting, the purposes for its use, and the categories of third parties with which personal information is shared. When implementing a session replay tool, you should review your privacy notice to make sure your disclosures remain accurate and complete. And as a best practice, review your notice with legal counsel to make sure it complies with the constantly evolving privacy laws and requirements applicable to your business and personal information data practices.
{{/partial:admonition}}

### Retention period

If your Amplitude plan includes Session Replay, Amplitude retains raw replay data for 30 days from the date of ingestion.

If you purchase extra session volume, Amplitude retains raw replay data for 90 days from the date of ingestion. If you need a more strict policy, contact Amplitude support to set the value to 30 days.

Changes to the retention period impact replays ingested after the change. Sessions captured and ingested before a retention period change retain the previous retention period.

Replays that are outside of the retention period aren't viewable in Amplitude.
{{partial:partials/session-replay/sr-retention}}

### DSAR API

Expand Down
6 changes: 3 additions & 3 deletions content/globals/en/sdk_versions.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
browser: 2.11.2
browser: 2.11.3
browser_sdk_sha: sha384-8fNco6Xiv+HOa+SIVGKVjByyY5LyircydGlHS9mXcHJpapcgF98L6UNOlauMTxJq
visual_labeling_plugin: 1.0.0
session_replay_plugin: 1.6.17
session_replay_standalone: 1.13.1
session_replay_plugin: 1.6.24
session_replay_standalone: 1.13.8
session_replay_android_plugin: 0.6.5
session_replay_android_standalone: 0.6.5
session_replay_ios: 0.0.2
Expand Down
20 changes: 18 additions & 2 deletions resources/views/partials/session-replay/_sr-retention.antlers.html
Original file line number Diff line number Diff line change
@@ -1,5 +1,21 @@
{{markdown}}
{{partial:admonition type="tip" heading="Replay retention"}}
By default, Amplitude retains replays for three months. Purchase extra retention and have your replays available for up to 12 months, or contact Amplitude to reduce retention to as little as 30 days.
## Data retention

Session replay uses existing Amplitude tools and APIs to handle privacy and deletion requests.

{{partial:admonition type="note" heading="Consent management and Session Replay"}}
While privacy laws and regulations vary across states and countries, certain constants exist, including the requirements to disclose in a privacy notice the categories of personal information you are collecting, the purposes for its use, and the categories of third parties with which personal information is shared. When implementing a session replay tool, you should review your privacy notice to make sure your disclosures remain accurate and complete. And as a best practice, review your notice with legal counsel to make sure it complies with the constantly evolving privacy laws and requirements applicable to your business and personal information data practices.
{{/partial:admonition}}

### Retention period

If your Amplitude plan includes Session Replay, Amplitude retains raw replay data for 30 days from the date of ingestion.

Purchase extra retention time, up to a maximum of 12 months. For more information, contact [Amplitude Support](https://support.amplitude.com).

If you purchase extra session volume, Amplitude retains raw replay data for 12 months from the date of ingestion. If you need a more strict policy, contact Amplitude support to set the value to 30 days.

Changes to the retention period impact replays ingested after the change. Sessions captured and ingested before a retention period change retain the previous retention period.

Replays that are outside of the retention period aren't viewable in Amplitude.
{{/markdown }}

0 comments on commit 53d5484

Please sign in to comment.