00 · Header

T1 · Control Hub & Platform Foundations

Data Residency & Security Basics

The country you select while provisioning permanently sets the GEO for the organization’s users and encryption keys. Webex does not currently support migrating between GEO locations. Meetings follow the site time zone. Calling follows the principal place of business given at order time. You read the result at Account > Info > Data Locations.

Expand all sections

01 · Executive summary

Five lines, then why it matters

• Check Meetings, Messaging, and common application data at Account > Info > Data Locations. Check Contact Center at Contact Center > Settings > Service Details > Country of Operation. [cite:1]
• CountryCodeGEOMapping.xlsx maps a country to a region. On the User page tab, cell B3 is the country and cell B4 is the region. [cite:2]
• Space content is stored in the region of the organization that owns the space. A 1:1 chat that includes a North America or rest-of-world user is stored in that GEO. [cite:1]
• Compliance officers keep visibility of user content regardless of where it is stored, including eDiscovery and CASB. [cite:1]
• Eligible legacy moves named on August 29, 2025 are European Union common application data, Saudi Arabia Webex Meetings sites, and UAE common application data. That header is older than 12 months. re-check [cite:3]

02 · Architecture map

Three residency decisions, one Account page

• 1Country Selector
• 2Meetings time zone
• 3Calling order
• 4Account info

flowchart LR
  Country[Country Selector] --> Messaging
  TZ[Meetings time zone] --> Meetings
  Order[Principal place of business] --> Calling

Studio asset still required: assets/diagrams/T1-R07/arch.svg

03 · Concept deep-dive

Residency is per service

Data residency, formerly called data locality, stores user data in regional data centers corresponding to the customer’s location. The offering described in the overview is for new customers. The retrieved article is dated September 24, 2026. [cite:1]

Checkmarks in the September 24, 2026 table

The article’s table marks where a service is offered. An empty cell is not a city name this room will invent. Read the privacy data sheet the article names before you add a rest-of-world site.

Rules that survive a design review

04 · Ecosystem

Ecosystem and sister technologies

Glossary

Data residency

Storage of user data in regional data centers that correspond to the customer’s location. Formerly called data locality. [cite:1]

GEO

The location set at provisioning for the organization’s users and encryption keys. A later move between GEOs is not supported. [cite:1]

KMS

The Key Management Service in the organization’s region. It handles requests for keys that encrypt and decrypt spaces, messages, and content in Webex App. [cite:1]

Country Selector

The Control Hub drop-down during provisioning that maps a country to a data center. [cite:1]

Data Locations

Account > Info > Data Locations, where an admin verifies Meetings, Messaging, and common application data. [cite:1]

Country of Operation

The Contact Center setting that confirms that service’s residency. [cite:1]

Space owner

The organization whose region stores the content that appears in the space. [cite:1]

iPOP

Internet Point of Presence. The Meetings article lists them separately from data centers. [cite:4]

Mind map

mindmap
  root((Residency))
    Country
    Meetings
    Calling
    Contact Center
    Compliance

Sister-technology matrix

Integration edges

Cross-platform bridges

Future-integration hooks

• The article says Messaging locations were introduced with the intention of expanding later. Treat new regions as a documentation change, not as a promise this room can schedule.
• Legacy customers eligible for a regional move are pointed at the data-center migration article. re-check s0lk5g. Header August 29, 2025. [cite:3]
• Canon planning: record Account > Info > Data Locations from a lab org next to the country that was selected. Study evidence only.

Ecosystem troubleshooting

05 · Flow

From country selection to the Account page

06 · Config

Click paths

1. During organization provisioning, use the Country Selector. Prefer the country where most users are, even if the business address differs. [cite:1]
2. Before you commit, download CountryCodeGEOMapping.xlsx. On the User page tab, set B3 and read B4. Or browse the Country Code GEO mapping tab. [cite:2]
3. After the org exists, sign in to Control Hub and open Account > Info > Data Locations for Meetings, Messaging, and common application data. [cite:1]
4. For Contact Center, open Contact Center > Settings > Service Details > Country of Operation. [cite:1]
5. When you create a Meetings site, the time zone selects the Meetings data center. An EU city time zone is Frankfurt in this article. [cite:1]
6. For Calling, confirm the principal place of business the partner submitted at order time. The article does not give a Control Hub control that moves that choice. [cite:1]
7. Do not plan a later move between Messaging GEOs. The article says that migration is not supported. [cite:1]
8. If the customer is in a legacy migration program, read the data-center migration article before you promise a move. re-check [cite:3]

