Data Processing Agreement

Customer Data Processing Agreement

This Data Processing Addendum (“DPA”), forms part of, and is subject to, the Master SaaS Agreement or other written or electronic terms of service or subscription agreement between Heidi Computers Ltd (HCL) and Customer for Customer’s purchase of Services from HCL that references this DPA (the “Agreement”). By signing the Agreement, the parties enter into this DPA on behalf of themselves and, to the extent required under applicable Data Protection Laws, in the name and on behalf of their Affiliates, and this DPA shall be effective on the effective date of the Agreement (“Effective Date”). All capitalized terms not defined in this DPA shall have the meanings set forth in the Agreement.

1.

Definitions

“Affiliate” has the meaning set forth in the Agreement.
“Authorised Affiliate” means any of Customer Affiliate(s) permitted to or otherwise receiving the
benefit of the Services pursuant to the Agreement.

“Control” means an ownership, voting or similar interest representing fifty percent (50%) or more of the total interests then outstanding of the entity in question. The term “Controlled” shall be
construed accordingly.

“Customer Data” has the meaning set forth in the Agreement.
“Customer Personal Data” means any Customer Data that is Personal Data.

“Data Protection Laws” means all data protection and privacy laws applicable to the respective party in its role in the processing of Personal Data under the Agreement, including, where applicable, EU Data Protection Law.

“Data Controller” means an entity that determines the purposes and means of the processing of Personal Data.

“Data Processor” means an entity that processes Personal Data on behalf of a Data Controller.

“EU Data Protection Law” means (i) prior to 25 May 2018, Directive 95/46/EC of the European Parliament and of the Council on the protection of individuals with regard to the processing of Personal Data and on the free movement of such data (“Directive”) and (ii) on and after 25 May 2018, Regulation 2016/679 of the European Parliament and of the Council on the protection of natural persons with regard to the processing of Personal Data and on the free movement of such data (General Data Protection Regulation) (“GDPR”), and repealing Directive 95/46/EC.

“EEA” means, for the purposes of this DPA, the European Economic Area, United Kingdom and Switzerland.

“Model Clauses” means the Standard Contractual Clauses for Processors as approved by the European Commission in the form set out in Annex C.

“Personal Data” means any information relating to an identified or identifiable natural person.

“Privacy Shield” means the EU-U.S. Privacy Shield and Swiss-U.S. Privacy Shield Framework self-certification program operated by the U.S. Department of Commerce and approved by the European Commission pursuant to Decision C(2016)4176 of 12 July 2016 and by the Swiss Federal Council on January 11, 2017 respectively.

“Privacy Shield Principles” means the Privacy Shield Framework Principles (as supplemented by
the Supplemental Principles) contained in Annex II to the European Commission Decision of 12 July 2016 pursuant to the Directive, details of which can be found at www.privacyshield.gov/eu-us-framework.

“Processing” has the meaning given to it in the GDPR and “process”, “processes” and “processed” will be interpreted accordingly.

“Security Incident” means any unauthorised or unlawful breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of or access to Customer Personal Data, but does not include any Unsuccessful Security Incident.

“Services” means the Service provided by HCL to Customer pursuant to the Agreement and any Support Services and Technical Services (formerly referred to as Professional Services) provided by HCL to Customer pursuant to the Agreement.

“Sensitive Personal Data” means any Customer Personal Data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purposes of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation.

“Sub-processor” means any Data Processor engaged by HCL or its Affiliates to assist in fulfilling its obligations with respect to providing the Services pursuant to the Agreement or this DPA. Sub-processors may include third parties or HCL’s Affiliates.

“Unsuccessful Security Incident” means an unsuccessful attempt or activity that does not compromise the security of Customer Personal Data, including (without limitation) pings and other broadcast attacks of firewalls or edge servers, port scans, unsuccessful log-on attempts, denial of service attacks, packet sniffing (or other unauthorised access to traffic data that does not result in access beyond headers) or similar incidents.

2.

Scope and Applicability of this DPA

2.1

This DPA applies where and only to the extent that HCL Processes Customer Personal Data on behalf of Customer as Data Processor in the course of providing Services pursuant to the Agreement. Nothing in the Agreement or this DPA shall prevent HCL from using or sharing any data that HCL would otherwise collect and process independently of Customer’s use of the Services.

2.2

Notwithstanding expiry or termination of the Agreement, this DPA will remain in effect until, and will automatically expire upon, deletion of all Customer Personal Data by HCL as described in this DPA.

3.

Roles and Scope of Processing

3.1

