Skip to content

Commit 6c2419a

Browse files
Merge pull request #5658 from segmentio/dineshraj-arunmozhi-patch-1
Update faq.md
2 parents ba805c5 + b6ba7e6 commit 6c2419a

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

src/privacy/faq.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,3 +69,12 @@ 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 regulation types does Segment support?
74+
75+
Segment supports the following regulation types:
76+
- **SUPPRESS_ONLY**: Suppress new data based on the `userId` without deleting existing data stored in your workspace and in downstream destinations.
77+
- **UNSUPPRESS**: Stop the ongoing suppression of a `userId`.
78+
- **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 Segment forwards the deletion request to your downstream destinations, Segment cannot guarantee deletion in your third-party tools.
79+
- **DELETE_INTERNAL**: Deletes user data from within Segment archives only and not from any connected destinations.
80+
- **DELETE_ONLY**: Deletes user data from Segment and your connected warehouses. Also sends a deletion request to your downstream destinations.

0 commit comments

Comments
 (0)