Data Processing Addendum

DPA Terms

1. What is this agreement about?

1.1.
Purpose. The parties are entering into this Data Processing Agreement (‘DPA’) for the purpose of processing Personal Data (as defined in the DPA Variables section above).
1.2
Definitions. Under this DPA:
1.2.1
adequate country means a country or territory that is recognised under Data Protection Laws from time to time as providing adequate protection for processing Personal Data, and
1.2.2
Controller, data subject, personal data breach, process/processing, Processor and supervisory authority have the same meanings as in the Data Protection Laws; and
1.2.3
Business and Service Provider have the same meanings as in the CCPA/CPRA; and
1.2.4
Sub-Processor means another processor engaged by the Processor to carry out specific processing activities with Personal Data.

2. What are each party’s obligations?

2.1.
Controller obligations. Controller instructs Processor to process Personal Data in accordance with this DPA, and is responsible for providing all notices and obtaining all consents, licences and legal bases required to allow Processor to process Personal Data.
2.2.
Processor/Sub-Processor obligations. Processor will:
2.2.1.
only process Personal Data in accordance with this DPA and Controller’s instructions (unless legally required to do otherwise);
2.2.2.
not sell, retain or use any Personal Data for any purpose other than as permitted by this DPA and the Main Agreement;
2.2.3.
inform Controller immediately if (in its opinion) any instructions infringe Data Protection Laws;
2.2.4.
use the technical and organisational measures described in Annex I when processing Personal Data to ensure a level of security appropriate to the risk involved;
2.2.5.
notify Controller of a Personal Data breach within the Breach Notification Period and provide assistance to Controller as required under Data Protection Laws in responding to it, as set out in more detail in clauses 6.2. to 6.5.;
2.2.6.
ensure that anyone authorised to process Personal Data is committed to confidentiality obligations;
2.2.7.
without undue delay, provide Controller with reasonable assistance with:
2.2.7.1.
data protection impact assessments;
2.2.7.1.
responses to data subjects’ requests to exercise their rights under Data Protection Laws in accordance with clause 6.3.; and 
2.2.7.1.
engagement with supervisory authorities;
2.2.8.
if requested, provide Controller with information necessary to demonstrate its compliance with obligations under Data Protection Laws and the DPA;
2.2.9.
allow for audits at Controller’s request, if the requirements of clause 7 are met; and
2.2.10.
return Personal Data upon Controller’s written request or delete Personal Data by the end of the Term, unless retention is legally required.
2.3.
Warranties. The parties warrant that they and any staff and/or subcontractors will comply with their respective obligations under Data Protection Laws for the Term.

3. Sub-processing

3.1.
Use of sub-processors. Controller authorises Processor engage other processors (referred to in this section as Sub-Processors) when processing Personal Data. Processor’s existing Sub-Processors are listed in Annex II.
3.2.
Sub-processor requirements. Processor will: 
3.2.1.
require its Sub-Processors to comply with equivalent terms as Processor’s obligations in this DPA;
3.2.2.
ensure appropriate safeguards are in place before internationally transferring Personal Data to its Sub-Processor; and
3.2.3.
be liable for any acts, errors or omissions of its Sub-Processors as if they were a party to this DPA.
3.3.
Approvals. Processor may appoint new Sub-Processors provided that they notify the Controller in writing in accordance with the Sub-Processor Notification Period.
3.4.
Objections. Controller may reasonably object in writing to any future sub-processor. If the parties cannot agree on a solution within a reasonable time, either party may terminate this DPA.

4. International Personal Data transfers

4.1.
Instructions. Processor will transfer Personal Data outside the UK, the EEA or an adequate country only on documented instructions from Controller, unless otherwise required by law.
4.2.
Transfer mechanism. Where a party is located outside the UK, the EEA or an adequate country and receives Personal Data: 
4.2.1.
that party will act as the data importer;
4.2.2.
the other party is the data exporter; and
4.2.3.
the relevant Transfer Mechanism will apply.
4.3.
Additional measures. If the Transfer Mechanism is insufficient to safeguard the transferred Personal Data, the data importer will promptly implement supplementary measures to ensure Personal Data is protected to the same standard as required under Data Protection Laws.
4.4.
Disclosures. Subject to terms of the relevant Transfer Mechanism, if the data importer receives a request from a public authority to access Personal Data, it will (if legally allowed):
4.4.1.
challenge the request and promptly notify the data exporter about it; and
4.4.2.
only disclose to the public authority the minimum amount of Personal Data required and keep a record of the disclosure. 

5. Other important information

