This Data Processing Addendum (“DPA”) forms part of the Terms of Service (“Terms”) between Rithum Corporation (or the applicable Rithum Corporation Affiliate identified in an Order Form that incorporates the Terms), acting on its own behalf and as agent for each Rithum Corporation Affiliate as may be applicable (collectively, “Rithum”), and Customer for the purchase of Services from Rithum (identified either as “Services” or otherwise in the Terms or an applicable Order Form, and hereinafter defined as “Services”) to reflect the parties’ agreement with regard to the Processing of Personal Data. For the avoidance of doubt, each reference to the DPA in this DPA means this DPA including its Schedules and Appendices.

Customer enters into this DPA on behalf of itself and, to the extent required under applicable Data Protection Laws and Regulations, in the name and on behalf of its Authorized Affiliates, if and to the extent Rithum processes Personal Data for which such Authorized Affiliates qualify as the Controller. For the purposes of this DPA only, and except where indicated otherwise, the term “Customer” shall include Customer and Authorized Affiliates. All capitalized terms not defined herein shall have the meaning set forth in the Terms or the applicable Data Protection Laws and Regulations.

In the course of providing the Services to Customer pursuant to the Terms, Rithum may Process Personal Data on behalf of Customer and the parties agree to comply with the following provisions with respect to any Personal Data, each acting reasonably and in good faith.

This DPA shall be effective as of the effective date of the Terms (“Effective Date”).

DATA PROCESSING TERMS

1. DEFINITIONS
“Affiliate” means any entity that directly or indirectly controls, is controlled by, or is under common control with a party. “Control,” for purposes of this definition, means direct or indirect ownership or control of more than 50% of the voting interests of a party.

“Authorized Affiliate” means any of Customer’s Affiliate(s) which (a) is subject to applicable Data Protection Laws and Regulations, and (b) is permitted to use the Services pursuant to the Terms between Customer and Rithum, and has signed its own Statement of Work with Rithum.

“Rithum Standard Business Hours” means 9:00 am-5:00 pm EDT, Monday through Friday, excluding holiday hours (which may vary based on time zone and geographic location).

“CCPA” means the California Consumer Privacy Act of 2018, Cal. Civ. Code §§ 1798.100 et seq., as amended, and its implementing regulations.

“Controller” means the entity which determines the purposes and means of the Processing of Personal Data, and in the case of the Services provided under the Terms, “Controller” means “Customer.”

“Data Protection Laws and Regulations” means all laws, rules, and regulations applicable to the Processing of Personal Data under the Terms, including without limitation, the GDPR, UK GDPR, CCPA, and the data protection laws of any other country, state, or territory which apply to such Processing.

“Data Subject” means the identified or identifiable person to whom Personal Data relates.

“EEA SCCs” means the standard contractual clauses set out in the European Implementing Decision (EU) 2021/914 on standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679, as updated, amended, replaced or superseded from time to time by the European Commission.

“GDPR” means the Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation).

“Personal Data” means any information provided by Customer or that Customer directs Processor to collect and process on Customer’s behalf for the purpose of performing the Services relating to (i) an identified or identifiable natural person and, (ii) an identified or identifiable legal entity (where such information is protected similarly as personal data or personally identifiable information under applicable Data Protection Laws and Regulations).

“Processing” means any operation or set of operations which is performed upon Personal Data, whether or not by automatic means, such as collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.

“Processor” means the entity which Processes Personal Data on behalf of the Controller, and in the case of the Services provided under the Terms, “Processor” means “Rithum.”

“Regulatory Authority” means the government agency, department or other competent organization given authority over the Processing of Personal Data relevant to this Terms, including, as applicable, as independent public authority an independent public authority which is (i) established by a European Union Member State pursuant to Article 51 of the GDPR; or (ii) the public authority governing data protection, which has supervisory authority and jurisdiction over Customer.

“Restricted Transfer” means a transfer of Personal Data from Customer to Rithum, where such transfer would be prohibited by Data Protection Laws and Regulations in the absence of the Standard Contractual Clauses.

“Standard Contractual Clauses” means either the EEA SCCs or the UK IDTA, as applicable to a Restricted Transfer. “Sub-processor” means any Processor engaged by Rithum or its Affiliates.

“UK GDPR” means the GDPR as transposed into United Kingdom national law by operation of section 3 of the European Union (Withdrawal) Act 2018 and as amended by the Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019.

“UK IDTA” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, issued by the Information Commissioner under Section 119A(1) Data Protection Act 2018, as updated, amended, replaced or superseded from time to time by the UK Government.

