Privacy Frequently Asked Questions

Get answers to common questions about Segment's Privacy Portal.

The Privacy Portal doesn't doesn't support fields from Cloud Object Sources like Salesforce or Zendesk.

Segment provides suggested classifications based on default PII matchers. These suggestions include exact and fuzzy matches for potential PII. You can update these classifications by following the instructions to change a recommended classification.

Only Workspace Owners can access the portal.

All Segment plans include access to the Privacy Portal. Data privacy is a fundamental Segment feature, not an add-on.

When you block data at the source level using Privacy Controls, the data never enters Segment. As a result, Segment can't replay the data. Segment recommends exercising caution when blocking data at the source level.

Segment classifications are recommendations. If a destination requires a field classified as Yellow, you can override the recommended classification to ensure the field gets sent downstream.

Find answers to common questions about deleting and suppressing users.

To locate a specific userId, query your Segment data warehouse for the users table. Use other known details about the user, like their email address, to identify the correct row and retrieve the userId.

You can send batches of up to 5,000 userIds, or 4 MB, per payload. Segment processes these batches asynchronously. Contact Segment if you need to process more than 110,000 users within a 30-day period.

In addition to your Raw Data destinations (Amazon S3 and data warehouses), Segment can forward requests to the following streaming destinations:

• Amplitude
• Iterable
• Braze
• Intercom
• Webhooks
• tray.io
• Appcues
• Vero
• Customer.io
• Optimizely Full Stack
• Google Analytics
• Google Cloud PubSub
• Amplitude (Actions)
• Customer.io (Actions)
• Braze Cloud Mode (Actions)
• Friendbuy (Cloud Destination)
• Fullstory Cloud Mode (Actions)
• Intercom Cloud Mode (Actions)

Segment forwards deletion requests but cannot guarantee that data is deleted from downstream destinations. You must contact these destinations to confirm that they executed the request.

To process deletion requests in Amplitude, find your secret key in your Amplitude project's General Settings page, then open the Segment app, navigate to your Amplitude destination's settings page, and paste your Amplitude secret key to the destination settings under "Secret Key."

To send deletion requests to Google Analytics, authenticate your account with Segment using OAuth. Go to the User Deletion settings in your Segment Google Analytics destination and use your email and password to complete authentication.

Segment supports the following regulation types:

• SUPPRESS\_ONLY: Suppresses new data for a userId without deleting existing data in your workspace or downstream destinations.
• UNSUPPRESS: Stops ongoing suppression of a userId.
• SUPPRESS\_WITH\_DELETE: Suppresses new data for a userId and deletes all existing data for that ID in your workspace and Segment's internal archives. Segment forwards the deletion request to downstream destinations but can't guarantee deletion in third-party tools.
• DELETE\_INTERNAL: Deletes user data only from Segment archives, without affecting downstream destinations.
• DELETE\_ONLY: Deletes user data from Segment and your connected warehouses. Also sends a deletion request to your downstream destinations.