5.1.
Survival. Any provision of this DPA which is intended to survive the Term will remain in full force.
5.2.
Order of precedence. In case of a conflict between this DPA and other relevant agreements, they will take priority in this order: 
5.2.1.
Transfer Mechanism;
5.2.2.
DPA; and
5.2.3.
Main Agreement.
5.3.
Notices. Formal notices under this DPA must be in writing and sent to the Contact on the DPA’s front page as may be updated by a party to the other in writing.
5.4.
Third parties. Except for affiliates, no one other than a party to this DPA has the right to enforce any of its terms.
5.5.
Entire agreement. This DPA supersedes all prior discussions and agreements and constitutes the entire agreement between the parties with respect to its subject matter (i.e. data protection) and neither party has relied on any statement or representation of any person in entering into this DPA.
5.6.
Amendments. Any amendments to this DPA must be agreed in writing.
5.7.
Assignment. Neither party can assign this DPA to anyone else without the other party's consent. 
5.8.
Waiver. If a party fails to enforce a right under this DPA, that is not a waiver of that right at any time.
5.9.
Governing law and jurisdiction. The Governing Law applies to this DPA and all disputes will only be litigated in the courts of the Jurisdiction.

6. Privacy and security

6.1.
Controller’s  Privacy Requirements. Without limiting any other clause of the DPA or the Main Agreement:
6.1.1.
Controller must publish a privacy policy that complies with applicable Data Protection Laws; and
6.1.2.
Controller is responsible for the accuracy, quality, integrity and legality of its Data (including Personal Data) and the means by which Controller acquired its Data (including ensuring a legal basis for collection and sharing of Personal Data with the Processor before transferring to Processor).
6.2.
Processor’s Privacy Requirements: Without limiting any other clause of the DPA or the Main Agreement:
6.2.1.
Processor must, in respect of all Personal Data held in connection with the DPA or the Main Agreement, comply with any reasonable requests or directions issued by Controller from time to time arising from the exercise of the functions of any privacy regulator;
6.2.2.
Processor must not, in respect of any Personal Data held in connection with the DPA, without the prior written approval of Controller (including in the Main Agreement): 
6.2.2.1.
disclose, transfer or permit the disclosure or transfer outside of the information outside of the data location specified (if any) in the Main Agreement; or
6.2.2.1.
allow or permit access to any such information by any person outside of the data location specified (if any) in the Main Agreement.
6.3.
Complaints handling:  We must inform You within the Breach Notification Period:
6.3.1.
if a request is received from a data subject to inspect, access or change Personal Data relating to that person; or
6.3.2.
of any privacy complaints received from a data subject or any events relating to Personal Data which may cause the Data Protection Laws to be breached, and comply with the reasonable directions of Controller regarding any request or complaint received.
6.4.
Mandatory Data Breach Protection: If Processor becomes aware of, or has a reasonable suspicion that there has been any unauthorised access to, or disclosure or loss of, any Personal Data that has been collected from or on behalf of Controller, directly or indirectly, pursuant to the DPA or the Main Agreement, Processor must notify Controller immediately ('Breach'). In the event of a Breach, Processor must:
6.4.1.
cooperate with Controller or any appointed authority in relation to any ensuing investigation or enquiry relating to the Breach;
6.4.2.
cooperate with Controller or any appointed authority in relation to the preparation of any determination, statement or notice regarding the Breach, and any notifications to affected individuals; and
6.4.3.
cooperate with Controller or any appointed authority in relation to the provision of information surrounding the circumstances of the Breach, such information which should include: the Personal Data in question; the data subjects that are likely to be affected by the Breach; details of the security measures in place and how these may be improved; and all other information relevant for an investigation.
6.4.4.
Processor must follow Controller’s reasonable directions in relation to any interactions We have with any individuals who may be potentially potentially affected by a Breach or a notification under clause 6.5.
6.5.
Notification processes:
6.5.1.
In the event of a disagreement between You and Us as to whether or not a Notification should be provided, the disagreeing Party must provide written notice of the basis of its disagreement to the other Party. The Parties must act in good faith to agree on whether or not to provide the Notification.
6.5.2.
If a party reasonably believes there is a legal requirement to submit a Notification, following the process set out in clause 6.7.1 above, either party may elect to provide a Notification, with written notice to the other party.

7. Audit

7.1.
SOC 2 report. Controller acknowledges that Processor is regularly audited against SOC 2 standards by an independent third-party auditor. Controller acknowledges that a recent SOC 2 audit report will, unless clause 7.2. or 7.3. applies,, satisfy any requirement of the Controller with respect to a request to conduct an audit of Processor.
7.2.
Breach as exceptional circumstances. In the event of a Breach as defined in clause 6.4., Controller may request an audit of Processor’s security and data processing practices.
7.3.
Conditions on audits. If Controller requires an audit of Processor’s practices which does not fall under clauses 7.1. or 7.2. above, Controller may request an audit of Processor’s practices, provided:
7.3.1.
audits are limited to once a year, conducted during business hours; and
7.3.2.
Controller reimburses Processor for its reasonable costs in participating in the audit (including internal resources at Processor’s hourly rate).