2. PROCESSING OF PERSONAL DATA
2.1 Roles of the Parties. The parties acknowledge and agree that with regard to the Processing of Personal Data, Customer is the Controller, Rithum (or its Affiliate, as applicable) is the Processor and that Rithum may engage Sub-processors pursuant to the requirements set forth in Section 5 “Sub-processors” below.

2.2 Customer’s Processing of Personal Data. Customer shall, in its use of the Services, Process Personal Data only in accordance with the requirements of Data Protection Laws and Regulations. For the avoidance of doubt, Customer’s instructions to Rithum for the Processing of Personal Data shall comply with Data Protection Laws and Regulations. Customer shall have sole responsibility for the accuracy, quality, and legality of Personal Data and the means by which Customer acquired Personal Data.

2.3 Rithum’s Processing of Personal Data. Rithum shall treat Personal Data as Confidential Information and shall only Process Personal Data on behalf of and in accordance with Customer’s documented instructions for the following purposes: (i) Processing in accordance with the Terms; (ii) Processing initiated by Customer personnel in their use of the Services; and (iii) Processing to comply with other documented reasonable instructions provided by authorized Customer personnel (e.g., via email) where such instructions are consistent with the terms of the Terms. Rithum will promptly inform Customer if Rithum has actual knowledge that a customer instruction infringes Data Protection Laws and Regulations, provided that Rithum’s will not incur any liability for its failure to provide such notice to Customer. Notwithstanding anything in this DPA to the contrary, Rithum shall not be prohibited from complying with Data Protection Laws and Regulations.

2.4 Details of the Processing. The subject-matter of Processing of Personal Data by Rithum is the performance of the Services pursuant to the Terms. The duration of the Processing, the nature and purpose of the Processing, the types of Personal Data and categories of Data Subjects Processed under this DPA are further specified in Schedule 2 (Details of the Processing) to this DPA.

2.5 Data Protection Impact Assessment. Upon Customer’s request and only during Rithum’s Standard Business Hours, Rithum shall provide Customer with reasonable cooperation and assistance needed to fulfill Customer’s obligation under Data Protection Laws and Regulations to carry out a data protection impact assessment related to Customer’s use of the Services, to the extent Customer does not otherwise have access to the relevant information, and to the extent such information is available to Rithum. Customer shall be responsible for any costs arising from Rithum’s provision of such assistance.

2.6 Audits. Upon Customer’s written request, and subject to the confidentiality obligations set forth in the Terms, Rithum shall make available to Customer that is not a competitor of Rithum (or Customer’s independent, third-party auditor that is not a competitor of Rithum) information as may be reasonably requested by Customer from time to time regarding the Rithum’s compliance with the obligations set forth in this DPA, and will allow for audits conducted by Customer, or another auditor mandated by Customer, by completing a data protection questionnaire of reasonable length not more than once annually during Rithum Standard Business Hours. To the extent Customer is able to demonstrate that Rithum’s questionnaire responses do not provide sufficient information to demonstrate compliance with this DPA, Customer may conduct follow up interviews with Rithum’s personnel and conduct information audits as mutually agreed by Customer and Rithum. Except when required by a Regulatory Authority, the audit described in Clause 8.9 of the Standard Contractual Clauses shall be carried out in accordance with this Section 2.6.

2.7 Limits to DPIAs and Audits. No assessment described in Section 2.5 or audit described in Section 2.6 above (or in Clause 8.9 of the Standard Contractual Clauses): (a) will be conducted in a manner that unreasonably interferes with Rithum’s business or provision of the Services; (b) will require Rithum to disclose information that in Rithum’s reasonable determination would compromise its security measures or that constitutes information that Rithum is obligated to keep confidential pursuant to contractual or fiduciary obligations to third parties or applicable legal obligations; or (c) will include networks, systems, or storage facilities, or other records or information, other than those that are reasonably related to the provision of the Services subject to the assessment or audit. Such assessments and audits do not include any rights to come on-site to any of Rithum’s premises or to access any of Rithum’s systems.

2.8 Representations and Responsibilities of Customer. Customer confirms that it (i) has all necessary rights or consents to collect the Personal Data from the applicable Data Subjects and transfer such Personal Data to Rithum for all Processing to be performed under the Terms, and (ii) will not transfer to Rithum any Personal Data that is not required for Rithum to perform the Services for Customer. Customer agrees that it will not use the Services in a manner that violates the rights of any Data Subject that has opted-out from disclosures of Personal Data under applicable Data Protection Laws and Regulations.

