From bc5701210f085e36be22dcef18227d98cecf4290 Mon Sep 17 00:00:00 2001 From: pwseg Date: Sun, 24 Nov 2024 00:52:09 -0600 Subject: [PATCH 1/6] remove currently --- src/privacy/faq.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/privacy/faq.md b/src/privacy/faq.md index 760492fb7a..4411a001a7 100644 --- a/src/privacy/faq.md +++ b/src/privacy/faq.md @@ -2,11 +2,11 @@ title: Privacy Frequently Asked Questions --- -## Privacy Portal Questions +## Privacy Portal questions -### Why aren't fields from my Cloud Object Sources (such as Salesforce and Zendesk) showing up in the Privacy Portal Inbox and Inventory? +### Why aren't fields from my Cloud Object Sources (like Salesforce and Zendesk) showing up in the Privacy Portal Inbox and Inventory? -We do not currently support Cloud Object Sources in the Privacy Portal, but it's on our roadmap. Stay tuned for new features in the future. +Segment doesn't support Cloud Object Sources in the Privacy Portal. ### Why is Segment suggesting my fields should be classified as Yellow or Red? @@ -33,13 +33,14 @@ Segment classifications are simply recommendations. If an integration you rely on requires a field that we recommend be classified as Yellow, you can override the recommended setting to send that field downstream. -## User Deletion and Suppression Questions +## User deletion and suppression Questions ### How can I find my user's userId? The easiest way to find a customer's `userId` is by querying an existing tool. Specifically, you can use your Segment [data warehouse](https://segment.com/warehouses) to query the `users` table for another known item of information about the user (their email address, for example) and then use that row to find their userId. ### How many deletion requests can I send? + You can send us batches of up to 5,000 `userIds`, or 4 MB, per payload. We process these batches asynchronously. [Contact Segment](https://segment.com/help/contact/){:target="_blank”} if you need to process more than 110,000 users within a 30 day period. ### Which Destinations can I send deletion requests to? From 3ec03d7008f089dc51493863d5f0bafb5a20d7a5 Mon Sep 17 00:00:00 2001 From: pwseg Date: Mon, 25 Nov 2024 21:59:45 -0600 Subject: [PATCH 2/6] PII fuzzy matching FAQ --- src/privacy/faq.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/privacy/faq.md b/src/privacy/faq.md index 4411a001a7..bca9ab098b 100644 --- a/src/privacy/faq.md +++ b/src/privacy/faq.md @@ -6,11 +6,11 @@ title: Privacy Frequently Asked Questions ### Why aren't fields from my Cloud Object Sources (like Salesforce and Zendesk) showing up in the Privacy Portal Inbox and Inventory? -Segment doesn't support Cloud Object Sources in the Privacy Portal. +The Privacy Portal doesn't doesn't support fields from Cloud Object Sources like Salesforce or Zendesk. -### Why is Segment suggesting my fields should be classified as Yellow or Red? +### Why does Segment suggest classifying my fields as Yellow or Red? -You can see a full list of the fields we exact-match and fuzzy-match against [by default](/docs/privacy/portal/#default-pii-matchers). These classifications are our best-guess suggestions, and you can easily change them by following the instructions to [change a recommended classification](/docs/privacy/portal/#change-a-recommended-classification). +Segment provides suggested classifications based on [default PII matchers](/docs/privacy/portal/#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](/docs/privacy/portal/#change-a-recommended-classification). ### Who can access the Privacy Portal? @@ -82,4 +82,4 @@ Segment supports the following regulation types: > info "" -> Using **SUPPRESS_WITH_DELETE** or **DELETE_ONLY** regulation types might lead to additional charges levied by your destination providers. +> Using **SUPPRESS_WITH_DELETE** or **DELETE_ONLY** regulation types might lead to additional charges levied by your destination providers. \ No newline at end of file From dd2b22821c63941f5c0edf589c436863b3c72d41 Mon Sep 17 00:00:00 2001 From: pwseg Date: Mon, 25 Nov 2024 22:01:07 -0600 Subject: [PATCH 3/6] plans don't access anything, people do --- src/privacy/faq.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/privacy/faq.md b/src/privacy/faq.md index bca9ab098b..fddd334715 100644 --- a/src/privacy/faq.md +++ b/src/privacy/faq.md @@ -16,10 +16,9 @@ Segment provides suggested classifications based on [default PII matchers](/docs Only Workspace Owners can access the portal. -### Which Segment plan types get access to the Privacy Portal? +### Which Segment plan types include access to the Privacy Portal? -All Segment plans have access to the Privacy Portal, because we believe data -privacy should be a right, not an add-on. +All Segment plans include access to the Privacy Portal. Data privacy is a fundamental Segment feature, not an add-on. ### If I block data at the Source level, can I reverse it or get that data back using Segment's Data Replay feature? From b11420778bcd74c7da327e0a28809482486c0c7a Mon Sep 17 00:00:00 2001 From: pwseg Date: Mon, 25 Nov 2024 22:03:06 -0600 Subject: [PATCH 4/6] source-level data blocking --- src/privacy/faq.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/src/privacy/faq.md b/src/privacy/faq.md index fddd334715..ea37c944b4 100644 --- a/src/privacy/faq.md +++ b/src/privacy/faq.md @@ -20,11 +20,10 @@ 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. -### If I block data at the Source level, can I reverse it or get that data back using Segment's Data Replay feature? +### If I block data at the source level, can I reverse it or recover the data using Segment's Data Replay feature? + +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. -If you use Privacy Controls to block data at the Source level, the data never -enters Segment, and we cannot Replay that data for you. We recommend caution -when blocking data at the Source level. ### The Privacy Portal classified my property as `Yellow`, but it's required for some of my destinations to function. What should I do? From ba84b86cd6041880ce7734a505189b0ca371974b Mon Sep 17 00:00:00 2001 From: pwseg Date: Mon, 25 Nov 2024 22:07:19 -0600 Subject: [PATCH 5/6] deletion requests FAQ --- src/privacy/faq.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/src/privacy/faq.md b/src/privacy/faq.md index ea37c944b4..1e87a2c8fb 100644 --- a/src/privacy/faq.md +++ b/src/privacy/faq.md @@ -24,22 +24,19 @@ All Segment plans include access to the Privacy Portal. Data privacy is a fundam 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. +### The Privacy Portal classified my property as Yellow, but my destinations require it to function. What should I do? -### The Privacy Portal classified my property as `Yellow`, but it's required for some of my destinations to function. What should I do? +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. -Segment classifications are simply recommendations. If an integration you rely -on requires a field that we recommend be classified as Yellow, you can override -the recommended setting to send that field downstream. +## User deletion and suppression questions -## User deletion and suppression Questions +### How can I find a specific `userId`? -### How can I find my user's userId? - -The easiest way to find a customer's `userId` is by querying an existing tool. Specifically, you can use your Segment [data warehouse](https://segment.com/warehouses) to query the `users` table for another known item of information about the user (their email address, for example) and then use that row to find their userId. +To locate a specific `userId`, query your Segment [data warehouse](https://segment.com/warehouses){:target="_blank”} for the `users` table. Use other known details about the user, like their email address, to identify the correct row and retrieve the `userId`. ### How many deletion requests can I send? -You can send us batches of up to 5,000 `userIds`, or 4 MB, per payload. We process these batches asynchronously. [Contact Segment](https://segment.com/help/contact/){:target="_blank”} if you need to process more than 110,000 users within a 30 day period. +You can send batches of up to 5,000 `userIds`, or 4 MB, per payload. Segment processes these batches asynchronously. [Contact Segment](https://segment.com/help/contact/){:target="_blank”} if you need to process more than 110,000 users within a 30-day period. ### Which Destinations can I send deletion requests to? From fd60c33c8ee78a0d437e8e2e2710e17a52c34790 Mon Sep 17 00:00:00 2001 From: pwseg Date: Mon, 25 Nov 2024 22:12:52 -0600 Subject: [PATCH 6/6] regulation types cleanup --- src/privacy/faq.md | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/src/privacy/faq.md b/src/privacy/faq.md index 1e87a2c8fb..01eeab0b9a 100644 --- a/src/privacy/faq.md +++ b/src/privacy/faq.md @@ -38,9 +38,9 @@ To locate a specific `userId`, query your Segment [data warehouse](https://segme You can send batches of up to 5,000 `userIds`, or 4 MB, per payload. Segment processes these batches asynchronously. [Contact Segment](https://segment.com/help/contact/){:target="_blank”} if you need to process more than 110,000 users within a 30-day period. -### Which Destinations can I send deletion requests to? +### Which destinations can I send deletion requests to? -In addition to your Raw Data destinations (Amazon S3 and Data Warehouses), we can forward requests to the following streaming destinations: +In addition to your Raw Data destinations (Amazon S3 and data warehouses), Segment can forward requests to the following streaming destinations: - Amplitude - Iterable @@ -56,25 +56,26 @@ In addition to your Raw Data destinations (Amazon S3 and Data Warehouses), we ca - Google Cloud PubSub - Friendbuy (Cloud Destination) -Segment cannot guarantee that data is deleted from your Destinations. When you issue a user deletion request, Segment forwards the request to supported streaming Destinations. You must still contact these Destinations to confirm that they've executed the request. +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. -### Which destinations require additional destination setting configuration? +### Which destinations require additional configuration to process deletion requests? #### Amplitude -If you have the Amplitude destination enabled in one or more sources, you must include Amplitude's secret key in each destination(s) settings so they can accept the deletion request. (You add it in the Amplitude destination settings, under "Secret Key"). You can find your Secret Key on the [General Settings](https://help.amplitude.com/hc/en-us/articles/235649848-Settings) of your Amplitude project. +To process deletion requests in Amplitude, add your Amplitude secret key to the destination settings under "Secret Key." You can find this key in your Amplitude project's [General Settings](https://help.amplitude.com/hc/en-us/articles/235649848-Settings){:target="_blank”}. + #### Google Analytics -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. +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. + ### What regulation types does Segment support? Segment supports the following regulation types: -- **SUPPRESS_ONLY**: Suppress new data based on the `userId` without deleting existing data stored in your workspace and in downstream destinations. -- **UNSUPPRESS**: Stop the ongoing suppression of a `userId`. -- **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. -- **DELETE_INTERNAL**: Deletes user data from within Segment archives only and not from any connected destinations. +- **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. - > info "" > Using **SUPPRESS_WITH_DELETE** or **DELETE_ONLY** regulation types might lead to additional charges levied by your destination providers. \ No newline at end of file