Merge pull request #1691 from segmentio/DOC-192_data-res-ga

DOC-192 update doc and screens

Author: markzegarelli

src/_data/products.yml

@@ -114,3 +114,11 @@ items:
     team: false
     business: true
     add-on: true
+- product_display_name: Data Residency
+  slug: data-residency
+  plan-note: "Data residency is available to customers on the Business Tier plan."
+  plans:
+    free: false
+    team: false
+    business: true
+    add-on: false

src/connections/data-residency.md

@@ -1,29 +1,22 @@
 ---
 title: Data Residency
-beta: true
 ---
+{% include content/plan-grid.md name="data-residency" %}
 
-> info ""
-> **Note**: Data residency is in public beta, and its use is governed by the [(1) Segment First Access and Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview/) and [(2) Segment Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/).
-
-
-Segment offers customers the option to lead on data residency by providing regional infrastructure across Europe, Middle East, Africa and Asia Pacific. The default region for all customers is in Oregon, United States. The regional infrastructure has the same [rate limits and SLA](/docs/connections/rate-limits/) as the default region.
 
-## Enable Local Data Ingest and Storage
 
-This feature is in Public Preview. You can enable Local Data Ingest and Storage from the Regional Settings tab within your Workspace settings. Enabling the feature here makes the feature available to both client-side and server-side sources.
 
-![enable](images/enable-regional-ingest.png)
+Segment offers customers the option to lead on data residency by providing regional infrastructure across Europe, Middle East, Africa and Asia Pacific. The default region for all customers is in Oregon, United States. The regional infrastructure has the same [rate limits and SLA](/docs/connections/rate-limits/) as the default region.
 
-## Local Data Ingest
+## Regional Data Ingestion
 
-Local Data Ingest enables you to send data to Segment from both Client-side and Server-side sources through locally hosted API ingest points. The regional infrastructure can fail-over across locations within a region, but never across regions.
+Regional Data Ingestion enables you to send data to Segment from both Device-mode and Cloud-mode sources through regionally hosted API ingest points. The regional infrastructure can fail-over across locations within a region, but never across regions.
 
 ### Client-side sources
 
-You can configure Segment's client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host after you've updated the Ingest Region in that source's settings.
+You can configure Segment's client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host after you've updated the Data Ingestion Region in that source's settings.
 
-![ingest region](images/regional-ingest.png)
+![ingestion region](images/regional-ingest.png)
 
 All regions are configured on a **per-source** basis. You'll need to configure the region for each source separately if you do not want to use the default region (Oregon). All Segment client-side SDKs read this setting and update themselves automatically to send data to new endpoints when the app is reloaded. You do not need to change code when you switch regions.
 
@@ -36,16 +29,21 @@ When you send data from a server-side or project source, you can use the `host`
 3. Singapore — `in.ap1.segmentapis.com/v1`
 4. Sydney — `in.au1.segmentapis.com/v1`
 
-## Local Data Storage
+## Regional Data Storage
 
-Local Data Storage allows you to preserve your raw events in Amazon S3 buckets hosted regionally. These buckets are hosted by you, in your desired region.
+Regional Data Storage allows you to preserve your raw events in Amazon S3 buckets hosted regionally. These buckets are hosted by you, in your desired region.
 
 > note ""
-> Configure Local Data Storage on new sources instead of enabling on an existing source to avoid deletion of historical data and a change in retention policy. Historical data that is expired due to a retention policy cannot be replayed at a time in the future. Historical data cannot be migrated from the US to your regional buckets.
+> Configure Regional Data Storage on new sources instead of enabling on an existing source to avoid deletion of historical data and a change in retention policy. Historical data that is expired due to a retention policy cannot be replayed at a time in the future. Historical data cannot be migrated from the US to your regional buckets.
+
+You can enable Regional Data Storage from the Regional Settings tab within your Workspace settings. Enabling the feature here makes the feature available to both client-side and server-side sources.
+
+> info ""
+> **Note**: Regional Data Storage is a Beta feature, and its use is governed by the [(1) Segment First Access and Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview/){:target="_blank"} and [(2) Segment Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/){:target="_blank"}.
 
 ### Pre-requisites
 
-To begin with Local Data Storage, complete the following steps in your AWS account:
+To begin with Regional Data Storage, complete the following steps in your AWS account:
 
 1. Create an S3 bucket in your preferred region
 2. Create a folder named `segment-logs` in the new bucket
