|
1 | 1 | ---
|
2 | 2 | title: Data Residency
|
3 |
| -beta: true |
4 | 3 | ---
|
| 4 | +{% include content/plan-grid.md name="data-residency" %} |
5 | 5 |
|
6 | 6 |
|
7 | 7 |
|
8 | 8 |
|
9 | 9 | 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.
|
10 | 10 |
|
11 |
| -## Enable Regional Data Ingest and Storage |
| 11 | +## Enable Regional Data Ingestion and Storage |
12 | 12 |
|
13 |
| -You can enable Regional 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. |
| 13 | +You can enable Regional Data Ingestion 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. |
14 | 14 |
|
15 | 15 | 
|
16 | 16 |
|
17 | 17 | > info ""
|
18 |
| -> **Note**: Regional Data Storage 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/) and [(2) Segment Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/). |
| 18 | +> **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/) and [(2) Segment Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/). |
19 | 19 |
|
20 |
| -## Regional Data Ingest |
| 20 | +## Regional Data Ingestion |
21 | 21 |
|
22 |
| -Regional 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. |
| 22 | +Regional Data Ingestion enables you to send data to Segment from both Client-side and Server-side sources through regionally hosted API ingest points. The regional infrastructure can fail-over across locations within a region, but never across regions. |
23 | 23 |
|
24 | 24 | ### Client-side sources
|
25 | 25 |
|
26 |
| -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. |
| 26 | +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. |
27 | 27 |
|
28 |
| - |
| 28 | + |
29 | 29 |
|
30 | 30 | 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.
|
31 | 31 |
|
|
0 commit comments