Data Processing Addendum

This Cameyo Data Processing Addendum (including its appendices, the “Addendum”) is incorporated into the Agreement(s) (as defined below) between Google and the Customer.

1. Overview

This Addendum describes the parties’ obligations, including under applicable privacy, data security, and data protection laws, with respect to the processing and security of Customer Data (as defined below). This Addendum will be effective on the Addendum Effective Date (as defined below), and will replace any terms previously applicable to the Services and/or Software. After the Addendum Effective Date, Google may provide an updated URL in place of any URL in this Addendum. Capitalized terms used but not defined in this Addendum have the meaning given to them in the Agreement.
2. Definitions
1. 2.1 In this Addendum:
  - “Addendum Effective Date” means the date on which Customer accepted, or the parties otherwise agreed to, this Addendum.
  - “Agreement” means the contract under which Google has agreed to provide the applicable Services to Customer.
  - “Applicable Privacy Law” means, as applicable to the processing of Customer Personal Data, any national, federal, European Union, state, provincial or other privacy, data security, or data protection law or regulation.
  - “Compliance Certifications” has the meaning given in Section 7.4 (Compliance Certifications).
  - “Cameyo by Google Terms of Service” means the then-current terms of services stated at https://cameyo.google/terms/terms-of-service/ or any successor URL.
  - “Customer Data”, means data provided to Google by Customer or End Users through the Software or the Services, and certain data that Customer or End Users derive from that data through their use of the Services.
  - “Customer Personal Data” means the personal data contained within the Customer Data, including any special categories of personal data or sensitive data defined under Applicable Privacy Law.
  - “Data Incident” means a breach of Google’s security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Data on systems managed by or otherwise controlled by Google, but for clarity excluding any breaches that are connected to hardware or infrastructure that is managed, hosted or operated by, or otherwise the responsibility of, Customer.
  - “EMEA” means Europe, the Middle East and Africa.
  - “EU GDPR” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.
  - “European Data Protection Law” means, as applicable: (a) the GDPR; or (b) the Swiss FADP.
  - “European Law” means, as applicable: (a) EU or EU Member State law (if the EU GDPR applies to the processing of Customer Personal Data); (b) the law of the UK or a part of the UK (if the UK GDPR applies to the processing of Customer Personal Data); or (c) the law of Switzerland (if the Swiss FADP applies to the processing of Customer Personal Data).
  - “GDPR” means, as applicable: (a) the EU GDPR; or (b) the UK GDPR.
  - “Google’s Third-Party Auditor” means a Google-appointed, qualified and independent third-party auditor, whose then-current identity Google will disclose to Customer.
  - “Instructions” has the meaning given in Section 5.2 (Compliance with Customer’s Instructions).
  - “Notification Email Address” means the email address(es) designated by Customer to receive certain notifications from Google, including the email address(es) provided by Customer in the Admin Console or an Order Form.
  - “Security Measures” has the meaning given in Section 7.1.1 (Google’s Security Measures).
  - “Services” means the applicable Services or Software, each as defined in the Cameyo by Google Terms of Service.
  - “Subprocessor” means a third party authorized as another processor under this Addendum to process Customer Data in order to provide parts of the Services and/or Software and TSS (if applicable).
  - “Supervisory Authority” means, as applicable: (a) a “supervisory authority” as defined in the EU GDPR; or (b) the “Commissioner” as defined in the UK GDPR or the Swiss FADP.
  - “Swiss FADP” means, as applicable, the Federal Act on Data Protection of 19 June 1992 (Switzerland) (with the Ordinance to the Federal Act on Data Protection of 14 June 1993) or the revised Federal Act on Data Protection of 25 September 2020 (Switzerland) (with the Ordinance to the Federal Act on Data Protection of 31 August 2022).
  - “Term” means the period from the Addendum Effective Date until the end of Google’s provision of the Services, including, if applicable, any period during which provision of the Services may be suspended and any post-termination period during which Google may continue providing the Services for transitional purposes.
  - “UK GDPR” means the EU GDPR as amended and incorporated into UK law under the UK European Union (Withdrawal) Act 2018, and applicable secondary legislation made under that Act.
2. 2.2 The terms “personal data”, “data subject”, “processing”, “controller”, and “processor” as used in this Addendum have the meanings given by Applicable Privacy Law or, absent any such meaning or law, by the EU GDPR.
3. 2.3 The terms “data subject”, “controller” and “processor” include “consumer”, “business”, and “service provider”, respectively, as required by Applicable Privacy Law.
3. Duration

