Suppress and delete user data in accordance with your data regulation policies.
RudderStack’s Data Regulation API lets you create regulations to suspend data collection and delete data for particular users.
The Data regulation API is applicable only for destinations configured to send events using cloud mode.
What is data regulation?
In order to comply with data regulation statutes and users’ privacy choices, we provide tools that allow you to:
Suppress incoming source data for a user or list of users
Delete collected data for users that resides in a given destination
You can leverage RudderStack’s data regulation feature to suppress any incoming data for a given user. RudderStack will drop the events for that user at the source. After suppression, events:
With our regulation APIs, perform the following actions:
Add a suppression regulation. A suppression regulation drops the user events at the source, and they will not be available for debugging, replay, or forwarded to destinations.
Add a suppress and delete regulation. A suppress/delete regulation deletes any user data that was sent to a destination.
List all regulations
Delete a specific regulation
Authorization
Our data regulation APIs use Bearer authentication in the format Authorization: Bearer <PERSONAL_ACCESS_TOKEN>.
When creating your data regulations with our API, you may wish to name specific sources for a suppress regulation, and specific destinations for a suppress/delete regulation. To do so you must first obtain the source and/or destination IDs.
Retrieve source and destination IDs for your data regulations from your RudderStack dashboard, or by using the /v2/sources and /v2/destinations endpoints:
For the above-mentioned destinations, you can delete a user by specifying the userId in the event. Except for Redis and S3 destinations, you can also specify a custom identifier (optional) in the event in addition to the userId.
Request body
regulationType
required
string
Defines the data regulation type. Can be one of suppress, which suppresses incoming user data or suppress_with_delete which suppresses and deletes events from your specified destinations.
Possible Values: suppress, suppress_with_delete
sourceIds
optional
array
Specify only sourceIds with the ‘suppress’ regulationType. If no sourceIds are specified, RudderStack will suppress data from all sources in the workspace associated with your access token.
destinationIds
optional
array
Specify only destinationIds with the ‘suppress_with_delete’ regulationType. Otherwise, RudderStack throws an error.
users
required
array
An array of user objects identifying users to be suppressed. The userId field is mandatory for all users. You can pass additional custom identifiers such as email in the users object.
Do not specify both sourceIds and destinationIds in your request body.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.