From 6888604a4ebe7ba6843ae3c49c6cb99126a2a1e3 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 1 Mar 2022 16:03:51 -0500 Subject: [PATCH 01/23] Basic first draft of BCR compliance docs --- src/privacy/bcr-compliance.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 src/privacy/bcr-compliance.md diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md new file mode 100644 index 0000000000..776868e39d --- /dev/null +++ b/src/privacy/bcr-compliance.md @@ -0,0 +1,21 @@ +--- +title: Complying with Twilio's Binding Corporate Rules (BCRs) +--- + +In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Twilio, Segment, and Sendgrid store and process personal data. + +## What are Binding Corporate Rules? + +### Where can I learn more about Twilio's Binding Corporate Rules? + +### How can I delete data from my workspace? + +To delete all data from your workspace, including customer data: + +1. Open the Segment app, and select **Settings.** +2. On the General Settings page, click the **Delete Workspace** button. +3. Follow the prompts on the pop-up to delete your workspace. + +After you delete your workspace, Segment will purge all data from internal servers after XYZ days. + +### What is a data purge? From afb5c201da7e94683ef1d58058f45c352506bc5e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 3 Mar 2022 16:05:04 -0500 Subject: [PATCH 02/23] DOC-460 Content updates --- src/privacy/bcr-compliance.md | 32 ++++++++++++++++++++++++++++---- 1 file changed, 28 insertions(+), 4 deletions(-) diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index 776868e39d..30304495c4 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -2,13 +2,23 @@ title: Complying with Twilio's Binding Corporate Rules (BCRs) --- -In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Twilio, Segment, and Sendgrid store and process personal data. + ## What are Binding Corporate Rules? +[Binding Corporate Rules (BCRs)](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/binding-corporate-rules-bcr_en) are enforceable, legally binding codes of conduct that explain the ways companies store and process personal data. BCRs must be approved by the data protection authority in all European Union member states, as stipulated in [Article 63 of the GDPR](https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32016R0679&from=EN). + ### Where can I learn more about Twilio's Binding Corporate Rules? + +You can learn more about Twilio's Binding Corporate Rules (BCRs) by navigating to the [web version of the BCRs](https://www.twilio.com/legal/bcr) or by reaching out to + + + +## What do the Binding Corporate Rules mean for my data? -### How can I delete data from my workspace? + + +## How can I delete data from my workspace? To delete all data from your workspace, including customer data: @@ -16,6 +26,20 @@ To delete all data from your workspace, including customer data: 2. On the General Settings page, click the **Delete Workspace** button. 3. Follow the prompts on the pop-up to delete your workspace. -After you delete your workspace, Segment will purge all data from internal servers after XYZ days. +After you delete your workspace, Segment removes all data associated with your workspace and users immediately in a process called a [complete data purge](#what-is-a-complete-data-purge). + +If you do not manually delete your data after you stop using Segment, it is removed from Segment servers after 30 days. + + + +> warning " " +> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, please reach out to the Deletions and Compliance team [friends@segment.com](mailto:friends@segment.com) with the slug, workplace owner, and nickname of the workspace you would like to have purged from Segment servers. + + + +### What is a complete data purge? -### What is a data purge? +A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or provide a written request to the Deletions and Compliance team [friends@segment.com](mailto:friends@segment.com) that contains the following information: +- slug +- workplace owner +- nickname of the workspace From 2d34465df6cb0f3f09941c5e22852dc16bca0015 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 3 Mar 2022 16:06:09 -0500 Subject: [PATCH 03/23] DOC-360 Forgot to save --- src/privacy/bcr-compliance.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index 30304495c4..ac514c6b77 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -2,6 +2,7 @@ title: Complying with Twilio's Binding Corporate Rules (BCRs) --- +In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Twilio, Segment, and Sendgrid store and process personal data. In order to be in alignment with Twilio's BCRs, Segment introduced a new data deletion process that allow customers to remove all of their workspace and user data immediately. ## What are Binding Corporate Rules? From 3842fb6e478b25f2a8a67a4fd65993e401ab8bd0 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 4 Mar 2022 16:03:07 -0500 Subject: [PATCH 04/23] DOC-460 Updating BCR page with info from meeting with PM --- src/_data/sidenav/main.yml | 2 + src/privacy/bcr-compliance.md | 47 +++++++++++--------- src/privacy/user-deletion-and-suppression.md | 2 +- 3 files changed, 30 insertions(+), 21 deletions(-) diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index b4fd3df6e4..f9a42e0602 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -322,6 +322,8 @@ sections: title: Complying With GDPR - path: /privacy/user-deletion-and-suppression title: User Deletion and Suppression + - path: /privacy/bcr-compliance + title: Twilio's Binding Corporate Rules - path: /privacy/faq title: Privacy FAQs - section_title: Protocols diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index ac514c6b77..21d2002bc5 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -1,46 +1,53 @@ --- -title: Complying with Twilio's Binding Corporate Rules (BCRs) +title: Twilio's Binding Corporate Rules (BCRs) --- -In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Twilio, Segment, and Sendgrid store and process personal data. In order to be in alignment with Twilio's BCRs, Segment introduced a new data deletion process that allow customers to remove all of their workspace and user data immediately. - +In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores and processes personal data. In order to be in alignment with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their workspace and user data within 30 days of deleting their workspace. ## What are Binding Corporate Rules? -[Binding Corporate Rules (BCRs)](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/binding-corporate-rules-bcr_en) are enforceable, legally binding codes of conduct that explain the ways companies store and process personal data. BCRs must be approved by the data protection authority in all European Union member states, as stipulated in [Article 63 of the GDPR](https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32016R0679&from=EN). +[Binding Corporate Rules (BCRs)](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/binding-corporate-rules-bcr_en) are enforceable, legally binding codes of conduct that explain the ways companies store and process personal data. These codes contain information about data protection principles, tools used to protect the security of your data, and a method of accountability, or some way that proves the BCRs are externally (outside of the company) and internally (inside of the company) binding. BCRs are often specific to the storage and transfer (Controller) or processing (Processor) of personal data. + +Twilio has two sets of BCRs: a [Controller policy](https://www.twilio.com/legal/bcr/controller) and a [Processor policy](https://www.twilio.com/legal/bcr/processor). Segment, as a processor of individual data, falls under the Processor policy. ### Where can I learn more about Twilio's Binding Corporate Rules? -You can learn more about Twilio's Binding Corporate Rules (BCRs) by navigating to the [web version of the BCRs](https://www.twilio.com/legal/bcr) or by reaching out to +You can learn more about Twilio's Binding Corporate Rules (BCRs) by reading the [latest version of the BCRs](https://www.twilio.com/legal/bcr) or by reaching out to privacy@twilio.com. - +### What do Twilio's Binding Corporate Rules mean for my data? -## What do the Binding Corporate Rules mean for my data? + - +Twilio's BCRs ## How can I delete data from my workspace? +You can choose to delete the data from an individual user, from an entire source, or from your entire workspace. + +### Deleting individual user data +To delete the data for an individual user from you workspace, follow the instructions on the [User Deletion and Suppression](/docs/privacy/user-deletion-and-suppression) page. + +### Deleting data from a source +To delete the data for an entire source, send a request to the the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com) with your workplace slug, the source you'd like to delete data from, and the time frame for the data you'd like to delete. + +> note "Deleting source data" +> When Segment deletes your data for a particular source, they do not forward that deletion to sources or data storage providers associated with your account. To remove your data from external providers, please reach out to the individual providers about their deletion practices. + +### Deleting your workspace data + To delete all data from your workspace, including customer data: 1. Open the Segment app, and select **Settings.** 2. On the General Settings page, click the **Delete Workspace** button. 3. Follow the prompts on the pop-up to delete your workspace. -After you delete your workspace, Segment removes all data associated with your workspace and users immediately in a process called a [complete data purge](#what-is-a-complete-data-purge). - -If you do not manually delete your data after you stop using Segment, it is removed from Segment servers after 30 days. - - +After you delete your workspace, Segment removes all data associated with your workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). -> warning " " -> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, please reach out to the Deletions and Compliance team [friends@segment.com](mailto:friends@segment.com) with the slug, workplace owner, and nickname of the workspace you would like to have purged from Segment servers. +> warning "Purging data from workspaces deleted prior to March 31, 2022" +> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, please raise a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). In your email to Customer Success, please include either the slug or the ID of the workspace you'd like to have purged from Segment servers. - +If you do not delete your data after you stop using Segment, it remains in Segment's internal servers until you submit a written request that your data be deleted. ### What is a complete data purge? -A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or provide a written request to the Deletions and Compliance team [friends@segment.com](mailto:friends@segment.com) that contains the following information: -- slug -- workplace owner -- nickname of the workspace +A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team [friends@segment.com](mailto:friends@segment.com) that contains either the workplace slug or the workspace ID of the workspace that you'd like to delete. diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index 2a3f8a3b58..a040560f63 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -6,7 +6,7 @@ In keeping with Segment's commitment to GDPR and CCPA readiness, Segment offers [Contact Support](https://segment.com/help/contact/) if you need to process more than 100,000 users within a 30 day period. -> info "Business Plan Customers)" +> info "Business Plan Customers" > If you use this feature to delete data, you can not Replay the deleted data. For standard Replay requests, you must wait for any pending deletions to complete, and you cannot submit new deletion requests for the period of time that Segment replays data for you. > info "" From cf6648dc2ce70060739f901b5ad3e72c542b4f6e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 4 Mar 2022 16:06:39 -0500 Subject: [PATCH 05/23] DOC-460 added status update note, removed weasel words --- src/privacy/bcr-compliance.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index 21d2002bc5..e3c3c96e85 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -31,7 +31,7 @@ To delete the data for an individual user from you workspace, follow the instruc To delete the data for an entire source, send a request to the the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com) with your workplace slug, the source you'd like to delete data from, and the time frame for the data you'd like to delete. > note "Deleting source data" -> When Segment deletes your data for a particular source, they do not forward that deletion to sources or data storage providers associated with your account. To remove your data from external providers, please reach out to the individual providers about their deletion practices. +> When Segment deletes your data for a particular source, they do not forward that deletion to sources or data storage providers associated with your account. To remove your data from external providers, reach out to the individual providers about their deletion practices. ### Deleting your workspace data @@ -41,10 +41,10 @@ To delete all data from your workspace, including customer data: 2. On the General Settings page, click the **Delete Workspace** button. 3. Follow the prompts on the pop-up to delete your workspace. -After you delete your workspace, Segment removes all data associated with your workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). +After you delete your workspace, Segment removes all data associated with your workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). For a status update on the deletion progress, raise a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). > warning "Purging data from workspaces deleted prior to March 31, 2022" -> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, please raise a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). In your email to Customer Success, please include either the slug or the ID of the workspace you'd like to have purged from Segment servers. +> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, raise a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from Segment servers. If you do not delete your data after you stop using Segment, it remains in Segment's internal servers until you submit a written request that your data be deleted. From 1c2afeef732e3d0848069d36082e1e6a0eb508f8 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 7 Mar 2022 11:24:36 -0500 Subject: [PATCH 06/23] DOC-460 updating an answer, minor grammar edits --- src/privacy/bcr-compliance.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index e3c3c96e85..ed58b12f3a 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -2,13 +2,13 @@ title: Twilio's Binding Corporate Rules (BCRs) --- -In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores and processes personal data. In order to be in alignment with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their workspace and user data within 30 days of deleting their workspace. +In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores and processes personal data. To be in alignment with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their workspace data within 30 days of deleting their workspace. ## What are Binding Corporate Rules? [Binding Corporate Rules (BCRs)](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/binding-corporate-rules-bcr_en) are enforceable, legally binding codes of conduct that explain the ways companies store and process personal data. These codes contain information about data protection principles, tools used to protect the security of your data, and a method of accountability, or some way that proves the BCRs are externally (outside of the company) and internally (inside of the company) binding. BCRs are often specific to the storage and transfer (Controller) or processing (Processor) of personal data. -Twilio has two sets of BCRs: a [Controller policy](https://www.twilio.com/legal/bcr/controller) and a [Processor policy](https://www.twilio.com/legal/bcr/processor). Segment, as a processor of individual data, falls under the Processor policy. +Twilio has two sets of BCRs: a [Controller policy](https://www.twilio.com/legal/bcr/controller) and a [Processor policy](https://www.twilio.com/legal/bcr/processor). Segment, as a processor of individual data, complies with the Processor policy. ### Where can I learn more about Twilio's Binding Corporate Rules? @@ -16,9 +16,7 @@ You can learn more about Twilio's Binding Corporate Rules (BCRs) by reading the ### What do Twilio's Binding Corporate Rules mean for my data? - - -Twilio's BCRs +Twilio's BCRs inform the way your user data must be stored and processed. While the ways Segment processes and stores user data are already in compliance with Twilio BCRs, [additional data deletion methods](#how-can-i-delete-data-from-my-workspace) were added to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. These new data deletion methods allow you to delete the data associated with [individual users](#deleting-individual-user-data), [sources](#deleting-data-from-a-source), and your [workspace](#deleting-your-workspace-data). ## How can I delete data from my workspace? @@ -31,7 +29,7 @@ To delete the data for an individual user from you workspace, follow the instruc To delete the data for an entire source, send a request to the the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com) with your workplace slug, the source you'd like to delete data from, and the time frame for the data you'd like to delete. > note "Deleting source data" -> When Segment deletes your data for a particular source, they do not forward that deletion to sources or data storage providers associated with your account. To remove your data from external providers, reach out to the individual providers about their deletion practices. +> When Segment deletes your data for a particular source, the deletion is not forwarded to sources or data storage providers associated with your account. To remove your data from external sources, reach out to the individual source about their deletion practices. ### Deleting your workspace data @@ -41,7 +39,7 @@ To delete all data from your workspace, including customer data: 2. On the General Settings page, click the **Delete Workspace** button. 3. Follow the prompts on the pop-up to delete your workspace. -After you delete your workspace, Segment removes all data associated with your workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). For a status update on the deletion progress, raise a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). +After you delete your workspace, Segment removes all data associated with your workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). For a data purge status update, create a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). > warning "Purging data from workspaces deleted prior to March 31, 2022" > If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, raise a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from Segment servers. From 01c30116d9d0ede7585d72e66f816e04f672ffed Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 7 Mar 2022 15:34:29 -0500 Subject: [PATCH 07/23] DOC-460 Editing pass --- src/privacy/bcr-compliance.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index ed58b12f3a..706df4bdf1 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -8,15 +8,15 @@ In response to the passage of the General Data Protection Regulation (GDPR) poli [Binding Corporate Rules (BCRs)](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/binding-corporate-rules-bcr_en) are enforceable, legally binding codes of conduct that explain the ways companies store and process personal data. These codes contain information about data protection principles, tools used to protect the security of your data, and a method of accountability, or some way that proves the BCRs are externally (outside of the company) and internally (inside of the company) binding. BCRs are often specific to the storage and transfer (Controller) or processing (Processor) of personal data. -Twilio has two sets of BCRs: a [Controller policy](https://www.twilio.com/legal/bcr/controller) and a [Processor policy](https://www.twilio.com/legal/bcr/processor). Segment, as a processor of individual data, complies with the Processor policy. +Twilio has two BCR policies: a [Controller policy](https://www.twilio.com/legal/bcr/controller) and a [Processor policy](https://www.twilio.com/legal/bcr/processor). Segment, as a processor of individual data, complies with the Processor policy. ### Where can I learn more about Twilio's Binding Corporate Rules? -You can learn more about Twilio's Binding Corporate Rules (BCRs) by reading the [latest version of the BCRs](https://www.twilio.com/legal/bcr) or by reaching out to privacy@twilio.com. +You can learn more about Twilio's Binding Corporate Rules (BCRs) by reading the [full version on twilio.com/legal](https://www.twilio.com/legal/bcr) or by reaching out to [privacy@twilio.com](mailto:privacy@twilio.com). ### What do Twilio's Binding Corporate Rules mean for my data? -Twilio's BCRs inform the way your user data must be stored and processed. While the ways Segment processes and stores user data are already in compliance with Twilio BCRs, [additional data deletion methods](#how-can-i-delete-data-from-my-workspace) were added to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. These new data deletion methods allow you to delete the data associated with [individual users](#deleting-individual-user-data), [sources](#deleting-data-from-a-source), and your [workspace](#deleting-your-workspace-data). +Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment processes and stores user data are already in compliance with Twilio BCRs, [additional data deletion methods](#how-can-i-delete-data-from-my-workspace) were added to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. These new data deletion methods allow you to delete the data associated with [individual users](#deleting-individual-user-data), [sources](#deleting-data-from-a-source), and your [workspace](#deleting-your-workspace-data). ## How can I delete data from my workspace? @@ -42,7 +42,7 @@ To delete all data from your workspace, including customer data: After you delete your workspace, Segment removes all data associated with your workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). For a data purge status update, create a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). > warning "Purging data from workspaces deleted prior to March 31, 2022" -> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, raise a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from Segment servers. +> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, raise a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from internal Segment servers. If you do not delete your data after you stop using Segment, it remains in Segment's internal servers until you submit a written request that your data be deleted. From 9b592c05ac397722777a73734f806002cc8fd02a Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 7 Mar 2022 16:04:57 -0500 Subject: [PATCH 08/23] DOC-460 More edits --- src/privacy/bcr-compliance.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index 706df4bdf1..2a6188a8d8 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -2,36 +2,36 @@ title: Twilio's Binding Corporate Rules (BCRs) --- -In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores and processes personal data. To be in alignment with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their workspace data within 30 days of deleting their workspace. +In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores, processes, and deletes personal data. To be in alignment with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their workspace data within 30 days of deleting their workspace. ## What are Binding Corporate Rules? -[Binding Corporate Rules (BCRs)](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/binding-corporate-rules-bcr_en) are enforceable, legally binding codes of conduct that explain the ways companies store and process personal data. These codes contain information about data protection principles, tools used to protect the security of your data, and a method of accountability, or some way that proves the BCRs are externally (outside of the company) and internally (inside of the company) binding. BCRs are often specific to the storage and transfer (Controller) or processing (Processor) of personal data. +[Binding Corporate Rules (BCRs)](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/binding-corporate-rules-bcr_en) are enforceable, legally binding codes of conduct that explain the ways companies store, process, and delete personal data. These codes contain information about data protection principles, tools used to protect the security of your data, and a method of accountability, or some way that proves the BCRs are externally (outside of the company) and internally (inside of the company) binding. BCRs are often specific to the storage and transfer (Controller) or processing (Processor) of personal data. Twilio has two BCR policies: a [Controller policy](https://www.twilio.com/legal/bcr/controller) and a [Processor policy](https://www.twilio.com/legal/bcr/processor). Segment, as a processor of individual data, complies with the Processor policy. ### Where can I learn more about Twilio's Binding Corporate Rules? -You can learn more about Twilio's Binding Corporate Rules (BCRs) by reading the [full version on twilio.com/legal](https://www.twilio.com/legal/bcr) or by reaching out to [privacy@twilio.com](mailto:privacy@twilio.com). +To learn more about Twilio's Binding Corporate Rules (BCRs,) read the [full version on twilio.com/legal](https://www.twilio.com/legal/bcr) or reach out to [privacy@twilio.com](mailto:privacy@twilio.com). ### What do Twilio's Binding Corporate Rules mean for my data? -Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment processes and stores user data are already in compliance with Twilio BCRs, [additional data deletion methods](#how-can-i-delete-data-from-my-workspace) were added to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. These new data deletion methods allow you to delete the data associated with [individual users](#deleting-individual-user-data), [sources](#deleting-data-from-a-source), and your [workspace](#deleting-your-workspace-data). +Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment stores and processes user data are already in compliance with Twilio's BCRs, [additional data deletion methods](#how-can-i-delete-data-from-my-workspace) were added to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. These data deletion methods now allow you to delete the data associated with [individual users](#delete-individual-user-data), [sources](#delete-data-from-a-source), and your [workspace](#delete-your-workspace-data). ## How can I delete data from my workspace? -You can choose to delete the data from an individual user, from an entire source, or from your entire workspace. +You can choose to delete the data from an individual user, an entire source, or your entire workspace. -### Deleting individual user data +### Delete individual user data To delete the data for an individual user from you workspace, follow the instructions on the [User Deletion and Suppression](/docs/privacy/user-deletion-and-suppression) page. -### Deleting data from a source -To delete the data for an entire source, send a request to the the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com) with your workplace slug, the source you'd like to delete data from, and the time frame for the data you'd like to delete. +### Delete data from a source +To delete the data for an entire source, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include your workplace slug, the source you'd like to delete data from, and the time frame for the data you'd like to delete. > note "Deleting source data" > When Segment deletes your data for a particular source, the deletion is not forwarded to sources or data storage providers associated with your account. To remove your data from external sources, reach out to the individual source about their deletion practices. -### Deleting your workspace data +### Delete your workspace data To delete all data from your workspace, including customer data: @@ -39,13 +39,13 @@ To delete all data from your workspace, including customer data: 2. On the General Settings page, click the **Delete Workspace** button. 3. Follow the prompts on the pop-up to delete your workspace. -After you delete your workspace, Segment removes all data associated with your workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). For a data purge status update, create a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). +After you delete your workspace, Segment removes all data associated with your workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). For a data purge status update, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. -> warning "Purging data from workspaces deleted prior to March 31, 2022" -> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, raise a support ticket with the Customer Success team by emailing [friends@segment.com](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from internal Segment servers. +If you do not delete your workspace after you stop using Segment, **your data remains in Segment's internal servers until you submit a written deletion request**. -If you do not delete your data after you stop using Segment, it remains in Segment's internal servers until you submit a written request that your data be deleted. +> warning "Purging data from workspaces deleted prior to March 31, 2022" +> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, email the Customer Success team [friends@segment.com](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from internal Segment servers. ### What is a complete data purge? -A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team [friends@segment.com](mailto:friends@segment.com) that contains either the workplace slug or the workspace ID of the workspace that you'd like to delete. +A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) that contains either the slug or the ID of the workspace that you'd like to delete. From dc3696cc3c636d73e37e34882a3f05356e671283 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 7 Mar 2022 16:08:59 -0500 Subject: [PATCH 09/23] [netlify-build] --- src/privacy/bcr-compliance.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index 2a6188a8d8..895ca3613c 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -49,3 +49,4 @@ If you do not delete your workspace after you stop using Segment, **your data re ### What is a complete data purge? A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) that contains either the slug or the ID of the workspace that you'd like to delete. + From 5b419ac2ed0df44f4345ca9d52223bee61f5869c Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 8 Mar 2022 12:52:02 -0500 Subject: [PATCH 10/23] Apply suggestions from code review! Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com> --- src/privacy/bcr-compliance.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index 895ca3613c..f821480da8 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -2,7 +2,7 @@ title: Twilio's Binding Corporate Rules (BCRs) --- -In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores, processes, and deletes personal data. To be in alignment with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their workspace data within 30 days of deleting their workspace. +In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores, processes, and deletes personal data. To align with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their workspace data within 30 days of deleting their workspace. ## What are Binding Corporate Rules? @@ -20,7 +20,7 @@ Twilio's BCRs inform the way your user data must be stored, processed, and delet ## How can I delete data from my workspace? -You can choose to delete the data from an individual user, an entire source, or your entire workspace. +You can delete data from an individual user, an entire source, or your entire workspace. ### Delete individual user data To delete the data for an individual user from you workspace, follow the instructions on the [User Deletion and Suppression](/docs/privacy/user-deletion-and-suppression) page. From ff502c76d2cb1c8ad1d2b680d20243ff7b0c6479 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 9 Mar 2022 12:14:32 -0500 Subject: [PATCH 11/23] Separating account deletion and BCR pages [netlify-build] --- src/_data/sidenav/main.yml | 4 ++- src/privacy/account-deletion.md | 50 +++++++++++++++++++++++++++++++++ src/privacy/bcr-compliance.md | 37 ++---------------------- 3 files changed, 55 insertions(+), 36 deletions(-) create mode 100644 src/privacy/account-deletion.md diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index f9a42e0602..c294843cb4 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -323,7 +323,9 @@ sections: - path: /privacy/user-deletion-and-suppression title: User Deletion and Suppression - path: /privacy/bcr-compliance - title: Twilio's Binding Corporate Rules + title: Twilio's Binding Corporate Rules + - path: /privacy/account-deletion + title: Account & Data Deletion - path: /privacy/faq title: Privacy FAQs - section_title: Protocols diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md new file mode 100644 index 0000000000..f7bca20c6f --- /dev/null +++ b/src/privacy/account-deletion.md @@ -0,0 +1,50 @@ +--- +title: Account & Data Deletion +--- + +Segment allows you to delete data at a variety of levels. You can delete specific data relating to an individual end user, all data from associated with a source, or all data within your entire workspace. + +## Delete individual user data +To delete the data for an individual user from you workspace, follow the instructions on the [User Deletion and Suppression](/docs/privacy/user-deletion-and-suppression) page. + +## Delete data from a source +To delete the data for an entire source, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include the following information: +- Your workplace slug +- The source you'd like to delete data from +- The time frame for the data you'd like to delete* + +**Due to the way Segment stores data internally, source-level deletions can only be scoped to one day in granularity. Deletion requests for smaller time frames are not supported.* + +> note "Deleting source data" +> When Segment deletes your data for a particular source, the deletion is not forwarded to sources or data storage providers associated with your account: your data is only removed from Segment's S3 archive buckets. To remove your data from external sources, reach out to the individual source about their deletion practices. + +## Delete your workspace data + +Workspace admins can delete all of the data associated with a workspace, including customer data. + +To delete all data from one workspace: + +1. Open the Segment app, and select **Settings.** +2. On the General Settings page, click the **Delete Workspace** button. +3. Follow the prompts on the pop-up to delete your workspace. + +To delete data from all workspaces associated with your account: + +1. Sign in to the Segment app. +2. Navigate to the [User Settings page](https://app.segment.com/settings/user). +3. Click the **Delete Account** button, located at the bottom of the page. +4. On the popup, enter your password and select **Yep, delete my account anyway!** to delete your account. + +After you delete your workspace or account, Segment removes all data associated with each workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). For a data purge status update, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com). + +If you do not delete your workspace after you stop using Segment, **your data remains in Segment's internal servers until you submit a written deletion request**. + +> warning "Purging data from workspaces deleted prior to March 31, 2022" +> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, email the Customer Success team [friends@segment.com](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from internal Segment servers. + +### What is a complete data purge? + +A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers across all product areas. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) that contains either the slug or the ID of the workspace that you'd like to delete. Data purge deletions will *not* be forwarded to your connected third-party destinations or raw destinations. + +> warning " " +> Segment waits for five days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible. \ No newline at end of file diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index f821480da8..7eafdb6e2d 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -2,7 +2,7 @@ title: Twilio's Binding Corporate Rules (BCRs) --- -In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores, processes, and deletes personal data. To align with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their workspace data within 30 days of deleting their workspace. +In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores, processes, and deletes personal data. To align with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their users' personal data associated with a workspace 30 days after either deleting their workspace or submitting a written deletion request. ## What are Binding Corporate Rules? @@ -16,37 +16,4 @@ To learn more about Twilio's Binding Corporate Rules (BCRs,) read the [full vers ### What do Twilio's Binding Corporate Rules mean for my data? -Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment stores and processes user data are already in compliance with Twilio's BCRs, [additional data deletion methods](#how-can-i-delete-data-from-my-workspace) were added to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. These data deletion methods now allow you to delete the data associated with [individual users](#delete-individual-user-data), [sources](#delete-data-from-a-source), and your [workspace](#delete-your-workspace-data). - -## How can I delete data from my workspace? - -You can delete data from an individual user, an entire source, or your entire workspace. - -### Delete individual user data -To delete the data for an individual user from you workspace, follow the instructions on the [User Deletion and Suppression](/docs/privacy/user-deletion-and-suppression) page. - -### Delete data from a source -To delete the data for an entire source, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include your workplace slug, the source you'd like to delete data from, and the time frame for the data you'd like to delete. - -> note "Deleting source data" -> When Segment deletes your data for a particular source, the deletion is not forwarded to sources or data storage providers associated with your account. To remove your data from external sources, reach out to the individual source about their deletion practices. - -### Delete your workspace data - -To delete all data from your workspace, including customer data: - -1. Open the Segment app, and select **Settings.** -2. On the General Settings page, click the **Delete Workspace** button. -3. Follow the prompts on the pop-up to delete your workspace. - -After you delete your workspace, Segment removes all data associated with your workspace within 30 days in a process called a [complete data purge](#what-is-a-complete-data-purge). For a data purge status update, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. - -If you do not delete your workspace after you stop using Segment, **your data remains in Segment's internal servers until you submit a written deletion request**. - -> warning "Purging data from workspaces deleted prior to March 31, 2022" -> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, email the Customer Success team [friends@segment.com](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from internal Segment servers. - -### What is a complete data purge? - -A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) that contains either the slug or the ID of the workspace that you'd like to delete. - +Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment stores and processes user data are already in compliance with Twilio's BCRs, [an additional data deletion method](/docs/privacy/account-deletion/#delete-your-workspace-data) was introduced to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. This new data deletion method, along with the existing methods of deleting [individual user data](/docs/privacy/account-deletion/#delete-individual-user-data) and [source data](/docs/privacy/account-deletion/#delete-data-from-a-source), means that Segment is now in alignment with Twilio's BCRs. From 1969a05bb23e2ff99886ed61d2cfe43e051186f3 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 9 Mar 2022 15:19:36 -0500 Subject: [PATCH 12/23] DOC-460 Editing pass [netlify-build] --- src/privacy/account-deletion.md | 5 ++--- src/privacy/bcr-compliance.md | 2 +- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md index f7bca20c6f..fa22f92f8f 100644 --- a/src/privacy/account-deletion.md +++ b/src/privacy/account-deletion.md @@ -40,11 +40,10 @@ After you delete your workspace or account, Segment removes all data associated If you do not delete your workspace after you stop using Segment, **your data remains in Segment's internal servers until you submit a written deletion request**. > warning "Purging data from workspaces deleted prior to March 31, 2022" -> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment servers, email the Customer Success team [friends@segment.com](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from internal Segment servers. +> If you deleted your workspace prior to March 31, 2022, and would like to have data associated with your workspace purged from Segment's S3 archive buckets, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include either the slug or the ID of the workspace you'd like to have purged from internal Segment servers. ### What is a complete data purge? -A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers across all product areas. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) that contains either the slug or the ID of the workspace that you'd like to delete. Data purge deletions will *not* be forwarded to your connected third-party destinations or raw destinations. -> warning " " +> error " " > Segment waits for five days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible. \ No newline at end of file diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index 7eafdb6e2d..debfdd16d0 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -16,4 +16,4 @@ To learn more about Twilio's Binding Corporate Rules (BCRs,) read the [full vers ### What do Twilio's Binding Corporate Rules mean for my data? -Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment stores and processes user data are already in compliance with Twilio's BCRs, [an additional data deletion method](/docs/privacy/account-deletion/#delete-your-workspace-data) was introduced to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. This new data deletion method, along with the existing methods of deleting [individual user data](/docs/privacy/account-deletion/#delete-individual-user-data) and [source data](/docs/privacy/account-deletion/#delete-data-from-a-source), means that Segment is now in alignment with Twilio's BCRs. +Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment stores and processes user data are already in compliance with Twilio's BCRs, [an additional data deletion method](/docs/privacy/account-deletion/#delete-your-workspace-data) was introduced to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. This new data deletion method, along with the existing methods of deleting [individual user data](/docs/privacy/account-deletion/#delete-individual-user-data) and [source data](/docs/privacy/account-deletion/#delete-data-from-a-source), ensure that Segment's policies are now in alignment with Twilio's BCRs. From 63deeb687e0853a484c7929ffc5c7a26dfe49bfb Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 9 Mar 2022 15:20:10 -0500 Subject: [PATCH 13/23] [netlify-build] --- src/privacy/account-deletion.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md index fa22f92f8f..790976fcc5 100644 --- a/src/privacy/account-deletion.md +++ b/src/privacy/account-deletion.md @@ -44,6 +44,7 @@ If you do not delete your workspace after you stop using Segment, **your data re ### What is a complete data purge? +A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers across all product areas. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team by emailing [(friends@segment.com)](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace that you'd like to delete. Deletions related to data purges will *not* be forwarded to your connected third-party destinations or raw data destinations. > error " " > Segment waits for five days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible. \ No newline at end of file From 086c295b8c37292c07f342ad4c74f2626bd2f159 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 10 Mar 2022 09:01:34 -0500 Subject: [PATCH 14/23] Editing pass [netlify-build] --- src/privacy/account-deletion.md | 12 ++++++------ src/privacy/bcr-compliance.md | 6 +++--- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md index 790976fcc5..27642d232b 100644 --- a/src/privacy/account-deletion.md +++ b/src/privacy/account-deletion.md @@ -2,7 +2,7 @@ title: Account & Data Deletion --- -Segment allows you to delete data at a variety of levels. You can delete specific data relating to an individual end user, all data from associated with a source, or all data within your entire workspace. +Segment allows you to delete specific data relating to an individual end user, all data from associated with a source, or all data within your entire workspace. ## Delete individual user data To delete the data for an individual user from you workspace, follow the instructions on the [User Deletion and Suppression](/docs/privacy/user-deletion-and-suppression) page. @@ -22,13 +22,13 @@ To delete the data for an entire source, email the Customer Success team [(frien Workspace admins can delete all of the data associated with a workspace, including customer data. -To delete all data from one workspace: +**To delete all data from one workspace:** -1. Open the Segment app, and select **Settings.** +1. Sign in to the Segment app, select the workspace you'd like to delete, and click **Settings.** 2. On the General Settings page, click the **Delete Workspace** button. 3. Follow the prompts on the pop-up to delete your workspace. -To delete data from all workspaces associated with your account: +**To delete data from all workspaces in which you have workspace admin permissions:** 1. Sign in to the Segment app. 2. Navigate to the [User Settings page](https://app.segment.com/settings/user). @@ -44,7 +44,7 @@ If you do not delete your workspace after you stop using Segment, **your data re ### What is a complete data purge? -A complete data purge is the mechanism Segment uses to completely remove all workspace and customer data from internal Segment servers across all product areas. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team by emailing [(friends@segment.com)](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace that you'd like to delete. Deletions related to data purges will *not* be forwarded to your connected third-party destinations or raw data destinations. +A complete data purge is the way Segment removes all workspace and customer data from internal servers across all product areas. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team by emailing [(friends@segment.com)](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace that you'd like to delete. Deletions related to data purges will *not* be forwarded to your connected third-party destinations or raw data destinations. > error " " -> Segment waits for five days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible. \ No newline at end of file +> Segment waits for five calendar days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible. \ No newline at end of file diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md index debfdd16d0..405a3be118 100644 --- a/src/privacy/bcr-compliance.md +++ b/src/privacy/bcr-compliance.md @@ -10,10 +10,10 @@ In response to the passage of the General Data Protection Regulation (GDPR) poli Twilio has two BCR policies: a [Controller policy](https://www.twilio.com/legal/bcr/controller) and a [Processor policy](https://www.twilio.com/legal/bcr/processor). Segment, as a processor of individual data, complies with the Processor policy. -### Where can I learn more about Twilio's Binding Corporate Rules? +## Where can I learn more about Twilio's Binding Corporate Rules? To learn more about Twilio's Binding Corporate Rules (BCRs,) read the [full version on twilio.com/legal](https://www.twilio.com/legal/bcr) or reach out to [privacy@twilio.com](mailto:privacy@twilio.com). -### What do Twilio's Binding Corporate Rules mean for my data? +## What do Twilio's Binding Corporate Rules mean for my data? -Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment stores and processes user data are already in compliance with Twilio's BCRs, [an additional data deletion method](/docs/privacy/account-deletion/#delete-your-workspace-data) was introduced to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. This new data deletion method, along with the existing methods of deleting [individual user data](/docs/privacy/account-deletion/#delete-individual-user-data) and [source data](/docs/privacy/account-deletion/#delete-data-from-a-source), ensure that Segment's policies are now in alignment with Twilio's BCRs. +Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment stores and processes user data are already in compliance with Twilio's BCRs, [an additional data deletion method](/docs/privacy/account-deletion/#delete-your-workspace-data) for all workspace data was introduced to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. This new data deletion method, along with the existing methods of deleting [individual user data](/docs/privacy/account-deletion/#delete-individual-user-data) and [source data](/docs/privacy/account-deletion/#delete-data-from-a-source), ensure that Segment's policies now align with Twilio's BCRs. From 01f21c3a54a8b4bc07f4ac4d177ece66c27f4f88 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 10 Mar 2022 14:00:46 -0500 Subject: [PATCH 15/23] Removing BCR compliance page, as per legal [netlify-build] --- src/privacy/bcr-compliance.md | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 src/privacy/bcr-compliance.md diff --git a/src/privacy/bcr-compliance.md b/src/privacy/bcr-compliance.md deleted file mode 100644 index 405a3be118..0000000000 --- a/src/privacy/bcr-compliance.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Twilio's Binding Corporate Rules (BCRs) ---- - -In response to the passage of the General Data Protection Regulation (GDPR) policy in the European Union, Twilio implemented a set of [Binding Corporate Rules (BCRs)](https://www.twilio.com/legal/binding-corporate-rules) that inform how Segment stores, processes, and deletes personal data. To align with Twilio's BCRs, Segment introduced a new data deletion process that allows customers to remove all of their users' personal data associated with a workspace 30 days after either deleting their workspace or submitting a written deletion request. - -## What are Binding Corporate Rules? - -[Binding Corporate Rules (BCRs)](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/binding-corporate-rules-bcr_en) are enforceable, legally binding codes of conduct that explain the ways companies store, process, and delete personal data. These codes contain information about data protection principles, tools used to protect the security of your data, and a method of accountability, or some way that proves the BCRs are externally (outside of the company) and internally (inside of the company) binding. BCRs are often specific to the storage and transfer (Controller) or processing (Processor) of personal data. - -Twilio has two BCR policies: a [Controller policy](https://www.twilio.com/legal/bcr/controller) and a [Processor policy](https://www.twilio.com/legal/bcr/processor). Segment, as a processor of individual data, complies with the Processor policy. - -## Where can I learn more about Twilio's Binding Corporate Rules? - -To learn more about Twilio's Binding Corporate Rules (BCRs,) read the [full version on twilio.com/legal](https://www.twilio.com/legal/bcr) or reach out to [privacy@twilio.com](mailto:privacy@twilio.com). - -## What do Twilio's Binding Corporate Rules mean for my data? - -Twilio's BCRs inform the way your user data must be stored, processed, and deleted. While the ways Segment stores and processes user data are already in compliance with Twilio's BCRs, [an additional data deletion method](/docs/privacy/account-deletion/#delete-your-workspace-data) for all workspace data was introduced to comply with the ["Storage limitation"](https://www.twilio.com/legal/bcr/processor#part-ii-our-obligations) section of the Processor policy. This new data deletion method, along with the existing methods of deleting [individual user data](/docs/privacy/account-deletion/#delete-individual-user-data) and [source data](/docs/privacy/account-deletion/#delete-data-from-a-source), ensure that Segment's policies now align with Twilio's BCRs. From b8ea3dbac5d7784ac139bd1f06f82c4a3ce0f3bc Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 10 Mar 2022 14:14:38 -0500 Subject: [PATCH 16/23] Removing BCR from main nav [netlify-build] --- src/_data/sidenav/main.yml | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index c294843cb4..aade032125 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -322,9 +322,6 @@ sections: title: Complying With GDPR - path: /privacy/user-deletion-and-suppression title: User Deletion and Suppression - - path: /privacy/bcr-compliance - title: Twilio's Binding Corporate Rules - - path: /privacy/account-deletion title: Account & Data Deletion - path: /privacy/faq title: Privacy FAQs From 528e5d5fe4bb20e6d8ba63de0a2c919dc5312709 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 10 Mar 2022 14:28:11 -0500 Subject: [PATCH 17/23] Fixing side nav [netlify-build] --- src/_data/sidenav/main.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index aade032125..eb4abca6c2 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -322,6 +322,7 @@ sections: title: Complying With GDPR - path: /privacy/user-deletion-and-suppression title: User Deletion and Suppression + - path: /privacy/account-deletion title: Account & Data Deletion - path: /privacy/faq title: Privacy FAQs From f5457fa222427c7760d8f4d7d01dbfcef6c31e32 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 15 Mar 2022 16:00:47 -0400 Subject: [PATCH 18/23] DOC-460 Small change requested by Legal --- src/privacy/account-deletion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md index 27642d232b..68cfafda75 100644 --- a/src/privacy/account-deletion.md +++ b/src/privacy/account-deletion.md @@ -10,7 +10,7 @@ To delete the data for an individual user from you workspace, follow the instruc ## Delete data from a source To delete the data for an entire source, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include the following information: - Your workplace slug -- The source you'd like to delete data from +- The source from which you'd like to delete data - The time frame for the data you'd like to delete* **Due to the way Segment stores data internally, source-level deletions can only be scoped to one day in granularity. Deletion requests for smaller time frames are not supported.* From 1e5cd2c774d668c5f89567c0444faf39f39d6bb6 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Mar 2022 11:49:00 -0400 Subject: [PATCH 19/23] [netlify-build] --- src/privacy/account-deletion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md index 68cfafda75..010aac5d62 100644 --- a/src/privacy/account-deletion.md +++ b/src/privacy/account-deletion.md @@ -47,4 +47,4 @@ If you do not delete your workspace after you stop using Segment, **your data re A complete data purge is the way Segment removes all workspace and customer data from internal servers across all product areas. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team by emailing [(friends@segment.com)](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace that you'd like to delete. Deletions related to data purges will *not* be forwarded to your connected third-party destinations or raw data destinations. > error " " -> Segment waits for five calendar days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible. \ No newline at end of file +> Segment waits for five calendar days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible. From d56882d26090cbb9531fc5ddf54e0349fe5c979e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Mar 2022 11:51:30 -0400 Subject: [PATCH 20/23] [netlify-build] --- src/privacy/account-deletion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md index 010aac5d62..68cfafda75 100644 --- a/src/privacy/account-deletion.md +++ b/src/privacy/account-deletion.md @@ -47,4 +47,4 @@ If you do not delete your workspace after you stop using Segment, **your data re A complete data purge is the way Segment removes all workspace and customer data from internal servers across all product areas. To trigger a complete data purge, either [delete your workspace](#how-can-i-delete-data-from-my-workspace) or raise a support ticket with the Customer Success team by emailing [(friends@segment.com)](mailto:friends@segment.com). In your email to Customer Success, include either the slug or the ID of the workspace that you'd like to delete. Deletions related to data purges will *not* be forwarded to your connected third-party destinations or raw data destinations. > error " " -> Segment waits for five calendar days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible. +> Segment waits for five calendar days before beginning a complete data purge to safeguard against malicious deletion requests. If you notice your workspace or account has been maliciously deleted, reach out to [friends@segment.com](mailto:friends@segment.com) to cancel the data purge. After the five-day grace period, the deletion will be irreversible. \ No newline at end of file From f55d84c71c8265a74e4bc1c184610bdef1bb9972 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Mar 2022 12:01:27 -0400 Subject: [PATCH 21/23] [netlify-build] --- src/privacy/account-deletion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md index 68cfafda75..2d898a7182 100644 --- a/src/privacy/account-deletion.md +++ b/src/privacy/account-deletion.md @@ -10,7 +10,7 @@ To delete the data for an individual user from you workspace, follow the instruc ## Delete data from a source To delete the data for an entire source, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include the following information: - Your workplace slug -- The source from which you'd like to delete data +- The source from which you'd like to delete data - The time frame for the data you'd like to delete* **Due to the way Segment stores data internally, source-level deletions can only be scoped to one day in granularity. Deletion requests for smaller time frames are not supported.* From 62a605b4555fb53e9867fbcaa1d0aed4a02b0619 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Mar 2022 12:13:47 -0400 Subject: [PATCH 22/23] DOC-460 netlify troubleshooting [netlify-build] --- src/privacy/account-deletion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md index 2d898a7182..27642d232b 100644 --- a/src/privacy/account-deletion.md +++ b/src/privacy/account-deletion.md @@ -10,7 +10,7 @@ To delete the data for an individual user from you workspace, follow the instruc ## Delete data from a source To delete the data for an entire source, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include the following information: - Your workplace slug -- The source from which you'd like to delete data +- The source you'd like to delete data from - The time frame for the data you'd like to delete* **Due to the way Segment stores data internally, source-level deletions can only be scoped to one day in granularity. Deletion requests for smaller time frames are not supported.* From 9d9c3a731cd32167da6d71962d84c0d4ad3265c3 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Mar 2022 12:25:28 -0400 Subject: [PATCH 23/23] Fixing changes [netlify-build] --- src/privacy/account-deletion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/account-deletion.md b/src/privacy/account-deletion.md index 27642d232b..68cfafda75 100644 --- a/src/privacy/account-deletion.md +++ b/src/privacy/account-deletion.md @@ -10,7 +10,7 @@ To delete the data for an individual user from you workspace, follow the instruc ## Delete data from a source To delete the data for an entire source, email the Customer Success team [(friends@segment.com)](mailto:friends@segment.com) to create a support ticket. In your email to Customer Success, include the following information: - Your workplace slug -- The source you'd like to delete data from +- The source from which you'd like to delete data - The time frame for the data you'd like to delete* **Due to the way Segment stores data internally, source-level deletions can only be scoped to one day in granularity. Deletion requests for smaller time frames are not supported.*