User Deletion and Suppression

In keeping with Segment’s commitment to GDPR and CCPA readiness, Segment offers the ability to delete and suppress data about end-users when they are identifiable by a userId, should they revoke or alter consent to data collection. For example, if an end-user invokes the Right to Object or Right to Erasure under the GDPR or CCPA, you can use these features to block ongoing data collection about that user and delete all historical data about them from Segment’s systems, connected S3 buckets and warehouses, and supported downstream partners.

Contact Support if you need to process more than 100,000 users within a 30 day period.

Business Plan Customers

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.

The legacy GraphQL APIs for user deletion and suppression are deprecated. Instead, use the Segment Public API to interact with the User Deletion and Suppression system.


All deletion and suppression actions in Segment are asynchronous and categorized as Regulations. Regulations are requests to Segment to control your data flow. You can issue Regulations from your Segment Workspace, in Settings > End User Privacy

With Regulations, you can issue a single request to delete and suppress data about a user by userId. Segment scopes Regulations to your workspace, and targets all sources within the workspace.

The three types of Regulation are:


SUPPRESS regulations add a user to your suppression list by the userId. Segment blocks suppressed users across all sources; 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. Suppression does not affect device-mode destinations.

When a customer exercises the right to erasure, they expect that you stop collecting data about them. Suppression regulations ensure that regardless of how you’re sending data to Segment, if a user opts out, Segment respects their wishes on an ongoing basis and across applications.

Suppression is not a substitute for gathering affirmative, unambiguous consent about data collection and its uses.

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.

To remove a user from the suppression list, create an UNSUPPRESSION regulation.

Deletion Support and the Right to Be Forgotten

When you create a SUPPRESS_AND_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.

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 delete from S3 by “recopying” clean versions of any files in your bucket that included data about that userId.

Segment forwards these deletion requests to a growing list of supported partners.

Note that Segment has a 30-day SLA for submitted deletion requests. Additionally, Segment’s deletion manager can only accommodate 100,000 users within a 30-day period and cannot guarantee a 30-day SLA if there are more than 100,000 deletion requests submitted within those 30 days.

Segment cannot guarantee that data is deleted from your Destinations.

Segment forwards deletion requests to supported streaming Destinations (such as Braze, Intercom, and Amplitude) 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.

Note that if you later UNSUPPRESS a user, the deletion functionality does not clean up data sent after removing the user from the suppression list.

Suppressed users

The Suppressed Users tab shows an up-to-date list of actively suppressed userIds. Segment blocks data about these users across all sources.

Suppress a new user

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.

Segment creates a SUPPRESS regulation, and adds the userId to your suppression list within 24 hours. Note that the suppression request can take up to 30 days to process.

Remove a user from the suppression list

To remove a user from the suppression list, click the ellipses () icon on the userId row, and click Remove.

This creates an UNSUPPRESS regulation, and removes the userId from your suppression list, within 24 hours.

Deletion requests

The deletion requests tab shows a log of all regulations with a deletion element along with status.

Click a deletion to view its status across Segment and your connected destinations.

Programmatic User Deletion and Suppression using the API

Use the Segment Public API to interact with the User Deletion and Suppression system.

Regulate User from a single Source in a Workspace

Refer to Create Source Regulation in the Public API.

Delete Object from a Cloud Source

Refer to the Create Cloud Source Regulation Public API endpoint.

Cloud Sources sync objects to Segment. As a result, Cloud Sources are regulated based on an objectId instead of a userId. Before you delete the object from Segment, you should delete it from the upstream system first.

List Suppressed Users for your Workspace

Refer to List Suppressions method in the Public API.

List Deletion Requests for your Workspace

Refer to the List Regulations from Source Public API method.

Data retention

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 and for troubleshooting purposes.

Segment recommends keeping your data for at least 30 days to enable replays of your data.

To change your data retention settings, navigate to Privacy > Settings > Data Retention in Segment.

Workspace Default Archive Retention Period

Select the default retention period for the workspace here. This value applies to all sources in the workspace, unless overridden.

Source-Level Archive Retention Periods

Override the workspace default retention period on a per-source level.

This page was last modified: 20 Apr 2023

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account