3. RIGHTS OF DATA SUBJECTS
3.1 Data Subject Requests. Rithum shall, to the extent legally permitted, promptly notify Customer if Rithum receives a request from a Data Subject to exercise the Data Subject’s rights under Data Protection Laws and Regulations (“Data Subject Request”). Customer shall then respond to such Data Subject Request in compliance with Data Protection Laws and Regulations. Contingent upon the nature of the Processing, Rithum shall assist Customer by technical and organizational measures, insofar as this is possible, for the fulfilment of Customer’s obligation to respond to a Data Subject Request under Data Protection Laws and Regulations. In addition, to the extent Customer, in its use of the Services, does not have the ability to address a Data Subject Request, Rithum shall upon Customer’s request provide commercially reasonable efforts to provide Customer with information relevant to the Data Subject Request so that Customer may respond to such Data Subject Request, to the extent Rithum is legally permitted to do so and the response to such Data Subject Request is required under Data Protection Laws and Regulations. To the extent legally permitted, Customer shall be responsible for any costs arising from Rithum’s provision of such assistance. Customer acknowledges that any Data Subject Request that results in deletions, modifications or restrictions on the Processing of Personal Data may adversely impact Rithum’s ability to accurately provide the Services relating to such Personal Data, and Customer agrees to hold Rithum harmless from any such failure of the Services (the “Modification Result”).

4. RITHUM PERSONNEL
4.1 Confidentiality. Rithum will inform its personnel engaged in the Processing of Personal Data (“Personnel”) of the confidential nature of the Personal Data, provide appropriate training to Personnel on their responsibilities, and execute written confidentiality agreements related to the Processing of Personal Data, the confidentiality obligations of which will survive the termination of the personnel engagement.

4.2 Reliability. Rithum shall take commercially reasonable steps to ensure the reliability of any Personnel.

4.3 Limitation of Access. Rithum shall ensure that the access of Personnel to Personal Data is limited to those Personnel performing Services in accordance with the Terms.

5. SUB-PROCESSORS
5.1 Appointment of Sub-processors. Customer acknowledges and agrees that (a) Rithum’s Affiliates may be retained as Sub-processors; and (b) Rithum and Rithum’s Affiliates respectively may engage third-party Sub-processors in connection with the provision of the Services. Rithum or a Rithum Affiliate has entered into a written agreement with each Sub-processor containing data protection obligations no less protective than those in this Terms with respect to the protection of Personal Data to the extent applicable to the nature of the Services provided by such Sub-processor.

5.2 List of Current Sub-processors and Notification of New Sub-processors. Rithum may use Sub-processors to fulfil its contractual obligations to Customer under the Terms or to provide certain Services. Customer hereby confirms its general written authorization for Rithum’s use of the Subprocessors listed at https://www.Rithum.com/terms/dpa/subprocessors. Rithum shall maintain an up-to-date list of the names and locations of all Sub-Processors used for the Processing of Personal Data under this DPA at https://www.Rithum.com/terms/dpa/subprocessors. Rithum shall update the list on its website for any Sub-Processor to be appointed at least thirty (30) days prior to the date on which the Sub-Processor shall commence Processing Personal Data.

5.3 Objection Right for New Sub-processors. Customer may object to Rithum’s use of a new Sub-processor by notifying Rithum promptly in writing within ten (10) business days after receipt of Rithum’s notice in accordance with the mechanism set out in Section 5.2. In the event Customer objects to a new Sub-processor, as permitted in the preceding sentence, Rithum will use reasonable efforts to make available to Customer a change in the Services or recommend a commercially reasonable change to Customer’s configuration or use of the Services to avoid Processing of Personal Data by the objected-to new Sub-processor without unreasonably burdening the Customer. If the parties are unable to implement such change within a reasonable period of time, which shall not exceed thirty (30) days, Customer may terminate the applicable Statement of Work(s) with respect only to those Services which cannot be provided by Rithum without the use of the objected-to new Sub-processor by providing written notice to Rithum. Rithum will refund Customer any prepaid unused fees covering the remainder of the term of Terms following the effective date of termination with respect to such terminated Services, without imposing a penalty for such termination on Customer.

5.4 Liability. Rithum shall be liable for the acts and omissions of its Sub-processors to the same extent Rithum would be liable if performing the services of each Sub-processor directly under the terms of this DPA, except as otherwise set forth in the Terms.

6. SECURITY
6.1 Controls for the Protection of Personal Data. Rithum shall maintain technical and organizational measures designed to protect the security (including protection against unauthorized or unlawful Processing and against accidental or unlawful destruction, loss or alteration or damage, unauthorized disclosure of, or access to, Personal Data), confidentiality and integrity of Personal Data, as set forth in the Rithum TOMs documentation. Rithum regularly monitors compliance with these measures. Rithum will not materially decrease the overall security of the Services during the then-current term.