Regardless of whether the applicable Agreement has terminated or expired, this Addendum will remain in effect until, and automatically expire when, Customer revokes Google’s access to Customer Data or when Google deletes all Customer Data as described in this Addendum (whichever occurs first).
4. Roles; Legal Compliance
1. 4.1 Roles of Parties. Google is a processor and Customer is a controller or processor, as applicable, of Customer Personal Data.
2. 4.2 Processing Summary. The subject matter and details of the processing of Customer Personal Data are described in Appendix 1 (Subject Matter and Details of Data Processing).
3. 4.3 Compliance with Law. Each party will comply with its obligations related to the processing of Customer Personal Data under Applicable Privacy Law.
4. 4.4 Additional Legal Terms. To the extent the processing of Customer Personal Data is subject to an Applicable Privacy Law described in Appendix 3 (Specific Privacy Laws), the corresponding terms in Appendix 3 will apply in addition to the terms in the body of this Addendum and prevail as described in Section 14.1 (Precedence).
5. Data Processing
1. 5.1 Processor Customers. If Customer is a processor:
  1. a. Customer warrants on an ongoing basis that the relevant third-party controller has authorized:
    1. i. the Instructions;
    2. ii. Customer’s engagement of Google as another processor; and.
    3. iii. Google’s engagement of Subprocessors as described in Section 11 (Subprocessors);
    b. Customer will forward to the third-party controller promptly and without undue delay any notice provided by Google under Section 7.2.1 (Incident Notification), 9.2.1 (Responsibility for Requests), or 11.4 (Opportunity to Object to Subprocessors); and
    1. c. Customer may make available to the third-party controller any other information made available by Google under this Addendum about the locations of Google data centers or the names, locations and activities of Subprocessors.
2. 5.2 Compliance with Customer’s Instructions. Customer instructs Google to process Customer Data in accordance with the applicable Agreement (including this Addendum) only as follows:
  1. a. to provide, secure, and monitor the Services and TSS (if applicable); and
  2. b. as further specified via:
    1. i. Customer’s use of the Services (including via the Admin Console) and TSS (if applicable); and
    2. ii. any other written instructions given by Customer and acknowledged by Google as constituting instructions under this Addendum
  (collectively, the “Instructions”).
  
  Google will comply with the Instructions unless prohibited by European Law, where European Data Protection Law applies, or prohibited by applicable law, where any other Applicable Privacy Law applies.
6. Data Deletion
1. 6.1 Deletion by Customer. Google will enable Customer to delete Customer Data during the Term in a manner consistent with the functionality of the Services. If Customer uses the Services to delete any Customer Data during the Term and that Customer Data cannot be recovered by Customer, this use will constitute an Instruction to Google to delete the relevant Customer Data from Google’s systems. Google will comply with this Instruction as soon as reasonably practicable and within a maximum period of 180 days, unless European Law requires storage, where European Data Protection Law applies, or applicable law requires storage, where any other Applicable Privacy Law applies.
2. 6.2 Return or Deletion When Term Ends. If Customer wishes to retain any Customer Data after the end of the Term, it may instruct Google in accordance with Section 9.1 (Access; Rectification; Restricted Processing; Portability) to return that data during the Term. Subject to Section 6.3 (Deferred Deletion Instruction), Customer instructs Google to delete all remaining Customer Data (including existing copies) from Google’s systems at the end of the Term.
3. 6.3. Deferred Deletion Instruction. To the extent any Customer Data covered by the deletion instruction described in Section 6.2 (Return or Deletion When Term Ends) is also processed, when the applicable Term under Section 6.2 expires, in relation to an Agreement with a continuing Term, such deletion instruction will take effect with respect to such Customer Data only when the continuing Term expires. For clarity, this Addendum will continue to apply to such Customer Data until its deletion by Google.
7. Data Security
1. 7.1 Google’s Security Measures, Controls and Assistance.
  1. 7.1.1 Google’s Security Measures. Google will implement and maintain technical, organizational, and physical measures to protect Customer Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure or access as described in Appendix 2 (Security Measures) (the “Security Measures”). Google may update the Security Measures from time to time provided that such updates do not result in a material reduction of the security of the Services.
  2. 7.1.2 Access and Compliance. Google will:
    1. a. authorize its employees, contractors and Subprocessors to access Customer Data only as strictly necessary to comply with Instructions;
    2. b. take appropriate steps to ensure compliance with the Security Measures by its employees, contractors and Subprocessors to the extent applicable to their scope of performance; and
    3. c. ensure that all persons authorized to process Customer Data are under an obligation of confidentiality.
  3. 7.1.4 Google’s Security Assistance. Google will (taking into account the nature of the processing of Customer Personal Data and the information available to Google) assist Customer in ensuring compliance with its (or, where Customer is a processor, the third-party controller’s) obligations relating to security and personal data breaches under Applicable Privacy Law, by:
    1. a. implementing and maintaining the Security Measures in accordance with Section 7.1.1 (Google’s Security Measures);
    2. b. complying with the terms of Section 7.2 (Data Incidents);
    3. c. making the Compliance Certifications available in accordance with Section 7.5.1 (Reviews of Compliance Certifications) and providing the information contained in the applicable Agreement (including this Addendum);
      
      and
    4. d. if subsections (a)-(c) above are insufficient for Customer (or the third-party controller) to comply with such obligations, upon Customer’s request, providing Customer with additional reasonable cooperation and assistance.
