From ba67d3fc7397208a87ba4c7ee6f2fd603142b61e Mon Sep 17 00:00:00 2001 From: Angela Costa Date: Tue, 3 Jun 2025 10:18:06 +0100 Subject: [PATCH] Updates order --- src/content/docs/data-localization/metadata-boundary/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/data-localization/metadata-boundary/index.mdx b/src/content/docs/data-localization/metadata-boundary/index.mdx index 45a95b1264c8bea..cedff72ce954984 100644 --- a/src/content/docs/data-localization/metadata-boundary/index.mdx +++ b/src/content/docs/data-localization/metadata-boundary/index.mdx @@ -2,7 +2,7 @@ pcx_content_type: concept title: Customer Metadata Boundary sidebar: - order: 1 + order: 5 --- As part of the Data Localization Suite, the Customer Metadata Boundary (CMB) ensures that Customer Logs — any traffic metadata that can identify a customer’s end user (that is, contains the customer's [Account ID](/fundamentals/account/find-account-and-zone-ids/)) — will stay in the `EU` (European Union) or in the `US` (United States), depending on the region the customer selects. For example, if a customer selects the `EU` Customer Metadata Boundary, metadata will **only** be sent to our core data center located in the European Union.