start update DOC-146

Author: markzegarelli

src/connections/data-residency.md

@@ -3,9 +3,6 @@ title: Data Residency
 ---
 Segment offers customers the option to mitigate risk by providing regional infrastructure across Europe, Middle East, Africa and Asia Pacific. The default region for all customers is United States (Oregon). The regional infrastructure has the same [rate limits and SLA](/docs/connections/rate-limits/) as the default region.
 
-> info ""
-> Contact [[email protected]](mailto:[email protected]) to enable regional infrastructure on your workspace.
-
 If your workspace is enabled to support regional services, you can select on the region on a per-source basis in that Source's settings.
 
 ![Data Residency Settings](images/data-residency.png)
@@ -14,4 +11,9 @@ All Segment client-side libraries dynamically read your preferred region when th
 
 For server-side routing, you can view endpoint details in the source's settings, and use the [`host`](https://github.com/segmentio/analytics-python/blob/c9f5ba6b58813eba1c3e5c778b0fc8d86f937f55/analytics/__init__.py#L9) configuration parameter to send data to the desired region.
 
-Regional infrastructure can failover across locations within the region, but does not failover across regions.
+Regional infrastructure can failover across locations within the region, but does not failover across regions.
+
+## Local data storage
+
+
+<!-- we need to add a section on Local Data Storage which outlines how customers can setup regional buckets so that their events are archived within the region. This will also need to include SLA and process details around replays and deletions as well as some caveats like: we cannot guarantee a replay if the customer tweaks the data in their bucket -->