Data Retention Policy #7377
Open
Data Retention Policy #7377
Conversation
This file contains 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
forstisabella
added
the
content-update
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
forstisabella
added
new-feature
and removed
content-update
stayseesong
requested changes
Jan 23, 2025
|
|
||
| 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. | ||
|
|
||
| Starting **15th April 2025**, Segment will enforce a strict data retention policy for all: |
There was a problem hiding this comment.
Suggested change
| Starting **15th April 2025**, Segment will enforce a strict data retention policy for all: | |
| Starting **April 15, 2025**, Segment will enforce a strict data retention policy for all: |
Comment on lines
+9
to
+13
| 1. **[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. | ||
| 2. **[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. | ||
| 3. **[Contracted customers](#contracted-customers):** A Business Tier customer that elects to stop using add-on features like Unify, Unify+, Engage and/or Linked. | ||
| 4. **[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. | ||
| 5. **[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. |
There was a problem hiding this comment.
should this be listed as bullets instead of numbers?
Comment on lines
+27
to
+31
| 1. **Event data:** Applicable to all customers that collect [events](/docs/connections/spec/) in Segment from sources for delivery to Unify/Engage or third party destinations. | ||
| 2. **Object data**: Applicable to all customers that collect object data in Segment from third party [Cloud Sources](/docs/connections/sources/about-cloud-sources/) or from the [Objects API](/docs/connections/sources/catalog/libraries/server/object-api/), [Set API](/docs/connections/sources/catalog/libraries/server/object-api/#set), or [Bulk API](/docs/connections/sources/catalog/libraries/server/object-bulk-api/). Object data is also created and updated by aggregating data from Segment’s [Identify](/docs/connections/spec/identify/) and [Group](/docs/connections/spec/group/) events. | ||
| 3. **Profile Events data**: Applicable to all Unify, Unify+, Engage and Linked customers that collect streaming Event data for building a Profile in Segment Unify. | ||
| 4. **Audit Events**: Applicable to all customers. Segment generates and stores audit events from Segment app user actions. | ||
| 5. **HIPAA Audit**: Applicable to all Business Tier customers with the “Segment for Healthcare” add-on. In addition to standard Audit events, Segment generates and stores more granular Segment app user actions events for customers with the “Segment for Healthcare" add-on. |
There was a problem hiding this comment.
should this be listed as bullets instead of numbers?
src/privacy/data-retention-policy.md
Outdated
| | **Team** | 365 days | 90 days | Not applicable | 365 days | Not applicable | | ||
| | **Free** | 180 days | 60 days | Not applicable | 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.
is “Workspace Default Archive Retention Period” a field in the UI? If so, should this be bolded instead?
Comment on lines
+75
to
+78
| Expired customers will have: | ||
|
|
||
| * Their data is immediately subject to data retention of an active, Free Tier customer. All data beyond the retention period will be deleted and unrecoverable. | ||
| * Their Unify data will be deleted and unrecoverable 90 days from the date their workspace was downgraded. |
There was a problem hiding this comment.
The bullets don't grammatically complete with the leading intro sentence. For example, "Expired customers will have their data is immediately..." Should it instead be: Expired customers will have their data immediately subject to data retention... or Expired customers will have their Unify data be deleted and...
|
|
||
| 1. **[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. | ||
| 2. **[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. | ||
| 3. **[Contracted customers](#contracted-customers):** A Business Tier customer that elects to stop using add-on features like Unify, Unify+, Engage and/or Linked. |
There was a problem hiding this comment.
Is Linked referring to Linked Events? Linked Audiences? or both?
Comment on lines
+100
to
+101
| * Explicitly terminated the contract **OR** | ||
| * Has unpaid invoices and has their workspace fully locked out. |
There was a problem hiding this comment.
it's a bit odd that one bullet has a period and the other doesn't. Maybe can just make the 2 bullets 1 line?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
Added docs for the new Data Retention and Deletion policy
Merge timing
Before Feb 3
Related issues (optional)