During provisioning, the administrator who sets up an organization sees a Country Selector drop-down menu in Control Hub. We determine the geographic region in which the organization's data resides based on the selected country. If your organization and your administrator account are enabled for this EFT, when you create a trial and select a country that maps to the European region, you'll see an additional check box on the trial creation page. The check box sets up the trial as a Phase 2 organization, so that the organization's user-generated content is stored in the region as well as the user identities and encryption keys.

Checking the Phase 2 check box indicates that you (and your customer, if applicable) agree to participate in beta functionality. A race condition can occur if multiple users sign in to the same administrator account and create Phase 2 trials at the same time. For this reason, we do not recommend using shared credentials for this trial.

To determine which region a country maps to, you can download the following Microsoft Excel file and select the country name from the drop-down menu: https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/datalocality/CountryCodeGEOmapping.xlsx (The file begins to download immediately when you access the link.)

The following tables describe how data is shared, processed, and stored in various scenarios for organizations created after Phase 2 release. Because Webex enables collaboration amongst users in multiple organizations, the rules for storage and processing depend in some cases on the type of collaboration, and whether you enable communication with other organizations.

In each table, the following designations are used for data residency:

Global—Data may be handled at a Cisco data center in any location.

Limited—Data resides in the organization's geographic region, but copies may be created or processed in other regions as needed.

Restricted—Data resides in the organization's geographic region.

In addition to sharing, processing, and storage, for each of these activities we use certain data for the purposes of logging and auditing. This data is handled as global and includes some service and user information to help generate business metrics and usage metrics. The data stored and managed in these centralized components is governed by the Cisco Corporate Information Security guidelines, which require strict adherence related to sharing with third parties, retention, and documentation of this data.

Table 1. Control Hub Administration Activities

Scenario	Data Involved	Shared With	Processing	Storage
Create a new customer organization.	Data collected or generated to manage a customer account, including administrative email addresses, organization id, claimed domains associated billing information	Cisco, partner	Global	Global
Use and manage a customer organization; add licensed services.	Operational data such as organization settings, subscription history, product catalog, usage data, analytics, stored CSV files	Cisco, partner, administrators	Global	Global
Create a new user.	Universally unique identifier (UUID)	—	Global	Global

Table 2. Webex User Sign-in and App Configuration

Scenario	Data Involved	Shared With	Processing	Storage
Sign in to user account.	OAuth token	Identity service	Limited	Restricted
	Password	Identity service	Restricted	Restricted
Configure and use the Webex app.	Data such as mobile device ID, device name, IP address; settings such as time zone and locale; personal directory data such as first name, last name, avatar, phone number	Organization and partner administrators	Global	Restricted
	Personal directory data such as first name, last name, avatar, phone number	Other users in the organization, or an external organization in the same region	Restricted	Restricted
		Users from an external organization in a different region*	Limited	Restricted

* Use Control Hub to block communication with external organizations to prevent this scenario. This blocks communication with all external organizations.

Table 3. Webex User Content Generation

Scenario	Data Involved	Shared With	Processing	Storage
Send a message or file, create a space, flag messages.	User-generated content	Compliance officers	Restricted	Restricted (based on space owner's region—see Space Ownership and Content Storage Region in Phase 2)
		Other users in the organization, or an external organization in the same region	Restricted	Restricted
		Users from an external organization in a different region*	Limited	Limited
	Encryption keys	Other users in the organization, or an external organization in the same region	Restricted	Restricted
		Users from an external organization in a different region*	Limited	Restricted (keys are not stored outside the region)
	Search indexes and derived metadata required to operate the service without "leaking" user-generated content or personally identifiable information outside of the region.	—	Limited	Limited
Share real-time media.	Voice, video, content share	Other users in the organization, or an external organization in the same region	Restricted	Restricted
		Users from an external organization in a different region	Limited	Limited
Record a meeting.	Meeting recordings stored in Webex Meetings	—	Restricted (meeting host's region)	Restricted (meeting host's region)
Create a whiteboard.	Whiteboard content (whiteboards between organizations are co-owned)	Other users in the organization, or an external organization in the same region	Restricted	Restricted
		Users from an external organization in a different region*	Limited	Limited

* Use Control Hub to block communication with external organizations to prevent this scenario. This blocks communication with all external organizations.

Table 4. Service Integrations

Entity	Data Involved	Shared With	Processing	Storage
Calendar environment integration	Calendar meetings and events, some personally identifiable information	Membership of all spaces (within the user's organization)	Limited	Limited
Developer APIs	API services for developers – transparent look-up and re-direct to the appropriate region's services.	Global look-up In-region processing	Depends on the rules of the content (as listed in previous tables) and the APIs supporting it	Depends on the rules of the content (as listed in previous tables) and the APIs supporting it

We store content in the region of the organization that owns the space where the content appears. Ownership depends on the type of space:

• Group space—The owner is generally the organization of the person who created the space. We store content in the region of the owner organization.

• Space within a team—The organization of the person who created the team owns spaces created within the team. Spaces created outside of the team and then moved into the team retain their original ownership. We store content in the region of the space owner organization.

• Conversation between two people (nongroup space)—If the people are in different organizations, each organization owns the content that its user posts. If the conversation includes a user from the North America/RoW GEO, we store the conversation content in the North America/RoW GEO.

• Space created by a bot—We assign ownership to the organization of the first nonbot participant, and store the content in the region of the owner organization.

  Bots aren’t currently expected to work for spaces that are owned by or have members from phase 2 EMEAR organizations. We expect to deliver this feature later.