# Webex suite data residency and the GEO model

Canonical: https://warmtransfer.net/knowledge/webex-suite-data-residency

Last verified: 2026-09-16

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[^7]. 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[^5].

## How it works

Under Webex suite data residency, identities, encryption keys, and encrypted user-generated content are placed in the organisation's geographic region[^7]. That user-generated content covers meetings, messages, whiteboards, files, and their metadata[^7].

WarmTransfer's reading of the sources is that Webex suite data residency and [Webex Contact Center data locality](https://warmtransfer.net/knowledge/webex-cc-data-locality) are different systems[^8]. We infer that 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[^8].

Webex audit log retention is 12 months in most regions and 3 years in India[^2].

## Region choice and migration

Cisco states that migrating an organisation between Webex geographic regions is not currently supported[^5]. Cisco also states that an organisation stays in the region it was created in[^5].

Cisco references a separate document covering data centre migration plans for legacy customers eligible to move their data to new regional data centres[^6].

## Webex Meetings placement

Sources disagree on how Webex Meetings data is placed[^4][^3]. This is disputed: in one document, Cisco states that Webex Meetings data is stored in a data centre chosen from the time zone selected for the Meetings site during provisioning, and gives Frankfurt as the result for a European Union time zone[^4]. This is disputed: in another document, 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[^3].

## Source document behaviour

Field reports suggest that the Data residency in Webex article carries a date line reading September 08 2026, which sits inside the text the corpus hashes[^1]. In the field, the article's rendered hash is identical to the value stored when the record was created against a stored date of 2 April 2026[^1].

See also [Document metadata as corpus evidence](https://warmtransfer.net/knowledge/cisco-doc-metadata-as-evidence).

## Applicability

Applies to: Cisco Webex Contact Center, Cisco Webex, and Cisco Webex Meetings. Deployments: cloud. Sources checked 2026-09-16. Audit log retention for India is 3 years rather than the 12 months that applies in most regions[^2].

## What remains uncertain

Sources disagree on whether Webex Meetings placement follows the provisioned time zone or the user's location and ordering details[^4][^3]. Where data at rest sits for each Webex suite service other than Webex Meetings, rather than for the suite as a whole, is not covered by the sources below. What the residency selector offers at organisation creation, and who can see the choice afterwards, is not covered by the sources below. The claims list the content classes that residency places in the organisation's region[^7]. Which data classes never leave a chosen region, and which are excluded from residency entirely, is not covered by the sources below. The claims establish only that Cisco references a legacy migration document[^6]. The contents of that document are not covered by the sources below.

## Sources

[^1]: The Data residency in Webex article carries a date line reading September 08 2026 which sits inside the text the corpus hashes, and its rendered hash is identical to the value stored when the record was created against a stored date of 2 April 2026 (field report). Source: [Data residency in Webex](https://help.webex.com/en-US/article/oybc4fb/Data-Residency-in-Webex), article date line against the source record as held before this tranche. Checked 2026-09-16.
[^2]: 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.
[^3]: 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.
[^4]: 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.
[^5]: 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.
[^6]: 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.
[^7]: 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.
[^8]: 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.