-
Notifications
You must be signed in to change notification settings - Fork 365
Data Retention Policy #7377
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.
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
Merged
Merged
Data Retention Policy #7377
Changes from 14 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
8202644
init
forstisabella 0801f35
[netlify-build]
forstisabella 2fb4068
nits [netlify-build]
forstisabella de5f990
Update data-retention-policy.md
forstisabella 03922e5
[netlify-build]
forstisabella 4e0425e
[netlify-build]
forstisabella 9b44a1e
[netlify-build]
forstisabella 48433c5
[netlify-build]
forstisabella 32628d0
[netlify-build]
forstisabella 355c017
[netlify-build]
forstisabella 770a00b
[netlify-build]
forstisabella ac69472
add disabled space [netlify-build]
forstisabella d129572
[netlify-build]
forstisabella 501042b
Merge branch 'master' into add-data-retention-policy
forstisabella 212072e
Apply suggestions from code review [netlify-build]
forstisabella 15c79b6
Update src/privacy/data-retention-policy.md
forstisabella File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,116 @@ | ||||||
--- | ||||||
title: Data Retention and Deletion Policy | ||||||
--- | ||||||
|
||||||
Twilio Segment’s Data Retention and Deletion Policy provides clarity, consistency and compliance across all Segment services and brings Segment’s data retention policy in line with industry standards and regulations. By implementing and enforcing this policy, Segment aims to enhance data governance and ensure that Segment customers can manage their data accurately, efficiently and securely within clearly defined retention periods. | ||||||
|
||||||
Segment will enforce a strict data retention policy for all: | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
- **[Active customers](#active-customers):** A Business or Team Tier customer that has an active Segment contract with no outstanding invoices and no locked workspace, or a Free Tier workspace that has had event traffic or user activity in the past 30 days. | ||||||
- **[Expired customers](#expired-customers):** A Business or Team Tier customer that hasn’t renewed their Segment contract and has their workspace downgraded to Free Tier. | ||||||
- **[Contracted customers](#contracted-customers):** A Business Tier customer that elects to stop using add-on features like Unify, Unify+, Engage and/or Linked. | ||||||
- **[Churned customers](#churned-customers):** A Business or Team Tier customer that has either explicitly terminated the contract or has unpaid invoices and has their workspace fully locked out. | ||||||
- **[Unused Free Tier workspace](#unused-free-tier-workspace)**: A workspace on the Free Tier that has not received any Segment event traffic or had any user activity in the last 30 days. | ||||||
|
||||||
 | ||||||
|
||||||
## Effective Date | ||||||
Segment’s enforcement of this data retention policy for active customers will begin on: | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
- **April 15, 2025** for Object Store data | ||||||
- **July 15, 2025** for Archive event and Profile events data stores | ||||||
|
||||||
## Active customers | ||||||
|
||||||
An active customer is a Business or Team Tier customer that has an active Segment contract with no outstanding invoices and no locked workspace, or a Free Tier workspace that has had event traffic or user activity in the past 30 days. | ||||||
|
||||||
Segment will enforce a data retention period of up to 3 years for Business Tier customers. If you currently have an extended retention period in place, Segment will continue to honor the previously agreed upon retention period. If your business requires a longer retention period, please contact your sales team to discuss available options. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
### Data retention period | ||||||
|
||||||
The default data retention period for each of the data types is as follows: | ||||||
|
||||||
| Tier | Archive Event Data Retention | Profile Event Data Retention | Object Data Retention | Audit | HIPAA Audit | | ||||||
| ------------ | ---------------------------- | ---------------------------- | --------------------- | ------- | -------------- | | ||||||
| **Business** | 3 years | 3 years | 180 days | 3 years | 3 years | | ||||||
| **Team** | 365 days | Not applicable | 90 days | 365 days | Not applicable | | ||||||
| **Free** | 180 days | Not applicable | 60 days | 180 days | Not applicable | | ||||||
|
||||||
Through the self-serve Data Retention configuration in your workspace, you can configure a custom data retention period through “Workspace Default Archive Retention Period”. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is this a field? If so, should be bolded instead
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
Segment will unrecoverably delete a [Unify Space](/docs/unify/identity-resolution/space-setup/#step-one-create-a-new-dev-space) 90 days after it was disabled. | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
### What data is impacted? | ||||||
|
||||||
With this data retention policy, all data beyond the retention period will be unrecoverably deleted from all of Segment and will impact the following: | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
* [Data Replays](/docs/guides/what-is-replay/) will only be available for data within the retention period. Unify, Engage and Linked customers that replay data to recreate Unify Spaces or Profiles may encounter variations in the number of profiles, as well as in the identifiers, traits and properties associated with the profiles, depending on the data available. | ||||||
* Backfill Data will only be available for data within the retention period. | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
* [Data residency](/docs/guides/regional-segment/) migrations across regions (US and EU) will only be available for data within the retention period. | ||||||
* Additional impacts to Object data: | ||||||
* Cloud Object Data (using push) updated using the [Object API](/docs/connections/sources/catalog/libraries/server/object-api/#set), [Bulk API](docs/connections/sources/catalog/libraries/server/object-bulk-api/), or webhook cloud sources (for example, [SendGrid](/docs/connections/sources/catalog/cloud-apps/sendgrid/#streaming) or [Mandrill](/docs/connections/sources/catalog/cloud-apps/mandrill/#streaming)): Any data older than 180 days is treated as a new record and may not contain any historic properties. To prevent loss of data properties, Segment recommends that you always send full objects with all properties. | ||||||
* Users and Accounts: Segment aggregates data from Identify and Group events for entities active within the last 180 days. Any data older than 180 days will be treated as a new record and will not have historic properties. To prevent loss of data properties, Segment advises customers to migrate to using Profile Sync. | ||||||
* [Computed traits](/docs/unify/Traits/computed-traits/) will be built using the available data within the retention period. Recreating these traits may result in different values based on the available data. | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
* [Profiles](/docs/unify/), [Engage](/docs/engage/) [Audiences](/docs/engage/audiences/) and [Journeys](/docs/engage/journeys/) that are built using Events will use available data within the retention period. Recreating these may result in different Profiles based on the available data. Further, depending on how the conditions are defined Profiles may or may not exit Computed traits, Engage Audiences, and Journeys due to the data retention policy, and this may result in mismatches in counts when comparing against a preview. | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
### What data is not impacted? | ||||||
|
||||||
With this policy the following data will be not impacted, but may be subject to other policies: | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
* **Cloud Object Data (using pull)**: This involves Segment fetching object data from third party Cloud Sources. Since Segment always fetches the full objects, the retention policy will have no impact. | ||||||
* **Profiles**: Unify Profiles created are not subject to this data retention policy. | ||||||
* **Third Party Destinations**: Data in your third party destinations shared by Segment in the course of your implementation will remain unaffected. Data stored in a third party system may be subject to the data retention policy of that system. | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
* Anything a user creates in the Segment App, like Audiences, Journeys, Data Graphs, Connections, and more, **are not subject to this data retention policy**. | ||||||
|
||||||
## Expired customers | ||||||
|
||||||
An expired customer is a Business or Team Tier customer that hasn’t renewed their Segment contract and has had their workspace downgraded to the Free Tier. | ||||||
|
||||||
Segment will enforce a maximum data retention period of 90 days for Unify data, unless customers explicitly request immediate deletion through a [support ticket](/docs/privacy/account-deletion/#delete-your-workspace-data). Once on the Free Tier, the workspace will be subject to the Free Tier data retention policies. | ||||||
|
||||||
### What data is impacted? | ||||||
|
||||||
Expired customers will have: | ||||||
|
||||||
* Their data immediately subject to data retention of an active, Free Tier customer. All data beyond the retention period will be deleted and unrecoverable. | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
* Their Unify data deleted and unrecoverable 90 days from the date their workspace was downgraded. | ||||||
|
||||||
## Contracted customers | ||||||
|
||||||
A contracted customer is a Business Tier customer that elects to stop using add-on features like Unify, Unify+, Engage and/or Linked. | ||||||
|
||||||
Segment will enforce a maximum data retention period of up to 90 days for all contracted customers, unless they explicitly request immediate deletion through a [support ticket](/docs/privacy/account-deletion/). All data beyond the retention period will be deleted and unrecoverable as described below. | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
### What data is impacted? | ||||||
|
||||||
With this data retention policy, all data in all your Unify Spaces after the retention period will be deleted and unrecoverable. If you opt-in to Unify, Unify+, Engage, and/or Linked after the retention period, you will be starting with a brand new implementation with no previous data. | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
### What data is not impacted? | ||||||
|
||||||
If contracting from Engage or Linked, your Connection and Unify data will remain unaffected and will be subject to the [Active customer retention policy](#active-customers). | ||||||
|
||||||
If contracting from Unify or Unify+, your Connection data will remain unaffected and will be subject to the [Active customer retention policy](#active-customers). | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
## Churned customers | ||||||
|
||||||
A churned customer is a Business or Team Tier customer that has either: | ||||||
- Explicitly terminated the contract | ||||||
- Has unpaid invoices and had their workspace fully locked out | ||||||
|
||||||
Customers that have explicitly terminated their Segment contract will have their data unrecoverably deleted within 30 days of contract termination. | ||||||
|
||||||
Customers that have unpaid invoices and have their workspaces fully locked out will have their data unrecoverably deleted after 30 days of full lock out, unless explicitly requested for immediate deletion through a [support ticket](/docs/privacy/account-deletion/#delete-your-workspace-data). | ||||||
|
||||||
| Tier | Data Retention | | ||||||
| ------------ | -------------------------- | | ||||||
| **Business** | 30 days post full lockout. | | ||||||
| **Team** | 30 days post full lockout. | | ||||||
|
||||||
## Unused Free Tier workspace | ||||||
|
||||||
An Unused Free Tier workspace is a workspace that has not received any Segment event traffic or user activity in the last 30 days. | ||||||
|
||||||
Segment will unrecoverably delete the workspace after 30 days of inactivity, unless explicitly requested for immediate deletion through a [support ticket](/docs/privacy/account-deletion/#delete-your-workspace-data). | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
### Data deletion delays | ||||||
|
||||||
When data reaches the end of its retention period, deletion will be scheduled in accordance with Segment’s data retention policy. While Segment aims to complete the deletion process promptly, there may be occasional delays due to processing times or technical constraints. Segment is committed to initiating data deletions as soon as possible and will strive to complete deletions within 7 days of the scheduled date. | ||||||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.