-
Notifications
You must be signed in to change notification settings - Fork 393
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.
Outdated
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.
Outdated
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. | ||||||
|
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. | |
Segment enforces 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. |
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The 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.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Outdated
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.