Data Processing Addendum
This Data Processing Addendum along with the exhibits thereto supplements the Agreement signed by and between Screenloop Ltd, and the customer.
Last updated September 13, 2022
Data Processing Addendum
Exhibit 1: Standard Contractual Clauses
SECTION I
SECTION II – OBLIGATIONS OF THE PARTIES
SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES
SECTION IV – FINAL PROVISIONS
APPENDIX
ANNEX I
A. List of Parties
B. Description of Transfer
C. Competent Supervisory Authority
ANNEX II - SECURITY MEASURES
ANNEX III - LIST OF SUB-PROCESSORS
Exhibit 2: International Data Transfer Addendum to the European Commission's New Standard Contractual Clauses
PART 1: TABLES
Table 1: Parties
Table 2: Selected SCCs, Modules and Selected Clauses
Table 3: Appendix Information
Table 4: Ending this Addendum when the Approved Addendum Changes
PART 2: MANDATORY CLAUSES
Entering into this Addendum
Interpretation of this Addendum
Hierarchy
Incorporation of and changes to the EU SCCs
Amendments to this Addendum
Data Processing Addendum
This Data Processing Addendum along with the exhibits thereto (collectively referred to as “DPA”) supplements the Agreement signed by and between Screenloop Ltd (“Screenloop”) and the Customer (the “Agreement”).
This DPA contains terms to ensure that adequate safeguards are in place with respect to the protection of Personal Data to be processed by Screenloop pursuant to the Agreement, as required by the Applicable Data Protection Laws. Any terms not defined in this DPA shall have the meaning set forth in the Agreement. Except as modified below, this DPA automatically expires upon deletion of all Personal Data as described in herein.
This Data Processing Addendum will take effect as of the Effective Date of the Agreement, between Customer and Screenloop.
1. Definitions
1.1 The following expressions are used in this DPA:
(a) "Adequate Country" means a country or territory that is recognized under UK or EU Data Protection Laws from time to time as providing adequate protection for Personal Data;
(b) "Customer Group" means Customer and any corporate entities which are from time to time:
(i) under Common Control with Customer; and
(i) established and/or doing business in the European Economic Area or Switzerland;
(c) "Data Protection Laws" means all laws and regulations, including laws and regulations of the European Union, the European Economic Area, their member states and the United Kingdom, as implemented in each jurisdiction, and any amending or replacement or equivalent legislation from time to time;
(d) "Standard Contractual Clauses" means collectively in respect of Transfers under the (i) EU GDPR: the agreement executed by and between Screenloop and Customer and attached hereto as Exhibit One (1) pursuant to the European Commission’s decision (EU) 2021/914 of 4 June 2021 on Standard Contractual Clauses for the transfer of personal data to third countries which do not have an adequate level of data protection, pursuant to Regulation (EU) 2016/679 and (ii) UK GDPR: the International Data Transfer Addendum to the European Commission’s New Standard Contractual Clauses executed by and between Customer and Screenloop and attached hereto as Exhibit Two (2);
(e) "UK GDPR" means the United Kingdom General Data Protection Regulation, Regulation (EU) 2016/679, as it forms part of domestic law in the United Kingdom by virtue of S.3 of the European Union (Withdrawal) Act 2018 as amended or modified from time to time;
(f) “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 (known as the General Data Protection Regulation);
(g) "GDPR" means the EU GDPR and the UK GDPR;
(h) "Personal Data" means all data which is defined and regulated as ‘Personal Data’ in the Data Protection Laws and which is provided by Customer to Screenloop or accessed, stored or otherwise processed by Screenloop in connection with the Screenloop Services;
(i) "processing", "data controller", "data subject", "supervisory authority" and "data processor" will have the meanings ascribed to them in the Data Protection Laws.
1.2 An entity "Controls" another entity if it: (a) holds a majority of the voting rights in it; (b) is a member or shareholder of it and has the right to remove a majority of its board of directors or equivalent managing body; (c) is a member or shareholder of it and controls alone or pursuant to an agreement with other shareholders or members, a majority of the voting rights in it; or
(d) has the right to exercise a dominant influence over it pursuant to its constitutional documents or pursuant to a contract; and two entities are treated as being in "Common Control" if either controls the other (directly or indirectly) or both are controlled (directly or indirectly) by the same entity.
2. Status of the Parties
2.1 The type of Personal Data processed pursuant to this Addendum and the subject matter, duration, nature and purpose of the processing, and the categories of data subjects, are as described in Exhibit 1.
2.2 As between the parties, Customer is solely responsible for obtaining, and represents and covenants that it has obtained and will obtain, all necessary consents, licenses and approvals for the processing, or otherwise has a valid legal basis under Data Protection Laws for the Processing of any Personal Data as part of the Services (the “Customer Legal Basis Assurance”). Each of Customer and Screenloop warrant in relation to Personal Data that it will comply with (and will ensure that any of its staff and/or subcontractors comply with), the Data Protection Laws; provided, however, that Screenloop’s warranty is subject to Customer Legal Basis Assurance.
2.3 In respect of the parties' rights and obligations under this DPA regarding the Personal Data, the parties hereby acknowledge and agree that Customer is the Data Controller and Screenloop is the Data Processor and accordingly Screenloop agrees that it will process all Personal Data in accordance with its obligations pursuant to this DPA.
2.4 Each of Screenloop and Customer will notify to each other one or more individuals within its organisation authorised to respond from time to time to enquiries regarding the Personal Data and each of Screenloop and Customer will deal with such enquiries promptly.
3. Screenloop Obligations
3.1 With respect to all Personal Data, Screenloop agrees that it will:
(a) only process the Personal Data in order to provide the Services and will act only in accordance with this Agreement and Customer's written instructions. The terms of the Agreement and this DPA, constitute the Customer’s written instructions to Screenloop in relation to the processing of Personal Data. For the avoidance of doubt, the Customer can issue further instructions for processing at any time;
(b) in the unlikely event that Data Protection Law requires Screenloop to process Personal Data other than pursuant to Customer's instructions, Screenloop will immediately notify the Customer (unless prohibited from so doing by Data Protection Law);
(c) without delay after becoming aware, inform the Customer if, in Screenloop's opinion, any instructions provided by the Customer under clause 3.1(a) infringe the GDPR;
(d) implement appropriate technical and organisational measures to ensure a level of security appropriate to the risks that are presented by the processing, in particular protection against accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data in Screenloop’s possession or under its control. Such measures include the security measures specified in Screenloop’s information security policies.
(e) ensure that its personnel have access to such Personal Data only as necessary to perform the Screenloop Services in accordance with the Agreement and this DPA, and that any persons whom it authorises to have access to the Personal Data are under obligations of confidentiality and will adhere with the Agreement and this DPA;
(f) without delay after becoming aware and in any case within twenty-four (24) hours, notify the Customer of any breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data in Screenloop’s possession or under its control (including when transmitted, stored or otherwise processed by Screenloop) (a "Security Breach");
(g) taking into account the nature of the processing, promptly provide the Customer with reasonable cooperation and assistance in respect of the Security Breach and information in Screenloop's possession concerning the Security Breach, including, to the extent known to Screenloop, the following:
(i) the nature of the Security Breach;
(ii) the categories and approximate number of data subjects concerned;
(iii) the categories and approximate number of Personal Data records concerned;
(iv) the likely consequences of the Security Breach;
(v) a summary of the unauthorised recipients of the Personal Data; and
(vi) the measures taken or proposed to be taken by Screenloop to address the Security Breach, including, where appropriate, measures to mitigate its possible adverse effects;
(h) insofar as a Security Breach relates to Customer, not make any announcement about a Security Breach (a "Breach Notice") without:
(i) the prior written consent from Customer; and
(ii) prior written approval by the Customer of the content, media and timing of the Breach Notice;
unless required to make a disclosure or announcement by applicable law.
(i) Screenloop will return or delete Customer’s Personal Data within sixty (60) days of termination or expiration of the Term. Screenloop shall comply with all directions provided by the Customer with respect to the return or disposal of Personal Data. This requirement shall not apply to the extent Screenloop is required by any EU (or any EU Member State) or UK law to retain some or all of the Personal Data, in which event Screenloop shall isolate and protect the Personal Data from any further processing except to the extent required by such law.
(j) assist the Customer when reasonably requested in relation to Customer’s obligations under Data Protection Laws with respect to:
(i) data protection impact assessments (as such term is defined in the GDPR);
(ii) subject access requests;
(iii) notifications to the supervisory authority under Data Protection Laws and/or communications to data subjects by the Customer in response to any Security Breach; and
(iv) Customer’s compliance with its obligations under the GDPR with respect to the security of processing.
(k) assist the Customer by appropriate technical and organisational measures, insofar as this is possible, to respond to data subjects’ requests to exercise their rights under Chapter III of the GDPR. Screenloop will promptly notify the Customer and in any case within twenty-four (24) hours of requests received by Screenloop, unless otherwise required by applicable law. Screenloop will not make changes to such data except as agreed in writing with Customer.
(l) maintain records of its processing activities as required by Article 30.2 of the GDPR and to demonstrate its compliance with this DPA and make such records available to the applicable supervisory authority and/or the Customer upon request.
4. Sub-processing
4.1 The Customer consents to Screenloop’s use of sub-processors to provide aspects of the Screenloop Services, and to Screenloop’s disclosure and provision of Personal Data to those sub-processors for the provision of the Services. Screenloop will require its sub-processors to comply with terms that provide substantially the same protection of Personal Data than those imposed on Screenloop in the Agreement and this DPA. Screenloop will be liable for all the acts and omissions of its sub-processors in relation to the Agreement and this DPA. Screenloop publishes a list of its sub-processors (“Sub-Processor List”, see “ANNEX III - LIST OF SUB-PROCESSORS”). When any new sub-processor is engaged, Screenloop will provide notice in line with clause 8 before the new sub-processor processes any Personal Data and add them to the Sub-Processor List.
4.2 Screenloop may authorise new sub-processors, provided that the new sub-processor only processes Personal Data in connection with the provision of Screenloop Services and Screenloop will update the list of all sub-processors engaged to process Personal Data under this Agreement published in the Sub-Processor List or make such updated version available to the Customer prior to such authorisation of the sub-processor.
4.3 If the Customer objects to the authorisation of any future sub-processor on reasonable data protection grounds, and if Screenloop is unable to provide an alternative or workaround to avoid processing of Personal Data by the objected to sub-processor to the satisfaction of the Customer within a reasonable period of time, not to exceed 14 days from receipt of the objection, then the Customer may elect to terminate the Agreement. Should the Customer terminate this Agreement in accordance with this paragraph 4.3 then the Customer shall receive a refund of all fees paid for Services and/or Support Services not provided as of the date of termination.
5. Audit and Records
5.1 Screenloop will, in accordance with Data Protection Law, make available to the Customer such information in Screenloop's possession or control as the Customer may reasonably request with a view to demonstrating Screenloop's compliance with the obligations of data processors under Data Protection Law in relation to its processing of Personal Data.
5.2 The Customer may exercise its right of audit under Data Protection Laws, through Screenloop providing additional information in Screenloop's possession or control to a supervisory authority when it requests or requires additional information in relation to the data processing activities carried out by Screenloop under this DPA.
6. Data Transfers
6.1 The Customer will ensure that the Customer and Customer’s authorised Users are entitled to transfer the Personal Data to Screenloop so that Screenloop, and its sub-processors, may lawfully process the Personal Data in accordance with this DPA.
6.2 The Customer acknowledges that the provision of the Services under the Agreement may require the processing of Personal Data by sub-processors in countries outside the EEA from time to time.
6.3 The Processor shall process Controller Data outside: (i) the UK and the European Economic Area (“EEA”); or (ii) any other territory in which restrictions are imposed on the Transfer of Controller Data across borders under the Data Protection Laws, only in compliance with the Standard Contractual Clauses attached hereto as Exhibit 1 for transfers outside the EEA and Exhibit 2, for Transfers outside the UK, in order to put in place appropriate safeguards to protect Controller Data. Screenloop will comply with the obligations of the ‘data importer’ in the Standard Contractual Clauses and the Customer will comply with the obligations of 'data exporter'. By entering into this DPA, the Parties are deemed to be signing the Standard Contractual Clauses, as updated from time to time, and its applicable Appendices. The parties agree to enter into any updated Standard Contractual Clauses as approved by the EU and the UK authorities under Data Protection Laws.
6.4 Should the Standard Contractual Clauses or other method applied for cross-border processing under Clause 6.3 cease to be a lawful means of transferring the Personal Data, the parties shall comply with any alternative lawful method of transfer required and complete any documentation required for such alternative lawful method of transfer.
6.5 The following terms will apply to the Standard Contractual Clauses set out in Exhibit 1 (whether used pursuant to clause 6.1 or 6.3(a)) and as updated from time to time:
(a) The Customer may exercise its right of audit under clause 5.1(f) of the Standard Contractual Clauses as set out in, and subject to the requirements of, clause 5.2 of this DPA; and
(b) The data importer may appoint sub-processors as set out, and subject to the requirements of, clauses 4 and 6.3 of this DPA.
7. General
7.1 This DPA is without prejudice to the rights and obligations of the parties under the Agreement which will continue to have full force and effect. This DPA is incorporated into and made a part of the Agreement by this reference. In the event of any conflict between the terms of this DPA and the terms of Agreement, the terms of this DPA will prevail so far as the subject matter concerns the processing of Personal Data.
7.2 The Customer and Screenloop each agree that any dispute resolution provisions of the Agreement (including governing law and venue) apply to this DPA.
8. Updates
Screenloop may modify this DPA as required as a result of (a) changes in applicable Data Protection Laws; (b) a merger, acquisition, corporate reorganisation or other similar occurrence; or (c) the release of new features, functions, products or services or material changes to any of the existing Services. Screenloop may make such modifications by posting a revised version of this DPA at https://www.screenloop.com/data-processing-addendum or by otherwise notifying Controller. The Screenloop will provide at least 14 days’ advance notice of any modifications. Subject to the 14 day advance notice requirement, the modified version of the DPA will become effective upon posting. By continuing to use the Services after the effective date of any modifications to this DPA, the Controller agrees to be bound by the modified DPA.
Exhibit 1: Standard Contractual Clauses
MODULE II (Controller to Processor)
SECTION I
Clause 1
Purpose and scope
The purpose of these standard contractual clauses is to ensure compliance with the requirements of 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 (General Data Protection Regulation) for the transfer of personal data to a third country.
The Parties:
(i) the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter “entity/ies”) transferring the personal data, as listed in Annex I.A. (hereinafter each “data exporter”), and
(ii) the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A. (hereinafter each “data importer”)
have agreed to these standard contractual clauses (hereinafter: “Clauses”).These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
Clause 2
Effect and invariability of the Clauses
These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46 (2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
Clause 3
Third-party beneficiaries
Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
(i) Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
(ii) Clause 8 - Clause 8.1(b), 8.9(a), (c), (d) and (e);
(iii) Clause 9 - Clause 9(a), (c), (d) and (e);
(iv) Clause 12 - Clause 12(a), (d) and (f);
(v) Clause 13;
(vi) Clause 15.1(c), (d) and (e);
(vii) Clause 16(e);
(viii) Clause 18 - Clause 18(a) and (b);Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
Clause 4
Interpretation
Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
Clause 5
Hierarchy
In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.
Clause 6
Description of the transfer(s)
The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.
Clause 7 - Optional
Docking clause
An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
SECTION II – OBLIGATIONS OF THE PARTIES
Clause 8
Data protection safeguards
The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.
8.1 Instructions
The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
8.2 Purpose limitation
The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter.
8.3 Transparency
On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679.
8.4 Accuracy
If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data.
8.5 Duration of processing and erasure or return of data
Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).
8.6 Security of processing
The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter “personal data breach”). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
8.7 Sensitive Data
Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter “sensitive data”), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.
8.8 Onward transfers
The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (in the same country as the data importer or in another third country, hereinafter “onward transfer”) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:
the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.
Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.
8.9 Documentation and compliance
The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
Clause 9
Use of sub-processors
The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 14 business days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects. The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
The data importer shall agree a third-party beneficiary clause with the sub-processor whereby - in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent - the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
Clause 10
Data subject rights
The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
Clause 11
Redress
The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
(i) lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
(ii) refer the dispute to the competent courts within the meaning of Clause 18.The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
Clause 12
Liability
Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its / their responsibility for the damage.
The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
Clause 13
Supervision
[Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.[Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority. [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.
The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES
Clause 14
Local laws and practices affecting compliance with the Clauses
The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
(i) the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
(ii) the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards;
(iii) any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
Clause 15
Obligations of the data importer in case of access by public authorities
15.1 Notification
The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
(i) receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
(ii) becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
15.2 Review of legality and data minimisation
The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
SECTION IV – FINAL PROVISIONS
Clause 16
Non-compliance with the Clauses and termination
The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
(i) the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
(ii) the data importer is in substantial or persistent breach of these Clauses; or
(iii) the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
Clause 17
Governing law
These Clauses shall be governed by the law of the EU Member State in which the data exporter is established. Where such law does not allow for third-party beneficiary rights, they shall be governed by the law of another EU Member State that does allow for third-party beneficiary rights. The Parties agree that this shall be the law of the Republic of Ireland.
Clause 18
Choice of forum and jurisdiction
Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
The Parties agree that those shall be the courts of the jurisdiction specified in Clause 17.
A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
The Parties agree to submit themselves to the jurisdiction of such courts.
Disclosures of your personal data
ANNEX I
A. List of Parties
Data exporter
Name: The Customer, as defined in the Order Form
Address: The Customer's address, as set out in the Order Form
Contact details: The Customer's contact details, as set out in the Order Form
Activities relevant to the data transferred under these Clauses: Processing of Personal Data in connection with Customer's use of the Services under the Screenloop Software-as-a-service (SAAS) Terms & Conditions
Role (controller/processor): Controller
Data importer
Name: Screenloop Ltd
Address: 27 New Dover Road, Canterbury, England, CT1 3DN
Contact details: privacy@screenloop.com, Screenloop, 133 Whitechapel High St, London E1 7QA,
Activities relevant to the data transferred under these Clauses: Processing of Personal Data in connection with Customer's use of the Services under the Screenloop Software-as-a-service (SAAS) Terms & Conditions
Role (controller/processor): Processor
B. Description of Transfer
The processing will comprise the following:
The provision of the Services will require the integration of the Customer’s video conferencing solution(s) (VCS) and/or applicant tracking system (ATS) with the Screenloop Technology. The Customer follows a simple setup process to authorise access to the aforementioned integrations. Once the ATS integration has been activated the Screenloop platform will collect data to auto-populate data fields i) related to the applicant’s first name, last name, email, role, interview stage, interview location/URL, and interview dates and ii) fields related to the jobs, including name, and department on its platform and iii) fields related to the interviewers’ name and email. Activity and usage data is also collected for technical/troubleshooting purposes as well as to generate interviewer coaching insights and decision maker insights for the Customer. Once the VCS integration has been activated the Screenloop Technology may collect data i) related to the meeting attendance, including participant names, emails, join and leaving times, and ii) the recordings of the meeting including audio, video, transcript and related recording metadata if available (and if the Customer is using Screenloop Interview). Some of the collected data will be used to generate interview insights, coaching tips, and link interview transcripts and recordings to interviews.
Categories of Data Subjects whose Personal Data is transferred
Data Subjects will include end users in your organisation who will be given access to Services and applicants or interview candidates for whose hiring process you are using Screenloop Technology.
Categories and types of Personal Data transferred
With the exception of Personal Data of end users from your organisation with access to the Services (which requires Screenloop to transfer name, email, and IP address), the extent to which you may submit Personal Data to the Services is determined and controlled by you in your use of the Services, and which may include but is not limited to the following categories of Personal Data:
Contact information of your applicants;
Usage data of your end users and/or applicants (e.g. interview join and leave time stamps or logins);
Any other Personal Data submitted by, sent to, or received by you, or your end users, via the Service.
Nature of the processing
Personal Data will be processed in accordance with the Agreement (including this DPA) and may be subject to the following processing activities:
Storage and other processing necessary to provide, maintain and improve the Services provided to you; and/or
Disclosure in accordance with the Agreement (including this DPA) and/or as compelled by applicable laws.
Purpose of the transfer and further processing
We will process Personal Data as necessary to provide the Subscription Services pursuant to the Agreement, as further specified in the Order Form, and as further instructed by you in your use of the Subscription Services.
Duration of processing:
The Processor’s processing of Data on behalf of the Controller may be performed when this Data Processing Agreement commences.
Processing shall not be time-limited and shall be performed until this DPA is terminated or cancelled by one of the parties.
For transfers to (sub-) processors: Subject matter, nature and duration of the processing:
Please refer to Annex III – list of sub-processors who can assist on subject matter, nature and duration of processing.
C. Competent Supervisory Authority
For the purposes of the Standard Contractual Clauses, the supervisory authority that shall act as competent supervisory authority is either (i) where Customer is established in an EU Member State, the supervisory authority responsible for ensuring Customer's compliance with the GDPR; (ii) where Customer is not established in an EU Member State but falls within the extra-territorial scope of the GDPR and has appointed a representative, the supervisory authority of the EU Member State in which Customer's representative is established; or (iii) where Customer is not established in an EU Member State but falls within the extra-territorial scope of the GDPR without having to appoint a representative, the supervisory authority of the EU Member State in which the Data Subjects are predominantly located. In relation to Personal Data that is subject to the UK GDPR or Swiss DPA, the competent supervisory authority is the UK Information Commissioner or the Swiss Federal Data Protection and Information Commissioner (as applicable).
ANNEX II - SECURITY MEASURES
We currently observe the Security Measures described in this Annex II.
Virtual Access Control:
Technical and organisational measures to prevent data processing systems from being used by unauthorised persons include:
Only using well-established, reputable software/infrastructure such as AWS;
User identification and authentication procedures;
ID/password security procedures (special characters, minimum length, change of password);
Password managers;
Automatic blocking (e.g. password or timeout);
Owner policy for each application storing/processing data;
Monitoring of break-in-attempts and automatic turn-off of the user ID upon several erroneous passwords attempts;
Creation of one master record per user.
Data Access Control:
Technical and organisational measures to ensure that persons entitled to use a data processing system gain access only to such customer data in accordance with their access rights, and that customer data cannot be read, copied, modified or deleted without authorisation, include:
Paperless policy i.e. digital data only;
Only using well-established, reputable software/infrastructure such as AWS;
Internal policies and procedures;
Control authorisation schemes;
Differentiated access rights (profiles, roles, transactions and objects);
Monitoring and logging of accesses;
Disciplinary action against employees who access customer data without authorisation;
Change procedure;
Deletion procedure;
Encryption.
Disclosure Control:
Technical and organisational measures to ensure that customer data cannot be read, copied, modified or deleted without authorisation during electronic transmission, transport or storage on storage media (manual or electronic), and that it can be verified to which companies or other legal entities customer data are disclosed, include:
Encryption/tunneling;
Monitoring and logging;
Paperless policy;
Control authorisation procedures.
Entry Control:
Technical and organisational measures to monitor whether data have been entered, changed or removed (deleted), and by whom, from data processing systems, include:
Access control (see Virtual Access Control and Data Access Control);
Logging and reporting systems;
Audit trails and documentation.
Availability Control:
Technical and organisational measures to ensure that customer data are protected against accidental destruction or loss (physical/logical) include:
Only using well-established, reputable software/infrastructure such as AWS;
Backup procedures;
Remote storage;
Anti-virus/firewall systems.
Separation Control:
Technical and organisational measures to ensure that customer data collected for different purposes can be processed separately include:
Need-only storage of data;
Separation of databases/processing infrastructure;
Segregation of functions (e.g. production/testing.);
Procedures for storage, amendment, deletion, transmission of data for different purposes.
ANNEX III - LIST OF SUB-PROCESSORS
The controller has authorised the use of the following sub-processors:
Name
Address
Description
More information
Google Cloud Computing Services
A company incorporated in the United States with a place of business at 1600 Amphitheatre Parkway. Mountain View, CA 94043, United States.
Processing personal data owned or licenced by Controller of interviews for the purposes of speech recognition, recording analytics, interview insights, and customer analytics processing to the Controller by the Processor and sub-processed by Sub-Processor
Google Cloud Terms Directory (incl. Terms of Service, Data Processing Terms, and more)
Amazon Web Services EMEA SARL (“AWS Europe”)
A company incorporated in Luxembourg whose registered office is at 5 Rue Plaetis, 2338 Luxembourg.
Processing personal data owned or licenced by Controller of interviews for the purposes of delivering coaching tips, and analytics on the hiring process to the Controller by the Processor and sub-processed by Sub-Processor
AWS | Privacy
Postmark (Wildbit, LLC)
A company incorporated in the United States with a place of business at 225 Chestnut St., Philadelphia, PA, 19106, United States.
Allowing the Processor to send email notifications to customers in regards to interview recording, and insights, receiving notifications from the Screenloop platform e.g. email notifying the customer that a recorded interview is available on the Screenloop platform.
EU Data Protection | Postmark (postmarkapp.com) (incl. GDPR and sub-processors)
Data Processing Addendum | Wildbit
Segment | Terms of Service
Algolia, Inc.
A company incorporated in the United States with a place of business at 301 Howard St, 3rd floor, San Francisco, CA 94105, United States.
Collecting, sorting and transferring for the purposes of allowing the Controller to search data owned or licenced by Controller i.e. the technology used to provide a modern search function when searching across interviews, candidates, and jobs on the Screenloop platform.
EU Data Protection | Postmark (postmarkapp.com) (incl. GDPR and sub-processors)
Postmark’s GDPR Compliance
Postmark (Wildbit, LLC)
A company incorporated in the United States with a place of business at 225 Chestnut St., Philadelphia, PA, 19106, United States.
Allowing the Processor to send email notifications to customers in regards to interview recording, and insights, receiving notifications from the Screenloop platform e.g. email notifying the customer that a recorded interview is available on the Screenloop platform.
Terms of Service | Algolia
Security & Compliance | Algolia
What do you do about General Data Protection Regulation (GDPR)? – Algolia
Data Processing Addendum | Algolia
Intercom R&D Unlimited Company / Intercom, Inc.
Intercom R&D Unlimited Company, a company registered in Ireland with a registered address at 2nd Floor, Stephen Court, 18-21 Saint Stephen's Green, Dublin 2, and Intercom, Inc. a Delaware corporation with offices at 55 2nd Street, 4th Fl., San Francisco, CA 94105, United States.
Collecting, sorting and transferring for the purposes of allowing Screenloop to communicate with the Controller via chat or email.
Terms and Policies | Intercom
Data Processing Agreement | Intercom
Privacy Policy | Intercom
AssemblyAI, Inc.
A company incorporated in the US whose registered office is at 320 Judah Street, Suite 5 San Francisco CA 94122.
Processing personal data owned or licenced by Controller of interviews for the purposes of speech recognition, recording analytics, interview insights, and customer analytics processing to the Controller by the Processor and sub-processed by Sub-Processor.
AssemblyAI Speech-to-Text API | Privacy Policy
AssemblyAI Speech-to-Text API | Terms of Service
HubSpot, Inc.
A Delaware corporation, with a place of business at 25 First Street, 2nd Floor, Cambridge, MA 02141, United States.
Collecting, sorting and transferring for the purposes of allowing the Processor to manage the relationship and communication with the Customer.
HubSpot Privacy Policy
Data Processing Agreement (hubspot.com)
Customer Terms of Service (hubspot.com)
Synthesia Limited
A company whose registered office is at Kent House, 14/17 Market Place, London W1W 8AJ, United Kingdom.
Processing and hosting generic and bespoke interview training video presentations accessible to the Customer through the Screenloop platform.
Terms of Service I Synthesia
Data Processing Agreement I Synthesia
Slack Technologies, Inc.
A company whose registered office is at 4th Floor, One Park Place, Hatch Street Upper, Dublin 2, Ireland.
Company communication and content moderation management.
Customer terms of service | Legal | Slack
Privacy policy | Legal | Slack
Slack’s GDPR commitment | Legal | Slack
OpenAI
A company incorporated in the United States with a place of business at 3180 18th St, San Francisco, California, 94110, United States
Chat GPT (Machine Learning)
OpenAI Terms of Use
OpenAI Privacy Policy
OpenAI Service Terms
OpenAI DPAAll
OpenAI policies
Credence Background Screening Limited
A company incorporated in the United Kingdom with a place of business at 160 London Road, Sevenoaks, Kent, TN13 1BT, United Kingdom
Background Checks
Credence Terms of Use
Credence Privacy Policy
Certn (Canada) Inc.
A company incorporated in Canada with a place of business at 1006 Fort St Suite 300, Victoria, BC V8V 3K4, Canada
Background Checks
Certn Terms of Use
Certn Privacy Policy
StackOne Technologies Limited
A company incorporated in the United Kingdom with a place of business at Camburgh House, 27 New Dover Road, Canterbury, Kent, CT1 3DN
API Integrations
StackOne Terms of Service
Exhibit 2: International Data Transfer Addendum to the European Commission's New Standard Contractual Clauses
Version B1.0, in force 21 March 2022
This Addendum has been issued by the Information Commissioner for Parties making Restricted Transfers. The Information Commissioner considers that it provides Appropriate Safeguards for Restricted Transfers when it is entered into as a legally binding contract.
PART 1: TABLES
Table 1: Parties
See ANNEX I - A. LIST OF PARTIES.
Table 2: Selected SCCs, Modules and Selected Clauses
Addendum EU SCCs
The Approved EU SCCs, including the Appendix Information and with only the following modules, clauses or optional provisions of the Approved EU SCCs brought into effect for the purposes of this
Addendum:
Module in operation: Module II (Controller to Processor)
Clause 7: Yes. Included.
Clause 11: No. Not included.
Clause 9a (Sub-processor): General authorisation.
Clause 9a (Time period): 14 days.
Table 3: Appendix Information
“Appendix Information” means the information which must be provided for the selected modules as set out in the Appendix of the Approved EU SCCs (other than the Parties), and which for this Addendum is set out in:
Annex 1A: List of Parties: ANNEX I - A. LIST OF PARTIES
Annex 1B: Description of Transfer: ANNEX I - B. DESCRIPTION OF TRANSFER
Annex II: Technical and organisational measures including technical and organisational measures to ensure the security of the data: ANNEX II - SECURITY MEASURES
Annex III: List of Sub processors: ANNEX III - LIST OF SUB-PROCESSORS
Table 4: Ending this Addendum when the Approved Addendum Changes
Ending this Addendum when the Approved Addendum changes
Which Parties may end this Addendum as set out in Section 19:
☒ Importer
☒ Exporter
☐ neither Party
PART 2: MANDATORY CLAUSES
Entering into this Addendum
1. Each Party agrees to be bound by the terms and conditions set out in this Addendum, in exchange for the other Party also agreeing to be bound by this Addendum.
2. Although Annex 1A and Clause 7 of the Approved EU SCCs require signature by the Parties, for the purpose of making Restricted Transfers, the Parties may enter into this Addendum in any way that makes them legally binding on the Parties and allows data subjects to enforce their rights as set out in this Addendum. Entering into this Addendum will have the same effect as signing the Approved EU SCCs and any part of the Approved EU SCCs.
Interpretation of this Addendum
3. Where this Addendum uses terms that are defined in the Approved EU SCCs those terms shall have the same meaning as in the Approved EU SCCs. In addition, the following terms have the following meanings:
Addendum
This International Data Transfer Addendum which is made up of this Addendum incorporating the Addendum EU SCCs.
Addendum EU SCCs
The version(s) of the Approved EU SCCs which this Addendum is appended to, as set out in Table 2, including the Appendix Information.
Appendix Information
As set out in Table 3
Appropriate Safeguards
The standard of protection over the personal data and of data subjects’ rights, which is required by UK Data Protection Laws when you are making a Restricted Transfer relying on standard data protection clauses under Article 46(2)(d) UK GDPR.
Approved Addendum
The template Addendum issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18.
Approved EU SCCs
The Standard Contractual Clauses set out in the Annex of Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
ICO
The Information Commissioner.
Restricted Transfer
A transfer which is covered by Chapter V of the UK GDPR.
UK
The United Kingdom of Great Britain and Northern Ireland.
UK Data Protection Laws
All laws relating to data protection, the processing of personal data, privacy and/or electronic communications in force from time to time in the UK, including the UK GDPR and the Data Protection Act 2018.
UK GDPR
As defined in section 3 of the Data Protection Act 2018.
4. This Addendum must always be interpreted in a manner that is consistent with UK Data Protection Laws and so that it fulfils the Parties’ obligation to provide the Appropriate Safeguards.
5. If the provisions included in the Addendum EU SCCs amend the Approved SCCs in any way which is not permitted under the Approved EU SCCs or the Approved Addendum, such amendment(s) will not be incorporated in this Addendum and the equivalent provision of the Approved EU SCCs will take their place.
6. If there is any inconsistency or conflict between UK Data Protection Laws and this Addendum, UK Data Protection Laws applies.
7. If the meaning of this Addendum is unclear or there is more than one meaning, the meaning which most closely aligns with UK Data Protection Laws applies.
8. Any references to legislation (or specific provisions of legislation) means that legislation (or specific provision) as it may change over time. This includes where that legislation (or specific provision) has been consolidated, re-enacted and/or replaced after this Addendum has been entered into.
Hierarchy
9. Although Clause 5 of the Approved EU SCCs sets out that the Approved EU SCCs prevail over all related agreements between the parties, the parties agree that, for Restricted Transfers, the hierarchy in Section 10 will prevail.
10. Where there is any inconsistency or conflict between the Approved Addendum and the Addendum EU SCCs (as applicable), the Approved Addendum overrides the Addendum EU SCCs, except where (and in so far as) the inconsistent or conflicting terms of the Addendum EU SCCs provides greater protection for data subjects, in which case those terms will override the Approved Addendum.
11. Where this Addendum incorporates Addendum EU SCCs which have been entered into to protect transfers subject to the General Data Protection Regulation (EU) 2016/679 then the Parties acknowledge that nothing in this Addendum impacts those Addendum EU SCCs.
Incorporation of and changes to the EU SCCs
12. This Addendum incorporates the Addendum EU SCCs which are amended to the extent necessary so that:
together they operate for data transfers made by the data exporter to the data importer, to the extent that UK Data Protection Laws apply to the data exporter’s processing when making that data transfer, and they provide Appropriate Safeguards for those data transfers;
Sections 9 to 11 override Clause 5 (Hierarchy) of the Addendum EU SCCs; and
this Addendum (including the Addendum EU SCCs incorporated into it) is (1) governed by the laws of England and Wales and (2) any dispute arising from it is resolved by the courts of England and Wales, in each case unless the laws and/or courts of Scotland or Northern Ireland have been expressly selected by the Parties.
13. Unless the Parties have agreed alternative amendments which meet the requirements of Section 12, the provisions of Section 15 will apply.
14. No amendments to the Approved EU SCCs other than to meet the requirements of Section 12 may be made.
15. The following amendments to the Addendum EU SCCs (for the purpose of Section 12) are made:
References to the “Clauses” means this Addendum, incorporating the Addendum EU SCCs;
In Clause 2, delete the words:
“and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679”;Clause 6 (Description of the transfer(s)) is replaced with:
“The details of the transfers(s) and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred) are those specified in Annex I.B where UK Data Protection Laws apply to the data exporter’s processing when making that transfer.”;Clause 8.7(i) of Module 1 is replaced with:
“it is to a country benefitting from adequacy regulations pursuant to Section 17A of the UK GDPR that covers the onward transfer”;Clause 8.8(i) of Modules 2 and 3 is replaced with:
“the onward transfer is to a country benefitting from adequacy regulations pursuant to Section 17A of the UK GDPR that covers the onward transfer;”References to “Regulation (EU) 2016/679”, “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 (General Data Protection Regulation)” and “that Regulation” are all replaced by “UK Data Protection Laws”. References to specific Article(s) of “Regulation (EU) 2016/679” are replaced with the equivalent Article or Section of UK Data Protection Laws;
References to Regulation (EU) 2018/1725 are removed;
References to the “European Union”, “Union”, “EU”, “EU Member State”, “Member State” and “EU or Member State” are all replaced with the “UK”;
The reference to “Clause 12(c)(i)” at Clause 10(b)(i) of Module one, is replaced with “Clause 11(c)(i)”;
Clause 13(a) and Part C of Annex I are not used;
The “competent supervisory authority” and “supervisory authority” are both replaced with the “Information Commissioner”;
In Clause 16(e), subsection (i) is replaced with:
“the Secretary of State makes regulations pursuant to Section 17A of the Data Protection Act 2018 that cover the transfer of personal data to which these clauses apply;”;Clause 17 is replaced with:
“These Clauses are governed by the laws of England and Wales.”;Clause 18 is replaced with:
“Any dispute arising from these Clauses shall be resolved by the courts of England and Wales. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of any country in the UK. The Parties agree to submit themselves to the jurisdiction of such courts.”; andThe footnotes to the Approved EU SCCs do not form part of the Addendum, except for footnotes 8, 9, 10 and 11.
Amendments to this Addendum
16. The Parties may agree to change Clauses 17 and/or 18 of the Addendum EU SCCs to refer to the laws and/or courts of Scotland or Northern Ireland.
17. If the Parties wish to change the format of the information included in Part 1: Tables of the Approved Addendum, they may do so by agreeing to the change in writing, provided that the change does not reduce the Appropriate Safeguards.
18. From time to time, the ICO may issue a revised Approved Addendum which:
makes reasonable and proportionate changes to the Approved Addendum, including correcting errors in the Approved Addendum; and/or
reflects changes to UK Data Protection Laws;
The revised Approved Addendum will specify the start date from which the changes to the Approved Addendum are effective and whether the Parties need to review this Addendum including the Appendix Information. This Addendum is automatically amended as set out in the revised Approved Addendum from the start date specified.
19. If the ICO issues a revised Approved Addendum under Section 18, if any Party selected in Table 4 “Ending the Addendum when the Approved Addendum changes”, will as a direct result of the changes in the Approved Addendum have a substantial, disproportionate and demonstrable increase in:
its direct costs of performing its obligations under the Addendum; and/or
its risk under the Addendum,
and in either case it has first taken reasonable steps to reduce those costs or risks so that it is not substantial and disproportionate, then that Party may end this Addendum at the end of a reasonable notice period, by providing written notice for that period to the other Party before the start date of the revised Approved Addendum.
20. The Parties do not need the consent of any third party to make changes to this Addendum, but any changes must be made in accordance with its terms.
