Data Processing Agreement

Last updated: Dec 20, 2022

Note: This data processing agreement is based on the Standard Contractual Clauses between Controllers and Processors in the EU under Article 28 (7) of Regulation (EU) 2016/679 of the European Parliament and of the Council and Article 29 (7) of Regulation (EU) 2018/1725 of the European Parliament and of the Council issued by the EU Commission on June 4, 2021 (Implementing Decision C(2021) 3701). As required pursuant to Section I, Clause 2 (a), the Clauses have not been modified by Decentriq. However, where the Clauses present a choice between different options, the non-applicable option has been deleted. Option choices are made transparent with footnotes. Further, in Section II, Clause 7.7 (a), the notification period for changes in the List of Sub-Processors has been set to 3 months. Annex I references the parties of the main agreement under which Decentriq provides its services as a Processor under these Clauses. Annexes II – IV reference additional information, including information published by Decentriq on its online resources, such as detailed processing descriptions, technical and organizational measures and the list of sub-processors. An additional Annex V has been added for processing under these Clauses that does not fall under the territorial scope 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.

STANDARD CONTRACTUAL CLAUSES

SECTION I

Clause 1: Purpose and scope 

  1. The purpose of these Standard Contractual Clauses (the Clauses) is to ensure compliance with Article 28(3) and (4) 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.
  2. The controllers and processors listed in Annex I have agreed to these Clauses in order to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 and/or Article 29 (3) and (4) Regulation (EU) 2018/1725. 
  3. These Clauses apply to the processing of personal data as specified in Annex II.
  4. Annexes I to IV are an integral part of the Clauses.
  5. These Clauses are without prejudice to obligations to which the controller is subject by virtue of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. 
  6. These Clauses do not by themselves ensure compliance with obligations related to international transfers in accordance with Chapter V of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

Clause 2: Invariability of the Clauses 

  • The Parties undertake not to modify the Clauses, except for adding information to the Annexes or updating information in them.
  • This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a broader contract, or from adding other clauses or additional safeguards provided that they do not directly or indirectly contradict  the Clauses or detract from the fundamental rights or freedoms of data subjects.

Clause 3: Interpretation

  • Where these Clauses use the terms defined in Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively, 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 or Regulation (EU) 2018/1725 respectively.
  • These Clauses shall not be interpreted in a way that runs counter to the rights and obligations provided for in Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or in a way that prejudices the fundamental rights or freedoms of the data subjects.

Clause 4: Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties existing at the time when these Clauses are agreed or entered into thereafter, these Clauses shall prevail. 

Clause 5 - Optional: Docking clause

  • Any entity that is not a Party to these Clauses may, with the agreement of all the Parties, accede to these Clauses at any time as a controller or a processor by completing the Annexes and signing Annex I.
  • Once the Annexes in (a) are completed and signed, the acceding entity shall be treated as a Party to these Clauses and have the rights and obligations of a controller or a processor, in accordance with its designation in Annex I.
  • The acceding entity shall have no rights or obligations resulting from these Clauses from the period prior to becoming a Party.

SECTION II – OBLIGATIONS OF THE PARTIES

Clause 6: Description of processing(s)

The details of the processing operations, in particular the categories of personal data and the purposes of processing for which the personal data is processed on behalf of the controller, are specified in Annex II.

Clause 7: Obligations of the Parties 

7.1. Instructions

  • The processor shall process personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. In this case, the processor shall inform the controller of that legal requirement before processing, unless the law prohibits this on important grounds of public interest. Subsequent instructions may also be given by the controller throughout the duration of the processing of personal data. These instructions shall always be documented. 
  • The processor shall immediately inform the controller if, in the processor’s opinion, instructions given by the controller infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the applicable Union or Member State data protection provisions.

7.2. Purpose limitation

The processor shall process the personal data only for the specific purpose(s) of the processing, as set out in Annex II, unless it receives further instructions from the controller.