7. DATA INCIDENT MANAGEMENT AND NOTIFICATION
7.1 Rithum maintains security incident management policies and procedures and shall, notify Customer without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Personal Data, transmitted, stored or otherwise Processed by Rithum or its Sub-processors (a “Data Incident”). Rithum shall make reasonable efforts to identify the cause of such Data Incident and take those steps as Rithum deems necessary and reasonable in order to remediate the cause of such a Data Incident to the extent the remediation is within Rithum’s reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer personnel; for those incidents, Customer shall bear full responsibility and take all actions necessary to remediate the incident.

8. DELETION OF DATA
8.1 Rithum shall, to the extent allowed by applicable law and in accordance with its then-applicable data retention policies, upon termination or expiration of the Terms and at Customer’s election, destroy all Personal Data (including all copies of the Personal Data) in Rithum’s possession or control, and in all cases subject to the Modification Result. This requirement will not apply to the extent that Rithum is required by any Data Protection Laws and Regulations, or due to financial or tax audit purposes, to retain some or all of the Personal Data, in which event Rithum will use reasonable efforts to isolate and protect the Personal Data from any further Processing except to the extent required by such law or legitimate business need.

9. AUTHORIZED AFFILIATES
9.1 Contractual Relationship. The parties acknowledge and agree that, by executing the Terms, the Customer enters into the DPA on behalf of itself and, as applicable, in the name and on behalf of its Authorized Affiliates, thereby establishing a separate DPA between Rithum and each such Authorized Affiliate subject to the provisions of the Terms and this Section 9 and Section 10. Each Authorized Affiliate agrees to be bound by the obligations under this DPA and, to the extent applicable, the Terms. All access to and use of the Services and associated content by Authorized Affiliates must comply with the terms and conditions of the Terms and any violation of the terms and conditions of the Terms by an Authorized Affiliate shall be deemed a violation by Customer. Rithum is authorized to enter into this Terms on behalf of its Affiliates and will provide instructions and other information to those Affiliates consistent with the terms of this Terms.

9.2 Communication. The Customer that is the contracting party to the Terms shall remain responsible for coordinating all communication with Rithum under this DPA and be entitled to make and receive any communication in relation to this DPA on behalf of its Authorized Affiliates.

9.3 Rights of Authorized Affiliates. Where an Authorized Affiliate becomes a party to the DPA with Rithum, it shall to the extent required under applicable Data Protection Laws and Regulations be entitled to exercise the rights and seek remedies under this DPA, subject to the following:

9.3.1 Except where applicable Data Protection Laws and Regulations require the Authorized Affiliate to exercise a right or seek any remedy under this DPA against Rithum directly by itself, the parties agree that (i) solely the Customer that is the contracting party to the Terms shall exercise any such right or seek any such remedy on behalf of the Authorized Affiliate, and (ii) the Customer that is the contracting party to the Terms shall exercise any such rights under this DPA not separately for each Authorized Affiliate individually but in a combined manner for all of its Authorized Affiliates together.

10. LIMITATION OF LIABILITY
10.1 Each party’s and all of its Affiliates’ liability, taken together in the aggregate, arising out of or related to this DPA, and all DPAs between Authorized Affiliates and Rithum, whether in contract, tort or under any other theory of liability, is subject to the ‘Limitation of Liability’ section of the Terms, and any reference in such section to the liability of a party means the aggregate liability of that party and all of its Affiliates under the Terms and all DPAs together.

10.2 For the avoidance of doubt, Rithum’s and its Affiliates’ total liability for all claims from the Customer and all of its Authorized Affiliates arising out of or related to the Terms and each DPA shall apply in the aggregate for all claims under both the Terms and all DPAs established under this Terms, including by Customer and all Authorized Affiliates, and, in particular, shall not be understood to apply individually and severally to Customer and/or to any Authorized Affiliate that is a contractual party to any such DPA. Notwithstanding any other provision in this Section 10, nothing in this Section 10 is intended to limit the parties’ obligations under Clause 12 of Schedule 3 of this DPA.

11. EUROPEAN SPECIFIC PROVISIONS
11.1 GDPR. With effect from 25 May 2018, Rithum will Process Personal Data in accordance with the GDPR requirements directly applicable to Rithum’s provision of its Services.

11.2 Transfer mechanisms for data transfers. Subject to the additional terms in Schedule 1, the Standard Contractual Clauses set forth in Schedule 3 to this DPA apply to the Services listed in Appendix 3 to the Standard Contractual Clauses, subject to the additional terms in Section 3 of Schedule 1.

