Data Retention Policy #7377
Merged
Data Retention Policy #7377
Conversation
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
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
src/privacy/data-retention-policy.md
Outdated
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?
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?
src/privacy/data-retention-policy.md
Outdated
|
|
||
| 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?
stayseesong
requested changes
Mar 7, 2025
src/privacy/data-retention-policy.md
Outdated
|
|
||
| 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.
Suggested change
| 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. |
src/privacy/data-retention-policy.md
Outdated
| | **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.
is this a field? If so, should be bolded instead
forstisabella
commented
Mar 7, 2025
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
stayseesong
approved these changes
Mar 7, 2025
forstisabella
commented
Mar 10, 2025
This was referenced Mar 10, 2025
This was referenced Apr 14, 2025
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
3/10
Related issues (optional)