# Webex Contact Center data locality by country

Canonical: https://warmtransfer.net/knowledge/webex-cc-data-locality

Last verified: 2026-09-05

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]:

| Data centre | Country count |
| --- | --- |
| United States | 28 |[^37]
| Canada | 2 |[^37]
| United Kingdom | 68 |[^37]
| Germany | 29 |[^37]
| Singapore | 23 |[^37]
| Australia | 7 |[^37]
| Japan | 1 |[^37]
| India | 1 |[^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](https://warmtransfer.net/knowledge/webex-suite-data-residency)
- [Webex Calling architecture and deployment models](https://warmtransfer.net/knowledge/webex-calling-architecture)
- [Webex Contact Center recording and contact data retention](https://warmtransfer.net/knowledge/webex-cc-recording-retention)

## Applicability

Applies to: Cisco Webex Contact Center, Cisco Webex, Cisco Webex Meetings, and Cisco Webex Calling. Deployments: cloud, multi-tenant, and dedicated instance. Sources checked 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 the sources below.

## Sources

[^1]: The residency table's footnote states that the requests marked global can end up in any data centre globally where the models are hosted. Source: [Cisco Webex Calling AI Receptionist - AI Transparency Note](https://www.cisco.com/c/dam/r/ctp/docs/transparency/webex-calling-ai-receptionist-ai-transparency-note.pdf), data residency table footnote. Checked 2026-09-05.
[^2]: The AI Receptionist transparency note publishes a data residency table covering 7 regions identified as produs1, prodeu1, prodeu2, prodca1, prodip1, prodanz1 and prodsg1. Source: [Cisco Webex Calling AI Receptionist - AI Transparency Note](https://www.cisco.com/c/dam/r/ctp/docs/transparency/webex-calling-ai-receptionist-ai-transparency-note.pdf), data residency table. Checked 2026-09-05.
[^3]: The Singapore region's row routes its internal model proxy through Sydney in Australia rather than through Singapore. Source: [Cisco Webex Calling AI Receptionist - AI Transparency Note](https://www.cisco.com/c/dam/r/ctp/docs/transparency/webex-calling-ai-receptionist-ai-transparency-note.pdf), data residency table, prodsg1 row. Checked 2026-09-05.
[^4]: The AI Receptionist note is the only one of the 9 to publish a data residency table, listing 7 regions, and its own footnote qualifies the guarantee for several of them. Source: [Cisco Webex Calling AI Receptionist - AI Transparency Note](https://www.cisco.com/c/dam/r/ctp/docs/transparency/webex-calling-ai-receptionist-ai-transparency-note.pdf), data residency table and footnote. Checked 2026-09-05.
[^5]: Administrators were told that audit logs would no longer be available in the Management Portal after a 90 day window and were advised to download any needed audit events before removal. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), release entry announcing the audit log removal. Checked 2026-09-05.
[^6]: The cloud Webex Contact Center product is not named anywhere in the Edge Connect article outside shared site navigation. Source: [Webex Edge Connect](https://help.webex.com/en-us/article/n68tcpb/Cisco-Webex-Edge-Connect), whole article. Checked 2026-09-05.
[^7]: A recorded utterance can leave the platform through the HTTP Request activity, because the Record activity produces a file reference that a later activity can send outward (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Record and HTTP Request activities read together. Checked 2026-09-05.
[^8]: Table 2 in an Offer Disclosure lists customer systems information categories and is where retention periods for telemetry events and configuration data are published (field report). Source: [Cisco Webex Contact Center Service Offer Disclosure](https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/webex-contact-center-offer-disclosure.pdf), Table 2. Checked 2026-09-05.
[^9]: Table 3 in a cloud Offer Disclosure lists data centre locations and the Webex Contact Center disclosure lists 12 Cisco locations plus 11 AWS regions while the Webex Contact Center Enterprise disclosure lists 7 Cisco locations and names no AWS regions and the Webex Engage disclosure lists 7 AWS regions and names no Cisco owned data centre. Source: [Cisco Webex Contact Center Service Offer Disclosure](https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/webex-contact-center-offer-disclosure.pdf), Table 3 compared across three cloud documents. Checked 2026-09-05.
[^10]: The Cisco Webex Contact Center Service Offer Disclosure is the document covering the cloud contact centre product, and it carries the full section set: an overview, data handling with tables 1 to 3, security with the access and controls table at table 6, and an artificial intelligence section with table 7. Source: [Cisco Webex Contact Center Service Offer Disclosure](https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/webex-contact-center-offer-disclosure.pdf), title page and section headings. Checked 2026-09-05.
[^11]: Webex WFO Agent Assist logs events to a tenant-specific database and this logging is opt-in only. Source: [Contact Center: Webex Workforce Optimization Agent Assist - AI Transparency Technical Note](https://trustportal.cisco.com/c/dam/r/ctp/docs/transparency/ai-transparency-webex-workforce-optimization-agent-assist-technical-note.pdf), logging section. Checked 2026-09-05.
[^12]: The AI Quality Management fine-tuned evaluation models are trained per customer organisation are never shared across customers and do not leave the Webex Contact Center cloud. Source: [Cisco Webex AI Quality Management AI Transparency Technical Note](https://trustportal.cisco.com/c/dam/r/ctp/docs/transparency/cisco-webex-ai-quality-management-ai-transparency-technical-note.pdf), Model Architecture. Checked 2026-09-05.
[^13]: The AWS Bedrock large language model calls in the WFO enhancement pipeline are described as stateless and as not using or storing customer data for model improvement. Source: [Contact Center: Webex Workforce Optimization Enhancements - AI Transparency Technical Note](https://trustportal.cisco.com/c/dam/r/ctp/docs/transparency/ai-transparency-webex-workforce-optimization-technical-note.pdf), data flow description. Checked 2026-09-05.
[^14]: In 5 of the 8 Webex AI Agent regions - Canada, Japan, Australia and New Zealand, Singapore and India - the Azure OpenAI inference column reads Global, which the table's own footnote defines as processing in any data centre worldwide where the models are hosted. Source: [Cisco Webex AI Agent AI Transparency Technical Note](https://trustportal.cisco.com/c/dam/r/ctp/docs/white-paper/collaboration/ai-transparency-webex-ai-agent-technical-note.pdf), section 3 Data Locality table, Azure Open AI column and the asterisk footnote below it. Checked 2026-09-05.
[^15]: Of the 8 Webex AI Agent regions, only London and Frankfurt are pinned outright (not marked Global) for Azure OpenAI inference, while the United States region reads US Regional plus Global. Source: [Cisco Webex AI Agent AI Transparency Technical Note](https://trustportal.cisco.com/c/dam/r/ctp/docs/white-paper/collaboration/ai-transparency-webex-ai-agent-technical-note.pdf), section 3 Data Locality table, Azure Open AI column and the asterisk footnote below it. Checked 2026-09-05.
[^16]: The Webex AI Agent note publishes a data locality table for 8 named regional deployments: produs1, prodeu1, prodeu2, prodca1, prodjp1, prodanz1, prodsg1 and prodin1. Source: [Cisco Webex AI Agent AI Transparency Technical Note](https://trustportal.cisco.com/c/dam/r/ctp/docs/white-paper/collaboration/ai-transparency-webex-ai-agent-technical-note.pdf), section 3 Data Locality for AI Agents Components table, deployment column. Checked 2026-09-05.
[^17]: For the India Webex AI Agent region the internal model proxy is located in Sydney Australia while the cloud and speech components for the same region are in Mumbai and Central India. Source: [Cisco Webex AI Agent AI Transparency Technical Note](https://trustportal.cisco.com/c/dam/r/ctp/docs/white-paper/collaboration/ai-transparency-webex-ai-agent-technical-note.pdf), section 3 Data Locality table, prodin1 row. Checked 2026-09-05.
[^18]: For the Singapore Webex AI Agent region the internal model proxy is located in Singapore while the Azure OpenAI inference for the same region is marked as processable in any data centre globally. Source: [Cisco Webex AI Agent AI Transparency Technical Note](https://trustportal.cisco.com/c/dam/r/ctp/docs/white-paper/collaboration/ai-transparency-webex-ai-agent-technical-note.pdf), section 3 Data Locality table, prodsg1 row, LLM Proxy and Azure Open AI columns. Checked 2026-09-05.
[^19]: Cisco states that for European Union customers and for India customers, Topic Analytics transcription and analysis are processed locally within those regions, and that other global customers' data is processed in the relevant United States European Union and Asia Pacific Japan and China regions. Source: [Cisco Contact Center Topic Analysis AI Transparency Technical Note](https://trustportal.cisco.com/c/dam/r/ctp/docs/transparency/ai-transparency-topic-analysis-technical-note.pdf), Data Sources for Training and Evaluation. Checked 2026-09-05.
[^20]: The audit cluster in India retains administrator activities for 3 years and other audit clusters retain them for 1 year. Source: [Review activity logs in Control Hub for Webex Contact Center](https://help.webex.com/en-us/article/hi3lqs/Review-activity-logs-in-Control-Hub-for-Webex-Contact-Center), Audit administrator activity section. Checked 2026-09-05.
[^21]: Although the India audit cluster retains administrator activities for 3 years, the search interface only offers a date range of up to 1 year, with no documented route to reach the remaining 2 years of retained data. Source: [Review activity logs in Control Hub for Webex Contact Center](https://help.webex.com/en-us/article/hi3lqs/Review-activity-logs-in-Control-Hub-for-Webex-Contact-Center), Audit administrator activity section. Checked 2026-09-05.
[^22]: Cisco states that media quality metrics are not currently supported for customers based in India and that support is planned for a later date. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Limitations, final bullet. Checked 2026-09-05.
[^23]: Webex audit log retention is 12 months in most regions and 3 years in India. Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), Overview section, bulleted list. Checked 2026-09-05.
[^24]: A Webex Contact Center tenant whose Country of Operation is Brazil is provisioned in the United States data centre; the article publishes no South American data centre. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), United States data center table, Brazil row. Checked 2026-09-05.
[^25]: Cisco states that Webex Calling data centre assignment is independent of the data centre assignment for common Webex services. Source: [Webex Calling Data Centers in the EMEA region](https://help.webex.com/en-us/article/np2csyb/Webex-Calling-Data-Center-in-the-European-Union), penultimate body paragraph. Checked 2026-09-05.
[^26]: The Webex Calling data centre location article explicitly excludes Webex Calling Dedicated Instance from its scope. Source: [Data Center locations for Webex Calling](https://help.webex.com/en-us/article/n70gvam/Data-Center-locations-for-Webex-Calling), closing note. Checked 2026-09-05.
[^27]: The Webex Calling data centre article names 16 data centre cities across 4 geographies: Chicago Dallas Vancouver and Toronto in North America; Amsterdam Frankfurt Manchester and London in Europe; Melbourne Sydney Osaka Tokyo Chennai and Mumbai in Asia Pacific; and Jeddah and Riyadh in the Middle East and Africa. Source: [Data Center locations for Webex Calling](https://help.webex.com/en-us/article/n70gvam/Data-Center-locations-for-Webex-Calling), Webex Calling Data centers table, all rows. Checked 2026-09-05.
[^28]: Webex Calling divides EMEA into 3 region identifiers with distinct data centre pairs: EU served from London and Frankfurt, EUN served from Frankfurt and Amsterdam, and UK served from London and Manchester. Source: [Webex Calling Data Centers in the EMEA region](https://help.webex.com/en-us/article/np2csyb/Webex-Calling-Data-Center-in-the-European-Union), Identifier and DC Locations table. Checked 2026-09-05.
[^29]: The first Webex Calling location created in Control Hub becomes the organisation's Calling region. Source: [Data Center locations for Webex Calling](https://help.webex.com/en-us/article/n70gvam/Data-Center-locations-for-Webex-Calling), body text preceding the data centre table. Checked 2026-09-05.
[^30]: New Webex Calling customers headquartered in Middle Eastern and African countries are assigned to the EUN region (disputed). Source: [Webex Calling Data Centers in the EMEA region](https://help.webex.com/en-us/article/np2csyb/Webex-Calling-Data-Center-in-the-European-Union), Headquarters Location and Webex Calling region assignment table. Checked 2026-09-05.
[^31]: The Webex Calling data centre article lists a Middle East and Africa geography served by data centres in Jeddah and Riyadh in Saudi Arabia (disputed). Source: [Data Center locations for Webex Calling](https://help.webex.com/en-us/article/n70gvam/Data-Center-locations-for-Webex-Calling), Webex Calling Data centers table, Middle East and Africa rows. Checked 2026-09-05.
[^32]: Webex Calling publishes a separate list of media points of presence in addition to its data centres, naming Los Angeles New Jersey Dallas Singapore Seoul Sao Paulo Cape Town and the United Arab Emirates. Source: [Data Center locations for Webex Calling](https://help.webex.com/en-us/article/n70gvam/Data-Center-locations-for-Webex-Calling), Additional Webex Calling Media PoP table. Checked 2026-09-05.
[^33]: Cisco states that a customer's Webex Calling region cannot be changed once assigned. Source: [Webex Calling Data Centers in the EMEA region](https://help.webex.com/en-us/article/np2csyb/Webex-Calling-Data-Center-in-the-European-Union), paragraph following the region identifier table. Checked 2026-09-05.
[^34]: Kazakhstan Kyrgyzstan Tajikistan Turkmenistan and Uzbekistan all map to the United Kingdom data centre. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), United Kingdom data center table, Central Asian country rows. Checked 2026-09-05.
[^35]: Chat data location is not governed by the Contact Center data locality mapping; the article refers the reader to the Webex data residency article for it. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), sentence immediately following the five data class list. Checked 2026-09-05.
[^36]: Cisco states the tenant is created in the data centre closest to the selected country and does not define what closest means or publish any tie-break rule. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), paragraph immediately before the country tables. Checked 2026-09-05.
[^37]: The country lists published for the 8 data centres contain 28 countries for the United States, 2 for Canada, 68 for the United Kingdom, 29 for Germany, 23 for Singapore, 7 for Australia, 1 for Japan and 1 for India. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), row counts of the eight per-data-centre tables. Checked 2026-09-05.
[^38]: The authoritative list of which countries can be selected as a Country of Operation is the Geographic Terms and Restrictions section of the Cisco Collaboration Flex Plan Contact Center Offer Description, not this article. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), introduction, second paragraph. Checked 2026-09-05.
[^39]: Adding a domain to the Webex Contact Center content security policy allowed list takes 10 minutes to take effect for an Agent Desktop embedded in an iframe. Source: [Set up security for Webex Contact Center](https://help.webex.com/en-us/article/3srgv1), Set up content security policy section. Checked 2026-09-05.
[^40]: A Webex Contact Center tenant's data centre is determined by the Country of Operation selected in the Contact Center tab of the Set-Up wizard. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), introduction, first paragraph. Checked 2026-09-05.
[^41]: Webex Contact Center tenants are provisioned into 1 of exactly 8 data centres: United States, Canada, United Kingdom, Germany, Singapore, Australia, Japan and India. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), the eight per-data-centre tables, header cell of each. Checked 2026-09-05.
[^42]: 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. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), list following the country tables. Checked 2026-09-05.
[^43]: Georgia maps to the Germany data centre while its neighbours Armenia and Azerbaijan map to the United Kingdom data centre. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), Germany data center table Georgia row; United Kingdom data center table Armenia and Azerbaijan rows. Checked 2026-09-05.
[^44]: Cisco does not publish inbound destination IP addresses for Webex Contact Center because inbound traffic passes through load balancers with dynamic addresses. Source: [Set up security for Webex Contact Center](https://help.webex.com/en-us/article/3srgv1), Source IP Addresses section, introductory paragraph. Checked 2026-09-05.
[^45]: Administrator activity records for Webex Calling and Contact Center events originating from India are stored in data centres located in India. Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), Administrator activity data residency section. Checked 2026-09-05.
[^46]: The Webex Meetings locality article distinguishes internet points of presence from data centres and lists them separately with a smaller set of locations. Source: [Where are the Webex Data Centers and iPOP Locations?](https://help.webex.com/en-us/article/WBX28754/Where-are-the-Webex-Data-Centers-and-iPOP-Locations), Data Centers table and IPOP table. Checked 2026-09-05.
[^47]: The Japan and India data centres each serve exactly 1 Country of Operation, their own. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), Japan data center and India data center tables. Checked 2026-09-05.
[^48]: The article does not state whether a Webex Contact Center tenant's data centre assignment can be changed after set-up (inferred). Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), whole article; no section addresses reassignment. Checked 2026-09-05.
[^49]: Sensitive data masking applies to the Agent Desktop only and does not apply to Supervisor Desktop users. Source: [Set up security for Webex Contact Center](https://help.webex.com/en-us/article/3srgv1), Manage sensitive data section, final sentence. Checked 2026-09-05.
[^50]: Sensitive data masking on the Agent Desktop is a user interface control only; Cisco states the data is not encrypted in the backend and that network traffic and console logs still contain the personal information. Source: [Set up security for Webex Contact Center](https://help.webex.com/en-us/article/3srgv1), Manage sensitive data section. Checked 2026-09-05.
[^51]: Webex Meetings billing data is stored in Texas and North Carolina in the United States and Webex analytics data in California and Texas. Source: [Where are the Webex Data Centers and iPOP Locations?](https://help.webex.com/en-us/article/WBX28754/Where-are-the-Webex-Data-Centers-and-iPOP-Locations), paragraph following the iPOP table. Checked 2026-09-05.
[^52]: Cisco states that for free Webex Meetings user accounts the data may be stored in a data centre outside the account holder's region. Source: [Where are the Webex Data Centers and iPOP Locations?](https://help.webex.com/en-us/article/WBX28754/Where-are-the-Webex-Data-Centers-and-iPOP-Locations), paragraph following the iPOP table. Checked 2026-09-05.
[^53]: Cisco attaches its own staleness warning to the Webex Meetings data centre list, stating the locations may change from time to time. Source: [Where are the Webex Data Centers and iPOP Locations?](https://help.webex.com/en-us/article/WBX28754/Where-are-the-Webex-Data-Centers-and-iPOP-Locations), Note preceding the closing cross-reference. Checked 2026-09-05.
[^54]: Cisco states that Webex Meetings user-generated information is stored in the data centre closest to the user's location or as provided during the ordering process, with no mention of time zone (disputed). Source: [Where are the Webex Data Centers and iPOP Locations?](https://help.webex.com/en-us/article/WBX28754/Where-are-the-Webex-Data-Centers-and-iPOP-Locations), paragraph following the iPOP table. Checked 2026-09-05.
[^55]: Cisco states that Webex 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 a European Union time zone (disputed). Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), Meetings Data residency section. Checked 2026-09-05.
[^56]: Webex Messaging is resident in fewer regions than Webex Contact Center on the same residency table. Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), data residency table, Webex Messaging row. Checked 2026-09-05.
[^57]: A Webex Contact Center tenant whose Country of Operation is Monaco is provisioned in the United Kingdom data centre rather than the Germany data centre that serves France. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), United Kingdom data center table, Monaco row. Checked 2026-09-05.
[^58]: Every African country listed in the article maps to the United Kingdom data centre; no African data centre exists for Webex Contact Center. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), United Kingdom data center table, African country rows. Checked 2026-09-05.
[^59]: None of the 7 data locality sources read in this tranche carries an unfilled authoring placeholder or other template artefact (inferred). Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), full-text scan of all seven extracted bodies. Checked 2026-09-05.
[^60]: Norway and Ukraine both map to the Germany data centre, so that table is an operational grouping and not a list of European Union member states. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), Germany data center table, Norway and Ukraine rows. Checked 2026-09-05.
[^61]: The Webex Calling EMEA data centre article is served from a URL whose slug says European Union while the article's own title says EMEA region. Source: [Webex Calling Data Centers in the EMEA region](https://help.webex.com/en-us/article/np2csyb/Webex-Calling-Data-Center-in-the-European-Union), URL slug against the rendered title element. Checked 2026-09-05.
[^62]: Cisco states that the country selected in the Webex Contact Center ordering flow determines data residency for Webex, referring the reader to the Webex data residency article. Source: [Create a Webex Contact Center Order for a Customer](https://help.webex.com/article/30mv2o/Create-a-Cisco-Webex-Contact-Center-Order-for-a-Customer), numbered step 8. Checked 2026-09-05.
[^63]: The partner ordering article names 2 Webex Contact Center order SKUs, A-CJP and A-FLEX-CC. Source: [Create a Webex Contact Center Order for a Customer](https://help.webex.com/article/30mv2o/Create-a-Cisco-Webex-Contact-Center-Order-for-a-Customer), opening paragraph. Checked 2026-09-05.
[^64]: Pausing a call recording does not stop metadata capture; Cisco states call duration dialled number routing path and other related information are still recorded in the Contact Center database. Source: [Set up security for Webex Contact Center](https://help.webex.com/en-us/article/3srgv1), Handle call recordings section. Checked 2026-09-05.
[^65]: The Webex Contact Center security article publishes no retention period for call recordings or for masked personal information (inferred). Source: [Set up security for Webex Contact Center](https://help.webex.com/en-us/article/3srgv1), Manage sensitive data and Handle call recordings sections. Checked 2026-09-05.
[^66]: Cisco publishes outbound source IP addresses for Webex Contact Center per data centre, for the same 8 data centres named by the data locality article. Source: [Set up security for Webex Contact Center](https://help.webex.com/en-us/article/3srgv1), Source IP Addresses for Webex Contact Center table. Checked 2026-09-05.
[^67]: On the Webex data residency table the Webex Contact Center row is available in 8 of the 10 listed regions - United States European Union Canada United Kingdom Japan Australia Singapore and India - and not in the Saudi Arabia or United Arab Emirates regions. Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), data residency table, Webex Contact Center row. Checked 2026-09-05.
[^68]: Cisco states that migrating an organisation between Webex geographic regions is not currently supported and that an organisation stays in the region it was created in. Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), FAQ: What is the recommendation when selecting a country for the GEO location. Checked 2026-09-05.
[^69]: Cisco references a separate document covering data centre migration plans for legacy customers eligible to move their data to new regional data centres. Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), FAQ: Where can I find out where my data is located. Checked 2026-09-05.
[^70]: Webex suite data residency places identities encryption keys and encrypted user-generated content including meetings messages whiteboards files and their metadata in the organisation's geographic region. Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), Overview section, bulleted list. Checked 2026-09-05.
[^71]: 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 (inferred). Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), Overview and How we determine the data residency region sections. Checked 2026-09-05.
[^72]: The 8 published country lists together name 159 countries; Cisco does not publish that total anywhere in the article (inferred). Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), sum of the row counts of the eight per-data-centre tables. Checked 2026-09-05.
[^73]: Turkey maps to the United Kingdom data centre rather than the Germany data centre. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), United Kingdom data center table, Turkey row. Checked 2026-09-05.
[^74]: Webex Contact Center ordering carries 2 separate country selections: 1 at order creation which sets Webex data residency, and 1 in the Contact Center tab of the Set-Up wizard which sets Contact Center data locality and which defaults to the first but can be changed. Source: [Create a Webex Contact Center Order for a Customer](https://help.webex.com/article/30mv2o/Create-a-Cisco-Webex-Contact-Center-Order-for-a-Customer), numbered step 8. Checked 2026-09-05.
[^75]: A Webex Contact Center tenant whose Country of Operation is the United Arab Emirates is provisioned in the Singapore data centre. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), Singapore data center table, United Arab Emirates row. Checked 2026-09-05.
[^76]: The United Arab Emirates media point of presence entry names only the country while every other entry in both Webex Calling location tables names a city. Source: [Data Center locations for Webex Calling](https://help.webex.com/en-us/article/n70gvam/Data-Center-locations-for-Webex-Calling), Additional Webex Calling Media PoP table, final row. Checked 2026-09-05.
[^77]: The United Kingdom data centre serves more Countries of Operation than any other, covering most of Africa the Middle East the Caucasus Central Asia and the Western Balkans as well as the United Kingdom itself. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), United Kingdom data center table, all rows. Checked 2026-09-05.
[^78]: The United Kingdom data centre serves 68 countries of operation, more than twice as many as the next-largest Webex Contact Center data centre. Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), United Kingdom data center table, all rows. Checked 2026-09-05.
[^79]: The transition guide states that agent desktop masking is visual only and that backend logs and attachments may still contain raw data unless further data loss prevention controls are enforced. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 23, Data Masking and PII Protection. Checked 2026-09-05.
[^80]: Cisco's current data locality article names an India data centre for Webex Contact Center that the March 2026 transition guide's region list omits (disputed). Source: [Data Locality in Webex Contact Center](https://help.webex.com/en-us/article/n0p6xa1/Data-Locality-in-Webex-Contact-Center), the eight per-data-centre tables, India data center table. Checked 2026-09-05.
[^81]: The transition guide gives configurable retention periods as an example, 13 months for call detail records generally and 6 months in the European Union, and states data can be deleted on request or on organisation deletion. Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), page 23, Data Retention and Deletion. Checked 2026-09-05.
[^82]: The transition guide names 7 Webex Contact Center regions - United States, Canada, United Kingdom, Germany, Singapore, Australia and Japan - and states the country of operation chosen at provisioning fixes the data centre (disputed). Source: [Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCE_to_WebexCC.pdf), pages 61 to 63, Region selection and table 20. Checked 2026-09-05.
[^83]: The Unified CCX transition guide names 5 data types Webex Contact Center stores in the cloud: call detail records, connected agent records, agent desktop data, call variables stored by the interactive voice response, and call recordings. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 12, understand security requirements. Checked 2026-09-05.
[^84]: Cisco states that Webex Contact Center call recordings are stored in the cloud for 30 days by default, a value its own revision history records as updated in June 2021. Source: [Contact Center: Transitioning from Unified Contact Center Express to Webex Contact Center Deployment Guide](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CONTACT_CENTER_UnifiedCCX_to_WebexCC.pdf), page 16, determine call recording requirements, and the publication history table. Checked 2026-09-05.
[^85]: The Enterprise disclosure lists 7 data centre locations: Australia, Brazil, Tokyo, the Netherlands, Singapore, the United Kingdom and the United States in Colorado and Texas. Source: [Cisco Webex Contact Center Enterprise Offer Disclosure](https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/cisco-webex-contact-center-enterprise-offer-disclosure.pdf), Table 3 Data Centers. Checked 2026-09-05.
[^86]: Cisco holds a French health data hosting certification for Webex Contact Center provisioned in the European Economic Area and states that customers relying on it must select a region within that area for data storage. Source: [Cisco Webex Contact Center Service Offer Disclosure](https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/webex-contact-center-offer-disclosure.pdf), section 3b Reports and Resources. Checked 2026-09-05.
[^87]: The offer disclosure enumerates 6 circumstances in which cross-border transfers of personal data may still occur despite a data residency selection, including collaboration outside the region, technical support, optional functionality, registration on a Cisco platform, ordering information and mobile push notifications. Source: [Cisco Webex Contact Center Service Offer Disclosure](https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/webex-contact-center-offer-disclosure.pdf), section 2b, paragraph beginning To facilitate certain operations. Checked 2026-09-05.
[^88]: Cisco states that when a subscription is purchased it creates, processes and stores the information in the United States regardless of the regional cloud the accounts are later provisioned in. Source: [Cisco Webex Contact Center Service Offer Disclosure](https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/webex-contact-center-offer-disclosure.pdf), section 2b Storage and Processing, note after the data centre table. Checked 2026-09-05.
[^89]: As of April 2020 Webex Contact Center Enterprise was available in North America, Europe and Australia with Asia planned pending regulatory approvals, and its country and data centre breakdown named no Japan presence at all. Source: [Cisco Collaboration Flex Plan Webex Contact Center Enterprise Add-On Overview](https://www.cisco.com/c/en/us/products/collateral/unified-communications/cisco-collaboration-flex-plan/datasheet-c78-743548.html), Global availability section. Checked 2026-09-05.
[^90]: The September 2025 Webex Contact Center Enterprise offer disclosure lists Tokyo among its data centre locations. Source: [Cisco Webex Contact Center Enterprise Offer Disclosure](https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/cisco-webex-contact-center-enterprise-offer-disclosure.pdf), Table 3 Data Centers. Checked 2026-09-05.
[^91]: The Connect CPaaS server's address varies by the customer's Webex Connect tenant region, with distinct addresses for Canada, Europe, India, Australia and Singapore, on a different domain from every other Webex server. Source: [Connect CPaaS MCP Server](https://developer.webex.com/mcp/docs/connect-mcp-server), server address table. Checked 2026-09-05.