Role of the Parties. As between HCL and Customer, Customer is either the Data Controller of Customer Personal Data, or in the case that Customer is acting on behalf of a third-party Data Controller, then a Data Processor, and HCL shall process Customer Personal Data only as a Data Processor acting on behalf of Customer.

3.2

Customer Processing of Personal Data. Customer agrees that (i) it will comply with its obligations under Data Protection Laws in respect of its processing of Personal Data, including any obligations specific to its role as a Data Controller and/or Data Processor (as applicable), and any processing instructions it issues to HCL; and (ii) it has provided notice and obtained (or will obtain) all consents and rights necessary under Data Protection Laws for HCL to process Personal Data and provide the Services pursuant to the Agreement and this DPA. If Customer is itself a Data Processor, Customer warrants to HCL that Customer’s instructions and actions with respect to that Customer Personal Data, including its appointment of HCL as another Data Processor, have been authorised by the relevant Data Controller.

3.3

Customer Instructions. HCL will process Customer Personal Data only for the purposes described in this DPA and only in accordance with Customer’s documented lawful instructions. The parties agree that this DPA and the Agreement set out the Customer’s complete and final instructions to HCL in relation to the processing of Customer Personal Data. Additional processing outside the scope of these instructions (if any) will require prior written agreement between Customer and HCL.

3.4

Details of Data Processing.

(a)

Subject matter: The subject matter of the data processing under this DPA is the Customer Personal Data.

(b)

Duration: As between HCL and Customer, the duration of the data processing under this DPA is until the termination of the Agreement in accordance with its terms.

(c)

Purpose: The purpose of the data processing under this DPA is the provision of the Services to the Customer and the performance of HCL’s obligations under the Agreement (including this DPA) or as otherwise agreed by the parties in mutually executed written form.

(d)

Nature of the processing: HCL provides enterprise cloud computing solutions and such as other Services as described in the Agreement, which process Customer Personal Data upon the instruction of the Customer in accordance with the terms of the Agreement.

(e)

Categories of data subjects: Customer may submit Customer Personal Data to the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include, but is not limited to, Personal Data relating to the following categories of data subjects:

(i)

Prospects, customers, business partners and vendors of Customer (who are natural persons);

(ii)

Employees or contact persons of Customer’s prospects, customers, business partners and vendors;

(iii)

Employees, agents, advisors, freelancers of Customer (who are natural persons); and/or

(iv)

Customer’s end-users authorised by Customer to use the Services.

(f)

Types of Personal Data: Customer may submit Customer Personal Data to the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include, but is not limited to, the following types of Personal Data:

(i)

Identification and contact data (name, address, title, contact details);

(ii)

Financial information (credit card details, account details, payment information);

(iii)

Employment details (employer, job title, geographic location, area of responsibility); and/or

(iv)

IT information (IP addresses, usage data, cookies data, location data).

(g)

Sensitive Personal Data (if applicable): Certain Editions of HCL’s Service have enhanced technical and organisational security measures. It is solely up to Customer to determine whether particular Services have appropriate technical and organisational security measures for Sensitive Personal Data. If Customer determines the Services have appropriate measures, then subject to any restrictions and/or conditions in the Agreement or Documentation, Customer may submit Sensitive Personal Data to the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include, but is not limited to, the following types of Sensitive Personal Data:

(i)

Protected health information

(ii)

Any other information that is Sensitive Personal Data (as defined under this DPA)

3.5

Access or Use. HCL will not access or use Customer Personal Data, except as necessary to maintain or provide the Services, or as necessary to comply with the law or binding order of a governmental body.

4.

Obligations of the data exporte

The data exporter agrees and warrants:

(a)

that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;

(b)

that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter’s behalf and in accordance with the applicable data protection law and the Clauses;

(c)

that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 to this contract;

(d)

that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;

(e)

that it will ensure compliance with the security measures;

(f)

that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;

(g)

to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;

(h)

 to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;

(i)

that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and

(j)

that it will ensure compliance with Clause 4(a) to (i).

5.

Obligations of the data importer

The data importer agrees and warrants:

(a)

to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;

(b)

that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;

(c)

that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred

(d)

that it will promptly notify the data exporter about:

(i)

any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,

(ii)

any accidental or unauthorised access, and

(e)

to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred;

(f)

at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority;

(g)

to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;

(i)

that the processing services by the subprocessor will be carried out in accordance with Clause 11;

(i)

to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.

6.

Liability

6.1

The parties agree that any data subject, who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered.

6.2

If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

6.2

If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

6.3

The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.

6.4

If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses.

7.

Mediation and jurisdiction

7.1

The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject:

(a)

to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority;

(b)

 to refer the dispute to the courts in the Member State in which the data exporter is established.