@@ -142,13 +140,13 @@ To begin with Local Data Storage, complete the following steps in your AWS accou
     }
   ```
 
-### Local Data Storage configuration
+### Regional Data Storage configuration
 
-After you configure the policy and roles, as defined above, navigate to the Regional Settings tab of the Settings page of the  source for which you want to store data regionally, and find the Local Data Storage section.
+After you configure the policy and roles, as defined above, navigate to the Regional Settings tab of the Settings page of the  source for which you want to store data regionally, and find the Regional Data Storage section.
 
 ![local storage](images/regional-data-source.png)
 
-To complete the configuration of Local Data Storage:
+To complete the configuration of Regional Data Storage:
 
 1. Enter the name of the S3 Bucket you created in the Pre-requisites section
 2. Add a regional label to help locate the bucket from AWS at a later date. For example, `us-west2-294048959147` or `country-REGION-AWS_ACCOUNT`
@@ -158,24 +156,24 @@ To complete the configuration of Local Data Storage:
 6. Identify the Source in the source-level archive retention periods list
 7. Set the Retention for this source to the suggested value of `7 days`* and click **Save**
 
-The Local Data Storage bucket will take roughly one hour to receive data.
+The Regional Data Storage bucket will take around one hour to receive data.
 
-* The data retention can be set to any value available in the portal. If you require less than 7 days of data stored in the Segment-owned Archives, please reach out to support.
+\* The data retention can be set to any value available in the portal. If you require less than 7 days of data stored in the Segment-owned Archives, please contact [Segment Support](https://segment.com/help/contact){:target="_blank"}.
 
-### Deletion from Local Data Storage
+### Deletion from Regional Data Storage
 
-Local Data Storage offers the same ability to delete end-user data when they revoke or alter their consent to have data collected, as long as they can be identified by a `userId`. For example, if an end-user invokes their Right to Object or Right to Erasure under the GDPR or CCPA, you can use these features to:
+Regional Data Storage offers the same ability to delete end-user data when they revoke or alter their consent to have data collected, as long as they can be identified by a `userId`. For example, if an end-user invokes their Right to Object or Right to Erasure under the GDPR or CCPA, you can use these features to:
 - block ongoing data collection for that user
 - delete all historical data about them from Segment's systems, connected S3 buckets and warehouses, and supported downstream partners
 
-Contact [Segment Support](https://segment.com/help/contact/) to initiate a deletion and provide a valid `userId` for each user to be deleted. Deletion requests are run within the region, and have a 30 day SLA, but requires that the raw data is accessible to Segment in an unaltered state. Deletion from Local Data Storage is not available from the [Privacy Portal](/docs/privacy/user-deletion-and-suppression/#deletion-requests) or through the API.
+Contact [Segment Support](https://segment.com/help/contact/){:target="_blank"} to initiate a deletion and provide a valid `userId` for each user to be deleted. Deletion requests are run within the region, and have a 30 day SLA, but requires that the raw data is accessible to Segment in an unaltered state. Deletion from Regional Data Storage is not available from the [Privacy Portal](/docs/privacy/user-deletion-and-suppression/#deletion-requests) or through the API.
 
 > note "Business Plan Customers"
 > If you use this feature to delete data, you cannot Replay the deleted data at the same time. For standard Replay requests, you must wait for any pending deletions to complete. You cannot submit new deletions requests for the period of time that Segment replays data for you.
 
-### Replays from Local Data Storage
+### Replays from Regional Data Storage
 
-Local Data Storage supports [Replays](/docs/guides/what-is-replay/#replays-for-tooling-changes) to both existing and new tools. To request a Replay, [contact Segment](https://segment.com/help/contact/) with the following:
+Regional Data Storage supports [Replays](/docs/guides/what-is-replay/#replays-for-tooling-changes) to both existing and new tools. To request a Replay, [contact Segment](https://segment.com/help/contact/){:target="_blank"} with the following:
 - Source ID
 - Date Range
 - Destination
@@ -184,4 +182,4 @@ Segment will initiate Replay jobs and update status as they progress.
 
 ### Debugging and support
 
-The Segment Customer Success and Support Engineering teams do not have access to customer hosted regional buckets used for Local Data Storage and cannot provide event level debug support.
+The Segment Customer Success and Support Engineering teams do not have access to customer hosted regional buckets used for Regional Data Storage and cannot provide event level debug support.