Data residency in Webex

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex

Published

2026-04-02

Updated

unknown

Accessed

2026-09-04

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Claims citing this source

• No Cisco source read for this topic offers a customer-managed encryption key or bring-your-own-key option for contact-centre data; the only key statements describe Cisco-managed keys in a regional Key Management Service and Cisco-managed at-rest encryption. inference in context
• None of the Cisco sources read for this topic mentions FedRAMP, Webex for Government, or any sovereign-cloud offering for contact-centre AI. inference in context
• Cisco does not support migrating an organisation's data between geographic residency locations: once an organisation is created in a given geography it stays there. fact in context
• Cisco states that AI-generated content for meetings and messages is stored in the same data centre as the underlying user-generated content so that all data remains in the same geographic region; the statement names meetings and messages and does not name contact centre. fact in context
• In Cisco's Webex data-centre table, Webex Contact Center is marked as having region-specific data residency in the United States, the European Union, Canada, the United Kingdom, Japan, Australia, Singapore and India, and not in Saudi Arabia or the United Arab Emirates. fact in context
• A Webex Contact Center tenant is created in the data centre closest to the Country of Operation selected in the setup wizard's Contact Center tab, according to a defined country-to-data-centre mapping. fact in context
• Webex audit log retention is 12 months in most regions and 3 years in India. fact in context
• Administrator activity records for Webex Calling and Contact Center events originating from India are stored in data centres located in India. fact in context
• 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 in context
• Webex Messaging is resident in fewer regions than Webex Contact Center on the same residency table. fact in context
• 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. fact in context
• 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. fact in context
• Cisco references a separate document covering data centre migration plans for legacy customers eligible to move their data to new regional data centres. fact in context
• 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. fact in context
• 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. inference in context

Cite this source record

APA

WarmTransfer. (2026, April 2). Data residency in Webex. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-oybc4fb-webex-data-residency

BibTeX

@misc{warmtransfer-cisco-help-oybc4fb-webex-data-residency,
  title  = {Data residency in Webex},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-oybc4fb-webex-data-residency},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-04}
}