7.2

The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law.

7.3

Alternative Transfer Mechanism. The parties agree that the data export solution identified in Section 7.2 will not apply if and to the extent that HCL adopts an alternative data export solution for the lawful transfer of Personal Data (as recognised under EU Data Protection Laws) outside of the EEA, in which event, Customer shall reasonably cooperate with HCL to the extent required to give effect to such solution and the Alternative Transfer Mechanism will apply instead (but only to the extent such Alternative Transfer Mechanism extends to the territories to which Customer Personal Data is transferred).

8.

Additional Security

8.1

Confidentiality of processing. HCL shall ensure that any person who is authorised by HCL to process Customer Personal Data (including its staff, agents and subcontractors) shall be under an appropriate obligation of confidentiality (whether a contractual or statutory duty).

8.2

Security Incident Response. Upon confirming a Security Incident, HCL shall: (i) notify Customer without undue delay, and in any event such notification shall, where feasible, occur no later than seventy two (72) hours from HCL confirming the Security Incident; (ii) provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer; and (iii) HCL shall promptly take reasonable steps to contain, investigate, and mitigate any Security Incident. HCL’s notification of or response to a Security Incident under this Section 8.2 (Security Incident Response) will not be construed as an acknowledgment by HCL of any fault or liability with respect to the Security Incident.

8.3

No Assessment of Customer Data by HCL. Customer acknowledges that HCL 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 Security Incidents.

9.

Changes to Sub-processors.

9.1

HCL shall (i) provide an up-to-date list of the Sub-processors it has appointed upon written request from Customer; and (ii) notify Customer (for which email will suffice) if it adds or removes Sub-processors at least fourteen (14) days’ prior to allowing such Sub-processor to process Customer Personal Data.

9.2

Customer may object in writing to HCL’s appointment of a new Sub-processor within five (5) calendar days of such notice, provided that such objection is based on reasonable grounds relating to data protection. In such event, the parties will discuss such concerns in good faith with a view to achieving resolution. If HCL cannot provide an alternative Sub-processor, or the parties are not otherwise able to achieve resolution as provided in the preceding sentence, Customer, as its sole and exclusive remedy, may terminate the Agreement (including this DPA but shall not be eligible for any refund and Customer must immediately pay all fees payable under the Agreement.

10.

Return or Deletion of Data

10.1

Deletion by Customer. HCL will enable Customer to delete Customer Data during the Subscription Term in a manner consistent with the functionality of the Service.

10.2

Deletion on Termination. For thirty (30) days following termination or expiration of the Agreement, Customer shall have the option to retrieve any remaining Customer Personal Data in accordance with the Agreement. Thereafter, Customer instructs HCL to automatically delete all remaining (if any) Customer Personal Data (including copies). HCL shall not be required to delete Customer Personal Data to the extent (i) HCL is required by applicable law or order of a governmental or regulatory body to retain some or all of the Customer Personal Data; and/or (ii), Customer Personal Data it has archived on back-up systems, which Customer Personal Data HCL shall securely isolate and protect from any further processing, except to the extent required by applicable law.

11.

Cooperation

11.1

The Services provide Customer with a number of controls that Customer may use to retrieve, correct, delete or restrict Customer Personal Data, which Customer may use to assist it in connection with its obligations under the GDPR, including its obligations relating to responding to requests from data subjects or applicable data protection authorities. To the extent that Customer is unable to access the relevant Customer Personal Data within the Services using such controls or otherwise, HCL shall (at Customer’s request and expense) provide reasonable cooperation to assist Customer to respond to any requests from individuals or applicable data protection authorities relating to the processing of Customer Personal Data under the Agreement. In the event that any request from individuals or applicable data protection authorities is made directly to HCL, HCL shall not respond to such communication directly without Customer’s prior authorisation, unless legally compelled to do so, and instead, after being notified by HCL, Customer shall respond. If HCL is required to respond to such a request, HCL will promptly notify Customer and provide it with a copy of the request unless legally prohibited from doing so.

11.2

If a law enforcement agency sends HCL a demand for Customer Personal Data (e.g., a subpoena or court order), HCL will attempt to redirect the law enforcement agency to request that data directly from Customer. As part of this effort, HCL may provide Customer’s contact information to the law enforcement agency. If compelled to disclose Customer Personal Data to a law enforcement agency, then HCL will give Customer reasonable notice of the demand to allow Customer to seek a protective order or other appropriate remedy to the extent HCL is legally permitted to do so.

11.3

Customer acknowledges that HCL is required under the GDPR to: (a) collect and maintain records of certain information, including the name and contact details of each Data Processor and/or Data Controller on behalf of which HCL is acting and, where applicable, of such Data Processor’s or Data Controller’s local representative and data protection officer; and (b) make such information available to the supervisory authorities. Accordingly, if GDPR applies to the processing of Customer Personal Data, Customer will, where requested, provide such information to HCL via the Services or other means provided by HCL, and will ensure that all information provided is kept accurate and up-to-date.

11.4

To the extent HCL is required under EU Data Protection Law, HCL shall (at Customer’s request and expense) provide reasonably requested information regarding the Services to enable the Customer to carry out data protection impact assessments or prior consultations with data protection authorities as required by law.

Part C: Miscellaneous.

12.

Obligation after the termination of personal data processing services

12.1

The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore.

12.2

The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1.

Appendix 1 to the Standard Contractual Clauses

This Appendix forms part of the Clauses and must be completed by the parties.

Data exporter: The data exporter is the entity identified as the “Customer” in the Data Processing Addendum in place between data exporter and data importer and to which these Clauses are appended (“DPA”).

Data importer: The data importer is the US headquartered company, HCL Computing, Inc (“HCL”). HCL provides enterprise cloud computing solutions, which process Customer Personal Data upon the instruction of the Customer in accordance with the terms of the Agreement.

Description of Data Processing: Please see Section 3.4 (Details of Processing) of DPA for a description of the data subjects, categories of data, special categories of data and processing operations.

Appendix 2 to the Standard Contractual Clauses

This Appendix forms part of the Clauses and must be completed by the parties.

Description of the technical and organisational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c) (or document/legislation attached):