7.3. Duration of the processing of personal data

Processing by the processor shall only take place for the duration specified in Annex II. 

7.4. Security of processing

  • The processor shall at least implement the technical and organisational measures specified in Annex III to ensure the security of the personal data. This includes protecting the data against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to the data (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 purposes of processing and the risks involved for the data subjects. 
  • The processor shall grant access to the personal data undergoing processing to members of its personnel only to the extent strictly necessary for implementing, managing and monitoring of the contract. The processor shall ensure that persons authorised to process the personal data received have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. 

7.5. Sensitive data

If the processing 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 (“sensitive data”), the processor shall apply specific restrictions and/or additional safeguards.

7.6 Documentation and compliance

  • The Parties shall be able to demonstrate compliance with these Clauses.
  • The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with these Clauses.  
  • The processor shall make available to the controller all information necessary to demonstrate compliance with the obligations that are set out in these Clauses and stem directly from Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. At the controller’s request, the processor shall also permit 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 an audit, the controller may take into account relevant certifications held by the processor.    
  • The controller may choose to conduct the audit by itself or mandate an independent auditor. Audits may also include inspections at the premises or physical facilities of the processor and shall, where appropriate, be carried out with reasonable notice. 
  • The Parties shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority/ies on request.

7.7. Use of sub-processors

  • The processor has the controller’s general authorisation for the engagement of sub-processors from an agreed list. The processor shall specifically inform in writing the controller of any intended changes of that list through the addition or replacement of sub-processors at least 3 months in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the concerned sub-processor(s). The processor shall provide the controller with the information necessary to enable the controller to exercise the right to object.
  • Where the processor engages a sub-processor for carrying out specific processing activities (on behalf of the controller), it shall do so by way of a contract which imposes on the sub-processor, in substance, the same data protection obligations as the ones imposed on the data processor in accordance with these Clauses. The processor shall ensure that the sub-processor complies with the obligations to which the processor is subject pursuant to these Clauses and to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
  • At the controller’s request, the processor shall provide a copy of such a sub-processor agreement and any subsequent amendments to the controller. To the extent necessary to protect business secret or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.
  • The processor shall remain fully responsible to the controller for the performance of the sub-processor’s obligations in accordance with its contract with the processor. The processor shall notify the controller of any failure by the sub-processor to fulfil its contractual obligations.
  • The processor shall agree a third party beneficiary clause with the sub-processor whereby - in the event the processor has factually disappeared, ceased to exist in law or has become insolvent - the controller shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

7.8. International transfers

  • Any transfer of data to a third country or an international organisation by the processor shall be done only on the basis of documented instructions from the controller or in order to fulfil a specific requirement under Union or Member State law to which the processor is subject and shall take place in compliance with Chapter V of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725. 
  • The controller agrees that where the processor engages a sub-processor in accordance with Clause 7.7. for carrying out specific processing activities (on behalf of the controller) and those processing activities involve a transfer of personal data within the meaning of Chapter V of Regulation (EU) 2016/679, the processor and the sub-processor can ensure compliance with Chapter V of Regulation (EU) 2016/679 by using standard contractual clauses adopted by the Commission in accordance with of Article 46(2) of Regulation (EU) 2016/679, provided the conditions for the use of those standard contractual clauses are met.

Clause 8: Assistance to the controller 

  • The processor shall promptly notify the controller of any request it has received from the data subject. It shall not respond to the request itself, unless authorised to do so by the controller.
  • The processor shall assist the controller in fulfilling its obligations to respond to data subjects’ requests to exercise their rights, taking into account the nature of the processing. In fulfilling its obligations in accordance with (a) and (b), the processor shall comply with the controller’s instructions
  • In addition to the processor’s obligation to assist the controller pursuant to Clause 8(b), the processor shall furthermore assist the controller in ensuring compliance with the following obligations, taking into account the nature of the data processing and the information available to the processor:
    • the obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a ‘data protection impact assessment’) where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons;
    • the obligation to consult the competent supervisory authority/ies prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk;
    • the obligation to ensure that personal data is accurate and up to date, by informing the controller without delay if the processor becomes aware that the personal data it is processing is inaccurate or has become outdated;
    • the obligations in Article 32 Regulation (EU) 2016/679.
  • The Parties shall set out in Annex III the appropriate technical and organisational measures by which the processor is required to assist the controller in the application of this Clause as well as the scope and the extent of the assistance required. 