12. CALIFORNIA SPECIFIC PROVISIONS
In cases where Rithum handles the Personal Data of California residents on Customer’s behalf in connection with the Services, the following terms will apply: (a) Rithum at all times under the Terms is acting as Customer’s Service Provider and has been engaged by Customer for the Business Purpose of providing the Services detailed in the Terms; (b) Rithum will not Sell Personal Data it handles in connection with the Services; (c) Rithum will not retain, use or disclose Personal Data for any purpose other than for the specific Business Purposes authorized by Customer. All capitalized terms in the immediately preceding sentence not otherwise defined in this DPA shall have the meaning given such term in the CCPA.

13. PARTIES TO THIS DPA
Only Rithum Corporation is a party to this DPA and/or the Standard Contractual Clauses, on behalf of its Affiliates. Where the Rithum entity referenced in the Terms is a different legal entity than Rithum Corporation, that Rithum entity is carrying out the obligations of the data importer as set out in Schedule 3 “Standard Contractual Clauses” on behalf of Rithum Corporation.

SCHEDULE 1 – TRANSFER MECHANISMS FOR EUROPEAN DATA TRANSFERS

1. ADDITIONAL TERMS
1.1 The additional terms in this Section 1 of Schedule 1 shall apply to the Processing of Personal Data of a Customer established in (i) European Economic Area member states whose Processing activities for the relevant data are governed by the EU Data Protection Directive 95/46/EC or the GDPR (“EU Data Protection Legislation”) and/or implementing national legislation; (ii) non-European Economic Area member states for which Customer has contractually specified that the EU Data Protection Legislation and implementing national legislation shall apply; and (iii) Switzerland and the United Kingdom.

2. ADDITIONAL SERVICES TERMS
2.1 Customers covered by the Standard Contractual Clauses. The Standard Contractual Clauses and the additional terms specified in this Section 2 of this Schedule 1 apply to (i) the legal entity that has executed the Standard Contractual Clauses as a data exporter and its Authorized Affiliates and, (ii) all Authorized Affiliates of Customer established within the European Economic Area, Switzerland and the United Kingdom, which have signed an SOW for the Services. For the purpose of the Standard Contractual Clauses and this Section 2, the aforementioned entities shall be deemed “data exporters”.

2.2 Instructions. This DPA and the Terms are Customer’s complete and final documented instructions at the time of signature of the Terms to Rithum for the Processing of Personal Data. Any additional or alternate instructions must be agreed upon separately. For the purposes of Clause 8.1(a) of the Standard Contractual Clauses, the following is deemed an instruction by the Customer to process Personal Data: (a) Processing in accordance with the Terms and applicable Statement of Work(s); (b) Processing initiated by Customer in its use of the Services and (c) Processing to comply with other reasonable documented instructions provided by Customer or Customer personnel (e.g., via email) where such instructions are consistent with the terms of the Terms.

2.3 Appointment of new Sub-processors and List of current Sub-processors. Pursuant to Clause 9(a) of the Standard Contractual Clauses, Customer acknowledges and expressly agrees that (a) Rithum’s Affiliates may be retained as Sub- processors; and (b) Rithum and Rithum’s Affiliates respectively may engage third-party Sub-processors in connection with the provision of the Services. Rithum shall make available to Customer the current list of Sub-processors in accordance with Section 5.2 of this DPA.

2.4 Notification of New Sub-processors and Objection Right for new Sub-processors. Pursuant to Clause 9(a) of the Standard Contractual Clauses, Customer acknowledges and expressly agrees that Rithum may engage new Sub- processors as described in Sections 5.2 and 5.3 of the DPA.

2.5 Deletion of Personal Data. The parties agree that Customer elects for Rithum to delete all personal data at the expiration or termination of the services.

2.6 Mitigation. The measures Rithum is required to take under Schedule 3, Clause 8.6(3) will only cover Rithum’s impacted systems.

2.7 Conflict. In the event of any conflict or inconsistency between the body of this DPA and any of its Schedules (not including the Standard Contractual Clauses) and the Standard Contractual Clauses in Schedule 3, the Standard Contractual Clauses shall prevail.