2. 7.2 Data Incidents.
  1. 7.2.1 Incident Notification. Google will notify Customer promptly and without undue delay after becoming aware of a Data Incident, and promptly take reasonable steps to minimize harm and secure Customer Data.
  2. 7.2.2 Details of Data Incident. Google’s notification of a Data Incident will describe: the nature of the Data Incident including the Customer resources impacted; the measures Google has taken, or plans to take, to address the Data Incident and mitigate its potential risk; the measures, if any, Google recommends that Customer take to address the Data Incident; and details of a contact point where more information can be obtained. If it is not possible to provide all such information at the same time, Google’s initial notification will contain the information then available and further information will be provided without undue delay as it becomes available.
  3. 7.2.3 No Assessment of Customer Data by Google. Google has no obligation to assess Customer Data in order to identify information subject to any specific legal requirements.
  4. 7.2.4 No Acknowledgement of Fault by Google. Google’s notification of or response to a Data Incident under this Section 7.2 (Data Incidents) will not be construed as an acknowledgement by Google of any fault or liability with respect to the Data Incident.
3. 7.3 Customer’s Security Responsibilities and Assessment.
  1. 7.3.1 Customer’s Security Responsibilities. Without prejudice to Google’s obligations under Sections 7.1 (Google’s Security Measures) and 7.2 (Data Incidents), and elsewhere in the applicable Agreement, Customer is responsible for its use of the Services and Software and its storage of any copies of Customer Data outside Google’s or Google’s Subprocessors’ systems, including:
    1. a. using the Services and/or Software to ensure a level of security appropriate to the risk to the Customer Data;
    2. b. securing the account authentication credentials, systems and devices Customer uses to access the Services and/or Software; and
    3. c. retaining copies of its Customer Data as appropriate.
  2. 7.3.2 Customer’s Security Assessment. Customer agrees that the Services, Security Measures, and Google’s commitments under this Section 7 (Data Security) provide a level of security appropriate to the risk to Customer Data (taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing of Customer Data as well as the risks to individuals).
4. 7.4 Compliance Certifications. Google will maintain the following for the Services, certificates for ISO 27001 (the “Compliance Certifications”) to verify the continued effectiveness of the Security Measures. Google may add standards at any time. Google may replace a Compliance Certification with an equivalent or enhanced alternative.
5. 7.5 Reviews and Audits of Compliance.
  1. 7.5.1 Reviews of Compliance Certifications. To demonstrate compliance by Google with its obligations under this Addendum, Google will make the Compliance Certifications available for review by Customer.
  2. 7.5.2 Customer’s Audit Rights.
    1. a. Customer Audit. Google will, if required under Applicable Privacy Law, allow Customer or an independent auditor appointed by Customer to conduct audits (including inspections) to verify Google’s compliance with its obligations under this Addendum in accordance with Section 7.5.3 (Additional Business Terms for Reviews and Audits). During an audit, Google will reasonably cooperate with Customer or its auditor as described in this Section 7.5 (Reviews and Audits of Compliance).
    2. b. Customer Independent Review. Customer may conduct an audit to verify Google’s compliance with its obligations under this Addendum by reviewing the Compliance Certifications (which reflects the outcome of audits conducted by Google’s Third-Party Auditor).
  3. 7.5.3 Additional Business Terms for Reviews and Audits.
    1. a. Customer must contact Google’s Data Protection Team to request an audit under Section 7.5.2(a) (Customer Audit).
    2. b. Following a Customer request under Section 7.5.3(a), Google and Customer will discuss and agree in advance on the reasonable start date, scope and duration of and security and confidentiality controls applicable to any audit under Section 7.5.2(a) (Customer Audit).
    3. c. Google may charge a fee (based on Google’s reasonable costs) for any audit under Section 7.5.2(a) (Customer Audit). Google will provide Customer with further details of any applicable fee, and the basis of its calculation, in advance of any such audit. Customer will be responsible for any fees charged by any auditor appointed by Customer to execute any such audit.
    4. d. Google may object in writing to an auditor appointed by Customer to conduct any audit under Section 7.5.2(a) (Customer Audit) if the auditor is, in Google’s reasonable opinion, not suitably qualified or independent, a competitor of Google, or otherwise manifestly unsuitable. Any such objection by Google will require Customer to appoint another auditor or conduct the audit itself.
    5. e. Any Customer requests under Appendix 3 (Specific Privacy Laws) will also be subject to this Section 7.5.3 (Additional Business Terms for Reviews and Audits).
8. Impact Assessments and Consultations
1. Taking into account the nature of processing and the information available to Google, Google will, with respect to the Customer Data processed by Google, provide reasonable cooperation and assistance to Customer, to comply with its obligations under Applicable Privacy Law.
9. Access; Data Subject Rights
1. 9.1 Access; Rectification; Restricted Processing; Portability. During the Term, Google will enable Customer, in a manner consistent with the functionality of the Services, to access and rectify Customer Data, including via the deletion functionality provided by Google as described in Section 6.1 (Deletion by Customer), and to export Customer Data. If Customer becomes aware that any Customer Personal Data is inaccurate or outdated, Customer will be responsible for using such functionality to rectify or delete that data if required by Applicable Privacy Law.
2. 9.2 Data Subject Requests.
  1. 9.2.1 Responsibility for Requests. During the Term, if Google’s Data Protection Team receives a request from a data subject that relates to Customer Personal Data and identifies Customer, Google will:
    1. a. advise the data subject to submit their request to Customer;
    2. b. promptly notify Customer; and
    3. c. not otherwise respond to that data subject’s request without authorization from Customer.
      
      Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Services.
  2. 9.2.2 Google’s Data Subject Request Assistance. Google will (taking into account the nature of the processing of Customer Personal Data) assist Customer in fulfilling its (or, where Customer is a processor, the third-party controller’s) obligations under Applicable Privacy Law to respond to requests for exercising the data subject’s rights by:
    1. a. complying with Sections 9.1 (Access; Rectification; Restricted Processing; Portability) and 9.2.1 (Responsibility for Requests); and
    2. b. if subsection (a) above is insufficient for Customer (or the third-party controller) to comply with such obligations, upon Customer’s request, providing Customer with additional reasonable cooperation and assistance.
