Skip to content

Commit 086c295

Browse files
committed
Editing pass [netlify-build]
1 parent 2507c34 commit 086c295

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

src/privacy/account-deletion.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Account & Data Deletion
33
---
44

5-
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.
5+
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.
66

77
## Delete individual user data
88
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
2222

2323
Workspace admins can delete all of the data associated with a workspace, including customer data.
2424

25-
To delete all data from one workspace:
25+
**To delete all data from one workspace:**
2626

27-
1. Open the Segment app, and select **Settings.**
27+
1. Sign in to the Segment app, select the workspace you'd like to delete, and click **Settings.**
2828
2. On the General Settings page, click the **Delete Workspace** button.
2929
3. Follow the prompts on the pop-up to delete your workspace.
3030

31-
To delete data from all workspaces associated with your account:
31+
**To delete data from all workspaces in which you have workspace admin permissions:**
3232

3333
1. Sign in to the Segment app.
3434
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
4444
4545
### What is a complete data purge?
4646

47-
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 [([email protected])](mailto:[email protected]). 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.
47+
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 [([email protected])](mailto:[email protected]). 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.
4848

4949
> error " "
50-
> 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 [[email protected]](mailto:[email protected]) to cancel the data purge. After the five-day grace period, the deletion will be irreversible.
50+
> 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 [[email protected]](mailto:[email protected]) to cancel the data purge. After the five-day grace period, the deletion will be irreversible.

src/privacy/bcr-compliance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,10 +10,10 @@ In response to the passage of the General Data Protection Regulation (GDPR) poli
1010

1111
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.
1212

13-
### Where can I learn more about Twilio's Binding Corporate Rules?
13+
## Where can I learn more about Twilio's Binding Corporate Rules?
1414

1515
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 [[email protected]](mailto:[email protected]).
1616

17-
### What do Twilio's Binding Corporate Rules mean for my data?
17+
## What do Twilio's Binding Corporate Rules mean for my data?
1818

19-
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.
19+
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.

0 commit comments

Comments
 (0)