2.8 In respect to any Restricted Transfer subject to FADP, the terms of Schedule 3 below will apply, with the following modifications:

  1. References to the GDPR shall be interpreted as references to the Swiss Federal Act on Data Protection of June 19, 1992 (“FADP”) or by any subsequent act, including the relevant amendments and implementing ordinances (whereby “the authority” shall mean the competent data protection authority in the territory in which the data exporter is established).
  2. “personal data”, “special categories of data/sensitive data”, “personality profiles”, “profiling” “profiling with high risk”, “process/processing”, “controller”, “processor”, “data subject” and “supervisory authority/authority” shall have the meaning assigned to them by the Swiss Federal Act on Data Protection of June 19, 1992 (“FADP”) or by any subsequent act, including the relevant amendments and implementing ordinances (whereby “the authority” shall mean the competent data protection authority in the territory in which the data exporter is established).
  3. The data importer acknowledges and agrees that the personal data transferred to data importer by data exporter may include personal data of legal persons and personality profiles of natural persons. The data importer shall process personal data of legal persons in the same manner as other personal data and personality profiles in the same manner as special categories of data (the special protection of data from legal persons and from personality profiles will be abolished upon entering into force of the revised Swiss Federal Data Protection Act of September 25, 2020 (“R-FADP”)).
  4. “Member State” shall be interpreted as including Switzerland.
  5. The term “Member State” must not be interpreted in such a way as to exclude data subjects in Switzerland from the possibility of suing for their rights in their habitual place of residence (Switzerland) in accordance with Clause 18c. June 19, 1992 (“FADP”) or by any subsequent act, including the relevant amendments and implementing ordinances (whereby “the authority” shall mean the competent data protection authority in the territory in which the data exporter is established).

In the event Customer transfers Customer Personal Data that relates to data subjects in Switzerland to Rithum, this Section 2.7 shall modify the corresponding references in this DPA. For clarity and avoidance of doubt, this Section 2.7 will amend this DPA to the extent necessary for compliance with the Swiss Federal Act on Data Protection. This Section 2.7 shall only apply to personal data subject to the Swiss Federal Act on Data Protection.

2.9 In respect of any Restricted Transfer subject to the UK GDPR, the Parties hereby enter into the UK IDTA (with Customer as data exporter and Rithum as data importer), which is incorporated by reference into this DPA and which shall come into effect upon the commencement of a Restricted Transfer. The Parties make the following selections for the purpose of the UK IDTA:

Part 1: Tables

  1. Table 1
    1. The Start Date is the Effective Date of the Terms.
    2. The Exporter is the Customer and the Importer is Rithum.
    3. The Exporter’s details are found in the Terms. The Importer is Rithum Corporation, a Delaware corporation, with principal address at: 1010 Sync Street, Suite 600, Morrisville, NC 27560, USA.
    4. The Exporter’s Key Contact is found in the Terms. The Importer’s Key Contact is Rithum General Counsel, Chief Revenue Officer, legal@Rithum.com.
  2. Table 2: The Parties choose the EEA SCCs, including the Appendix Information and with only the following modules, clauses or optional provisions of the EEA SCCs brought into effect for the purposes of this IDTA:
    1. Clause 7 – See Schedule 3, Clause 7, below.
    2. Clause 9 – See Schedule 3, Clause 9, below.
    3. Clause 11 – See Schedule 3, Clause 11, below.
  3. Table 3
    1. Annex IA: See Schedule 2 below.
    2. Annex IB: See Schedule 2 below.
    3. Annex II: See Schedule 3, Annex II below.
    4. Annex III: See Schedule 3, Annex III below.
  4. Table 4
    1. The Importer may end this IDTA.

Part 2: Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 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 of those Mandatory Clauses.

SCHEDULE 2 – DETAILS OF THE PROCESSING

Nature and Purpose of Processing
Rithum will Process Personal Data as necessary to perform the Services pursuant to the Terms and as further instructed by Customer in its use of the Services as follows, depending on the solution used by Customer:

For Services related to Rithum Marketplaces, Rithum Webstore Amplifier, Rithum First-Party (1P) Drop-ship, and Rithum Fulfillment Services:
Type of Personal Data Processed:

  • Rithum Processes first name and surname, phone number, physical or mailing address, and email address of buyers of Customer’s products.
  • Rithum Processes business contact information (company, first name and surname, phone number, physical or mailing address, email address) of Customer’s business partners, Customer’s vendors, and Customer’s clients.
  • Rithum Processes business contact information (company, first name and surname, phone number, physical or mailing address, email address) of (a) Customer personnel who are users of this solution; (b) Customer personnel who support users of this solution; and (c) agents and advisors of Customer.

Purpose of the Processing:

Customer can use Rithum’s proprietary middleware SaaS platform and associated Rithum Services (collectively, the “Services”): (1) to manage its product listings and product orders for Customer’s goods that Customer has listed for sale on specified online marketplaces or webstores to assist Customer to process orders that individual buyers make on the marketplaces and webstores on which Customer sells and that Customer has authorized to be connected to the Services; and (2) to connect Customer to its various authorized product warehouses and shipping destinations to manage data related to Customer’s order fulfillment activities.