10. Data Processing Locations
1. 10.1 Data Storage and Processing Facilities. Subject to Google’s data transfer commitments under Appendix 3 (Specific Privacy Laws), if applicable, Customer Data may be processed in any country where Google or its Subprocessors maintain facilities.
11. Subprocessors
1. 11.1 Consent to Subprocessor Engagement. Customer specifically authorizes Google’s engagement as Subprocessors of those entities disclosed as described in Section 11.2 (Information about Subprocessors) as of the Addendum Effective Date. In addition, without prejudice to Section 11.4 (Opportunity to Object to Subprocessors), Customer generally authorizes Google’s engagement of other third parties as Subprocessors (“New Subprocessors”).
2. 11.2 Information about Subprocessors. Names, locations, and activities of then-current Subprocessors are stated at https://www.google.com/chrome/terms/subprocessors.html or such successor URL as Google may designate from time to time, where: (i) any references to the “Chrome Enterprise Services” shall mean and include the Services, as defined herein; and (ii) the subprocessors referred to therein for the “Chrome Enterprise Services” shall mean and constitute the Subprocessors, as defined herein.
3. 11.3 Requirements for Subprocessor Engagement. When engaging any Subprocessor, Google will:
  1. a. ensure via a written contract that:
    1. i. the Subprocessor only accesses and uses Customer Data to the extent required to perform the obligations subcontracted to it, and does so in accordance with the applicable Agreement (including this Addendum); and
    2. ii. if required under Applicable Privacy Laws, the data protection obligations described in this Addendum are imposed on the Subprocessor (as may be further described in Appendix 3 (Specific Privacy Laws)); and
  2. b. remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor.
4. 11.4 Opportunity to Object to Subprocessors.
  1. a. When Google engages any New Subprocessor during the Term, Google will, at least 30 days before the New Subprocessor starts processing any Customer Data, notify Customer of the engagement (including the name, location and activities of the New Subprocessor).
  2. b. Customer may, within 90 days after being notified of the engagement of a New Subprocessor, object by immediately terminating the applicable Agreement for convenience:
    1. i. in accordance with that Agreement's termination for convenience provision; or
    2. ii. if there is no such provision, by notifying Google.
12. Google Data Protection Team; Processing Records
1. 12.1 Google Data Protection Team. Google’s Data Protection Team will provide prompt and reasonable assistance with any Customer queries related to processing of Customer Data under the applicable Agreement at https://support.google.com/a/answer/1047213?hl=en (or any successor URL); and/or by Customer providing a notice to Google as described in the Notices section of the applicable Agreement.
2. 12.2 Google’s Processing Records. Google will keep appropriate documentation of its processing activities as required by Applicable Privacy Law. To the extent any Applicable Privacy Law requires Google to collect and maintain records of certain information relating to Customer, Customer will use the Admin Console or other means consistent with the functionality of the Services to supply such information and keep it accurate and up-to-date. Google may make any such information available to competent regulators, including a Supervisory Authority, if required by Applicable Privacy Law.
3. 12.3 Controller Requests. During the Term, if Google’s Data Protection Team receives a request or instruction from a third party purporting to be a controller of Customer Personal Data, Google will advise the third party to contact Customer.
13. Notices
1. Notices under this Addendum (including notifications of any Data Incidents) will be delivered to the Notification Email Address. Customer is responsible for using the Admin Console, or otherwise notifying Google, to ensure that its Notification Email Address remains current and valid.
14. Interpretation
1. 14.1 Precedence. To the extent of any conflict between:
  1. a. Appendix 3 (Specific Privacy Laws) and the remainder of the Addendum, Appendix 3 will prevail; and
  2. b. this Addendum and the remainder of the Agreement, this Addendum will prevail.
    
    For clarity, if Customer has more than one Agreement, this Addendum will amend each of the Agreements separately.
2. 14.2 Section References. Unless indicated otherwise, section references in any Appendix to this Addendum refer to sections in the body of this Addendum.

Appendix 1

Subject Matter and Details of Data Processing

Subject Matter

Google’s provision of the Services and TSS (if applicable) to Customer.

Duration of the Processing

The Term plus the period from the end of the Term until deletion of all Customer Data by Google in accordance with this Addendum.

Nature and Purpose of the Processing

Google will process Customer Personal Data for the purposes of providing the Services and TSS (if applicable) to Customer in accordance with this Addendum.

Categories of Data

