Skip to content

Commit ff99c9e

Browse files
Update faq.md
Addition of new content to the deletion and suppression questions section.
1 parent fa1449b commit ff99c9e

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

src/privacy/faq.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,3 +69,11 @@ If you have the Amplitude destination enabled in one or more sources, you must i
6969

7070
#### Google Analytics
7171
To send user deletion requests to Google Analytics you must authenticate your Google Analytics account with Segment using OAuth. If you have the Google Analytics destination enabled in one or more sources, you must authenticate your account in each destination(s) settings. Navigate to the **User Deletion** settings in your Segment Google Analytics settings and use your email and password to authenticate your account.
72+
73+
### What are different regulation types supported and when they can used?
74+
75+
- **SUPPRESS_ONLY**: Suppress new data based on the `userId` without deleting existing data.
76+
- **UNSUPPRESS**: Stop the ongoing suppression of a `userId`.
77+
- **SUPPRESS_WITH_DELETE**: Suppress new data based on the `userId` and also delete all existing data for that ID from your workspace and our internal archives. While we do forward the deletion request to our supported destinations, we cannot guarantee deletion.
78+
- **DELETE_INTERNAL**: Deletes user data from within Segment archives only and not from any connected destinations.
79+
- **DELETE_ONLY**: Deletes user data from Segment, connected warehouses along with a request being sent to the supported destinations.

0 commit comments

Comments
 (0)