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 (viaSettings > End User Privacy)

-[Public API](https://docs.segmentapis.com/tag/Deletion-and-Suppression){:target="_blank"}

- Your Segment Workspace (Settings > End User Privacy)

-[Segment'sPublic API](https://docs.segmentapis.com/tag/Deletion-and-Suppression){:target="_blank"}

You can programmatically interact with the User Deletion and Suppression systemvia the[Public API](https://docs.segmentapis.com/tag/Deletion-and-Suppression){:target="_blank"}.

You can programmatically interact with the User Deletion and Suppression systemusing the[Public API](https://docs.segmentapis.com/tag/Deletion-and-Suppression){:target="_blank"}.

With Regulations, you can issue a single request to delete and suppress data about a user by`userId`. Segmentcanscopes Regulations to your workspace (which targets all sources within the workspace),orto a specific source or a cloud source.

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), to a specific source, or to a cloud source.

The following regulation types are available:

`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. However, ifa destnation isset up in[device-mode](/docs/connections/destinations/#connection-modes),thenthe events are sent directly to destinations as well and, andSuppressionwill notsuppressevents in this case.

`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. However, ifyouset upa destinationin[device-mode](/docs/connections/destinations/#connection-modes), the events are sent directly to destinations as well. In this case,Suppressiondoesn'tsuppressthe events.

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.

Segment forwards these deletion requests to a[growing list of supported partners](/docs/privacy/faq/#which-destinations-can-i-send-deletion-requests-to).

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.[Contact Support](https://segment.com/help/contact/) if you need to process more than 100,000 users within a 30 day period.

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.[Contact Support](https://segment.com/help/contact/){:target="_blank"} if you need to process more than 100,000 users within a 30 day period.

**Segment cannot guarantee that data is deleted from your Destinations.**

The Suppressed Users tab in Segment App (Settings > End User Privacy) allows you to create new Suppression requests and also shows an list of`userId`s which are**actively** being suppressed. It can take a fewhour/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.

The Suppressed Users tab in Segment App (Settings > End User Privacy) allows you to create new Suppression requests and also shows an list of`userId`s which are**actively** being suppressed. It can take a fewhours/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.

Note that list onlyinclude regulations of type "SUPPRESS_ONLY". If you created a User Deletion request using UI, you will need to check the'Deletion Requests' tab, as thoseregulationsarebasically of type "SUPPRESS_WITH_DELETE".

Note that list onlyincludes`SUPPRESS_ONLY` regulations. If you created a User Deletion request using UI, you will need to check the**Deletion Requests** tab, as those are`SUPPRESS_WITH_DELETE` regulation types.

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.

The deletion request can have one of the following statuses:

1."FAILED"

2."FINISHED"

3."INITIALIZED"

4."INVALID"

5."NOT_SUPPORTED"

6."PARTIAL_SUCCESS"

7."RUNNING"

When checking the status of deletion requestsvia the API, the deletion will report an overall status of all of the deletion processes. As a result,we will return a 'FAILED' status because ofa failure ona unsupported destination, even if the deletion from Segment Internal Systems and supported destinations were completed successfully.

When checking the status of deletion requestsusing 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 onan unsupported destination, even if the deletion from the Segment Internal Systems and supported destinations were completed successfully.