Android Enterprise Data Processing and Security Terms
Version date: February 2022
The customer agreeing to these terms (“Customer”), and Google LLC (formerly known as Google Inc.), Google Ireland Limited, Google Asia Pacific Pte. Ltd., or any other entity that directly or indirectly controls, is controlled by, or is under common control with Google LLC (as applicable, “Google”), have entered into an agreement found at www.android.com/enterprise/terms (or as otherwise contracted for other Android Enterprise services) under which Google has agreed to provide Android Enterprise services (as described at www.android.com/enterprise) and related technical support to Customer (as amended from time to time, the "Agreement").
These Data Processing and Security Terms, including their appendices (the “Terms”) will be effective and replace any previously applicable data processing and security terms as from the Terms Effective Date (as defined below).
These Terms supplement the Agreement.
These Terms reflect the parties’ agreement with respect to the terms governing the processing and security of Customer Data under the Agreement.
2.1 Capitalized terms used but not defined in these Terms have the meanings set out in the Agreement. In these Terms, unless stated otherwise:
- Additional Security Controls means security resources, features, functionality and/or controls that Customer may use at its option and/or as it determines, including the admin console and other features and/or functionality of the Services such as encryption, logging and monitoring, identity and access management, security scanning, and firewalls.
- Adequate Country means: (a) for data processed subject to the EU GDPR: the EEA, or a country or territory that is the subject of an adequacy decision by the Commission under Article 45(1) of the EU GDPR; (b) for data processed subject to the UK GDPR: the UK or a country or territory that is the subject of the adequacy regulations under Article 45(1) of the UK GDPR and Section 17A of the Data Protection Act 2018; and/or (c) for data processed subject to the Swiss FDPA: Switzerland, or a country or territory that (i) is included in the list of the states whose legislation ensures an adequate level of protection as published by the Swiss Federal Data Protection and Information Commissioner, or (ii) is the subject of an adequacy decision by the Swiss Federal Council under the Swiss FDPA.
- Agreed Liability Cap means the maximum monetary or payment-based amount at which a party’s liability is capped under the Agreement, either per annual period or event giving rise to liability, as applicable.
- Alternative Transfer Solution means a solution, other than SCCs, that enables the lawful transfer of personal data to a third country in accordance with the European Data Protection Legislation.
- Customer Data has the meaning given in the Agreement or, if no such meaning is given, means data provided by or on behalf of Customer or Customer End Users via the Services under the Account.
- Customer End Users means end users utilizing the Service(s).
- Customer Personal Data means the personal data contained within the Customer Data.
- 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. “Data Incidents” will not include unsuccessful attempts or activities that do not compromise the security of Customer Data, including unsuccessful log-in attempts, pings, port scans, denial of service attacks, and other network attacks on firewalls or networked systems.
- EEA means the European Economic Area.
- 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 Legislation means, as applicable: (a) the GDPR; and/or (b) the Federal Data Protection Act of 19 June 1992 (Switzerland).
- European or National Law means, as applicable: (a) EU or EU Member State law (if the EU GDPR applies to the processing of Customer Personal Data); and/or (b) the law of the UK or a part of the UK (if the UK GDPR applies to the processing of Customer Personal Data).
- GDPR means, as applicable: (a) the EU GDPR; and/or (b) the UK GDPR.
- Instructions has the meaning given in Section 5.2 (Customer’s Instructions).
- New Subprocessor has the meaning given in Section 11.1 (Consent to Subprocessor Engagement).
- Non-European Data Protection Legislation means data protection or privacy legislation In force outside the EEA, Switzerland, and the UK.
- Notification Email Address means the email address(es) designated by Customer in the Admin Console, to receive certain notifications from Google.
- “SCCs (EU Controller-to-Processor)” means the terms at business.safety.google/gdprcontrollerterms/sccs/eu-c2p-dpa.
- “SCCs (EU Processor-to-Controller)” means the terms at business.safety.google/gdprprocessorterms/sccs/p2c.
- “SCCs (EU Processor-to-Processor)” means the terms at business.safety.google/gdprprocessorterms/sccs/eu-p2p-dpa.
- “SCCs (EU Processor-to-Processor, Google Exporter)” means the terms at business.safety.google/gdprprocessorterms/sccs/eu-p2p-intra-group.
- “SCCs (UK Controller-to-Processor)” means the terms at business.safety.google/gdprprocessorterms/sccs/uk-c2p-dpa.
- Security Measures has the meaning given in Section 7.1.1 (Google’s Security Measures).
- Subprocessors means third parties authorized under these Terms to have logical access to and process Customer Data in order to provide parts of the Services.
- Term means the period from the Terms 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.
- Terms Effective Date means, as applicable:
- 25 May 2018, if Customer clicked to accept or the parties otherwise agreed to these Terms prior to or on such date; or
- the date on which Customer clicked to accept or the parties otherwise agreed to these Terms, if such date is after 25 May 2018.
- UK GDPR means the EU GDPR as amended and incorporated into UK law under the UK European Union (Withdrawal) Act 2018, if in force.
2.2 The terms “personal data”, “data subject”, “processing”, “controller”, “processor” and “supervisory authority” as used in these Terms have the meanings given in the GDPR, and the terms “data importer” and “data exporter” have the meanings given in the relevant SCCs.
2.3 The terms “including”, “include” or any similar expression will be construed as illustrative and will not limit the sense of the words preceding those terms. Any examples in these Terms are illustrative and not the sole examples of a particular concept.
2.4 Any reference to a legal framework, statute or other legislative enactment is a reference to it as amended or re-enacted from time to time.
2.5 If these Terms are translated into any other language, and there is a discrepancy between the English text and the translated text, the English text will govern.
3. Duration of these Terms
These Terms will take effect on the Terms Effective Date and, notwithstanding expiry of the Term, will remain in effect until, and automatically expire upon, deletion of all Customer Data by Google as described in these Terms.
4. Scope of Data Protection Legislation
4.1 Application of European Legislation. The parties acknowledge and agree that the European Data Protection Legislation will apply to the processing of Customer Personal Data if, for example:
- the processing is carried out in the context of the activities of an establishment of Customer in the territory of the EEA or the UK; and/or
- the Customer Personal Data is personal data relating to data subjects who are in the EEA or the UK and the processing relates to the offering to them of goods or services in the EEA or the UK or the monitoring of their behaviour in the EEA or the UK.
4.2 Application of Non-European Legislation. The parties acknowledge and agree that Non-European Data Protection Legislation may also apply to the processing of Customer Personal Data.
4.3 Application of Terms. Except to the extent these Terms state otherwise, these Terms will apply irrespective of whether the European Data Protection Legislation or Non-European Data Protection Legislation applies to the processing of Customer Personal Data.
5. Processing of Data
5.1 Roles and Regulatory Compliance; Authorization.
5.1.1 Processor and Controller Responsibilities. If the European Data Protection Legislation applies to the processing of Customer Personal Data, the parties acknowledge and agree that:
- the subject matter and details of the processing are described in Appendix 1;
- Google is a processor of that Customer Personal Data under the European Data Protection Legislation;
- Customer is a controller or processor, as applicable, of that Customer Personal Data under European Data Protection Legislation; and
- each party will comply with the obligations applicable to it under the European Data Protection Legislation with respect to the processing of that Customer Personal Data.
5.1.2 Processor Customers. If Customer is a processor:
(a) Customer warrants on an ongoing basis that the relevant controller has authorized (i) the instructions, (ii) Customer’s appointment of Google as another processor, and (iii) Google’ engagement of Subprocessors as described in Section 11 (Subprocessors);
(b) Customer will immediately forward to the relevant controller any notice provided by Google under Sections 5.4 (Instruction Notifications), 7.2.1 (Incident Notification), 11.4 (Opportunity to Object to Subprocessor Changes) or that refers to any SCCs; and
(c) Customer may make available to the relevant controller any information made available by Google under Sections 7.4 (Security Certification), 10.6 (Data Centre Information) and 11.2 (Information about Subprocessors).
5.1.3 Responsibilities under Non-European Legislation. If Non-European Data Protection Legislation applies to either party’s processing of Customer Personal Data, the parties acknowledge and agree that the relevant party will comply with any obligations applicable to it under that legislation with respect to the processing of that Customer Personal Data.
5.2 Scope of Processing.
5.2.1 Customer’s Instructions. By entering into these Terms, Customer instructs Google to process Customer Personal Data in accordance with applicable law and only: (a) to provide the Services; as further specified via Customer’s use of the Services (including the Admin Console and other functionality of the Services); (b) as documented in the form of the Agreement, including these Terms; and (c) as further documented in any other written instructions given by Customer and acknowledged by Google as constituting instructions for purposes of these Terms (collectively, the “Instructions”).
5.2.2 Google’s Compliance with Instructions. Google will comply with the Instructions unless prohibited by European or National Laws in which case Google will inform Customer (unless that law prohibits Google from doing so on important grounds of public interest) via the Notification Email Address.
6. Data Deletion
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 in accordance with applicable law. Google will comply with this instruction as soon as reasonably practicable and within a maximum period of 180 days, unless European or National Law requires storage.
6.2 Deletion on Termination. On expiry of the Term, Customer instructs Google to delete all Customer Data (including existing copies) from Google’s systems in accordance with applicable law. Google will, after a recovery period of up to 30 days following such expiry, comply with this instruction as soon as reasonably practicable and within a maximum period of 180 days, unless European or National Law requires storage. Without prejudice to Section 9.1 (Access; Rectification; Restricted Processing; Portability), Customer acknowledges and agrees that Customer will be responsible for exporting, before the Term expires, any Customer Data it wishes to retain afterwards.
7. Data Security
7.1 Google’s Security Measures, Controls and Assistance.
7.1.1 Google’s Security Measures. Google will implement and maintain technical and organizational measures to protect Customer Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure or access as described in Appendix 2 (the "Security Measures"). As described in Appendix 2, the Security Measures include measures to encrypt personal data; to help ensure ongoing confidentiality, integrity, availability and resilience of Google’s systems and services; to help restore timely access to personal data following an incident; and for regular testing of effectiveness. Google may update or modify the Security Measures from time to time provided that such updates and modifications do not result in the degradation of the overall security of the Services.
7.1.2 Security Compliance by Google Staff. Google will 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, including ensuring that all persons authorized to process Customer Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
7.1.3 Additional Security Controls. In addition to the Security Measures, Google will make the Additional Security Controls available to: (a) allow Customer to take steps to secure Customer Data; and (b) provide Customer with information about securing, accessing and using Customer Data.
7.1.4 Google’s Security Assistance. Customer agrees that 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 any of Customer’s obligations in respect of security of personal data and personal data breaches, including if applicable Customer’s obligations pursuant to Articles 32 to 34 (inclusive) of the GDPR, by:
- implementing and maintaining the Security Measures in accordance with Section 7.1.1 (Google’s Security Measures);
- making the Additional Security Controls available to Customer in accordance with Section 7.1.3 (Additional Security Controls);
- complying with the terms of Section 7.2 (Data Incidents).
7.2 Data Incidents
7.2.1 Incident Notification. If Google becomes aware of a Data Incident, Google will: (a) notify Customer of the Data Incident promptly and without undue delay after becoming aware of the Data Incident; and (b) promptly take reasonable steps to minimize harm and secure Customer Data.
7.2.2 Details of Data Incident. Notifications made pursuant to this section will describe, to the extent possible, details of the Data Incident, including steps taken to mitigate the potential risks and steps Google recommends Customer take to address the Data Incident.
7.2.3 Delivery of Notification. Notification(s) of any Data Incident(s) will be delivered to the Notification Email Address or, at Google’s discretion, by direct communication (for example, by phone call or an in-person meeting). Customer is solely responsible for ensuring that the Notification Email Address is current and valid.
7.2.4 No Assessment of Customer Data by Google. Google will not assess the contents of Customer Data in order to identify information subject to any specific legal requirements. Customer is solely responsible for complying with incident notification laws applicable to Customer and fulfilling any third party notification obligations related to any Data Incident(s).
7.2.5 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.
7.3 Customer’s Security Responsibilities and Assessment.
7.3.1 Customer’s Security Responsibilities. Customer agrees that, without prejudice to Google’s obligations under Section 7.1 (Google’s Security Measures, Controls and Assistance) and Section 7.2 (Data Incidents):
- Customer is solely responsible for its use of the Services, including:
- making appropriate use of the Services and the Additional Security Controls to ensure a level of security appropriate to the risk in respect of the Customer Data;
- securing the account authentication credentials, systems and devices Customer uses to access the Services;
- backing up its Customer Data; and
- Google has no obligation to protect Customer Data that Customer elects to store or transfer outside of Google’s and its Subprocessors’ systems (for example, offline or on-premise storage), or to protect Customer Data by implementing or maintaining Additional Security Controls except to the extent Customer has opted to use them.
7.3.2 Customer’s Security Assessment.
- Customer is solely responsible for evaluating for itself whether the Services, the Security Measures, the Additional Security Controls and Google’s commitments under this Section 7 (Data Security) will meet Customer’s needs, including with respect to any security obligations of Customer under the European Data Protection Legislation and/or Non-European Data Protection Legislation, as applicable.
- Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing of Customer Personal Data as well as the risks to individuals) the Security Measures implemented and maintained by Google as set out in Section 7.1.1 (Google’s Security Measures) provide a level of security appropriate to the risk in respect of the Customer Data.
7.4 Reviews and Audits of Compliance
7.4.1 Customer’s Audit Rights.
- If the European Data Protection Legislation applies to the processing of Customer Personal Data, Google will allow Customer or an independent auditor appointed by Customer to conduct audits (including inspections) to verify Google’s compliance with its obligations under these Terms. Customer may also conduct an audit to verify Google’s compliance with its obligations under these Terms.
- If Customer has entered into SCC’s as described in Section 10 (Data Transfers), Google will, allow Customer or an independent auditor appointed by Customer to conduct audits as described in the applicable SCCs in accordance with Section 7.4.2 (Additional Business Terms for Reviews and Audits).
7.4.2 Additional Business Terms for Reviews and Audits.
- Following receipt by Google of a request for an audit, 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.
- Google may charge a fee (based on Google’s reasonable costs) for any audit. Google will provide Customer with further details of any applicable fee, and the basis of its calculation, in advance of any such review or audit. Customer will be responsible for any fees charged by any auditor appointed by Customer to execute any such audit.
- Google may object in writing to an auditor appointed by Customer to conduct any 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.
8. Impact Assessments and Consultations
Customer agrees that Google will (taking into account the nature of the processing and the information available to Google) assist Customer in ensuring compliance with any obligations of Customer in respect of data protection impact assessments and prior consultation, including if applicable Customer’s obligations pursuant to Articles 35 and 36 of the GDPR, by:
- providing the Additional Security Controls in accordance with Section 7.1.3 (Additional Security Controls) and
- providing the information contained in the Agreement including these Terms.
9. Data Subject Rights; Data Export
9.1 Access; Rectification; Restricted Processing; Portability. During the Term, Google will, in a manner consistent with the functionality of the Services, enable Customer to access, rectify and restrict processing of Customer Data, including via the deletion functionality provided by Google as described in Section 6.1 (Deletion by Customer), and to export Customer Data.
9.2 Data Subject Requests
9.2.1 Customer’s Responsibility for Requests. During the Term, if Google receives any request from a data subject in relation to Customer Personal Data, Google will advise the data subject to submit their request to Customer and Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Services.
9.2.2 Google’s Data Subject Request Assistance. Customer agrees that Google will (taking into account the nature of the processing of Customer Personal Data) assist Customer in fulfilling any obligation to respond to requests by data subjects, including if applicable Customer’s obligation to respond to requests for exercising the data subject’s rights laid down in Chapter III of the GDPR, by:
- providing the Additional Security Controls in accordance with Section 7.1.3 (Additional Security Controls); and
- complying with the commitments set out in Section 9.1 (Access; Rectification; Restricted Processing; Portability) and Section 9.2.1 (Customer’s Responsibility for Requests).
9.2.3 Rectification. If Customer becomes aware that any Customer Personal Data is inaccurate or outdated, Customer will be responsible for rectifying or deleting that data if required by the European Data Protection Legislation.
10. Data Transfers
10.1 Data Storage and Processing Facilities. Google may, subject to the remainder of this Section 10 (Data Transfers) store and process the relevant Customer Data anywhere Google or its Subprocessors maintains facilities.
10.2 Permitted Transfers. The parties acknowledge that the European Data Protection Legislation does not require the SCCs or an Alternative Transfer Solution in order to process Customer Personal Data in or transfer it to an Adequate Country (“Permitted Transfers”).
10.3 Restricted Transfers. If the processing of Customer Personal Data involves any transfers that are not Permitted Transfers, and the European Data Protection Legislation applies to those transfers (“Restricted Transfer”), then:
(a) if Google announces its adoption of an Alternative Transfer Solution for any Restricted Transfers, then Google will ensure that they are made in accordance with that Alternative Transfer Solution; and/or
(b) if Google has not adopted an Alternative Transfer Solution for any Restricted Transfers, then:
(i) if Google’s address is in an Adequate Country:
(A) the SCCs (EU Processor-to-Processor, Google Exporter) will apply with respect to all Restricted Transfers from Google to Subprocessors; and
(B) in addition, if Customer’s address is not in an Adequate Country, the SCCs (EU Processor-to-Controller) will apply with respect to Restricted Transfers between Google and Customer (regardless of whether Customer is a controller and/or a processor); or
(ii) if Google’s address is not in an Adequate Country:
(A) the SCCs (EU Controller-to-Processor) and/or SCCs (EU Processor-to Processor) will apply (according to whether Customer is a controller and/or processor) with respect to Restricted Transfers between Customer and Google that are subject to the EU GDPR and/or the Swiss FDPA; and
(B) the SCCs (UK Controller-to-Processor) will apply (regardless of whether Customer is a controller and/or processor) with respect to Restricted Transfers between Customer and Google that are subject to the UK GDPR.
10.4 Supplementary Measures and Information. Google will provide Customer with information relevant to Restricted Transfers, including information about supplementary measures protect Customer Personal Data, as described in Section 7.5.1 (Reviews of Security Documentation), Appendix 2 (Security Measures) and other materials concerning the nature of the Android Enterprise services and the processing of Customer Personal Data (for example, help center articles).
10.5 Termination. If Customer concludes, based on its current or intended use of the Android Enterprise services, that the Alternative Transfer Solution and/or SCCs, as applicable, do not provide appropriate safeguards for Customer Personal Data, then Customer may immediately terminate the Agreement for convenience by notifying Google in writing.
10.6 Data Center Information. Information about the locations of Google data centers is available at: www.google.com/about/datacenters/locations/ (as may be updated by Google from time to time).
11.1 Consent to Subprocessor Engagement. Customer specifically authorizes the engagement of the Subprocessors listed in Section 11.2 (Information about Subprocessors) as of the Terms Effective Date.. In addition, Customer generally authorizes the engagement of any other third parties as Subprocessors (“ New Subprocessors”), subject to Section 11.4 (Opportunity to Object to Subprocessor Changes).
11.2 Information about Subprocessors. Information about Subprocessors, including their locations, is available at www.android.com/enterprise/data-protection/subprocessors (as may be updated by Google from time to time in accordance with these Terms).
11.3 Requirements for Subprocessor Engagement. When engaging any Subprocessor, Google will:
- ensure via a written contract that:
- 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 Agreement (including these Terms) ; and
- if the processing of Customer Personal Data is subject to the European Data Processing Legislation, the data protection obligations set out in Article 28(3) of the GDPR, as described in these Terms, are imposed on the Subprocessor; and
- remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor.
11.4 Opportunity to Object to Subprocessor Changes.
- When any new New Subprocessor is engaged during the Term, Google will, at least 30 days before the new New Subprocessor processes any Customer Data, inform Customer of the engagement (including the name and location of the relevant subprocessor and the activities it will perform) either by sending an email to the Notification Email Address or via the Admin Console.
- Customer may object to any new New Subprocessor by terminating the Agreement for convenience immediately upon written notice to Google, on condition that Customer provides such notice within 90 days of being informed of the engagement of the subprocessor as described in this Section 11.4.
12. Google Data Protection Team; Processing Records
12.1 Google’s Data Protection Team. Android Enterprise’s Data Protection Team can be contacted at email@example.com (and/or via such other means as Google may provide from time to time).
12.2 Google’s Processing Records. Google will keep appropriate documentation of its processing activities as required by the GDPR. Customer acknowledges that Google is required under the GDPR to: (a) collect and maintain records of certain information, including (i) the name and contact details of each processor and/or controller on behalf of which Google is acting and, where applicable, of such processor’s or controller’s local representative and data protection officer, and (ii) if applicable under the relevant SCC’s, Customer’s supervisory authority; and (b) make such information available to any supervisory authorities. Accordingly, if the GDPR applies to the processing of Customer Personal Data, Customer will, where requested, provide such information to Google via the Admin Console or other means provided by Google, and will use the Admin Console or such other means to ensure that all information provided is kept accurate and up-to-date.
12.3 Controller Requests. If Google 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 the Customer.
13.1 Total Liability. Notwithstanding anything else in the Agreement, the total combined liability of either party and its affiliates towards the other party under or in connection with Terms will be limited to the maximum monetary or payment-based amount at which that party’s liability is capped under the Agreement (for clarity, any exclusion of confidentiality or indemnification claims from the Agreement’s limitation of liability will not apply to claims under the Agreement relating to the European Data Protection Legislation or Non-European Data Protection Legislation). Nothing in this Section 13 (Liability) will exclude or limit either party’s liability for: death or personal injury resulting from its negligence or the negligence of its employees or agents; fraud or fraudulent misrepresentation; or matters for which liability cannot be excluded or limited under applicable law.
14. Effect of These Terms
Notwithstanding anything to the contrary in the Agreement, to the extent of any conflict or inconsistency between these Terms, the relevant SCC’s and the remaining terms of the Agreement, the following order of precedence will apply:
(a) the relevant SCC’s;
(b) the remainder of these Terms; and
(c) the remainder of the Agreement.
14.2 No Modification of SCCs. Nothing in the Agreement (including these Terms) is intended to modify or contradict any SCCs or prejudice the fundamental rights or freedoms of data subjects under the European Data Protection Legislation.
14.3 No Effect on Controller Terms. These Terms will not affect any separate terms between Google and Customer reflecting a controller-controller relationship for a service other than the Android Enterprise services.
14.4 Legacy MCCs. Customer agrees that, as of their effective date, the SCCs will supersede and terminate any Model Contract Clauses approved under Article 26(2) of Directive 95/46/EC and previously entered into by Customer with Google LLC (“Model Contract Clauses”). Where Google LLC is not a party to the Agreement, Google LLC will be a third party beneficiary of this Section 14.4 (Legacy MCCs). This Section 14.4 (Legacy MCCs) will not affect either party’s rights, or any data subject’s rights, that may have accrued under the Model Contract Clauses while they were in force.
15. Changes to these Terms
15.1 Changes to URLs. From time to time, Google may change any URL referenced in these Terms and the content at any such URL, except that Google may only change the SCCs in accordance with Sections 15.2(b) - 15.2(d) (Changes to the Terms) or to incorporate any new version of the SCCs that may be adopted under the European Data Protection Legislation, in each case in a manner that does not affect the validity of the SCC’s under the European Data Protection Legislation.
15.2 Changes to these Terms. Google may change these Terms if the change:
(a) is expressly permitted by these Terms, including as described in Section 15.1 (Changes to URLs);
(b) reflects a change in the name or form of a legal entity;
(c) is required to comply with applicable law, applicable regulation, a court order, or guidance issued by a governmental regulator or agency, or reflects Google’s adoption of an Alternative Transfer Solution; or
(d) does not (i) result in a degradation of the overall security of the Android Enterprise services; (ii) expand the scope of or remove any restrictions on, (x) in the case of the Additional Terms for Non-European Data Protection Legislation, Google’s rights to use or otherwise process the data in scope of the Additional Terms for Non-European Data Protection Legislation or (y) in the case of the remainder of these Terms,, Google’s processing of Customer Personal Data, as described in Section 5.3 (Google’s Compliance with Instructions); and (iii) otherwise have a material adverse impact on Customer’s rights under these Terms, as reasonably determined by Google.
Appendix 1: Subject Matter and Details of the Data Processing
Google’s provision of the Services to Customer.
Duration of the Processing
The Term plus the period from the expiry of the Term until deletion of all Customer Data by Google in accordance with the Terms.
Nature and Purpose of the Processing
Google will process Customer Personal Data for the purposes of providing the Services to Customer in accordance with the Terms.
Categories of Data
Data relating to individuals provided to Google via the Services, by (or at the direction of) Customer or by Customer End Users.
Data subjects include the individuals about whom data is provided to Google via the Services by (or at the direction of) Customer or by Customer End Users.
Appendix 2: Security Measures
As from the Terms Effective Date, Google will implement and maintain the Security Measures set out in this Appendix 2. Google may update or modify such Security Measures from time to time provided that such updates and modifications do not result in the degradation of the overall security of the Services.
1. Data Center and Network Security
(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 diesel generator systems take over. The diesel 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. 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 replicates data over multiple systems to help to protect against accidental destruction or loss. Google has designed and regularly plans and tests its business continuity planning/disaster recovery programs.
(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:
- tightly controlling the size and make-up of Google’s attack surface through preventative measures;
- employing intelligent detection controls at data entry points; and
- 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
(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 an electronic card key and biometric 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.
(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 must authenticate themselves via a central authentication system or via a single sign on system in order to administer 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/or systems from gaining access to systems used to process personal data. Google designs its systems to (i) only allow authorized persons to access data they are authorized to access; and (ii) ensure that personal 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. LDAP, Kerberos and a proprietary system utilizing SSH certificates 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 password expiry, restrictions on password reuse and sufficient password strength. Access to the corporate and production environments require a second factor authenticator such as a hardware token.
(a) Data Storage, Isolation and Logging. Google stores data in a multi-tenant environment on Google owned servers. The data and file system architecture are replicated between multiple geographically dispersed data centers. Google also logically isolates the Customer’s 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 Customer End Users for specific purposes. Customer may choose to make use of certain logging capability that Google may make available via the Services.
(b) Decommissioned Disks and Disk Erase Policy. Certain 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 backgrounds checks to the extent legally permissible and in accordance with applicable local labor law and statutory regulations.
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 (eg., 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 set out in Section 11.3 (Requirements for Subprocessor Engagement) of these Terms, the Subprocessor is required to enter into appropriate security, confidentiality and privacy contract terms.