Data relating to individuals provided to Google via the Services, by (or at the direction of) Customer or by its End Users.

Data Subjects

Data subjects include the individuals about whom data is provided to Google via the Services by (or at the direction of) Customer or by its End Users.

Appendix 2

Security Measures
1. (a) Data Centers.
  
  Infrastructure. Google maintains geographically distributed data centers. Google stores all production data in physically secure data centers.
  
  Redundancy. Infrastructure systems have been designed to eliminate single points of failure and minimize the impact of anticipated environmental risks. Dual circuits, switches, networks or other necessary devices help provide this redundancy. The Services are designed to allow Google to perform certain types of preventative and corrective maintenance without interruption. All environmental equipment and facilities have documented preventative maintenance procedures that detail the process for and frequency of performance in accordance with the manufacturer’s or internal specifications. Preventative and corrective maintenance of the data center equipment is scheduled through a standard change process according to documented procedures.
  
  Power. The data center electrical power systems are designed to be redundant and maintainable without impact to continuous operations, 24 hours a day, 7 days a week. In most cases, a primary as well as an alternate power source, each with equal capacity, is provided for critical infrastructure components in the data center. Backup power is provided by various mechanisms such as uninterruptible power supplies (UPS) batteries, which supply consistently reliable power protection during utility brownouts, blackouts, over voltage, under voltage, and out-of-tolerance frequency conditions. If utility power is interrupted, backup power is designed to provide transitory power to the data center, at full capacity, for up to 10 minutes until the backup generator systems take over. The backup generators are capable of automatically starting up within seconds to provide enough emergency electrical power to run the data center at full capacity typically for a period of days.
  
  Server Operating Systems. Google servers use a Linux based implementation customized for the application environment. Data is stored using proprietary algorithms to augment data security and redundancy.
  
  Code Quality. Google employs a code review process to increase the security of the code used to provide the Services and enhance the security products in production environments.
  
  Businesses Continuity. Google has designed and regularly plans and tests its business continuity planning/disaster recovery programs.
2. (b) Networks and Transmission.
  
  Data Transmission. Data centers are typically connected via high-speed private links to provide secure and fast data transfer between data centers. This is designed to prevent data from being read, copied, altered or removed without authorization during electronic transfer or transport or while being recorded onto data storage media. Google transfers data via Internet standard protocols.
  
  External Attack Surface. Google employs multiple layers of network devices and intrusion detection to protect its external attack surface. Google considers potential attack vectors and incorporates appropriate purpose built technologies into external facing systems.
  
  Intrusion Detection. Intrusion detection is intended to provide insight into ongoing attack activities and provide adequate information to respond to incidents. Google’s intrusion detection involves: (i) tightly controlling the size and make-up of Google’s attack surface through preventative measures; (ii) employing intelligent detection controls at data entry points; and (iii) employing technologies that automatically remedy certain dangerous situations.
  
  Incident Response. Google monitors a variety of communication channels for security incidents, and Google’s security personnel will react promptly to known incidents.
  
  Encryption Technologies. Google makes HTTPS encryption (also referred to as SSL or TLS connection) available. Google servers support ephemeral elliptic curve Diffie-Hellman cryptographic key exchange signed with RSA and ECDSA. These perfect forward secrecy (PFS) methods help protect traffic and minimize the impact of a compromised key, or a cryptographic breakthrough.
2. Access and Site Controls
1. (a) Site Controls.
  
  On-site Data Center Security Operation. Google’s data centers maintain an on-site security operation responsible for all physical data center security functions 24 hours a day, 7 days a week. The on-site security operation personnel monitor closed circuit TV (CCTV) cameras and all alarm systems. On-site security operation personnel perform internal and external patrols of the data center regularly.
  
  Data Center Access Procedures. Google maintains formal access procedures for allowing physical access to the data centers. The data centers are housed in facilities that require electronic card key access, with alarms that are linked to the on-site security operation. All entrants to the data center are required to identify themselves as well as show proof of identity to on-site security operations. Only authorized employees, contractors and visitors are allowed entry to the data centers. Only authorized employees and contractors are permitted to request electronic card key access to these facilities. Data center electronic card key access requests must be made through e-mail, and require the approval of the requestor’s manager and the data center director. All other entrants requiring temporary data center access must: (i) obtain approval in advance from the data center managers for the specific data center and internal areas they wish to visit; (ii) sign in at on-site security operations; and (iii) reference an approved data center access record identifying the individual as approved.
  
  On-site Data Center Security Devices. Google’s data centers employ a dual authentication access control system that is linked to a system alarm. The access control system monitors and records each individual’s electronic card key and when they access perimeter doors, shipping and receiving, and other critical areas. Unauthorized activity and failed access attempts are logged by the access control system and investigated, as appropriate. Authorized access throughout the business operations and data centers is restricted based on zones and the individual’s job responsibilities. The fire doors at the data centers are alarmed. CCTV cameras are in operation both inside and outside the data centers. The positioning of the cameras has been designed to cover strategic areas including, among others, the perimeter, doors to the data center building, and shipping/receiving. On-site security operations personnel manage the CCTV monitoring, recording and control equipment. Secure cables throughout the data centers connect the CCTV equipment. Cameras record on site via digital video recorders 24 hours a day, 7 days a week. The surveillance records are retained for up to 30 days based on activity.