Please see Annex B of the DPA, which describes the technical and organisational security measures implemented by HCL.

Appendix 3 to the Standard Contractual Clauses

This Appendix forms part of the Clauses and must be completed by the parties.

This Appendix sets out the parties’ interpretation of their respective obligations under specific Clauses identified below. Where a party complies with the interpretations set out in this Appendix, that party shall be deemed by the other party to have complied with its commitments under the Clauses.

Clause 5(a): Suspension of data transfers and termination:

1.

The parties acknowledge that data importer may process the personal data only on behalf of the data exporter and in compliance with its instructions as provided by the data exporter and the Clauses.

2.

The parties acknowledge that if data importer cannot provide such compliance for whatever reason, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract.

3.

If the data exporter intends to suspend the transfer of personal data and/or terminate these Clauses, it shall endeavour to provide notice to the data importer and provide data importer with a reasonable period of time to cure the non-compliance (“Cure Period”).

4.

If after the Cure Period the data importer has not or cannot cure the non-compliance then the data exporter may suspend or terminate the transfer of personal data immediately. The data exporter shall not be required to provide such notice in instance where it considers there is a material risk of harm to data subjects or their personal data.

Clause 5(f): Audit:

1.

Data exporter acknowledges and agrees that it exercises its audit right under Clause 5(f) by instructing data importer to comply with the audit measures described in Section 6 (Security Reports and Audits) of the DPA.

Clause 5(j): Disclosure of subprocessor agreements

1.

The parties acknowledge the obligation of the data importer to send promptly a copy of any onward subprocessor agreement it concludes under the Clauses to the data exporter.

2.

The parties further acknowledge that, pursuant to subprocessor confidentiality restrictions, data importer may be restricted from disclosing onward subprocessor agreements to data exporter. Notwithstanding this, data importer shall use reasonable efforts to require any subprocessor it appoints to permit it to disclose the subprocessor agreement to data exporter.

3.

Even where data importer cannot disclose a subprocessor agreement to data exporter, the parties agree that, upon the request of data exporter, data importer shall (on a confidential basis) provide all information it reasonably can in connection with such subprocessing agreement to data exporter.

Clause 6: Liability

1.

Any claims brought under the Clauses shall be subject to the terms and conditions, including but to limited to, the exclusions and limitations set forth in the Agreement. In no event shall any party limit its liability to a data subject with respect to any data subject rights under these Clauses.

Clause 11: Onward subprocessing

1.

The parties acknowledge that, pursuant to FAQ II.1 in Article 29 Working Party Paper WP 176 entitled “FAQs in order to address some issues raised by the entry into force of the EU Commission Decision 2010/87/EU of 5 February 2010 on standard contractual clauses for the transfer of personal data to processors established in third countries under Directive 95/46/EC” the data exporter may provide a general consent to onward subprocessing by the data importer.

2.

Accordingly, data exporter provides a general consent to data importer, pursuant to Clause 11 of these Clauses, to engage onward subprocessors. Such consent is conditional on data importer’s compliance with the requirements set out in Section 4 (Subprocessing) of the DPA.