Screenshot placeholder. The paths above are the articles.

07 · Limits

Values the articles state

08 · Troubleshooting

Eight failures that follow from the articles

09 · Self-question ladder

Twelve rungs

10 · Lab

Spreadsheet desk, no production org

• Goal: for six paper orgs, name which input sets Messaging, Meetings, and Calling.
• Prereq: this room. Do not create a production organization to test a GEO.
• Step 1. Users are mostly in one country and the billing address is another. Expected: select the users’ country.
• Step 2. Meetings time zone is an EU city. Expected: Frankfurt for Meetings data.
• Step 3. Someone plans to move the Messaging GEO next year. Expected: not supported.
• Step 4. A 1:1 includes a North America or RoW user. Expected: conversation content is stored in that GEO.
• Step 5. An audit search asks for 18 months. Expected: the search window is the past year.
• Evidence: the six answers with the cite.
• Break it: read WBX28754’s California analytics line as the Messaging GEO. Recovery: that article is Meetings data centers and iPOPs. Messaging GEOs are in oybc4fb.
• Reflection: which of your designs still has one region for every Webex service.

11 · Quiz

Twelve questions

12 · Audio

Slots for Studio

13 · Interview

Oral answers

30 seconds. The Country Selector permanently sets the GEO for users and encryption keys. I cannot move that GEO later. I verify Meetings, Messaging, and common application data at Account, Info, Data Locations.

2 minutes. Messaging Europe is Frankfurt and Amsterdam for Continental Europe, the Middle East, and Africa. North America and the rest of the world is in the United States. If most users are in one country, I pick that country. If they are spread out, I pick the country with the most users, and everyone is stored there. Meetings use the site time zone, and an EU city is Frankfurt. Calling uses the principal place of business from the order. Contact Center uses Country of Operation. AI content stays with the user-generated content. Audit retention is a year in most regions and three years in India, and search is only the past year.

30 seconds, spaces. The creating organization owns a group space. A team owns spaces created in it. A space moved into a team later keeps its original owner. A 1:1 that includes North America or the rest of the world is stored in that GEO.

2 minutes, what I will not merge. I will not read the Meetings data-center list as the Messaging GEO. Free Meetings accounts may sit outside the holder’s region, and that list can change. I will not promise the August 29, 2025 migration regions without a re-check. Compliance visibility continues across regions. Partners can create customer orgs in any region where the service is offered.

What you will say about a later country change. The article says the organization stays in the GEO where it was created.

14 · Citations

1. Data residency in Webex — help.webex — article oybc4fb — help.webex.com article oybc4fb — header September 24, 2026 — retrieved 2026-10-14. Country Selector, permanent GEO, service table, space ownership, audit retention, AI content, Calling order address, Contact Center country, Account > Info > Data Locations.
2. Find the Data Residency Region That Maps to a Country — help.webex — article wej14b — help.webex.com article wej14b — header April 14, 2026 — retrieved 2026-10-14. CountryCodeGEOMapping.xlsx. Cell B3 country, cell B4 region.
3. Data center migration plans for your organization’s data in Control Hub — help.webex — article s0lk5g — help.webex.com article s0lk5g — header August 29, 2025 — retrieved 2026-10-14. re-check. EU common application data, Saudi Arabia Meetings sites, UAE common application data.
4. Where are the Webex Data Centers and iPOP Locations? — help.webex — article WBX28754 — help.webex.com article WBX28754 — header February 13, 2026 — retrieved 2026-10-14. Meetings data centers and iPOPs. Locations may change. Free accounts may be stored outside the holder’s region. Billing in Texas and North Carolina. Analytics in California and Texas.

15 · Re-engineer later

• Open questions: whether s0lk5g’s eligible regions are unchanged since August 29, 2025.
• Facts still TODO-verify: 0. The legacy migration list is re-check.
• Assets missing: Data Locations screenshot, audio.
• Ideas for v1.0: a three-column card for country, Meetings time zone, and Calling order address.
• Next review: when oybc4fb adds a Messaging region or changes the no-migration sentence.