Skip to content

Commit 32628d0

Browse files
committed
[netlify-build]
1 parent 48433c5 commit 32628d0

File tree

1 file changed

+19
-20
lines changed

1 file changed

+19
-20
lines changed

src/privacy/data-retention-policy.md

Lines changed: 19 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Data Retention and Deletion Policy
44

55
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.
66

7-
Starting **15th April 2025**, Segment will enforce a strict data retention policy for all:
7+
Segment will enforce a strict data retention policy for all:
88

99
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.
1010
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.
@@ -14,6 +14,11 @@ Starting **15th April 2025**, Segment will enforce a strict data retention polic
1414

1515
![A flowchart depicting the progression of active and no longer active customers.](images/data-retention-policy-flowchart.png)
1616

17+
## Effective Date
18+
Segment’s enforcement of this data retention policy will begin on:
19+
- **April 15, 2025** for Object Store data
20+
- **July 15, 2025** for Archive event and Profile events data stores
21+
1722
## Active customers
1823

1924
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.
@@ -30,33 +35,30 @@ The following data types are subject to the 3 year retention period:
3035
4. **Audit Events**: Applicable to all customers. Segment generates and stores audit events from Segment app user actions.
3136
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.
3237

33-
### Data retention
38+
### Data retention period
3439

3540
The default data retention period for each of the data types is as follows:
3641

37-
| Tier | Event Data Retention | Object Data Retention | Profile Event Data Retention <sup>*<sup> | Audit | HIPAA Audit |
38-
| ------------ | -------------------- | --------------------- | ---------------------------------------- | ------- | -------------- |
39-
| **Business** | 3 years | 180 days | 3 years | 3 years | 3 years |
40-
| **Team** | 365 days | 90 days | Not applicable | 365 days | Not applicable |
41-
| **Free** | 180 days | 60 days | Not applicable | 180 days | Not applicable |
42-
43-
44-
<sup>*</sup>: _Segment will implement the Profile event data retention period in June 2025. Until this point, Unify users might see Profile Event Data that is more than 3 years old._
42+
| Tier | Archive Event Data Retention | Profile Event Data Retention | Object Data Retention | Audit | HIPAA Audit |
43+
| ------------ | ---------------------------- | ---------------------------------------- | --------------------- | ------- | -------------- |
44+
| **Business** | 3 years | 3 years | 180 days | 3 years | 3 years |
45+
| **Team** | 365 days | Not applicable | 90 days | 365 days | Not applicable |
46+
| **Free** | 180 days | Not applicable | 60 days | 180 days | Not applicable |
4547

4648
Through the self-serve Data Retention configuration in your workspace, you can configure a custom data retention period through “Workspace Default Archive Retention Period”.
4749

48-
### What is the impact of this policy?
50+
### What data is impacted?
4951

5052
With this data retention policy, all data beyond the retention period will be unrecoverably deleted from all of Segment and will impact the following:
5153

5254
* [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.
5355
* Backfill Data will only be available for data within the retention period.
5456
* [Data residency](/docs/guides/regional-segment/) migrations across regions (US and EU) will only be available for data within the retention period.
5557
* Additional impacts to Object data:
56-
* Cloud Object Data (using push) updated using the [Set API](/docs/connections/sources/catalog/libraries/server/object-api/#set) or [Bulk API](docs/connections/sources/catalog/libraries/server/object-bulk-api/): 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.
58+
* 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 or Mandrill): 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.
5759
* 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.
5860
* [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.
59-
* [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.
61+
* [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.
6062

6163
### What data is not impacted?
6264

@@ -73,7 +75,7 @@ An expired customer is a Business or Team Tier customer that hasn’t renewed th
7375

7476
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.
7577

76-
### What is the impact of this policy?
78+
### What data is impacted?
7779

7880
Expired customers will have:
7981

@@ -86,7 +88,7 @@ A contracted customer is a Business Tier customer that elects to stop using add-
8688

8789
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.
8890

89-
### What is the impact of this policy?
91+
### What data is impacted?
9092

9193
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.
9294

@@ -98,10 +100,7 @@ If contracting from Unify or Unify+, your Connection data will remain unaffected
98100

99101
## Churned customers
100102

101-
A churned customer is a Business or Team Tier customer that has:
102-
103-
* Explicitly terminated the contract **OR**
104-
* Has unpaid invoices and has their workspace fully locked out.
103+
A churned customer is a Business or Team Tier customer that has explicitly terminated the contract or has unpaid invoices and has their workspace fully locked out.
105104

106105
Customers that have explicitly terminated their Segment contract will have their data unrecoverably deleted within 30 days of contract termination.
107106

@@ -118,6 +117,6 @@ An Unused Free Tier workspace is a workspace that has not received any Segment e
118117

119118
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).
120119

121-
### Data deletion timeline
120+
### Data deletion delays
122121

123122
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.

0 commit comments

Comments
 (0)