Chronicle Data Processing and Security Terms

Last modified: October 01, 2020

The customer agreeing to these terms ("Customer"), and Chronicle LLC, Chronicle Security Ireland Limited, or any other entity that directly or indirectly controls, is controlled by, or is under common control with Chronicle LLC (as applicable, "Chronicle"), have entered into an agreement under which Chronicle has agreed to provide the Services and related 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. Where the Agreement was entered into offline with Chronicle, these Terms supersede the "Data Privacy and Security" Clause, the "DPA", and "Security Terms" in that agreement (if applicable).

1. Definitions

1.1 Terms defined in the Agreement apply to these Terms. Words and expressions used in this DPST but not independently defined have the meanings given to them in the Agreement or in the GDPR. In addition, in these Terms:

  • Additional Security Controls means security resources, features, functionality and/or controls that the Customer may use at its option and/or as it determines, including encryption, logging, monitoring, and security scanning.

  • Agreed Liability Cap means the maximum monetary or payment-based amount at which a party's liability is capped under the Agreement.

  • Alternative Transfer Solution means a solution, other than the Model Contract Clauses, that enables the lawful transfer of personal data to a third country in accordance with European Data Protection Law.

  • Chronicle's Third Party Auditor means a Chronicle-appointed, qualified and independent third party auditor, whose then-current identity Chronicle will disclose to Customer.

  • Customer Personal Data means the personal data contained within the Customer Data.

  • Data Incident means a breach of Chronicle'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 Chronicle.

  • 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 Law 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.

  • Model Contract Clauses or MCCs mean standard data protection clauses for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the EU GDPR and set out at https://chronicle.security/legal/model-contract-clauses.

  • Non-European Data Protection Law means data protection or privacy laws in force outside the European Economic Area, Switzerland and the UK.

  • Notification Email Address means the email address(es) designated by Customer in the Order Form or Ordering Document (as applicable) or otherwise as authorised by Chronicle, to receive certain notifications from Chronicle. Customer is responsible for ensuring that its Notification Email Address remains current and valid.

  • Security Documentation means all documents and information made available by Chronicle under Section 6.5.1 (Reviews of Security Documentation).

  • Security Measures has the meaning given in Section 6.1.1 (Chronicle's Security Measures).

  • Subprocessor means a third party authorized as another processor under these Terms to have logical access to and process Customer Data in order to provide parts of the Services and Chronicle TSS.

  • Supervisory Authority means, as applicable: (a) a "supervisory authority" as defined in the EU GDPR; and/or (b) the "Commissioner" as defined in the UK GDPR.

  • Term means the period from the Terms Effective Date until the end of Chronicle'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 Chronicle may continue providing the Services for transitional purposes.

  • Terms Effective Date means the date on which Customer accepted, or the parties otherwise agreed to, these Terms.

  • UK GDPR means the EU GDPR as amended and incorporated into UK law under the UK European Union (Withdrawal) Act 2018, if in force.

The terms "personal data", "data subject", "processing", "controller" and "processor" as used in these Terms have the meanings given in the GDPR irrespective of whether European Data Protection Law or Non-European Data Protection Law applies.

2. Duration

These Terms will notwithstanding expiry of the Term, remain in effect until, and automatically expire upon, deletion of all Customer Data by Chronicle as described in these Terms.

3. Scope of Data Protection Law

3.1 Application of European Law. The parties acknowledge that European Data Protection Law will apply to the processing of Customer Personal Data if, for example:

  1. 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

  2. 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 behavior in the EEA or the UK.

3.2 Application of Non-European Law. The parties acknowledge that Non-European Data Protection Law may also apply to the processing of Customer Personal Data.

3.3 Application of Terms. Except to the extent these Terms state otherwise, these Terms will apply irrespective of whether European Data Protection Law or Non-European Data Protection Law applies to the processing of Customer Personal Data.

4. Processing of Data

4.1 Roles and Regulatory Compliance; Authorization.

4.1.1 Processor and Controller Responsibilities. If European Data Protection Law applies to the processing of Customer Personal Data:

  1. the subject matter and details of the processing are described in Appendix 1;

  2. Chronicle is a processor of that Customer Personal Data under European Data Protection Law;

  3. Customer is a controller or processor, as applicable, of that Customer Personal Data under European Data Protection Law; and

  4. each party will comply with the obligations applicable to it under European Data Protection Law with respect to the processing of that Customer Personal Data.

4.1.2 Authorization by Third Party Controller. If European Data Protection Law applies to the processing of Customer Personal Data and Customer is a processor, Customer warrants that its instructions and actions with respect to that Customer Personal Data, including its appointment of Chronicle as another processor, have been authorized by the relevant controller.

4.1.3 Responsibilities under Non-European Law. If Non-European Data Protection Law applies to either party's processing of Customer Personal Data, the relevant party will comply with any obligations applicable to it under that law with respect to the processing of that Customer Personal Data.

4.2 Scope of Processing.

4.2.1 Customer's Instructions. Customer instructs Chronicle to process Customer Personal Data in accordance with applicable law only: (a) to provide the Services and Chronicle TSS; (b) as further specified via Customer's use of any of the functionality of the Services and Chronicle TSS; (c) as documented in the form of the Agreement, including these Terms; and (d) as further documented in any other written instructions given by Customer and acknowledged by Chronicle as constituting instructions for purposes of these Terms.

4.2.2 Chronicle's Compliance with Instructions. Chronicle will comply with the instructions described in Section 4.2.1 (Customer's Instructions) (including with regard to data transfers) unless European or National Law to which Chronicle is subject requires other processing of Customer Personal Data by Chronicle, in which case Chronicle will notify Customer (unless that law prohibits Chronicle from doing so on important grounds of public interest) before such other processing.