Clause 9: Notification of personal data breach

In the event of a personal data breach, the processor shall cooperate with and assist the controller for the controller to comply with its obligations under Articles 33 and 34 Regulation (EU) 2016/679 or under Articles 34 and 35 Regulation (EU) 2018/1725, where applicable, taking into account the nature of processing and the information available to the processor.

9.1 Data breach concerning data processed by the controller

In the event of a personal data breach concerning data processed by the controller, the processor shall assist the controller:

  • in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the controller has become aware of it, where relevant/(unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons); 
  • in obtaining the following information which, pursuant to Article 33(3) Regulation (EU) 2016/679, shall be stated in the controller’s notification, and must at least include:   
    • the nature of the personal data including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned; 
    • the likely consequences of the personal data breach;  
    • the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects. 

Where, and insofar as, it is not possible to provide all this 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.

  • in complying, pursuant to Article 34 Regulation (EU) 2016/679, with the obligation to communicate without undue delay the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons.

9.2 Data breach concerning data processed by the processor

In the event of a personal data breach concerning data processed by the processor, the processor shall notify the controller without undue delay after the processor having become aware of the breach. Such notification shall contain, at least:

  • a description of the nature of the breach (including, where possible, the categories and approximate number of data subjects and data records concerned);
  • the details of a contact point where more information concerning the personal data breach can be obtained;
  • its likely consequences and the measures taken or proposed to be taken to address the breach, including to mitigate its possible adverse effects.

Where, and insofar as, it is not possible to provide all this 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 Parties shall set out in Annex III all other elements to be provided by the processor when assisting the controller in the compliance with the controller’s obligations under Articles 33 and 34 of Regulation (EU) 2016/679.

SECTION III – FINAL PROVISIONS

Clause 10: Non-compliance with the Clauses and termination

  • Without prejudice to any provisions of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725, in the event that the processor is in breach of its obligations under these Clauses, the controller may instruct the processor to suspend the processing of personal data until the latter complies with these Clauses or the contract is terminated. The processor shall promptly inform the controller in case it is unable to comply with these Clauses, for whatever reason.
  • The controller shall be entitled to terminate the contract insofar as it concerns processing of personal data in accordance with these Clauses if:
    • the processing of personal data by the processor has been  suspended by the controller pursuant to point (a) and if compliance with these Clauses is not restored within a reasonable time and in any event within one month following suspension;
    • the processor is in substantial or persistent breach of these Clauses or its obligations under Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725; 
    • the processor fails to comply with a binding decision of a competent court or the competent supervisory authority/ies regarding its obligations pursuant to these Clauses or to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
  • The processor shall be entitled to terminate the  contract insofar as it concerns processing of personal data under these Clauses where, after having informed the controller that its instructions infringe applicable legal requirements in accordance with Clause 7.1 (b), the controller insists on compliance with the instructions.
  • Following termination of the contract, the processor shall, at the choice of the controller, delete all personal data processed on behalf of the controller and certify to the controller that it has done so, or, return all the personal data to the controller and delete existing copies unless Union or Member State law requires storage of the personal data. Until the data is deleted or returned, the processor shall continue to ensure compliance with these Clauses.

ANNEX I LIST OF PARTIES

Processor(s) 

dq technologies AG, Josefstr. 219, 8005 Zurich, Switzerland (Decentriq)

Controller(s)

