You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/privacy/user-deletion-and-suppression.md
+57-53Lines changed: 57 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: User Deletion and Suppression
3
3
---
4
4
5
-
Segment offers you the ability to delete and suppress data about your end-users when they are identifiable by a `userId` to support your compliance with privacy regulations like the GDPR and CCPA. For example, if your end-user invokes the Right to Object or Right to be Forgotten, you can block ongoing data collection about that user and delete all historical data about them from Segment’s systems, any of your connected warehouses or S3 buckets, and some supported downstream partners.
5
+
Segment offers you the ability to delete and suppress data about your end-users when they are identifiable by a `userId` to support your compliance with privacy regulations like the GDPR and CCPA. For example, if your end-user invokes the Right to Object or Right to be Forgotten, you can block ongoing data collection about that user and delete all historical data about them from Segment's systems, any of your connected warehouses or S3 buckets, and some supported downstream partners.
6
6
7
7
> info "Business Plan Customers"
8
8
> If you use this feature to delete data, you can not Replay the deleted data. For standard Replay requests, you must wait for any pending deletions to complete, and you cannot submit new deletion requests for the period of time that Segment replays data for you.
@@ -11,12 +11,12 @@ Segment offers you the ability to delete and suppress data about your end-users
11
11
12
12
All deletion and suppression actions in Segment are asynchronous and categorized as Regulations, or requests to Segment to control your data flow. You can issue Regulations from:
13
13
14
-
- Your Segment Workspace (**Settings > End User Privacy**)
14
+
- Your Segment Workspace (Settings > End User Privacy)
15
15
-[Segment's Public API](https://docs.segmentapis.com/tag/Deletion-and-Suppression){:target="_blank"}. You can delete up to 5000 `userId`s per call using the Public API.
16
16
17
-
With Regulations, you can issue a single request to delete and suppress data about a user by `userId`. Segment scopes Regulations to your workspace (which targets all sources within the workspace).
17
+
With Regulations, you can issue a single request to delete and suppress data about a user by `userId`. Segment scopes Regulations to all sources in your workspace.
18
18
19
-
> warning "Data sent to device-mode destinations cannot be suppressed"
19
+
> warning "Data sent to device-mode destinations cannot be suppressed"
20
20
> Destinations set up in device mode are sent directly to destinations and bypass the point in the pipeline where Segment suppresses events.
21
21
22
22
The following regulation types are available:
@@ -28,96 +28,100 @@ The following regulation types are available:
28
28
-**SUPPRESS_WITH_DELETE:** Suppress new data and delete existing data
29
29
-**DELETE_ONLY:** Delete existing data without suppressing any new data
30
30
31
-
*To send more than 110,000 SUPPRESS_ONLY, UNSUPRESS, DELETE_INTERNAL and/or SUPPRESS_WITH_DELETE_INTERNAL Regulations over a 30 day period, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"}. Segment can’t increase the limit for SUPPRESS_WITH_DELETE and DELETE_ONLY regulations. Regulations submitted after you’ve hit the 110,000 Regulations in a 30 day period are rate limited.
31
+
> info "All regulations are rate limited to 110,000 users within a 30-day period"
32
+
> To send more than 110,000 `SUPPRESS_ONLY`, `UNSUPRESS`, `DELETE_INTERNAL` and/or `SUPPRESS_WITH_DELETE_INTERNAL` Regulations over a 30 day period, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"}.
32
33
33
-
> info " "
34
-
> Using **SUPPRESS_WITH_DELETE** or **DELETE_ONLY** regulation types might lead to additional charges levied by your destination providers.
34
+
## Deletion Support
35
35
36
-
## The Right to be Forgotten and Suppression Support
36
+
When you create a `SUPPRESS_WITH_DELETE` and `SUPPRESS_WITH_DELETE_INTERNAL` regulation, Segment begins to suppress new data ingestion for that user, and begins to permanently delete previously ingested data associated with this user from your workspace. This includes scanning and removing all messages related to that `userId` from all data stores that don't automatically expire data within 30 days.
37
37
38
-
When your customers exercise their Right to be Forgotten, sometimes known as Right to Erasure, they expect you to stop collecting new data and delete all previously collected data from your systems: including Segment and other downstream tools.
38
+
Segment deletes messages with this `userId` from the following warehouses and storage destinations:
39
+
- Redshift
40
+
- BigQuery
41
+
- Postgres
42
+
- Snowflake
43
+
- Amazon S3
39
44
40
-
Segment offers suppression tools to help you manage the challenge of users opting-out across different channels and platforms. Segment encourages and expects that you design your systems and applications so you don't collect or forward data to Segment until you have unambiguous, specific, informed consent or have established another lawful legal basis to do so.
45
+
Warehouse deletions occur using a DML run against your cluster or instance. Segment deletes from S3 by "recopying" clean versions of any files in your bucket that included data about that `userId`.
41
46
42
-
**Suppression is not a substitute for gathering affirmative, unambiguous consent about data collection and its uses.**
47
+
<!--- not supported yet > warning "Connected warehouses deletions"
48
+
> Segment will attempt to delete messages with the target `userId` from your connected warehouses for 7 days. If, after 7 days, Segment cannot delete all identified messages from your connected data warehouse, Segment displays a status of `unsuccessful`. If Segment is unable to delete all identified messages, you will be responsible for removing any --->
43
49
44
-
###Suppression support
50
+
#### Deletion requests tab
45
51
46
-
[`SUPPRESS` regulations](#suppress-a-new-user) add a user to your suppression list by the `userId`. Segment blocks suppressed users across all sources, and messages you send to Segment with a suppressed `userId` are blocked at the API. These messages do not appear in the debugger, are not saved in archives and systems, and are not sent to any downstream server-side destinations.
52
+
The deletion requests tab shows a log of all regulations and their status.
47
53
48
-
To [remove a user from the suppression list](#remove-a-user-from-the-suppression-list), create an `UNSUPPRESS` regulation.
54
+
In the Segment App (Settings > End User Privacy > Deletion Requests), you can click a `userId` to view its status in Segment internal systems and in the connected destinations.
49
55
50
-
##### Suppress a new user
51
-
52
-
To create a suppression regulation and add a `userId` to this list, click **Suppress New User**, and enter the `userId` in the field that appears. Then click **Request Suppression**.
56
+
The deletion request can have one of the following statuses:
53
57
54
-
Segment creates a `SUPPRESS` regulation, and adds the `userId` to your suppression list, mostly processed within 24 hours. In some cases, the suppression request can take up to 30 days to process.
58
+
1.`INITIALIZED`
59
+
2.`INVALID`
60
+
3.`NOT_SUPPORTED`
61
+
4.`RUNNING`
62
+
5.`PARTIAL_SUCCESS`
63
+
6.`FAILED`
64
+
7.`FINISHED`
55
65
56
-
##### Remove a user from the suppression list
66
+
When checking the status of deletion requests using Segment's API, the deletion will report an overall status of all of the deletion processes. As a result, Segment returns a `FAILED` status because of a failure on an unsupported destination, even if the deletion from the Segment Internal Systems and supported destinations were completed successfully.
57
67
58
-
To remove a user from the suppression list, click the ellipses (**...**) icon on the `userId` row and click **Remove**.
68
+
#### Deletion request SLA
59
69
60
-
This creates an `UNSUPPRESS` regulation and removes the `userId` from your suppression list. Segment processes most `UNSUPPRESS` regulations within 24 hours.
70
+
Segment has a 30-day SLA for completing deletion requests in Segment's internal stores for deletion requests of fewer than 110,000 users made over 30 days. Your requests will be rate limited if you submit more than 110,000 deletion requests within 30 days.
61
71
62
-
### Suppressed Users
72
+
> warning "This 30-day SLA is limited to only Segment's internal stores"
73
+
> Segment cannot guarantee that deletions in your Amazon S3 instance, your connected data warehouse, or other third-party destinations will be completed during that 30-day period.
63
74
64
-
The Suppressed Users tab in Segment App (**Settings > End User Privacy**) allows you to create new Suppression requests and also shows a list of `userId`s which are **actively** being suppressed. It can take a few hours/days for the suppression to become active, depending on the number of requests that are in the queue for your workspace. Once the request is active, Segment blocks data about these users across all sources.
75
+
Segment forwards your deletion requests to a [growing list of supported partners](/docs/privacy/faq/#which-destinations-can-i-send-deletion-requests-to), but you should confirm that each partner fulfills the request. You will also need to contact any unsupported Destinations separately to manage user data deletion.
65
76
66
-
> info "`SUPPRESS_WITH_DELETE` requests"
67
-
> The Suppressed Users tab only includes `SUPPRESS_ONLY` regulations. If you created a User Deletion request using the UI, you will need to check the [**Deletion Requests**](#deletion-requests-tab) tab, as those are `SUPPRESS_WITH_DELETE` regulation types.
77
+
> info "Users that you UNSUPPRESS after issuing a deletion request may have remaining data"
78
+
> If you **UNSUPPRESS** a user after issuing a deletion request for that user, Segment's deletion functionality does not clean up data sent after removing the user from the suppression list.
68
79
69
-
## Deletion Support
80
+
## The Right to be Forgotten and Suppression Support
70
81
71
-
When you create a `SUPPRESS_WITH_DELETE` regulation, the user is actively suppressed, and Segment begins permanently deleting all data associated with this user from your workspace. This includes scanning and removing all messages related to that `userId`from all storage mediums that don't automatically expire data within 30 days, including archives, databases, and intermediary stores.
82
+
When your customers exercise their Right to be Forgotten, sometimes known as Right to Erasure, they expect you to stop collecting new data and delete all previously collected data from your systems: including from Segment and other downstream tools.
72
83
73
-
Segment deletes messages with this `userId` from connected raw data Destinations, including Redshift, BigQuery, Postgres, Snowflake, and Amazon S3. Warehouse deletions occur using a DML run against your cluster or instance, and Segment deletes from S3 by "recopying" clean versions of any files in your bucket that included data about that `userId`.
84
+
Segment offers suppression tools to help you manage the challenge of users opting-out across different channels and platforms. Segment encourages and expects that you design your systems and applications so you don't collect or forward data to Segment until you have unambiguous, specific, informed consent or have established another lawful legal basis to do so.
74
85
75
-
> warning "Connected warehouses deletions"
76
-
> Segment will attempt to delete messages with the target `userId` from your connected warehouses for 7 days. If, after 7 days, Segment cannot delete all identified messages from your connected data warehouse, Segment displays a status of `unsuccessful`. If Segment is unable to delete all identified messages, you will be responsible for removing any remaining messages.
86
+
**Suppression is not a substitute for gathering affirmative, unambiguous consent about data collection and its uses.**
77
87
78
-
#### Deletion request SLA
88
+
###Suppression support
79
89
80
-
Segment has a 30-day SLA for completing deletion requests in Segment’s internal stores for deletion requests of fewer than 110,000 users made over 30 days. Your requests will be rate limited If you submit more than 110,000 deletion requests within 30 days.
90
+
[`SUPPRESS` regulations](#suppress-a-new-user) add a user to your suppression list by the `userId`. Segment blocks suppressed users across all sources, and messages you send to Segment with a suppressed `userId` are blocked at the API. These messages do not appear in the debugger, are not saved in archives and systems, and are not sent to any downstream server-side destinations.
81
91
82
-
**This 30-day SLA is limited to only Segment’s internal stores.** Segment cannot guarantee that deletions in your Amazon S3 instance, your connected data warehouse, or other third-party destinations will be completed during that 30-day period.
92
+
To [remove a user from the suppression list](#remove-a-user-from-the-suppression-list), create an `UNSUPPRESS` regulation.
83
93
84
-
Segment forwards your deletion requests to a [growing list of supported partners](/docs/privacy/faq/#which-destinations-can-i-send-deletion-requests-to), but you should confirm that each partner fulfills the request. You will also need to contact any unsupported Destinations separately to manage user data deletion.
94
+
##### Suppress a new user
85
95
86
-
> info "Users that you `UNSUPPRESS` after issuing a deletion request may have remaining data"
87
-
> If you **UNSUPPRESS** a user after issuing a deletion request for that user, Segment’s deletion functionality does not clean up data sent after removing the user from the suppression list.
96
+
The Suppressed Users tab in Segment App (Settings > End User Privacy) allows you to create new Suppression requests and also shows a list of `userId`s which are **actively** being suppressed.
88
97
89
-
#### Deletion requests tab
98
+
To create a suppression regulation and add a `userId` to this list, click **Suppress New User**, and enter the `userId` in the field that appears. Then click **Request Suppression**.
90
99
91
-
The deletion requests tab shows a log of all regulations with a deletion element along with status. Deletion requests can take up to 30 days to process.
100
+
Segment creates a `SUPPRESS` regulation, and adds the `userId` to your suppression list, mostly processed within 24 hours. In some cases, the suppression request can take up to 30 days to process, depending on the number of requests that are in the queue for your workspace. Once you've created the request, Segment blocks data about these users across all sources.
92
101
93
-
In the Segment App (Settings > End User Privacy > Deletion Requests), you can click a userId to view its status in Segment internal systems and in the connected destinations.
102
+
> info "SUPPRESS_WITH_DELETE requests"
103
+
> The Suppressed Users tab only includes `SUPPRESS_ONLY` regulations. If you created a User Deletion request using the UI, you will need to check the [**Deletion Requests**](#deletion-requests-tab) tab, as those are `SUPPRESS_WITH_DELETE` regulation types.
94
104
95
-
The deletion request can have one of the following statuses:
105
+
##### Remove a user from the suppression list {#remove-a-user-from-the-suppression-list}
96
106
97
-
1.`FAILED`
98
-
2.`FINISHED`
99
-
3.`INITIALIZED`
100
-
4.`INVALID`
101
-
5.`NOT_SUPPORTED`
102
-
6.`PARTIAL_SUCCESS`
103
-
7.`RUNNING`
107
+
To remove a user from the suppression list, click the ellipses (**...**) icon on the `userId` row, and click **Remove**.
104
108
105
-
When checking the status of deletion requests using Segment's API, the deletion will report an overall status of all of the deletion processes. As a result, Segment returns a `FAILED` status because of a failure on an unsupported destination, even if the deletion from the Segment Internal Systems and supported destinations were completed successfully.
109
+
This creates an `UNSUPPRESS` regulation and removes the `userId` from your suppression list. Segment processes most `UNSUPPRESS` regulations within 24 hours.
106
110
107
111
## Data retention
108
112
109
-
Segment stores a copy of all event data received in Segment’s secure event archives on S3. By default, all workspaces store data for an unlimited period of time, but you can modify the lifecycle policies for the data stored internally. Segment uses this data for [data replays](/docs/guides/what-is-replay/) and for troubleshooting purposes.
113
+
Segment stores a copy of all event data received in Segment's secure event archives on S3. By default, all workspaces store data for an unlimited period of time, but you can modify the lifecycle policies for the data stored internally. Segment uses this data for [data replays](/docs/guides/what-is-replay/) and for troubleshooting purposes.
110
114
111
115
Segment recommends keeping your data for at least 30 days to enable [replays](/docs/guides/what-is-replay/) of your data.
112
116
113
-
To change your data retention settings, navigate to **Privacy > Settings > Data Retention** in Segment.
117
+
To change your data retention settings, open Segment and navigate to **Privacy > Settings > Data Retention**.
114
118
115
119
### Workspace Default Archive Retention Period
116
120
117
121
Select the default retention period for the workspace in this setting. This value applies to all sources in the workspace, unless overridden in the [Source-Level Archive Retention Periods](#source-level-archive-retention-periods) setting.
118
122
119
123
> warning "7 day Retention Periods will be deprecated on March 6, 2025"
120
-
> After March 6, you will no longer be able to set your workspace’s retention period to 7 days. All workspaces with 7 day retention periods will be updated to have 14 day retention periods.
124
+
> After March 6, you will no longer be able to set your workspace's retention period to 7 days. All workspaces with 7 day retention periods will be updated to have 14 day retention periods.
121
125
122
126
You can select from the following Archive Retention time periods:
123
127
@@ -131,7 +135,7 @@ You can select from the following Archive Retention time periods:
131
135
### Source-Level Archive Retention Periods
132
136
133
137
> warning "Source-Level Archive Retention Periods will be deprecated on April 15, 2025"
134
-
> After April 15, you will no longer be able to override your workspace’s default retention period on a source-by-source basis.
138
+
> After April 15, you will no longer be able to override your workspace's default retention period on a source-by-source basis.
135
139
136
140
Override the workspace default retention period on a per-source level.
137
141
@@ -143,4 +147,4 @@ You can select from the following Archive Retention time periods:
0 commit comments