From 4162e3b4b5020f08cc4ece19ab87a830b413e761 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 5 Jun 2025 11:03:27 -0400 Subject: [PATCH 01/13] update docs file structure to match app --- src/_data/sidenav/main.yml | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index 8fcf0bfa3e..18daaae20f 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -561,23 +561,20 @@ sections: title: Privacy Overview - section_title: Privacy Portal slug: protocols/portal - expanded: true section: - path: /privacy/portal title: Detect PII - path: /privacy/data-controls title: Data Controls and Alerts - - section_title: GDPR - slug: protocols/complying-with-the-gdpr - expanded: true + - section_title: Deletion and Suppression + slug: privacy/user-deletion-and-suppression section: - - path: /privacy/complying-with-the-gdpr - title: Complying With GDPR - path: /privacy/user-deletion-and-suppression title: User Deletion and Suppression + - path: /privacy/account-deletion + title: Account & Data Deletion - section_title: Consent Management slug: privacy/consent-management - expanded: true section: - path: /privacy/consent-management title: Consent Management Overview @@ -593,8 +590,8 @@ sections: title: Consent FAQs - path: /privacy/data-retention-policy title: Data Retention and Deletion Policy - - path: /privacy/account-deletion - title: Account & Data Deletion + - path: /privacy/complying-with-the-gdpr + title: Complying With GDPR - path: /privacy/hipaa-eligible-segment title: HIPAA Eligible Segment - path: /privacy/faq From d2e0fd5f85d978f91fbd0ce2ff18f4d1e65e240b Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 5 Jun 2025 13:02:18 -0400 Subject: [PATCH 02/13] update privacy portal overview page --- src/_data/privacy.yml | 43 ++++++++++++++++++++++++++++++-------- src/_data/sidenav/main.yml | 14 ++++++------- 2 files changed, 41 insertions(+), 16 deletions(-) diff --git a/src/_data/privacy.yml b/src/_data/privacy.yml index e03789d66c..3a48d58a34 100644 --- a/src/_data/privacy.yml +++ b/src/_data/privacy.yml @@ -3,22 +3,47 @@ sections: section_col: 6 section: - name: Detect and classify customer data - description: "The Privacy Portal helps automate preparing for new privacy regulations." + description: "The Privacy Portal helps streamline your response to new privacy regulations." path: /privacy/portal/ icon: media/classify.svg - name: Control what data you collect - description: "Take control over whether specific data is allowed to enter Segment" + description: "Take control of the data that comes into your workspace." path: /privacy/data-controls/ icon: media/control.svg -- section_title: Prepare for GDPR & CCPA +- section_title: Respect your end user's consent preferences + section_col: 4 + section: + - name: Consent in Segment Connections + description: "Manage end user consent in your downstream tools with Consent Management." + path: /privacy/consent-management/consent-in-segment-connections/ + - name: Consent in Reverse ETL + description: "Enforce consent preferences stored in your data warehouse." + path: /privacy/consent-management/consent-in-retl/ + - name: Consent stored on the Profile + description: "Create Audiences of users that consent to receive marketing communications." + path: /docs/privacy/consent-management/consent-in-unify/ + +- section_title: Delete and suppress user information section_col: 6 section: - - name: Understand and Comply with regulations - description: "Segment is committed to making it easier for you to comply with the GDPR." - path: /privacy/complying-with-the-gdpr/ - icon: media/comply.svg - - name: Delete and suppress data about end-users - description: "Easily remove your company's end-users from Segment and supported connections." + - name: Delete and suppress data about end users + description: "Remove your company's end users from Segment and supported connections." path: /privacy/user-deletion-and-suppression/ + icon: media/detect.svg + - name: Delete data from sources, a Unify space, or your entire workspace + description: "Remove all data from a source, a Unify space, or a workspace." + path: /privacy/account-deletion/ icon: media/delete.svg + +- section_title: Comply with privacy regulations + section_col: 12 + section: + - name: Data Deletion and Retention Policy + icon: media/comply.svg + description: "Manage your data accurately, efficiently and securely within clearly defined retention periods." + path: /privacy/data-retention-policy/ + - name: HIPAA-Eligible Segment + icon: media/database-star.svg + description: "Segment is a HIPAA eligible platform, and meets the data privacy and security requirements of healthcare customers and their stakeholders." + path: /privacy/hipaa-eligible-segment/ diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index 18daaae20f..1385dab3cd 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -566,13 +566,6 @@ sections: title: Detect PII - path: /privacy/data-controls title: Data Controls and Alerts - - section_title: Deletion and Suppression - slug: privacy/user-deletion-and-suppression - section: - - path: /privacy/user-deletion-and-suppression - title: User Deletion and Suppression - - path: /privacy/account-deletion - title: Account & Data Deletion - section_title: Consent Management slug: privacy/consent-management section: @@ -588,6 +581,13 @@ sections: title: Consent in Reverse ETL - path: /privacy/consent-management/consent-faq title: Consent FAQs + - section_title: Deletion and Suppression + slug: privacy/user-deletion-and-suppression + section: + - path: /privacy/user-deletion-and-suppression + title: User Deletion and Suppression + - path: /privacy/account-deletion + title: Account & Data Deletion - path: /privacy/data-retention-policy title: Data Retention and Deletion Policy - path: /privacy/complying-with-the-gdpr From f39070b903bfc306173134349fe9108f34a4a5f8 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 5 Jun 2025 13:08:55 -0400 Subject: [PATCH 03/13] [netlify-build] --- src/_data/privacy.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_data/privacy.yml b/src/_data/privacy.yml index 3a48d58a34..ea32d48c94 100644 --- a/src/_data/privacy.yml +++ b/src/_data/privacy.yml @@ -46,4 +46,4 @@ sections: - name: HIPAA-Eligible Segment icon: media/database-star.svg description: "Segment is a HIPAA eligible platform, and meets the data privacy and security requirements of healthcare customers and their stakeholders." - path: /privacy/hipaa-eligible-segment/ + path: /privacy/hipaa-eligible-segment/ \ No newline at end of file From 897d5842d47b70dcbc8ecec19ba3c77b793cb191 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 5 Jun 2025 14:59:25 -0400 Subject: [PATCH 04/13] [netlify-build] --- src/_data/privacy.yml | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/src/_data/privacy.yml b/src/_data/privacy.yml index ea32d48c94..5ce0a82be3 100644 --- a/src/_data/privacy.yml +++ b/src/_data/privacy.yml @@ -24,26 +24,27 @@ sections: description: "Create Audiences of users that consent to receive marketing communications." path: /docs/privacy/consent-management/consent-in-unify/ -- section_title: Delete and suppress user information - section_col: 6 +- section_title: Delete user and workspace data + section_col: 4 section: - - name: Delete and suppress data about end users + - name: Comply with GDPR and CCPA by deleting information about your company's end users from Segment description: "Remove your company's end users from Segment and supported connections." path: /privacy/user-deletion-and-suppression/ - icon: media/detect.svg - name: Delete data from sources, a Unify space, or your entire workspace description: "Remove all data from a source, a Unify space, or a workspace." path: /privacy/account-deletion/ - icon: media/delete.svg - -- section_title: Comply with privacy regulations - section_col: 12 - section: - name: Data Deletion and Retention Policy - icon: media/comply.svg description: "Manage your data accurately, efficiently and securely within clearly defined retention periods." path: /privacy/data-retention-policy/ + +- section_title: Tools to comply with privacy regulations + section_col: 6 + section: - name: HIPAA-Eligible Segment icon: media/database-star.svg description: "Segment is a HIPAA eligible platform, and meets the data privacy and security requirements of healthcare customers and their stakeholders." + path: /privacy/hipaa-eligible-segment/ + - name: Complying with the GDPR + icon: media/comply.svg + description: "Learn more about the tools and strategies you can use to maintain GDPR compliance." path: /privacy/hipaa-eligible-segment/ \ No newline at end of file From 903985c52dca150149c828dfba3132898d91e242 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 5 Jun 2025 17:46:03 -0400 Subject: [PATCH 05/13] Update src/_data/privacy.yml Co-authored-by: rchinn1 <93161299+rchinn1@users.noreply.github.com> --- src/_data/privacy.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_data/privacy.yml b/src/_data/privacy.yml index 5ce0a82be3..7846fac3a0 100644 --- a/src/_data/privacy.yml +++ b/src/_data/privacy.yml @@ -34,7 +34,7 @@ sections: description: "Remove all data from a source, a Unify space, or a workspace." path: /privacy/account-deletion/ - name: Data Deletion and Retention Policy - description: "Manage your data accurately, efficiently and securely within clearly defined retention periods." + description: "Manage your data accurately, efficiently, and securely within clearly defined retention periods." path: /privacy/data-retention-policy/ - section_title: Tools to comply with privacy regulations From ca9eb360772b86f9fe9d1cbca58b2fd1e2778560 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 5 Jun 2025 17:49:44 -0400 Subject: [PATCH 06/13] fix [netlify-build] --- src/_data/privacy.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/_data/privacy.yml b/src/_data/privacy.yml index 5ce0a82be3..5882a899bc 100644 --- a/src/_data/privacy.yml +++ b/src/_data/privacy.yml @@ -27,8 +27,8 @@ sections: - section_title: Delete user and workspace data section_col: 4 section: - - name: Comply with GDPR and CCPA by deleting information about your company's end users from Segment - description: "Remove your company's end users from Segment and supported connections." + - name: Delete and suppress data about end usersDelete and suppress data about end users + description: "Comply with GDPR and CCPA by deleting information from Segment about your company's end users." path: /privacy/user-deletion-and-suppression/ - name: Delete data from sources, a Unify space, or your entire workspace description: "Remove all data from a source, a Unify space, or a workspace." From 0157936ae0d81b0a74fe14fd4a1e4c52e9afc457 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 6 Jun 2025 10:23:27 -0400 Subject: [PATCH 07/13] fixes [netlify-build] --- src/_data/privacy.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/_data/privacy.yml b/src/_data/privacy.yml index c5681302d6..80a9090a28 100644 --- a/src/_data/privacy.yml +++ b/src/_data/privacy.yml @@ -21,13 +21,13 @@ sections: description: "Enforce consent preferences stored in your data warehouse." path: /privacy/consent-management/consent-in-retl/ - name: Consent stored on the Profile - description: "Create Audiences of users that consent to receive marketing communications." + description: "Create Audiences of users based on consent status." path: /docs/privacy/consent-management/consent-in-unify/ - section_title: Delete user and workspace data section_col: 4 section: - - name: Delete and suppress data about end usersDelete and suppress data about end users + - name: Delete and suppress data about end users description: "Comply with GDPR and CCPA by deleting information from Segment about your company's end users." path: /privacy/user-deletion-and-suppression/ - name: Delete data from sources, a Unify space, or your entire workspace From dc19d0f2d2b65b4acecc9b767c39b2903a02d823 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 18 Jun 2025 10:04:05 -0400 Subject: [PATCH 08/13] Update user-deletion-and-suppression.md --- src/privacy/user-deletion-and-suppression.md | 42 +++++++++++++++----- 1 file changed, 31 insertions(+), 11 deletions(-) diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index 9ca47c665a..dd1f7f6e41 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -14,22 +14,32 @@ All deletion and suppression actions in Segment are asynchronous and categorized - Your Segment Workspace (Settings > End User Privacy) - [Segment's Public API](https://docs.segmentapis.com/tag/Deletion-and-Suppression){:target="_blank"}. You can delete up to 5000 `userId`s per call using the Public API. -With Regulations, you can issue a single request to delete and suppress data about a user by `userId`. Segment scopes Regulations to all sources in your workspace. +With Regulations, you can issue a single request to delete and suppress data about a user by `userId`. Segment scopes Regulations to all sources in your workspace. > warning "Data sent to device-mode destinations cannot be suppressed" -> Destinations set up in device mode are sent directly to destinations and bypass the point in the pipeline where Segment suppresses events. +> Destinations set up in device mode are sent directly to destinations and bypass the point in the pipeline where Segment suppresses events. -The following regulation types are available: +Segment has 2 types of Regulations - Segment-only Regulations, or those that only impact data from Segment systems, and Segment & destination Regulations, or Regulations that Segment completes on internal systems and then forwards to your connected destinations. + +While both Regulation types are limited to 110,000 users every calendar month, you can temporarily increase your rate limit for Segment-only regulations. + +To send more than 110,000 Segment-only Regulations over a 30 day period, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"}. + +### Segment-only Regulations +The following Segment-only Regulation types are available: - **SUPPRESS_WITH_DELETE_INTERNAL*:** Suppress new data and delete from Segment internal systems only - **DELETE_INTERNAL*:** Delete data from Segment internal systems only - **SUPPRESS_ONLY***: Suppress new data without deleting existing data - **UNSUPPRESS*:** Stop an ongoing suppression + +### Segment & destination Regulations + +The following Segment & destination Regulations are available: + - **SUPPRESS_WITH_DELETE:** Suppress new data and delete existing data - **DELETE_ONLY:** Delete existing data without suppressing any new data -> info "All regulations are rate limited to 110,000 users within a 30-day period" -> To send more than 110,000 `SUPPRESS_ONLY`, `UNSUPRESS`, `DELETE_INTERNAL` and/or `SUPPRESS_WITH_DELETE_INTERNAL` Regulations over a 30 day period, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"}. ## Deletion Support @@ -47,13 +57,23 @@ Warehouse deletions occur using a DML run against your cluster or instance. Segm -#### Deletion requests tab +### Deletion requests tab + +The deletion requests tab shows a 30-day overview of your deletions pipeline, including a regulations usage tracker and a deletion requests status table. + +To navigate to the deletion requests tab, open the Segment app and navigate to **Settings** > **End-user Privacy** > **Deletion Requests**. + +#### Regulations usage tracker + +The usage tracker on the deletion requests tab shows you how many Segment & destination regulations and how many Segment-only regulations you have remaining for the calendar month. + +#### Deletion requests status -The deletion requests tab shows a log of all regulations and their status. +The deletion requests status table allows you to see the status of each of the regulations that you've submitted, including if the regulation was forwarded to your destinations, the deletion type, the date the regulation was received, and the date the regulation was completed. -In the Segment App (Settings > End User Privacy > Deletion Requests), you can click a `userId` to view its status in Segment internal systems and in the connected destinations. +If you need to verify that a information about a specific user was deleted or suppressed, you can search for a `userId` to view its status in Segment internal systems and in the connected destinations. -The deletion request can have one of the following statuses: +A deletion request can have one of the following statuses: 1. `INITIALIZED` 2. `INVALID` @@ -65,9 +85,9 @@ The deletion request can have one of the following statuses: When checking the status of deletion requests using Segment's API, the deletion will report an overall status of all of the deletion processes. As a result, Segment returns a `FAILED` status because of a failure on an unsupported destination, even if the deletion from the Segment Internal Systems and supported destinations were completed successfully. -#### Deletion request SLA +### Deletion request SLA -Segment has a 30-day SLA for completing deletion requests in Segment's internal stores for deletion requests of fewer than 110,000 users made over 30 days. Your requests will be rate limited if you submit more than 110,000 deletion requests within 30 days. +Segment has a 30-day SLA for completing deletion requests in Segment's internal stores for deletion requests of fewer than 110,000 users made over a calendar month. Your requests will be rate limited if you submit more than 110,000 deletion requests in a calendar month. > warning "This 30-day SLA is limited to only Segment's internal stores" > Segment cannot guarantee that deletions in your Amazon S3 instance, your connected data warehouse, or other third-party destinations will be completed during that 30-day period. From b27ee8c587057e0ee35cb2bd4d2d8b0d575195a6 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 27 Jun 2025 15:25:11 -0400 Subject: [PATCH 09/13] requested updates [netlify-build] --- src/privacy/user-deletion-and-suppression.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index dd1f7f6e41..0d3f617130 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -19,11 +19,11 @@ With Regulations, you can issue a single request to delete and suppress data abo > warning "Data sent to device-mode destinations cannot be suppressed" > Destinations set up in device mode are sent directly to destinations and bypass the point in the pipeline where Segment suppresses events. -Segment has 2 types of Regulations - Segment-only Regulations, or those that only impact data from Segment systems, and Segment & destination Regulations, or Regulations that Segment completes on internal systems and then forwards to your connected destinations. +Segment has 2 types of Regulations: +- **Segment-only Regulations**: These Regulations *only* delete or suppress data about your user from internal Segment systems. +- **Segment & Destination Regulations**: These Regulations delete user data from internal Segment systems and then forward a deletion request to any connected destinations that support programmatic deletion. For a list of destination that support programmatic deletion, see [Which destinations can I send deletion requests to?](/docs/privacy/faq/#which-destinations-can-i-send-deletion-requests-to). -While both Regulation types are limited to 110,000 users every calendar month, you can temporarily increase your rate limit for Segment-only regulations. - -To send more than 110,000 Segment-only Regulations over a 30 day period, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"}. +While both Regulation types are limited to 110,000 users every calendar month, you can temporarily increase your rate limit for Segment-only regulations. To send more than 110,000 Segment-only Regulations over a 30 day period, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"}. ### Segment-only Regulations The following Segment-only Regulation types are available: @@ -33,9 +33,9 @@ The following Segment-only Regulation types are available: - **SUPPRESS_ONLY***: Suppress new data without deleting existing data - **UNSUPPRESS*:** Stop an ongoing suppression -### Segment & destination Regulations +### Segment & Destination Regulations -The following Segment & destination Regulations are available: +The following Segment & Destination Regulations are available: - **SUPPRESS_WITH_DELETE:** Suppress new data and delete existing data - **DELETE_ONLY:** Delete existing data without suppressing any new data From 0f4b82591cfda8ac10d5ac0610fbd18372da1472 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 27 Jun 2025 15:55:27 -0400 Subject: [PATCH 10/13] one more [netlify-build] --- src/privacy/user-deletion-and-suppression.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index 0d3f617130..4d441c22f6 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -61,7 +61,7 @@ Warehouse deletions occur using a DML run against your cluster or instance. Segm The deletion requests tab shows a 30-day overview of your deletions pipeline, including a regulations usage tracker and a deletion requests status table. -To navigate to the deletion requests tab, open the Segment app and navigate to **Settings** > **End-user Privacy** > **Deletion Requests**. +To navigate to the deletion requests tab, open the Segment app and navigate to **Privacy > Deletion and Suppression > Deletion**. #### Regulations usage tracker From a2fc71a39a02b8ba5dc3969aa5e5da283336bb0b Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 2 Jul 2025 13:53:30 -0400 Subject: [PATCH 11/13] Apply suggestions from code review --- src/privacy/user-deletion-and-suppression.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index 4d441c22f6..eb62adf3e6 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -23,7 +23,7 @@ Segment has 2 types of Regulations: - **Segment-only Regulations**: These Regulations *only* delete or suppress data about your user from internal Segment systems. - **Segment & Destination Regulations**: These Regulations delete user data from internal Segment systems and then forward a deletion request to any connected destinations that support programmatic deletion. For a list of destination that support programmatic deletion, see [Which destinations can I send deletion requests to?](/docs/privacy/faq/#which-destinations-can-i-send-deletion-requests-to). -While both Regulation types are limited to 110,000 users every calendar month, you can temporarily increase your rate limit for Segment-only regulations. To send more than 110,000 Segment-only Regulations over a 30 day period, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"}. +While both Regulation types are limited to 110,000 users every calendar month, you can temporarily increase your rate limit for Segment-only Regulations. To send more than 110,000 Segment-only Regulations over a 30 day period, [contact Segment Support](https://segment.com/help/contact/){:target="_blank"}. ### Segment-only Regulations The following Segment-only Regulation types are available: @@ -59,17 +59,17 @@ Warehouse deletions occur using a DML run against your cluster or instance. Segm ### Deletion requests tab -The deletion requests tab shows a 30-day overview of your deletions pipeline, including a regulations usage tracker and a deletion requests status table. +The deletion requests tab shows a 30-day overview of your deletions pipeline, including a Regulations usage tracker and a deletion requests status table. To navigate to the deletion requests tab, open the Segment app and navigate to **Privacy > Deletion and Suppression > Deletion**. #### Regulations usage tracker -The usage tracker on the deletion requests tab shows you how many Segment & destination regulations and how many Segment-only regulations you have remaining for the calendar month. +The usage tracker on the deletion requests tab shows you how many Segment & destination Regulations and how many Segment-only Regulations you have remaining for the calendar month. #### Deletion requests status -The deletion requests status table allows you to see the status of each of the regulations that you've submitted, including if the regulation was forwarded to your destinations, the deletion type, the date the regulation was received, and the date the regulation was completed. +The deletion requests status table allows you to see the status of each of the Regulations that you've submitted, including if the Regulation was forwarded to your destinations, the deletion type, the date the Regulation was received, and the date the Regulation was completed. If you need to verify that a information about a specific user was deleted or suppressed, you can search for a `userId` to view its status in Segment internal systems and in the connected destinations. From 24aa2c6f94a7a00d5a22d7b956946729ab9ebcab Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 3 Jul 2025 09:09:05 -0400 Subject: [PATCH 12/13] Update src/privacy/user-deletion-and-suppression.md Co-authored-by: Sharon Adewusi --- src/privacy/user-deletion-and-suppression.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index eb62adf3e6..6f056051c0 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -71,7 +71,7 @@ The usage tracker on the deletion requests tab shows you how many Segment & dest The deletion requests status table allows you to see the status of each of the Regulations that you've submitted, including if the Regulation was forwarded to your destinations, the deletion type, the date the Regulation was received, and the date the Regulation was completed. -If you need to verify that a information about a specific user was deleted or suppressed, you can search for a `userId` to view its status in Segment internal systems and in the connected destinations. +If you need to verify if information about a specific user was deleted or suppressed, you can search for a `userId` to view its status in Segment internal systems and in the connected destinations. A deletion request can have one of the following statuses: From 0d8885a5c20f232bc93a668429b957bd31577f92 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 14 Jul 2025 10:30:39 -0400 Subject: [PATCH 13/13] Update src/_data/privacy.yml --- src/_data/privacy.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_data/privacy.yml b/src/_data/privacy.yml index 80a9090a28..be80df6fd2 100644 --- a/src/_data/privacy.yml +++ b/src/_data/privacy.yml @@ -7,7 +7,7 @@ sections: path: /privacy/portal/ icon: media/classify.svg - name: Control what data you collect - description: "Take control of the data that comes into your workspace." + description: "Take control of the data that enters your workspace." path: /privacy/data-controls/ icon: media/control.svg