Apply suggestions from code review [netlify-build]

Co-authored-by: stayseesong <[email protected]>

Author: forstisabella

src/privacy/data-retention-policy.md

@@ -4,7 +4,7 @@ title: Data Retention and Deletion Policy
 
 Twilio Segment’s Data Retention and Deletion Policy provides clarity, consistency and compliance across all Segment services and brings Segment’s data retention policy in line with industry standards and regulations. By implementing and enforcing this policy, Segment aims to enhance data governance and ensure that Segment customers can manage their data accurately, efficiently and securely within clearly defined retention periods.
 
-Segment will enforce a strict data retention policy for all:
+Segment enforces a strict data retention policy for all:
 
 - **[Active customers](#active-customers):** A Business or Team Tier customer that has an active Segment contract with no outstanding invoices and no locked workspace, or a Free Tier workspace that has had event traffic or user activity in the past 30 days.   
 - **[Expired customers](#expired-customers):** A Business or Team Tier customer that hasn’t renewed their Segment contract and has their workspace downgraded to Free Tier.   
@@ -15,15 +15,15 @@ Segment will enforce a strict data retention policy for all:
 ![A flowchart depicting the progression of active and no longer active customers.](images/data-retention-policy-flowchart.png)
 
 ## Effective Date
-Segment’s enforcement of this data retention policy for active customers will begin on:
+Segment’s enforcement of this data retention policy for active customers begins on:
 - **April 15, 2025** for Object Store data
 - **July 15, 2025** for Archive event and Profile events data stores
 
 ## Active customers
 
 An active customer is a Business or Team Tier customer that has an active Segment contract with no outstanding invoices and no locked workspace, or a Free Tier workspace that has had event traffic or user activity in the past 30 days. 
 
-Segment will enforce a data retention period of up to 3 years for Business Tier customers. If you currently have an extended retention period in place, Segment will continue to honor the previously agreed upon retention period. If your business requires a longer retention period, please contact your sales team to discuss available options.
+Segment enforces a data retention period of up to 3 years for Business Tier customers. If you currently have an extended retention period in place, Segment continues to honor the previously agreed upon retention period. If your business requires a longer retention period, please contact your sales team to discuss available options.
 
 ### Data retention period
 
@@ -35,30 +35,30 @@ The default data retention period for each of the data types is as follows:
 | **Team**     | 365 days                     | Not applicable               | 90 days                           | 365 days | Not applicable |
 | **Free**     | 180 days                     | Not applicable               | 60 days                           | 180 days | Not applicable |
 
-Through the self-serve Data Retention configuration in your workspace, you can configure a custom data retention period through “Workspace Default Archive Retention Period”.
+Through the self-serve Data Retention configuration in your workspace, you can configure a custom data retention period through the **Workspace Default Archive Retention Period** setting.
 
-Segment will unrecoverably delete a [Unify Space](/docs/unify/identity-resolution/space-setup/#step-one-create-a-new-dev-space) 90 days after it was disabled. 
+Segment unrecoverably deletes a [Unify Space](/docs/unify/identity-resolution/space-setup/#step-one-create-a-new-dev-space) 90 days after it was disabled. 
 
 ### What data is impacted?
 
-With this data retention policy, all data beyond the retention period will be unrecoverably deleted from all of Segment and will impact the following:
+With this data retention policy, all data beyond the retention period is unrecoverably deleted from all of Segment and impacts the following:
 
 * [Data Replays](/docs/guides/what-is-replay/) will only be available for data within the retention period. Unify, Engage and Linked customers that replay data to recreate Unify Spaces or Profiles may encounter variations in the number of profiles, as well as in the identifiers, traits and properties associated with the profiles, depending on the data available.
-* Backfill Data will only be available for data within the retention period.  
-* [Data residency](/docs/guides/regional-segment/) migrations across regions (US and EU) will only be available for data within the retention period.  
+* Backfill Data is only available for data within the retention period.  
+* [Data residency](/docs/guides/regional-segment/) migrations across regions (US and EU) is only available for data within the retention period.  
 * Additional impacts  to Object data:  
   * Cloud Object Data (using push) updated using the [Object API](/docs/connections/sources/catalog/libraries/server/object-api/#set), [Bulk API](docs/connections/sources/catalog/libraries/server/object-bulk-api/), or webhook cloud sources (for example, [SendGrid](/docs/connections/sources/catalog/cloud-apps/sendgrid/#streaming) or [Mandrill](/docs/connections/sources/catalog/cloud-apps/mandrill/#streaming)): Any data older than 180 days is treated as a new record and may not contain any historic properties. To prevent loss of data properties, Segment recommends that you always send full objects with all properties.  
-  * Users and Accounts: Segment aggregates data from Identify and Group events for entities active within the last 180 days. Any data older than 180 days will be treated as a new record and will not have historic properties. To prevent loss of data properties, Segment advises customers to migrate to using Profile Sync.  
-* [Computed traits](/docs/unify/Traits/computed-traits/) will be built using the available data within the retention period. Recreating these traits may result in different values based on the available data.  
-* [Profiles](/docs/unify/), [Engage](/docs/engage/) [Audiences](/docs/engage/audiences/) and [Journeys](/docs/engage/journeys/) that are built using Events will use available data within the retention period. Recreating these may result in different Profiles based on the available data. Further, depending on how the conditions are defined Profiles may or may not exit Computed traits, Engage Audiences, and Journeys due to the data retention policy, and this may result in mismatches in counts when comparing against a preview.
+  * Users and Accounts: Segment aggregates data from Identify and Group events for entities active within the last 180 days. Any data older than 180 days is treated as a new record and won't have historic properties. To prevent loss of data properties, Segment advises customers to migrate to using Profile Sync.  
+* [Computed traits](/docs/unify/Traits/computed-traits/) is built using the available data within the retention period. Recreating these traits may result in different values based on the available data.  
+* [Profiles](/docs/unify/), [Engage](/docs/engage/) [Audiences](/docs/engage/audiences/) and [Journeys](/docs/engage/journeys/) that are built using Events will use available data within the retention period. Recreating these may result in different Profiles based on the available data. Depending on how the conditions are defined, Profiles may or may not exit Computed traits, Engage Audiences, and Journeys due to the data retention policy, and this may result in mismatches in counts when comparing against a preview.
 
 ### What data is not impacted?
 
-With this policy the following data will be not impacted, but may be subject to other policies:
+With this policy the following data is not impacted, but may be subject to other policies:
 
 * **Cloud Object Data (using pull)**: This involves Segment fetching object data from third party Cloud Sources. Since Segment always fetches the full objects, the retention policy will have no impact.  
 * **Profiles**: Unify Profiles created are not subject to this data retention policy.   
-* **Third Party Destinations**: Data in your third party destinations shared by Segment in the course of your implementation will remain unaffected. Data stored in a third party system may be subject to the data retention policy of that system.    
+* **Third Party Destinations**: Data in your third party destinations shared by Segment in the course of your implementation remains unaffected. Data stored in a third party system may be subject to the data retention policy of that system.    
 * Anything a user creates in the Segment App, like Audiences, Journeys, Data Graphs, Connections, and more, **are not subject to this data retention policy**.
 
 ## Expired customers
@@ -71,24 +71,24 @@ Segment will enforce a maximum data retention period of 90 days for Unify data,
 
 Expired customers will have:
 
-* Their data immediately subject to data retention of an active, Free Tier customer. All data beyond the retention period will be deleted and unrecoverable.  
+* Their data immediately subject to data retention of an active, Free Tier customer. All data beyond the retention period is deleted and unrecoverable.  
 * Their Unify data deleted and unrecoverable 90 days from the date their workspace was downgraded.
 
 ## Contracted customers 
 
 A contracted customer is a Business Tier customer that elects to stop using add-on features like Unify, Unify+, Engage and/or Linked.
 
-Segment will enforce a maximum data retention period of up to 90 days for all contracted customers, unless they explicitly request immediate deletion through a [support ticket](/docs/privacy/account-deletion/). All data beyond the retention period will be deleted and unrecoverable as described below.
+Segment enforces a maximum data retention period of up to 90 days for all contracted customers, unless they explicitly request immediate deletion through a [support ticket](/docs/privacy/account-deletion/). All data beyond the retention period is deleted and unrecoverable as described below.
 
 ### What data is impacted?
 
-With this data retention policy, all data in all your Unify Spaces after the retention period will be deleted and unrecoverable. If you opt-in to Unify, Unify+, Engage, and/or Linked after the retention period, you will be starting with a brand new implementation with no previous data.
+With this data retention policy, all data in all your Unify Spaces after the retention period is deleted and unrecoverable. If you opt-in to Unify, Unify+, Engage, and/or Linked after the retention period, you'll be starting with a brand new implementation with no previous data.
 
 ### What data is not impacted?
 
 If contracting from Engage or Linked, your Connection and Unify data will remain unaffected and will be subject to the [Active customer retention policy](#active-customers).
 
-If contracting from Unify or Unify+, your Connection data will remain unaffected and will be subject to the [Active customer retention policy](#active-customers).
+If contracting from Unify or Unify+, your Connection data remains unaffected and will be subject to the [Active customer retention policy](#active-customers).
 
 ## Churned customers 
 
@@ -109,8 +109,8 @@ Customers that have unpaid invoices and have their workspaces fully locked out w
 
 An Unused Free Tier workspace is a workspace that has not received any Segment event traffic or user activity in the last 30 days. 
 
-Segment will unrecoverably delete the workspace after 30 days of inactivity, unless explicitly requested for immediate deletion through a [support ticket](/docs/privacy/account-deletion/#delete-your-workspace-data). 
+Segment unrecoverably deletes the workspace after 30 days of inactivity, unless explicitly requested for immediate deletion through a [support ticket](/docs/privacy/account-deletion/#delete-your-workspace-data). 
 
 ### Data deletion delays
 
-When data reaches the end of its retention period, deletion will be scheduled in accordance with Segment’s data retention policy. While Segment aims to complete the deletion process promptly, there may be occasional delays due to processing times or technical constraints. Segment is committed to initiating data deletions as soon as possible and will strive to complete deletions within 7 days of the scheduled date.
+When data reaches the end of its retention period, deletion is scheduled in accordance with Segment’s data retention policy. While Segment aims to complete the deletion process promptly, there may be occasional delays due to processing times or technical constraints. Segment is committed to initiating data deletions as soon as possible and strives to complete deletions within 7 days of the scheduled date.