2. (b) Access Control.
  
  Infrastructure Security Personnel. Google has, and maintains, a security policy for its personnel, and requires security training as part of the training package for its personnel. Google’s infrastructure security personnel are responsible for the ongoing monitoring of Google’s security infrastructure, the review of the Services, and responding to security incidents.
  
  Access Control and Privilege Management. Customer’s Administrators and End Users must authenticate themselves via a central authentication system or via a single sign on system in order to use the Services.
  
  Internal Data Access Processes and Policies – Access Policy. Google’s internal data access processes and policies are designed to prevent unauthorized persons and systems from gaining access to systems used to process Customer Data. Google designs its systems to (i) only allow authorized persons to access data they are authorized to access; and (ii) ensure that Customer Data cannot be read, copied, altered or removed without authorization during processing, use and after recording. The systems are designed to detect any inappropriate access. Google employs a centralized access management system to control personnel access to production servers, and only provides access to a limited number of authorized personnel. Google’s authentication and authorization systems utilize SSH certificates and security keys, and are designed to provide Google with secure and flexible access mechanisms. These mechanisms are designed to grant only approved access rights to site hosts, logs, data and configuration information. Google requires the use of unique user IDs, strong passwords, two factor authentication and carefully monitored access lists to minimize the potential for unauthorized account use. The granting or modification of access rights is based on: the authorized personnel’s job responsibilities; job duty requirements necessary to perform authorized tasks; and a need to know basis. The granting or modification of access rights must also be in accordance with Google’s internal data access policies and training. Approvals are managed by workflow tools that maintain audit records of all changes. Access to systems is logged to create an audit trail for accountability. Where passwords are employed for authentication (e.g. login to workstations), password policies that follow at least industry standard practices are implemented. These standards include restrictions on password reuse and sufficient password strength. For access to extremely sensitive information (e.g. credit card data), Google uses hardware tokens.
3. Data
1. (a) Data Storage, Isolation and Logging. Google stores data in a multi-tenant environment on Google-owned servers. Subject to any Instructions to the contrary (e.g. in the form of a data location selection), Google replicates Customer Data between multiple geographically dispersed data centers. Google also logically isolates Customer Data. Customer will be given control over specific data sharing policies. Those policies, in accordance with the functionality of the Services, will enable Customer to determine the product sharing settings applicable to its End Users for specific purposes. Customer may choose to use logging functionality that Google makes available via the Services.
2. (b) Decommissioned Disks and Disk Erase Policy. Disks containing data may experience performance issues, errors or hardware failure that lead them to be decommissioned (“Decommissioned Disk”). Every Decommissioned Disk is subject to a series of data destruction processes (the “Disk Erase Policy”) before leaving Google’s premises either for reuse or destruction. Decommissioned Disks are erased in a multi-step process and verified complete by at least two independent validators. The erase results are logged by the Decommissioned Disk’s serial number for tracking. Finally, the erased Decommissioned Disk is released to inventory for reuse and redeployment. If, due to hardware failure, the Decommissioned Disk cannot be erased, it is securely stored until it can be destroyed. Each facility is audited regularly to monitor compliance with the Disk Erase Policy.
4. Personnel Security

Google personnel are required to conduct themselves in a manner consistent with the company’s guidelines regarding confidentiality, business ethics, appropriate usage, and professional standards. Google conducts reasonably appropriate background checks to the extent legally permissible and in accordance with applicable local labor law and statutory regulations.

Google personnel are required to execute a confidentiality agreement and must acknowledge receipt of, and compliance with, Google’s confidentiality and privacy policies. Personnel are provided with security training. Personnel handling Customer Data are required to complete additional requirements appropriate to their role (e.g. certifications). Google’s personnel will not process Customer Data without authorization.
5. Subprocessor Security

Before onboarding Subprocessors, Google conducts an audit of the security and privacy practices of Subprocessors to ensure Subprocessors provide a level of security and privacy appropriate to their access to data and the scope of the services they are engaged to provide. Once Google has assessed the risks presented by the Subprocessor, then subject to the requirements described in Section 11.3 (Requirements for Subprocessor Engagement), the Subprocessor is required to enter into appropriate security, confidentiality and privacy contract terms.

Appendix 3

Specific Privacy Laws

The terms in each subsection of this Appendix 3 apply only where the corresponding law applies to the processing of Customer Personal Data.

European Data Protection Law

1. Additional Definitions.
- “Adequate Country” means:
  1. (a) for data processed subject to the EU GDPR: the European Economic Area, or a country or territory recognized as ensuring adequate protection under the EU GDPR;
  2. (b) for data processed subject to the UK GDPR: the UK, or a country or territory recognized as ensuring adequate protection under the UK GDPR and the Data Protection Act 2018; or
  3. (c) for data processed subject to the Swiss FADP: Switzerland, or a country or territory that is: (i) included in the list of the states whose legislation ensures adequate protection as published by the Swiss Federal Data Protection and Information Commissioner, if applicable; or (ii) recognized as ensuring adequate protection by the Swiss Federal Council under the Swiss FADP;
  in each case, other than on the basis of an optional data protection framework.
