Skip to content

Commit 3cd26a5

Browse files
author
Anand Ramakrishnan
authored
Update user-deletion-and-suppression.md
1 parent 97cebb2 commit 3cd26a5

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

src/privacy/user-deletion-and-suppression.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,8 @@ The following regulation types are available:
3131
- **SUPPRESS_WITH_DELETE_INTERNAL:** Suppress new data and delete from Segment internals only
3232
- **DELETE_ONLY:** Delete existing data without suppressing any new data
3333

34+
**Note**: Using **SUPPRESS_WITH_DELETE** or **DELETE_ONLY** regulation types might incur additional charges levied by your destination provider.
35+
3436
## Suppression Support and the Right to Revoke Consent
3537

3638
`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, if you set up a destination in [device-mode](/docs/connections/destinations/#connection-modes), the events are sent directly to destinations as well. In this case, Suppression doesn't suppress the events.

0 commit comments

Comments
 (0)