Effective 14 October 2020
See change log

What is a Third-Party Subprocessor:

A subprocessor is a vendor Zoom uses to process data on behalf of our customers, who are the data controllers of that data.

Zoom’s Process for Contracting with Third-Party Subprocessors

Zoom requires its subprocessors to satisfy equivalent obligations as those required from Zoom (as a Data Processor) as outlined in Zoom's Data Processing Agreement (DPA), including but not limited to the requirements to:

  • process personal data following data controller's (i.e., Customer's) documented instructions (as communicated in writing to the relevant subprocessor by Zoom);
  • in connection with the subprocessing activities, use only personnel who are reliable and subject to a contractually binding obligation to observe data privacy and security, to the extent applicable, under applicable data protection laws;
  • promptly inform Zoom about any security breach; and
  • cooperate with Zoom to address requests from data controllers, data subjects, or data protection authorities, as applicable.

Except for as provided below, Zoom owns or controls access to the infrastructure that hosts real-time and stored personal data (should the Customer choose to store such content, e.g., recordings and transcripts). Personal data may be shifted among data centers within a region to ensure Zoom's performance and availability. Zoom also works with the listed service subprocessors below to provide the noted functionality.

The following table describes the countries and legal entities engaged in the processing and storage of personal data by Zoom acting as a data processor on behalf of its customers, the data controllers.

Zoom Third-Party Subprocessors

Zoom Authorized Third-Party Subprocessors

Name

Purpose 

Data Shared with Subprocessor

Location

International Transfer Mechanism 

Additional Safeguards

(links to subprocessor resources)

Amazon Web Services

Cloud Service Provider  

  • Real-time meeting and webinar traffic
  • Meeting and call recordings (if saved to the cloud by Customer
  • Transcriptions of meeting or call recordings (if meeting recorded and saved to the cloud by Customer) 
  • Uploaded files

United States, E.U., Canada, Australia

SCCs

Risk and Compliance whitepaper and AWS Security Center.

Oracle

Cloud Service Provider 

  • Real-time meeting and webinar traffic
  • Meeting and call recordings
  • Transcriptions of meeting or call recordings

United States 

Binding Corporate Rules (BCRs)

Technical Brief Whitepaper

Google Firebase

Send push notifications on Android phones. Customers can choose not to use this service.

  • Chat Message Notification
  • SMS Message Notification
  • PBX (Phone Call) Message Notification

United States

SCCs

Privacy and Security in Firebase

Apple 

Send push notifications on iOS phones. Customers can choose not to use this service.

  • Chat Message Notification
  • SMS Message Notification
  • PBX (Phone Call) Message Notification

United States

SCCs

Apple Push Notification Service Overview

Rocket Science Group, LLC

For webinars. Send notification emails to webinar registrants with Webinar details.


For Zoom meetings. Send "your meeting attendee is waiting” emails.

  • Name
  • email address
  • meeting or webinar subject
  • meeting/webinar ID
  • Meeting date and start time
  • Name of a waiting meeting participant

United States

SCCs

Privacy & Security 



Zendesk

Cloud-based Customer Service Platform

Communications Content such as cloud recordings or in-meeting chat transcripts MAY be shared with Zendesk but only if Customer chooses to provide it directly to a Zoom support agent through a support interaction.

USA 

BCRs

Compliance Certifications and Memberships

Updates

As our business grows and evolves, the Subprocessors we utilize may also change. We will provide the owner of Customer’s account with notice of any new Subprocessors to the extent required under contractual agreement, along with posting such updates here.

You may also use the form below to subscribe to updates.

 

Date of Change 

Change

Notes

14 October 2020

Removed vendors erroneously classified as subprocessors 

Following an internal assessment, we identified some vendors previously listed that did not, in fact, process any customer data for which Zoom is the data processor. For that reason, we removed them.

14  October 2020

Added Apple and Google Firebase for accuracy

Following an internal assessment, we identified the absence of two vendors for mobile phone push notifications. Zoom has always used these vendors for that purpose; they are not new subprocessors.