- “Alternative Transfer Solution” means a solution, other than SCCs, that enables the lawful transfer of personal data to a third country in accordance with European Data Protection Law, for example a data protection framework recognized as ensuring that participating entities provide adequate protection.
- “Customer SCCs” means the SCCs (Controller-to-Processor), the SCCs (Processor-to-Processor), or the SCCs (Processor-to-Controller), as applicable.
- “SCCs” means the Customer SCCs or SCCs (Processor-to-Processor, Google Exporter), as applicable.
- “SCCs (Controller-to-Processor)” means the terms at: https://cameyo.google/terms/scc/controller-to-processor/
- “SCCs (Processor-to-Controller)” means the terms at: https://cameyo.google/terms/scc/processor-to-controller/
- “SCCs (Processor-to-Processor)” means the terms at: https://cameyo.google/terms/scc/processor-to-processor/
- “SCCs (Processor-to-Processor, Google Exporter)” means the terms at: https://cameyo.google/terms/scc-google-exporter/processor-to-processor/
2. Instruction Notifications. Without prejudice to Google’s obligations under Section 5.2 (Compliance with Customer’s Instructions) or any other rights or obligations of either party under the applicable Agreement, Google will immediately notify Customer if, in Google’s opinion:
1. a. European Law prohibits Google from complying with an Instruction;
2. b. an Instruction does not comply with European Data Protection Law; or
3. c. Google is otherwise unable to comply with an Instruction,
in each case unless such notice is prohibited by European Law.