The relevant company(ies) or organisation(s) using the data analytics service provided by Decentriq.* 

*These Clauses either form integral part of the agreement under which Decentriq provides its data analytics service to the Controller(s). If there is no such agreement, the Controler had to accept these Clauses prior to any processing of personal data on data analytics service provided by Decentriq.

ANNEX II: DESCRIPTION OF THE PROCESSING

Categories of data subjects whose personal data is processed

  • The categories of data subjects whose personal data is processed are solely determined by the Controller and vary depending on the specific use-case.
  • Where the Controller requires contractual documentation of the relevant categories of data subjects, the parties shall execute an addendum to this Annex II.
  • For certain use-cases, Decentriq provides detailed standard descriptions.

Categories of personal data processed

  • The categories of personal data processed are solely determined by the Controller and vary depending on the specific use-case.
  • Where the Controller requires contractual documentation of the relevant categories of personal data, the parties shall execute an addendum to this Annex II.
  • For certain use-cases, Decentriq provides detailed standard descriptions.

Sensitive data processed

Sensitive data processed(if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures.

  • Decentriq provides the same restrictions and safeguards for any types of data processed under these Clauses. 
  • In particular, data are encrypted and protected by confidential computing at all times and only the encryption keys for Controller data are under the Controller’s sole and exclusive control.
  • Decentriq staff do not have access to unencrypted Controller data or the keys to decrypt that data.

Nature of the processing

  • Decentriq provides a data analytics service that the Controller can use for broad range of purposes determined solely by the Controller itself or by the Controller together with one or more third parties. 
  • This section provides a generic high-level description of the processing without taking into consideration the specificities and details of individual use-cases.
  • Where the Controller requires contractual documentation of the specific nature of the processing in light of the individual use-case(s), the parties shall execute an addendum to this Annex II.
  • For certain use-cases, Decentriq provides detailed standard descriptions.

Step 1 – Local encryption and upload

Prior to any data processing by Decentriq under these Clauses, the Controller locally encrypts its data with a locally generated (or provided) encryption key only known to the Controller itself. This is ensured by the interfaces provided by Decentriq.

The encrypted data is then uploaded to the Decentriq platform. The encryption keys remain with the Controller at this step.

Step 2 – DCR configuration and data provisionning

The Controller or a third party the Controller has chosen to collaborate with through Decentriq configures a new Data Clean Room (DCR).

The DCR configuration determines:

  1. the functionality of the DCR (i.e. what exact computations can be run on the Controller’s data in the DCR); and 
  2. the authorizations associated with the DCR (i.e. who can perform computations and who can receive results from such computations).

Decentriq provides fully configurable DCRs for advanced users and partially pre-configured DCRs delivering easy-to-use functionality for certain specific use cases (e.g. marketing insights, lookalike modelling, re-marketing). 

Subject to the Controller’s approval, the DCR configuration is deemed a processing instruction under Section 7.1(a) of the Clauses. This includes configurations entirely made by the Controller itself, configurations made by any third party the Controller has chosen to collaborate with through Decentriq and pre-configurations provided by Decentriq. Any pre-configurations made available by Decentriq are fully documented and transparent to the Controller, including underlying software code.

If the Controller approves the DCR configruation, it can provision its data by sharing its encryption keys with this DCR. The keys are transmitted through an end-to-end encrypted channel. Due to confidential computing, the keys remain inaccessible to all parties, including Decentriq and any third party the Controller has chose to collaborate with thorugh Decentriq. By design, these keys can only be used to decrypt the Controller’s data in the context of this DCR (i.e. to execute the computations that form part of the DCR configuration and to deliver the results to authorized recipients thereof in accordance with the DCR configuration).

Step 3 – Executing computations

Once the Controller has provisioned its data to the DCR, the authorized users can execute the approved computations on the Controller’s data.

Where the Controller uses any of the partially pre-configured DCRs provided by Decentriq (see Step 2 above), this may include training one or more machine learning models on the Controller’s data, including to assess model quality on behalf of the Controller and provide the Controller with results based on the best performing model.

The execution computations that form part of the DCR configuration is deemed a processing instruction under Section 7.1(a) of the Clauses.

The Decentriq platform ensures that only the approved computations can be executed in the context of the DCR.

Step 4 – Output delivery

The output of the computations can be accessed by or may be automatically delivered to the authorized recipients.

The delivery of output to authorized reciptients in accordance with the DCR configuration is deemed a processing instruction under Section 7.1(a) of the Clauses.

The Decentriq platform technically ensures that only the authorized recipients can receive the results of approved computations.

Step 5 – DCR decommissioning and data deletion

The Controller can decommission its DCRs and/or delete its data from the Decentriq platform anytime.

Once a DCR has been decommissioned, the Controller’s data and any output derived from such data are no longer accessible on the Decentriq platform, neither to the Controller or to any party previously authrized by the Controller. The data remains on the Decentriq platform for further use in any other DCR, subject to Steps 2 – 4 above.

Once the Controller deleted its data from the Decentriq platform, it can no longer be used in any DCR and all derived results cannot be accessed anymore (unless they have been previously exported by the authorized recipients). In that case, if the Controller wants to use the data in a DCR, it needs to re-upload the data as described in Step 1.

DCR decommissioning and/or data deletion are deemed processing instructions under Section 7.1(a) of the Clauses.

Purpose(s) for which the personal data is processed on behalf of the controller

  • The purposes of the processing are solely determined by the Controller and vary depending on the specific use-case.
  • Where the Controller requires contractual documentation of the specific purpose(s) for which it uses Decentriq, the parties shall execute an addendum to this Annex II.
  • For certain use-cases, Decentriq provides detailed standard descriptions.

Duration of the processing

  • The duration of the processing is solely determined by the Controller and varies depending on the specific use-case. Generally, Decentriq processes the Controller’s data for as long as it remains on the Decentriq platform (i.e. until the Controller deletes its data as described in the section Nature of the processing under Step 6).
  • Where the Controller requires contractual documentation of the specific duration of the processing, the parties shall execute an addendum to this Annex II.
  • For certain use-cases, Decentriq provides detailed standard descriptions.

For processing by (sub-) processors, also specify subject matter, nature and duration of the processing

For information on processing by (sub-)processors, see Annex IV below. The duration of the processing by (sub-)processors is the same as the duration of the processing by Decentriq itself as described in the section Duration of the processing above.

ANNEX III TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA

The technical and organizational measures implemented by Decentriq are described in the Decentriq Trust Center at https://trust.decentriq.com

Note: Additional details on specific measures, in particular, Decentriq’s technical implementation of confidential computing technology to encrypt personal data processed on behalf of the Controller under these Clauses are available on request.

ANNEX IV: LIST OF SUB-PROCESSORS

Sub-Processors utilized by Decentriq for any processing activities under these Clauses are published at https://decentriq.com/legal/processing-locations.

Note: The list reflects processing activities for which Decentriq acts as a processor and utilizes sub-processors as well as processing activities for which Decentriq acts as a controller and utilizes processors. Sub-processors and processors are marked accordingly. Only sub-processors utilized by Decentriq in the context of processing activities for which Decentriq acts as a processor are in-scope of these Clauses. Processing activities for which Decentriq acts as a controller are not in-scope of these Clauses but governed by Decentriq’s Privacy Policy published at https://www.decentriq.com/legal/privacy-policy.

ANNEX V: NON-EU/EEA RIDER

Where the processing under these Clauses does not fall under the territorial scope 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, these Clauses shall be read and interpreted in the light of the provisions of the data protection laws applicable to the processing hereunder. In no event, these Clauses shall be interpreted in a way that prejudices the fundamental rights or freedoms of the data subjects.