Webex Contact Center data locality by country

Verified 2026-09-05 · 91 claims · sources tier 2 · 6 disputed · 1 superseded

Also known as Country of Operation, HDS certification, Voice Access Points, data locality, prodeu2, produs1.

Webex Contact Center provisions tenants into 1 of exactly 8 data centres based on the Country of Operation chosen during set-up 41​40. WarmTransfer's reading of the sources is that this selection determines the physical storage location for specific contact centre data classes independently of broader Webex suite data residency 42​71.

How data locality is assigned

A tenant's data centre is determined by the Country of Operation selected in the Contact Center tab of the Set-Up wizard 40. Cisco states that the tenant is created in the data centre closest to the selected country, but Cisco does not define what closest means or publish any tie-break rule 36.

The authoritative list of countries eligible for selection as a Country of Operation is the Geographic Terms and Restrictions section of the Cisco Collaboration Flex Plan Contact Center Offer Description, rather than the data locality article 38. When placing orders under partner SKUs A-CJP or A-FLEX-CC, ordering carries 2 separate country selections: 1 at order creation that sets Webex data residency, and 1 in the Contact Center tab of the Set-Up wizard that sets Contact Center data locality 63​74. Cisco states that the ordering flow country determines data residency for Webex, and while the Contact Center tab defaults to this initial selection, it can be altered 74​62. WarmTransfer's reading of the sources is that the data locality documentation does not state whether a Webex Contact Center tenant's data centre assignment can be changed after set-up 48.

Data centres and country distribution

Tenants reside in 1 of 8 data centres: United States, Canada, United Kingdom, Germany, Singapore, Australia, Japan, and India 41. Across the published tables, the country counts per data centre are distributed as follows 37:

WarmTransfer's reading of the sources is that The 8 published country lists together name 159 countries; Cisco does not publish that total anywhere in the article 72.

The United Kingdom data centre acts as the largest operational bucket, serving 68 countries of operation, more than twice as many as the next-largest data centre 78. It covers most of Africa, the Middle East, the Caucasus, Central Asia, the Western Balkans, and the United Kingdom itself 77. Every African country listed in the article maps to the United Kingdom data centre, as no African data centre exists for Webex Contact Center 58. Central Asian nations—Kazakhstan, Kyrgyzstan, Tajikistan, Turkmenistan, and Uzbekistan—also map to the United Kingdom data centre 34.

Several regional mappings do not follow simple geographic or political groupings:

• A tenant whose Country of Operation is Monaco maps to the United Kingdom data centre, whereas France maps to Germany 57.
• Turkey maps to the United Kingdom data centre rather than Germany 73.
• Georgia maps to Germany, while neighbouring Armenia and Azerbaijan map to the United Kingdom 43.
• Norway and Ukraine map to Germany, indicating the Germany table is an operational grouping rather than an inventory of European Union member states 60.
• The United Arab Emirates maps to Singapore 75.
• Brazil maps to the United States data centre, as the article publishes no South American data centre 24.
• Japan and India each serve exactly 1 Country of Operation, their own 47.

Data classes and boundary limits

Cisco names 5 data classes held in a Webex Contact Center tenant's data centre: tenant configuration, call data records, call recordings, reporting and digital channels 42.

Chat data location is explicitly excluded from the Contact Center data locality mapping, and the article directs readers to the Webex data residency article for chat governance 35.

Regarding data security controls, Cisco publishes outbound source IP addresses per data centre for all 8 locations 66. Destination IP addresses for inbound traffic are not published because inbound connections terminate at load balancers using dynamic addresses 44. Adding a domain to the content security policy allowlist takes 10 minutes to take effect for an Agent Desktop embedded in an iframe 39.

Sensitive data masking on the Agent Desktop functions strictly as a user interface control 50. Cisco states that masked data is not encrypted in the backend, meaning network traffic and console logs continue to hold personal information 50. Furthermore, masking applies only to the Agent Desktop and does not protect Supervisor Desktop users 49. Pausing call recording does not stop metadata capture; call duration, dialled number, routing path, and related details continue to be captured in the Contact Center database 64. WarmTransfer's reading of the sources is that the Webex Contact Center security article publishes no retention period for call recordings or masked personal information 65.

Suite residency and platform relationships