5. Data Deletion

5.1 Deletion by Customer. During the Term, Chronicle will enable Customer to delete Customer Data upon request in a manner consistent with the functionality of the Services. If Customer requests deletion of any Customer Data during the Term and that Customer Data cannot be recovered by Customer, this request will constitute an instruction to Chronicle to delete the relevant Customer Data from Chronicle's systems in accordance with applicable law. Chronicle 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.

5.2 Deletion on Termination; Data Export. On expiry of the Term, Customer instructs Chronicle to delete all Customer Data (including existing copies) from Chronicle's systems in accordance with applicable law. Chronicle 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. Customer is responsible for notifying Chronicle at least 14 days before the Term expires of any Customer Data that Customer wishes to export and, if Customer does so, Chronicle will assist Customer in exporting such Customer Data.

6. Data Security

6.1 Chronicle Security Measures, Controls and Assistance.

6.1.1 Chronicle Security Measures. Chronicle 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"). The Security Measures include measures to encrypt personal data; to help ensure ongoing confidentiality, integrity, availability and resilience of Chronicle's systems and services; to help restore timely access to personal data following an incident; and for regular testing of effectiveness. Chronicle may update the Security Measures from time to time provided that such updates do not result in the degradation of the overall security of the Services.

6.1.2 Security Compliance by Chronicle Staff. Chronicle will: (a) 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 (b) ensure that all persons authorized to process Customer Personal Data are under an obligation of confidentiality.

6.1.3 Additional Security Controls. Chronicle may make 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.

6.1.4 Chronicle Security Assistance. Chronicle will (taking into account the nature of the processing of Customer Personal Data and the information available to Chronicle) assist Customer in ensuring compliance with its obligations pursuant to Articles 32 to 34 of the GDPR, by:

  1. implementing and maintaining the Security Measures in accordance with Section 6.1.1 (Chronicle Security Measures);

  2. making Additional Security Controls available to Customer in accordance with Section 6.1.3 (Additional Security Controls);

  3. complying with the terms of Section 6.2 (Data Incidents);

  4. providing Customer with the Security Documentation in accordance with Section 6.5.1 (Reviews of Security Documentation) and the information contained in the Agreement including these Terms; and

  5. if subsections (a)-(d) above are insufficient for Customer to comply with such obligations, upon Customer's request, providing additional reasonable assistance.

6.2 Data Incidents.

6.2.1 Incident Notification. Chronicle 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.

6.2.2 Details of Data Incident. Chronicle's notification of a Data Incident will describe, to the extent possible, the nature of the Data Incident, the measures taken to mitigate the potential risks and the measures Chronicle recommends Customer take to address the Data Incident.

6.2.3 Delivery of Notification. Notification(s) of any Data Incident(s) will be delivered to the Notification Email Address.

6.2.4 No Assessment of Customer Data by Chronicle. Chronicle has no obligation to assess Customer Data in order to identify information subject to any specific legal requirements.

6.2.5 No Acknowledgement of Fault by Chronicle. Chronicle's notification of or response to a Data Incident under this Section 6.2 (Data Incidents) will not be construed as an acknowledgement by Chronicle of any fault or liability with respect to the Data Incident.

6.3 Customer's Security Responsibilities and Assessment.