This Section does not reduce either party’s rights and obligations elsewhere in the Agreement. If Customer is a processor, Customer will immediately forward to the third-party controller any notice provided by Google under this section.
3. Customer’s Audit Rights. Google will allow Customer or an independent auditor appointed by Customer to conduct audits (including inspections) as described in Section 7.5.2(a) (Customer Audit). During such an audit, Google will make available all information necessary to demonstrate compliance with its obligations under this Addendum and contribute to the audit as described in Section 7.5 (Reviews and Audits of Compliance) and this section.
4. Data Transfers.
1. 4.1 Restricted Transfers. The parties acknowledge that European Data Protection Law does not require SCCs or an Alternative Transfer Solution in order for Customer Personal Data to be processed in or transferred to an Adequate Country. If Customer Personal Data is transferred to any other country and European Data Protection Law applies to the transfers (as certified by Customer under Section 4.2 (Certification by Non-EMEA Customers) (“Restricted Transfers”), then:
  1. a. if Google has adopted an Alternative Transfer Solution for any Restricted Transfers, Google will inform Customer of the relevant solution and ensure that such Restricted Transfers are made in accordance with it; or
  2. b. if Google has not adopted an Alternative Transfer Solution for any Restricted Transfers, or informs Customer that Google is no longer adopting, an Alternative Transfer Solution for any Restricted Transfers (without adopting a replacement Alternative Transfer Solution):
    1. i. if Google’s address is in an Adequate Country:
      1. A. the SCCs (Processor-to-Processor, Google Exporter) will apply with respect to such Restricted Transfers from Google to Subprocessors; and
      2. B. in addition, if Customer’s billing address is not in an Adequate Country, the SCCs (Processor-to Controller) will apply (regardless of whether Customer is a controller or processor) with respect to such Restricted Transfers between Google and Customer;
      or
    2. ii. if Google’s address is not in an Adequate Country, the SCCs (Controller-to-Processor) or SCCs (Processor-to-Processor) will apply (according to whether Customer is a controller or processor) with respect to such Restricted Transfers between Google and Customer.
2. 4.2 Information about Restricted Transfers. Google will provide Customer with information relevant to Restricted Transfers, and other supplementary protective measures in relation to Google’s adoption of an Alternative Transfer Solution, at https://cloud.google.com/terms/alternative-transfer-solution .
3. 4.3 SCC Audits. If Customer SCCs apply as described in Section 4.1 (Restricted Transfers) of these European Data Protection Law terms, Google will allow Customer (or an independent auditor appointed by Customer) to conduct audits as described in those SCCs and, during an audit, make available all information required by those SCCs, both in accordance with Section 7.5.3 (Additional Business Terms for Reviews and Audits).
4. 4.4 SCCs and Third-Party Controllers. If Customer is a processor, Customer acknowledges that Google, as another processor, may not be able to identify the third-party controller and, accordingly, Customer will forward to the third-party controller promptly and without undue delay any notice that refers to any SCCs.
5. 4.5 Termination Due to Data Transfer Risk. If Customer concludes, based on its current or intended use of the Services, that appropriate safeguards are not provided for transferred Customer Personal Data, then Customer may immediately terminate the applicable Agreement in accordance with that Agreement's termination for convenience provision or, if there is no such provision, by notifying Google.
6. 4.6 No Modification of SCCs. Nothing in the Agreement (including this Addendum) is intended to modify or contradict any SCCs or prejudice the fundamental rights or freedoms of data subjects under European Data Protection Law.
7. 4.7 Precedence of SCCs. To the extent of any conflict or inconsistency between any Customer SCCs (which are incorporated by reference into this Addendum) and the remainder of the Agreement (including this Addendum), the Customer SCCs will prevail.
5. Requirements for Subprocessor Engagement. European Data Protection Law requires Google to ensure via a written contract that the data protection obligations described in this Addendum, as referred to in Article 28(3) of the GDPR, if applicable, are imposed on any Subprocessor engaged by Google.

CCPA

1. Additional Definitions.
- “CCPA” means the California Consumer Privacy Act of 2018, as amended, including as amended by the California Privacy Rights Act of 2020, together with all implementing regulations.
- “Customer Personal Data” includes “personal information”.
- The terms “business”, “business purpose”, “consumer”, “personal information”, “processing”, “sale”, “sell”, “service provider”, and “share” have the meanings given in the CCPA.
2. Prohibitions. Without prejudice to Google’s obligations under Section 5.2 (Compliance with Customer’s Instructions), with respect to the processing of Customer Personal Data in accordance with the CCPA, Google will not, unless otherwise permitted under the CCPA:
1. a. sell or share Customer Personal Data;
2. b. retain, use or disclose Customer Personal Data:
  1. i. other than for a business purpose under the CCPA on behalf of Customer and for the specific purpose of performing the Services and TSS (if applicable); or
  2. ii. outside of the direct business relationship between Google and Customer; or
3. c. combine or update Customer Personal Data with personal information that Google receives from or on behalf of a third party or collects from its own interactions with the consumer.
3. Compliance. Without prejudice to Google’s obligations under Section 5.2 (Compliance with Customer’s Instructions) or any other rights or obligations of either party under the applicable Agreement, Google will notify Customer if, in Google’s opinion, Google is unable to meet its obligations under the CCPA, unless such notice is prohibited by applicable law.
4. Customer Intervention. If Google notifies Customer of any unauthorized use of Customer Personal Data, including under Section 3 (Compliance) of this subsection or Section 7.2.1 (Incident Notification), Customer may take reasonable and appropriate steps to stop or remediate such unauthorized use by:
1. a. taking any measures recommended by Google pursuant to Section 7.2.2 (Details of Data Incident), if applicable; or
2. b. exercising its rights under Section 7.5.2(a) (Customer Audit) or 9.1 (Access; Rectification; Restricted Processing; Portability).

Turkey

1. Additional Definitions.
- “Turkish Data Protection Law” means the Turkish Law on the Protection of Personal Data No. 6698 dated April 7, 2016.
- “Turkish Personal Data Protection Authority” means the Kişisel Verileri Koruma Kurumu.
- “Turkish SCCs” means standard contract clauses under Turkish Data Protection Law.
2. Data Transfers.
1. 2.1 Supplementary Terms. If Customer’s billing address is in Turkey and Google makes any optional additional terms (including Turkish SCCs) available for acceptance by Customer in relation to transfers of Customer Personal Data under Turkish Data Protection Law, those terms will supplement this Addendum as from the date they are notified to the Turkish Personal Data Protection Authority in accordance with Section 2.2 (Notification to the Competent Authority) below, as evidenced by Customer to Google.
2. 2.2 Notification to the Competent Authority. If Customer enters into Turkish SCCs under this Section 2 (Data Transfers), Customer will be responsible for notifying the Turkish Personal Data Protection Authority of use of Turkish SCCs within five (5) business days of signature of the Turkish SCCs as required by Turkish Data Protection Law.
3. 2.3 SCC Audits. If Customer enters into Turkish SCCs under this Section 2 (Data Transfers), Google will allow Customer (or an independent auditor appointed by Customer) to conduct audits as described in those SCCs and, during an audit, make available all information required by those SCCs, both in accordance with Section 7.5.3 (Additional Business Terms for Reviews and Audits).
4. 2.4 Termination Due to Data Transfer Risk. If Customer concludes, based on its current or intended use of the Services, that appropriate safeguards are not provided for transferred Customer Personal Data, then Customer may immediately terminate the applicable Agreement in accordance with that Agreement's termination for convenience provision or, if there is no such provision, by notifying Google.
5. 2.5 No Modification of Turkish SCCs. Nothing in the Agreement (including this Addendum) is intended to modify or contradict the Turkish SCCs or prejudice the fundamental rights or freedoms of data subjects under Turkish Data Protection Law.
6. 2.6 Precedence of SCCs. To the extent of any conflict or inconsistency between the Turkish SCCs (which will be incorporated by reference into this Addendum if entered into by Customer) and the remainder of the Agreement (including this Addendum), the Turkish SCCs will prevail.

Israel

1. Additional Definition.
- “Israeli Privacy Protection Law” means the Israeli Privacy Protection Law, 1981 and any regulations promulgated thereunder.
2. Equivalent Terms. Any terms equivalent to “controller”, “personal data”, “processing”, and “processor”, as used in this Addendum, have the meanings given in the Israeli Privacy Protection Law.
3. Customer’s Audit Rights. Google will allow Customer or an independent auditor appointed by Customer to conduct audits (including inspections) as described in Section 7.5.2(a) (Customer Audit).