For Services related to Rithum Performance Marketing and Rithum Retail Media:
Type of Personal Data Processed:

  • Rithum Processes the IP addresses of consumers that interact with Customer advertising through this solution.
  • Rithum Processes business contact information (company, first name and surname, phone number, physical or mailing address, email address) of (a) Customer personnel who are users of this solution; (b) Customer personnel who support users of this solution; and (c) agents and advisors of Customer.

Purpose of the Processing:
Customer can use Rithum’s proprietary middleware SaaS and associated Rithum Services (collectively, the “Services”) to place and manage Customer’s advertisements for Customer’s goods on specified online advertising areas that Customer has authorized to be connected to the Services.

For Rithum Project Services:
Type of Personal Data Processed:

  • Rithum Processes business contact information (company, first name and surname, phone number, physical or mailing address, email address) of Customer’s business partners, Customer’s vendors, and Customer’s clients.
  • Rithum Processes business contact information (company, first name and surname, phone number, physical or mailing address, email address) of (a) Customer personnel who use these services; (b) Customer personnel who support users of these services; and (c) agents and advisors of Customer.

Purpose of the Processing:
Customer can use Rithum Consulting Services for a variety of custom projects wherein Rithum imparts its expertise to Customer on various e-commerce topics; the details of these Services are set forth in the applicable SOW.

Duration of Processing
Subject to Section 8 of the DPA, Rithum will Process Personal Data for the duration of the Terms, unless otherwise agreed upon in writing.
Categories of Data Subjects
Customer may submit (or direct Rithum to submit, on Customer’s behalf) Personal Data to the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include, but is not limited to Personal Data relating to the following categories of data subjects:

  • Prospects, customers, business partners and vendors of Customer (who are natural persons)
  • Employees or contact persons of Customer’s prospects, customers, business partners and vendors
  • Employees, agents, advisors, freelancers of Customer (who are natural persons)
  • Customer’s Users authorized by Customer to use the Services
  • Buyers of Customer’s products

Type of Personal Data
Customer may submit (or direct Rithum to submit, on Customer’s behalf) Personal Data to the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include, but is not limited to the following categories of Personal Data:

  • First and last name
  • Contact information (company, email, phone, physical address)
  • IP address
  • Geolocation data

SCHEDULE 3 – STANDARD CONTRACTUAL CLAUSES
Controller to Processor Module 2

SECTION I
Clause 1
Purpose and scope

  1. 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 data to a third country.
  2. The Parties:
    1. 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
    2. 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’).
    3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
    4. 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

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

  1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
    1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
    2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
    3. Clause 9(a), (c), (d) and (e);
    4. Clause 12(a), (d) and (f);
    5. Clause 13;
    6. Clause 15.1(c), (d) and (e);
    7. Clause 16(e);
    8. Clause 18(a) and (b).
  2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4
Interpretation

  1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
  2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
  3. 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
Docking clause

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

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

  1. 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.
  2. 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.
  3. 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.
  4. 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:

  1. 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;
  2. 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;
  3. 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
  4. 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

  1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
  2. 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.
  3. 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.
  4. 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.
  5. 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

  1. 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 thirty (30) 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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

  1. 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.
  2. 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.
  3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.

Clause 11
Redress

  1. 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.
  2. 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.
  3. 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:
    1. 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;
    2. refer the dispute to the competent courts within the meaning of Clause 18.
  4. 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.
  5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
  6. 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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.

Clause 13
Supervision

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

  1. 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.
  2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
    1. 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;
    2. 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 ();
    3. 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.
  3. 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.
  4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
  5. 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).
  6. 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

  1. 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:
    1. 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
    2. 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.
  2. 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.
  3. 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.).
  4. 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.
  5. 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

  1. 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).
  2. 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.
  3. 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

  1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
  2. 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).
  3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
    1. 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;
    2. the data importer is in substantial or persistent breach of these Clauses; or
    3. 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.

  1. 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.
  2. 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 one of the EU Member States, provided such law allows 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

  1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
  2. The Parties agree that those shall be the courts of the Republic of Ireland.
  3. 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.
  4. The Parties agree to submit themselves to the jurisdiction of such courts.

ANNEX I

A. LIST OF PARTIES
Data exporter(s):
Name: The entity identified as “Customer” in the Terms to which the DPA is attached or as otherwise specified in the DPA.
Address: The address for Customer in the Terms to which the DPA is attached or as otherwise specified in the DPA.
Contact person’s name, position and contact details: The contact details associated with Customer’s account in the Terms to which the DPA is attached or as otherwise specified in the DPA.
Activities relevant to the data transferred under these Clauses: The activities specified in Schedule 2 to the DPA.
Signature and date: By using the Rithum Services to transfer personal data to the data importer in the United States or other Third Country, and by executing the Statement of Work with Rithum, data exporter will be deemed to have signed this Annex I.
Role (controller/processor): Controller