6.3.1 Customer's Security Responsibilities. Without prejudice to Chronicle's obligations under Sections 6.1 (Chronicle Security Measures, Controls and Assistance) and 6.2 (Data Incidents), and elsewhere in the Agreement, Customer is responsible for its use of the Services and its storage of any copies of Customer Data outside Chronicle or Chronicle's Subprocessors' systems, including:

  1. using the Services and Additional Security Controls to ensure a level of security appropriate to the risk in respect of the Customer Data;

  2. securing the account authentication credentials, systems and devices Customer uses to access the Services; and

  3. backing up its Customer Data as appropriate.

6.3.2 Customer's Security Assessment. Customer agrees, based on its current and intended use of the Services, that the Services, Security Measures, Additional Security Controls and Chronicle's commitments under this Section 6 (Data Security): (a) meet Customer's needs, including with respect to any security obligations of Customer under European Data Protection Law and/or Non-European Data Protection Law, as applicable, and (b) provide a level of security appropriate to the risk in respect of the Customer Data.

6.4 Compliance Certification and SOC Report. Chronicle will maintain at least the following for the Services: ISO 27001 certification (the "Compliance Certification") and SOC 2 Type 2 accreditation (the "SOC Report"). Chronicle may add standards at any time. Chronicle may replace a Compliance Certification or SOC Report with an equivalent or enhanced alternative.

6.5 Reviews and Audits of Compliance.

6.5.1 Reviews of Security Documentation. Chronicle will make the Compliance Certification and the SOC Report available for review by Customer to demonstrate compliance by Chronicle with its obligations under these Terms.

6.5.2 Customer's Audit Rights.

  1. If European Data Protection Law applies to the processing of Customer Personal Data, Chronicle will allow Customer or an independent auditor appointed by Customer to conduct audits (including inspections) to verify Chronicle's compliance with its obligations under these Terms in accordance with Section 6.5.3 (Additional Business Terms for Reviews and Audits). Chronicle will contribute to such audits as described in Section 6.4 (Compliance Certification and SOC Report) and this Section 6.5 (Reviews and Audits of Compliance).

  2. If Customer has entered into Model Contract Clauses as described in Section 9.2 ( Transfers of Data), Chronicle will allow Customer or an independent auditor appointed by Customer to conduct audits as described in the Model Contract Clauses in accordance with Section 6.5.3 (Additional Business Terms for Reviews and Audits).

  3. Customer may conduct an audit to verify Chronicle's compliance with its obligations under these Terms by reviewing the Security Documentation (which reflects the outcome of audits conducted by Chronicle's Third Party Auditor or another third party auditor).

