diff --git a/content/security/compliance/gdpr.md b/content/security/compliance/gdpr.md index b8c01725e8..55660546aa 100644 --- a/content/security/compliance/gdpr.md +++ b/content/security/compliance/gdpr.md @@ -8,9 +8,9 @@ variants: -flyte +union # GDPR alignment -Union.ai's architecture inherently supports GDPR through its data residency model. For EU-region data planes, all customer data remains within the European Union. Union.ai operates control plane endpoints in EU West-1 (Ireland), EU West-2 (London), and EU Central (Frankfurt), ensuring organizations can deploy with full EU data residency. +Union.ai's architecture inherently supports GDPR through its data residency model. On this page, an EU region is a cloud region located in an EU member state. EU West-2 (London) is in the United Kingdom, which is outside the EU, so it is not an EU region. For EU-region data planes, all customer data remains within the European Union. At signup, an organization's control plane can be placed in two European regions: EU West-2 (London) and EU Central (Frankfurt). Full EU data residency requires the EU Central control plane. -The control plane stores orchestration metadata (including task definitions), encrypted at rest. When both planes are in EU regions (EU West-1, EU West-2, or EU Central), all data and metadata (both at rest and in transit) stay within the EU. +The control plane stores orchestration metadata (including task definitions), encrypted at rest. When the data plane is in an EU region and the control plane is in EU Central, all data and metadata (both at rest and in transit) stay within the EU. For details on how data residency is enforced architecturally, see [Data classification and residency](../data-protection/classification-and-residency) and [Two-plane separation](../architecture/two-plane-separation). @@ -24,6 +24,6 @@ For details on how data residency is enforced architecturally, see [Data classif 1. Follow the data residency verification steps described in [Data classification and residency](../data-protection/classification-and-residency#data-residency). All data resides in EU-region infrastructure. -2. Confirm that the control plane endpoints are deployed in EU regions (EU West-1, EU West-2, EU Central). +2. Confirm that the organization's control plane endpoint is deployed in EU Central (eu-central-1). 3. This is architectural verification. The [two-plane separation](../architecture/two-plane-separation) ensures data never leaves the customer's cloud account. diff --git a/content/security/data-protection/classification-and-residency.md b/content/security/data-protection/classification-and-residency.md index 698a7193ea..11ae58c2bd 100644 --- a/content/security/data-protection/classification-and-residency.md +++ b/content/security/data-protection/classification-and-residency.md @@ -32,9 +32,9 @@ Every data type in the Union.ai platform is classified by its residency and acce All customer data resides in the customer's own cloud account and region. The customer chooses the region for their data plane deployment, and all data plane resources (object storage, container registry, secrets backend, log aggregator, and compute) are provisioned within that region. -The control plane is available in the following regions: US West (us-west-2), US East (us-east-2), EU West-1 (Ireland), EU West-2 (London), and EU Central (eu-central-1). No customer data of any kind is replicated to, cached in, or routed through Union.ai infrastructure; inline data is served from the customer's data plane through the Direct-to-Data-Plane tunnel and never traverses the control plane region. Only orchestration metadata (run IDs, schedules, phase transitions, task definitions, error messages, and the RBAC graph) resides in the control plane region. +The control plane is available in the following regions: US West (us-west-2), US East (us-east-2), EU West-2 (London), and EU Central (eu-central-1). No customer data of any kind is replicated to, cached in, or routed through Union.ai infrastructure; inline data is served from the customer's data plane through the Direct-to-Data-Plane tunnel and never traverses the control plane region. Only orchestration metadata (run IDs, schedules, phase transitions, task definitions, error messages, and the RBAC graph) resides in the control plane region. -Customers whose data-residency policy extends to orchestration metadata (e.g., GDPR, or jurisdiction-specific policies that cover operational records about workflows in addition to the workflow data itself) should select a control plane region consistent with that policy. For EU-deployed data planes using an EU control plane region, all data and metadata (both at rest and in transit) stay within the EU, supporting GDPR data residency requirements. +Customers whose data-residency policy extends to orchestration metadata (e.g., GDPR, or jurisdiction-specific policies that cover operational records about workflows in addition to the workflow data itself) should select a control plane region consistent with that policy. For data planes in an EU member state (not eu-west-2, London) using the EU Central (eu-central-1) control plane, all data and metadata (both at rest and in transit) stay within the EU, supporting GDPR data residency requirements. For details on the architectural separation that enforces these residency guarantees, see [Two-plane separation](../architecture/two-plane-separation).