Data importer(s):
Name: Rithum Corporation
Address: 1201 Peachtree Street, NE Building 400, Suite #600, Atlanta, GA 30361, US
Contact person’s name, position and contact details: Jason Rodriguez, Deputy General Counsel, legal@rithum.com
Activities relevant to the data transferred under these Clauses: The activities specified in Schedule 2 to the DPA.
Signature and date: By receiving Personal Data from or on behalf of Customer in the United States or another Third Country on Customers’ instructions, the data importer will be deemed to have signed this Annex I.
Role (controller/processor): Processor

B. DESCRIPTION OF TRANSFER
Categories of data subjects whose personal data is transferred: The categories of data subjects are specified in Schedule 2 to the DPA.
Categories of personal data transferred: The categories of personal data transferred are described in Schedule 2 to the DPA.
Sensitive data transferred (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: N/A
The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis): The personal data is transferred in accordance with Customer’s instructions as described in Section 2.3 of the DPA.
Nature of the processing: The nature of the processing is described in Schedule 2 to the DPA:
Purpose(s) of the data transfer and further processing: The purpose of the data transfer and further processing is described in Schedule 2 to the DPA.
For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing: All personal data processed for Customer may be transferred to Rithum’s sub-processors for the purpose of performing the Services for Customer. These transfers take place on a continuous basis to support Customer.

C. COMPETENT SUPERVISORY AUTHORITY
Identify the competent supervisory authority/ies in accordance with Clause 13:
Where Customer is established in an EU Member State, the supervisory authority with responsibility for ensuring compliance by Customer with Regulation (EU) 2016/679 as regards the data transfer shall act as competent supervisory authority.
Where Customer 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 shall act as competent supervisory authority.
Where Customer 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 Irish Data Protection Commission shall act as competent supervisory authority.

ANNEX II

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

Rithum Technical and Organizational Measures

This document describes the measures taken and implemented by Rithum to protect and secure the personal information that we process.

Physical Access Control
Web applications, backend processing systems and database servers (information systems) of Rithum are located in secure data centers, distributed across a hosted colocation and Amazon Web Services (AWS) in US and EU Regions. Rithum has implemented suitable measures in order to prevent unauthorized persons from gaining access to the data processing equipment where personal data are processed or stored.
This is accomplished by:

  • An access control policy that works in coordination with our data center provider policy and procedures;
  • Protection of secured cages and cabinets where systems and storage are housed;
  • Establishing, approving and maintaining a list of individuals with authorized access to the facility where the information systems resides;
  • Under the AWS Shared Responsibility model, AWS inherits all physical and environmental controls for our information systems running in Amazon EC2; and
  • Annual review of Data Center SOC reports.

Logical Access Control
Rithum has implemented measures to prevent unauthorized access to data processing systems, data in transit and data at rest.
This is accomplished by:

  • Established policy and procedures for authorizing and granting access to the network and systems used to process data;
  • Multifactor authentication is enforced for access to systems and storage;
  • Implementing and maintaining monitoring systems that detect malicious, unauthorized activities within the network and information systems;
  • Prohibiting the use of insecure protocols over the management plane;
    Customer personal data is encrypted in transit and at rest in the database;
  • All data on storage disk arrays is encrypted at rest;
  • Periodic review of user permissions and access control lists; and
  • Restricting access to information systems based upon the principle of least privilege.

Data Protection in Cloud Based Services (SaaS, IaaS, IaaS+, PaaS)
Rithum has implemented technical and organizational measures to secure PII in cloud-based applications, infrastructure, and services utilized by our organizational business units.
This is accomplished by:

  • Performing a vendor risk analysis against all third-party providers of SaaS applications in use by the organization. Analysis includes review of data protection compliance and assurance measures implemented by those third parties;
  • Documenting assigned ownership and accountability for the third-party relationship;
  • Tracking access to data based on data type in SaaS applications;
  • Periodically reviewing user access applications, systems and services;
  • Establishing policy and procedures for authorizing and granting access to AWS VPCs and EC2 instances;
  • Establishing best practices for preventing public exposure of data in transit and stored in the cloud;
  • Implementing and administering threat detection technologies for cloud-based systems, services and tools;
  • Establishing security policy prohibiting the storage of confidential data in unsanctioned cloud applications;
  • Conducting annual security awareness training covering secure use of cloud-based services; and
  • Maintaining a registry of processing activities that identifies our third-party subservice providers and the data which we store in their platform.

ANNEX III

LIST OF SUB-PROCESSORS
See the list of Rithum Sub-processors at:
https://www.rithum.com/terms/dpa/subprocessors