6.5.3 Additional Business Terms for Reviews and Audits.

  1. Customer must send any requests for reviews of the SOC Report under Section 6.5.1 or audits under Section 6.5.2(a) or 6.5.2(b) to the Chronicle support team who can be contacted as described in the Chronicle Technical Support Services Guidelines.

  2. Following receipt by Chronicle of a request under Section 6.5.3(a), Chronicle and Customer will discuss and agree in advance on: (i) the reasonable date(s) of and security and confidentiality controls applicable to any review of the SOC Report under Section 6.5.1; and (ii) the reasonable start date, scope and duration of and security and confidentiality controls applicable to any audit under Section 6.5.2(a) or 6.5.2(b).

  3. Chronicle may charge a fee (based on Chronicle's reasonable costs) for any audit under Section 6.5.2(a) or 6.5.2(b). Chronicle 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. Chronicle may object in writing to an auditor appointed by Customer to conduct any audit under Section 6.5.2(a) or 6.5.2(b) if the auditor is, in Chronicle's reasonable opinion, not suitably qualified or independent, a competitor of Chronicle, or otherwise manifestly unsuitable. Any such objection by Chronicle will require Customer to appoint another auditor or conduct the audit itself.

6.5.4 No Modification of MCCs. Nothing in this Section 6.5 (Reviews and Audits of Compliance) varies or modifies any rights or obligations of Customer or Chronicle LLC under any Model Contract Clauses entered into as described in Section 9.2 (Transfers of Data).

7. Impact Assessments and Consultations

Chronicle will (taking into account the nature of the processing and the information available to Chronicle) assist Customer in ensuring compliance with its obligations pursuant to Articles 35 and 36 of the GDPR, by:

  1. providing Additional Security Controls in accordance with Section 6.1.3 (Additional Security Controls) and the Security Documentation in accordance with Section 6.5.1 (Reviews of Security Documentation);

  2. providing the information contained in the Agreement including these Terms; and

  3. if subsections (a) and (b) above are insufficient for Customer to comply with such obligations, upon Customer's request, providing additional reasonable assistance.

8. Access etc.; Data Subject Rights

8.1 Access; Rectification; Restricted Processing. During the Term, Chronicle will enable Customer, in a manner consistent with the functionality of the Services, to access, rectify and restrict processing of Customer Data, including via the deletion functionality provided by Chronicle as described in Section 5.1 (Deletion by Customer).

8.2 Data Subject Requests.

8.2.1 Customer's Responsibility for Requests. During the Term, if Chronicle receives a request from a data subject in relation to Customer Personal Data, and the request identifies Customer, Chronicle will advise the data subject to submit their request to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Services.

8.2.2 Chronicle's Data Subject Request Assistance. Chronicle will (taking into account the nature of the processing of Customer Personal Data) assist Customer in fulfilling its obligations under Chapter III of the GDPR to respond to requests for exercising the data subject's rights by:

  1. providing Additional Security Controls in accordance with Section 6.1.3 (Additional Security Controls);

  2. complying with Sections 8.1 (Access; Rectification; Restricted Processing) and 8.2.1 (Customer's Responsibility for Requests); and

  3. if subsections (a) and (b) above are insufficient for Customer to comply with such obligations, upon Customer's request, providing additional reasonable assistance.

9. Data Transfers

9.1 Data Storage and Processing Facilities. Chronicle may store and process Customer Data anywhere Chronicle or its Subprocessors maintain facilities, subject to:

  1. Section 9.2 (Transfers of Data) with respect to the Model Contract Clauses or Alternative Transfer Solution; and

  2. Any data location commitments given elsewhere in the Agreement.

9.2 Transfers of Data. If the storage and/or processing of Customer Personal Data involves transfers of Customer Personal Data from the EEA, Switzerland or the UK to any third country that does not ensure an adequate level of protection, and European Data Protection Law applies to those transfers, then:

  1. if Customer (as data exporter) enters into the Model Contract Clauses with Chronicle LLC (as data importer) in offline form, then:

    1. the transfers will be subject to the Model Contract Clauses; and

    2. Chronicle will ensure that Chronicle LLC complies with its obligations under the Model Contract Clauses in respect of those transfers; or

  2. if Customer does not enter into the Model Contract Clauses as described in Section 9.2:

    1. if an Alternative Transfer Solution is made available by Chronicle: (A) Customer will be deemed to be using it and will take any action (which may include execution of documents) strictly required to give it full effect; and (B) Chronicle will ensure that the transfers are made in accordance with such Alternative Transfer Solution; or

    2. if an Alternative Transfer Solution is not made available by Chronicle: (A) Customer (as data exporter) will be deemed to have entered into the Model Contract Clauses with Chronicle LLC (as data importer); (B) the transfers will be subject to the Model Contract Clauses; and (C) Chronicle will ensure that Chronicle LLC complies with its obligations under the Model Contract Clauses in respect of those transfers.

  3. if Customer has entered into the Model Contract Clauses but reasonably determines subsequently that they do not provide an adequate level of protection, then:

    1. if an Alternative Transfer Solution is made available by Chronicle, Customer may, by notifying Chronicle LLC, terminate any Model Contract Clauses applicable under Section 9.2(a), such that Section 9.2(b)(i) will apply;

    2. or if an Alternative Transfer Solution is not made available by Chronicle, Customer may terminate the Agreement immediately by notifying Chronicle.

9.3 Data Center Information. Information about the locations of Chronicle's and its Affiliate Subprocessors' facilities is available at https://cloud.google.com/about/locations/ (as may be updated from time to time).

9.4 Disclosure of Confidential Information Containing Personal Data. If Customer has entered into the Model Contract Clauses as described in Section 9.2 (Transfers of Data), Chronicle will, notwithstanding any term to the contrary in the Agreement, ensure that any disclosure of Customer's Confidential Information containing personal data, and any notifications relating to any such disclosures, will be made in accordance with such Model Contract Clauses.

10. Subprocessors

10.1 Consent to Subprocessor Engagement. Customer specifically authorizes the engagement as Subprocessors of: (a) those entities listed in Section 10.2 (Information about Subprocessors); and (b) all other Chronicle Affiliates from time to time. In addition, without prejudice to Section 10.4 (Opportunity to Object to Subprocessor Changes), Customer generally authorizes the engagement as Subprocessors of any other third parties ("New Third Party Subprocessors"). If Customer has entered into the Model Contract Clauses as described in Section 9.2 (Transfers of Data), the above authorizations constitute Customer's prior written consent to the subcontracting by Chronicle LLC of the processing of Customer Data.

10.2 Information about Subprocessors.

Information about Subprocessors, including their functions and locations, is available at https://cloud.google.com/terms/subprocessors, as such URL may be updated from time to time in accordance with these Terms.

10.3 Requirements for Subprocessor Engagement. When engaging any Subprocessor, Chronicle will:

  1. ensure via a written contract that: 

    1. 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 the Model Contract Clauses or Alternative Transfer Solution as applicable under Section 9.2 (Transfers of Data); and

    2. if the GDPR applies to the processing of Customer Personal Data, the data protection obligations described in Article 28(3) of the GDPR, as described in these Terms, are imposed on the Subprocessor; and

  2. remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor.

10.4 Opportunity to Object to Subprocessor Changes.

  1. When any New Third Party Subprocessor is engaged during the Term, Chronicle will, at least 30 days before the New Third Party Subprocessor starts processing any Customer Data, notify Customer of the engagement (including the name and location of the relevant subprocessor and the activities it will perform).

  2. Customer may, within 90 days after being notified of the engagement of a New Third Party Subprocessor, object by terminating the Agreement immediately upon written notice to Chronicle, This termination right is Customer's sole and exclusive remedy if Customer objects to any New Third Party Subprocessor.

11. Processing Records

11.1 Chronicle's Processing Records. To the extent the GDPR requires Chronicle to collect and maintain records of certain information relating to Customer, Customer will supply such information and keep it accurate and up-to-date. Chronicle may make any such information available to the Supervisory Authorities if required by the GDPR.

12. Liability

12.1 Liability Cap. If the Model Contract Clauses have been entered into as described in Section 9.2 (Transfers of Data) then, subject to Section 12.2 (Liability Cap Exclusions), the total combined liability of either party and its Affiliates towards the other party and its Affiliates under or in connection with the Agreement and such Model Contract Clauses combined will be limited to the Agreed Liability Cap for the relevant party.

12.2 Liability Cap Exclusions. Nothing in Section 12.1 (Liability Cap) will affect the remaining terms of the Agreement relating to liability (including any specific exclusions from any limitation of liability).

13. Third Party Beneficiary

Notwithstanding anything to the contrary in the Agreement, where Chronicle LLC is not a party to the Agreement, Chronicle LLC will be a third party beneficiary of Sections 6.5 (Reviews and Audits of Compliance), 9.2 (Transfers of Data), 10.1 (Consent to Subprocessor Engagement) and 12 (Liability).

14. Effect of These Terms

Notwithstanding anything to the contrary in the Agreement, to the extent of any conflict or inconsistency between these Terms and the remaining terms of the Agreement, these Terms will govern.

Appendix 1: Subject Matter and Details of the Data Processing

Subject Matter

Chronicle's provision of the Services and Chronicle TSS to Customer.

Duration of the Processing

The Term plus the period from the expiry of the Term until deletion of all Customer Data by Chronicle in accordance with the Terms.

Nature and Purpose of the Processing

Chronicle will process Customer Personal Data for the purposes of providing the Services and Chronicle TSS to Customer in accordance with the Terms.

Categories of Data

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

Data Subjects

Data subjects include the individuals about whom data is provided to Chronicle 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, Chronicle will implement and maintain the Security Measures described in this Appendix 2.

1. Subprocessor Security

Chronicle conducts an audit of the security and privacy practices of all Subprocessors before they are onboarded to ensure they 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 Chronicle has assessed the risks presented by the Subprocessor, then subject to the requirements described in Section 10.3 (Requirements for Subprocessor Engagement) of these Terms, the Subprocessor is required to enter into appropriate security, confidentiality and privacy contract terms.

2. Infrastructure Security

Chronicle is built on core infrastructure provided by Google LLC and other Chronicle Affiliate Subprocessors (hereinafter "Google"). Chronicle will ensure that, as from the Terms Effective Date, Google will implement and maintain the additional Security Measures described in this Appendix 2.

(a) Data Center and Network Security

(i) Data Centers.

Infrastructure. Google maintains geographically distributed data centers. Google stores all production data in Google's 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 has designed and regularly plans and tests its business continuity planning/disaster recovery programs.

(ii) 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:

  1. tightly controlling the size and make-up of Google's attack surface through preventative measures;

  2. employing intelligent detection controls at data entry points; and

  3. 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.

(b) Access and Site Controls

(i) 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.

(ii) 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. 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 Chronicle'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.

(c) Data

(i) Data Storage, Isolation and Logging. Google stores data in a multi-tenant environment on Google-owned servers. Subject to any Customer instructions to the contrary (for example, in the form of a data location selection), Google replicates Customer Data 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.

(ii) 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.

(d) 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 (e.g., certifications). Google's personnel will not process Customer Data without authorization.