WarmTransfer's reading of the sources is that Webex suite data residency and Webex Contact Center data locality are different systems: residency assigns an organisation to a named geographic region through a country-code mapping file while locality maps individual countries to 1 of 8 contact centre data centres 71. Suite residency maintains identities, encryption keys, and encrypted user-generated content (including meetings, messages, whiteboards, files, and their metadata) in the assigned geographic region 70.

On the broader Webex data residency table, Webex Contact Center is listed as available in 8 of 10 regions (United States, European Union, Canada, United Kingdom, Japan, Australia, Singapore, and India), but is omitted from the Saudi Arabia and United Arab Emirates regions 67. On that same table, Webex Messaging is resident in fewer regions than Webex Contact Center 56. Cisco states that migrating an organisation between Webex geographic regions is not currently supported, though it references a separate migration document for eligible legacy customers moving to new regional data centres 68​69.

Regional exceptions apply to administrative and audit records:

• Administrator activity records for Webex Calling and Contact Center events originating from India are stored locally in data centres in India 45.
• Audit log retention lasts 12 months in most regions, but extends to 3 years in India 23.

For Webex Calling multi-tenant deployments, the first location created in Control Hub dictates the Calling region, which Cisco states cannot be changed once assigned 29​33. This Calling assignment operates independently of common Webex services assignments 25. Multi-tenant Calling documentation identifies 16 data centre cities: Chicago, Dallas, Vancouver, Toronto, Amsterdam, Frankfurt, Manchester, London, Melbourne, Sydney, Osaka, Tokyo, Chennai, Mumbai, Jeddah, and Riyadh 27. In EMEA, Calling defines 3 sub-regions served by data centre pairs: EU (London and Frankfurt), EUN (Frankfurt and Amsterdam), and UK (London and Manchester) 28. Sources disagree on Calling data centre assignments for Middle East and African countries, as new customers headquartered there are assigned to the EUN region in one document while another source lists a Middle East and Africa geography served by data centres in Jeddah and Riyadh in Saudi Arabia 30​31. Calling also publishes standalone media points of presence (PoPs) in Los Angeles, New Jersey, Dallas, Singapore, Seoul, Sao Paulo, Cape Town, and the United Arab Emirates, where the UAE entry specifies only the country rather than a city 32​76. The Calling data centre document explicitly excludes Dedicated Instance 26.

Sources disagree on how Webex Meetings data storage rules and locations are selected, as Cisco states Meetings data is stored in a data centre chosen from the time zone selected for the Meetings site during provisioning (giving Frankfurt as the result for an EU time zone), while also stating that user-generated information is stored in the data centre closest to the user's location or as provided during the ordering process 55​54. Cisco notes that free account data may reside outside the account holder's region, and meetings billing data is stored in Texas and North Carolina, with analytics in California and Texas 52​51. Internet points of presence (iPOPs) for Meetings are classified separately from full data centres 46. Cisco also warns that Meetings data centre locations may change over time 53.

See also

• Webex suite data residency and the GEO model
• Webex Calling architecture and deployment models
• Webex Contact Center recording and contact data retention

Applicability

Across the claims in this article, the evidence covers Cisco Webex Contact Center, Cisco Webex, Cisco Webex Meetings, and Cisco Webex Calling across cloud, multi-tenant, and dedicated instance deployments, verified as of 2026-09-05. The Webex Calling data centre location article explicitly excludes Webex Calling Dedicated Instance from its scope 26.

What remains uncertain

Sources disagree on whether new Webex Calling tenants in the Middle East and Africa are assigned to European data centres under the EUN region or to regional facilities located in Jeddah and Riyadh 30​31. Sources disagree on whether Webex Meetings data locality is governed by the time zone chosen during provisioning or geographic proximity to the user 55​54. Cisco documentation states that Webex Contact Center tenants are assigned to the closest data centre but leaves how that proximity is evaluated undefined 36. Cisco notes that the Webex Calling EMEA data centre article is served under a URL slug that references the European Union despite the article title specifying the EMEA region 61. WarmTransfer's reading of the sources is that the 7 reviewed locality sources contain no template artefacts or authoring placeholders 59. Any formal process for reassigning a Webex Contact Center tenant to a different data centre after initial set-up is not covered by any claim in this article.

WarmTransfer. (2026, September 5). Webex Contact Center data locality by country. WarmTransfer. https://warmtransfer.net/knowledge/webex-cc-data-locality

@misc{warmtransfer-webex-cc-data-locality,
  title  = {Webex Contact Center data locality by country},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-cc-data-locality},
  note   = {Verified 2026-09-05}
}