Skip to content

Commit 1969a05

Browse files
committed
DOC-460 Editing pass [netlify-build]
1 parent ff502c7 commit 1969a05

File tree

2 files changed

+3
-4
lines changed

2 files changed

+3
-4
lines changed

src/privacy/account-deletion.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,11 +40,10 @@ After you delete your workspace or account, Segment removes all data associated
4040
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**.
4141

4242
> warning "Purging data from workspaces deleted prior to March 31, 2022"
43-
> 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 [[email protected]](mailto:[email protected]) 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.
43+
> 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 [([email protected])](mailto:[email protected]) 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.
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 [([email protected])](mailto:[email protected]) 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.
4847

49-
> warning " "
48+
> error " "
5049
> 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.

src/privacy/bcr-compliance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,4 @@ To learn more about Twilio's Binding Corporate Rules (BCRs,) read the [full vers
1616

1717
### 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), means that Segment is 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) 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.

0 commit comments

Comments
 (0)