[netlify-build]

stayseesong · markzegarelli · commit 09da99133a90 · 2021-11-02T16:49:09.000-07:00
diff --git a/src/connections/regional-segment-eu.md b/src/connections/regional-segment-eu.md
@@ -1,5 +1,6 @@
 ---
 title: Regional Segment (Europe)
+hidden: true
 ---
 {% include content/plan-grid.md name="data-residency" %}
 
@@ -8,10 +9,7 @@ title: Regional Segment (Europe)
 
 Segment provides regional infrastructure across Europe, Middle East, Africa and Asia Pacific with [rate limits and SLA](/docs/connections/rate-limits/).
 
-As Schrems II restricts the transfer of personal data to any processors established in countries outside of Europe, all data in European workspaces must be ingested, stored, processed and delivered locally within the EU. Workspaces you configure to use the EU West Data Processing Region ingest (for supported sources), process, filter, deduplicate, and archive data through Segment-hosted archives hosted in S3 AWS Dublin, Ireland.
-
-> info ""
-> [Cloud object sources](/docs/connections/sources/#object-cloud-sources) and cloud event sources aren't supported in EU workspaces. 
+As Schrems II restricts the transfer of personal data to any processors established in countries outside of Europe, all data in European workspaces ingest, store, process and deliver locally within the EU. You can set up workspaces in the EU where data is received via the Dublin, Ireland endpoint hosted in the EU for all sources, with the exception of [cloud object sources](/docs/connections/sources/#object-cloud-sources) and cloud event sources that aren't supported. Segment-hosted archives hosted in S3 AWS Dublin, Ireland, process, filter, validate, deduplicate, and archive data for EU workspaces.
 
 > info ""
 > Regional Segment for Europe is currently in beta. Segment’s [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature.
@@ -20,7 +18,7 @@ As Schrems II restricts the transfer of personal data to any processors establis
 To create a workspace with a different data processing region:
 1. Log in to your segment account.
 2. Click **New Workspace**.
-3. Select your **Data processing region**. This determines the location in which Segment collects, processes, and stores data that’s sent to and from your workspace. You can choose from *US West* or *EU West*.  
+3. Select your **Data processing region**. This determines the location in which Segment collects, processes, and stores data that’s sent to and from your workspace. You can choose from *US West* or *EU Central*.  
 4. Click **Create workspace**.
 
 ## Regional Data Ingestion
@@ -34,16 +32,16 @@ To set your Data Ingestion Region:
 2. Select the **Settings** tab.
 3. Click **Regional Settings**.
 4. Choose your **Data Ingestion Region**.
-    * If you’re in the *US West* data processing region, you can select from: Dublin, Singapore, Oregon, and Sydney.
-    * If you're in the *EU West* data processing region, Segment’s EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com` endpoint.
+    * If you’re in the US region, you can select from: Dublin, Singapore, Oregon, and Sydney.
+    * Segment’s EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com` endpoint.
 
 ### 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 Data Ingestion Region in that source’s settings.
 
 All regions are configured on a per-source basis. Configure the region for each source separately if you don't want to use the default region.
 
 > info ""
-> For workspaces that use the EU West Data Processing region, the Dublin Ingestion region is preselected for all sources.
+> Dublin is the only region for EU instances and defaults automatically.
 
 All Segment client-side SDKs read this setting and update themselves automatically to send data to new endpoints when the app reloads. You don't need to change the code when you switch regions.
 
