Data Processing Addendum

This Data Processing Addendum (“DPA”) forms part of, and is subject to, the Master Subscription Agreement (“Agreement”) or other written or electronic terms of service or subscription agreement between Nexza, Inc., a Delaware corporation doing business as Ruddr (also referred to herein as “we”, “our”, or “us”), or any of its successors or assignees, and the legal entity accessing our Services (collectively, for purposes of this DPA, “Customer”, and together with us, the “Parties” and each a “Party”). All capitalized terms not defined in this DPA shall have the meanings set forth in the Agreement.

Section 1. Definitions.

“Account” means Customer’s account in the Service in which Customer stores and processes Customer Data.

“Affiliate” has the meaning set forth in the Agreement.

“Authorized Affiliate” shall mean a Customer Affiliate who has not signed an Order Form pursuant to the Agreement, but is either a Data Controller or Data Processor for the Customer Personal Data processed by us pursuant to the Agreement, for so long as such entity remains a Customer Affiliate.

“California Consumer Privacy Act” or “CCPA” means the California Consumer Privacy Act of 2018, as may be amended from time to time.

“Customer Data” means any data or data files of any type that are uploaded by or on behalf of Customer for storage or processing in the Service.

“Customer Personal Data” means any Customer Data that is Personal Data.

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

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

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

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

“EU & UK Data Protection Law” means (i) Regulation 2016/679 of the European Parliament and of the Council on the protection of natural persons with regard to the Processing of Personal Data and on the free movement of such data (General Data Protection Regulation) (“GDPR”); and (ii) the GDPR as it forms part of United Kingdom law pursuant to Section 3 of the European Union (Withdrawal) Act 2018 (“UK GDPR”) and the Data Protection Act 2018.

“Personal Data” means any information, including opinions, relating to an identified or identifiable natural person and includes similarly defined terms in Data Protection Laws, including, but not limited to, the definition of “personal information” in the CCPA.

“Processing” shall mean any operation or set of operations which is performed on Personal Data or on sets of Personal Data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination, and “Process”, “Processes” and “Processed” will be interpreted accordingly.

“Purposes” shall mean (i) our provision of the Services as described in the Agreement, including Processing initiated by Users in their use of the Services; and (ii) further documented, reasonable instructions from Customer agreed upon by the Parties.

“Security Incident” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of or access to Customer Personal Data.

“Service” has the meaning set forth in the Agreement.

“Sub-processor” means any other Data Processors engaged by us to Process Customer Personal Data

Section 2. Scope and Applicability of this DPA.

This DPA applies where and only to the extent that we Process Customer Personal Data on behalf of Customer as Data Processor in the course of providing the Services.

Section 3. Roles and Scope of Processing.

3.1 Role of the Parties. As between Ruddr and Customer, we shall Process Customer Personal Data only as a Data Processor (or sub-processor) acting on behalf of Customer and, with respect to CCPA, as a “service provider” as defined therein, in each case regardless of whether Customer acts as a Data Controller or as a Data Processor on behalf of a third-party Data Controller (such third-party, the “Third-Party Controller”) with respect to Customer Personal Data. To the extent any Usage Data (as defined in the Agreement) is considered Personal Data under applicable Data Protection Laws, we are the Data Controller of such data and shall Process such data in accordance with the Agreement and applicable Data Protection Laws.

3.2 Customer Instructions. We will Process Customer Personal Data only for the Purposes. Customer shall ensure its Processing instructions are lawful and that the Processing of Customer Personal Data in accordance with such instructions will not violate applicable Data Protection Laws. The Parties agree that the Agreement (including this DPA) sets out the exclusive and final instructions to us for all Processing of Customer Personal Data, and (if applicable) include and are consistent with all instructions from Third-Party Controllers. Any additional requested instructions require our prior written agreement. We shall promptly notify Customer if, in our opinion, such instruction violates EU & UK Data Protection Law. Where applicable, Customer shall be responsible for any communications, notifications, assistance and/or authorizations that may be required in connection with a Third-Party Controller.

3.3 Customer Affiliates. Our obligations set forth in this DPA also extend to Authorized Affiliates, subject to the following conditions:

3.4 Processing of Personal Data. Each Party will comply with its respective obligations under Data Protection Laws. Customer agrees (i) it will use the Service in a manner designed to ensure a level of security appropriate to the particular content of the Customer Personal Data, such as pseudonymizing and backing-up Customer Personal Data; and (ii) it has obtained all consents, permissions and/or rights necessary under Data Protection Laws for us to lawfully Process Customer Personal Data for the Purposes, including, without limitation, Customer’s sharing and/or receiving of Customer Personal Data with third-parties via the Service.

Section 4. Sub-Processing.

4.1. Authorized Sub-Processors. Customer provides us with a general authorization to engage Sub-processors, subject to Section 4.3 (Changes to Sub-processors), as well as our current Sub-processors listed within our Privacy Policy located at https://www.ruddr.com/privacy-policy as of the effective date of this DPA.

4.2 Sub-processor Obligations. We shall: (i) enter into a written agreement with each Sub-processor imposing data protection obligations no less protective of Customer Personal Data as our obligations under this DPA to the extent applicable to the services provided by the Sub-processor; and (ii) remain liable for each Sub-processor’s compliance with the obligations under this DPA. Upon written request, and subject to any confidentiality restrictions, we shall provide Customer all relevant information it reasonably can in connection with its applicable Sub-processor agreements where required to satisfy Customer’s obligations under Data Protection Laws.

4.3 Changes to Sub-processors. Upon request, we shall subscribe Customer to notifications of new Sub-processors. We shall provide such notification to subscribers at least twenty-eight (28) days in advance of allowing the new Sub-processor to Process Customer Personal Data (the “Objection Period”). During the Objection Period, objections (if any) to our appointment of the new Sub-processor must be provided to us in writing and based on reasonable grounds. In such event, the Parties will discuss those objections in good faith with a view to achieving resolution. If it can be reasonably demonstrated to us that the new Sub-processor is unable to Process Customer Personal Data in compliance with the terms of this DPA and we cannot provide an alternative Sub-processor, or the Parties are not otherwise able to achieve resolution as provided in the preceding sentence, Customer, as its sole and exclusive remedy, may terminate the Agreement by providing written notice to us of such termination. We will refund Customer any prepaid unused fees associated with the Agreement following the effective date of such termination.

Section 5. Security.

5.1. Security Measures. We shall implement and maintain appropriate technical and organizational security measures designed to protect Customer Personal Data from Security Incidents and to preserve the security and confidentiality of the Customer Personal Data.

5.2. Confidentiality of Processing. We shall ensure that any person who is authorized by us to Process Customer Personal Data (including its staff, agents and subcontractors) shall be under an appropriate obligation of confidentiality (whether a contractual or statutory duty).

5.3. No Assessment of Customer Personal Data by Us. We shall have no obligation to assess the contents or accuracy of Customer Personal Data, including to identify information subject to any specific legal, regulatory, or other requirement. Customer is responsible for making an independent determination as to whether its use of the Service will meet Customer’s requirements and legal obligations under Data Protection Laws.

Section 6. Customer Audit Rights.

6.1. Upon written request and at no additional cost to Customer, we shall provide Customer, and/or its appropriately qualified third-party representative (collectively, the “Auditor”), access to reasonably requested documentation evidencing our compliance with its obligations under this DPA.

6.2. Customer may also send a written request for an audit of our applicable controls, including inspection of our facilities. Following receipt of such request, the Parties shall mutually agree in advance on the details of the audit, including the reasonable start date, scope and duration of, and security and confidentiality controls applicable to, any such audit. We may charge a fee (rates shall be reasonable, taking into account the resources expended by us) for any such audit. The Reports, audit, and any information arising therefrom shall be considered our Confidential Information and may only be shared with a third-party (including a Third-Party Controller) with our prior written agreement.

6.3. Where the Auditor is a third-party, the Auditor may be required to execute a separate confidentiality agreement with us prior to any review of Reports or an audit of us, and we may object in writing to such Auditor, if in our reasonable opinion, the Auditor is not suitably qualified or is a direct competitor. Any such objection by us will require Customer to either appoint another Auditor or conduct the audit itself. Any expenses incurred by an Auditor in connection with any review of Reports or an audit shall be borne exclusively by the Auditor. For clarity, the exercise of audit rights under a Transfer Mechanism shall be as described in this Section 6 (Customer Audit Rights) and Customer agrees those rights are carried out on behalf of Customer and all relevant Third-Party Controllers, subject to the confidentiality and non-use restrictions of the Agreement.

Section 7. Data Transfers.

7.1. Hosting and Processing Locations. We will only host Customer Personal Data in the region(s) offered by us. Customer is solely responsible for the regions from which its Users access the Customer Personal Data, for any transfer or sharing of Customer Personal Data by Customer or its Users.

Section 8. Security Incident Response.

8.1. Security Incident Reporting. If we become aware of a Security Incident, we shall notify Customer without undue delay, and in any case, where feasible, notify Customer within seventy-two (72) hours after becoming aware. Our notification shall be sent to the workspace administrator email addresses. We shall promptly take reasonable steps to contain, investigate, and mitigate any Security Incident.

8.2. Security Incident Communications. We shall provide Customer timely information about the Security Incident, including, but not limited to, the nature and consequences of the Security Incident, the measures taken and/or proposed by us to mitigate or contain the Security Incident, the status of our investigation, a contact point from which additional information may be obtained, and the categories and approximate number of data records concerned. Notwithstanding the foregoing, Customer acknowledges that because our personnel may not have visibility to the content of Customer Personal Data, it is unlikely we can provide information as to the particular nature of the Customer Personal Data, or where applicable, the identities, number or categories of affected Data Subjects. Communications by or on behalf of us with Customer in connection with a Security Incident shall not be construed as an acknowledgment by us of any fault or liability with respect to the Security Incident.

Section 9. Cooperation.

9.1. Data Subject Requests. We shall promptly notify Customer if we receive a request from a Data Subject that identifies Customer Personal Data or otherwise identifies Customer, including where the Data Subject seeks to exercise any of its rights under applicable Data Protection Laws (collectively, “Data Subject Request”). The Service provides Customer with a number of controls that Customer may use to assist it in responding to Data Subject Requests and, subject to the next sentence, Customer will be responsible for responding to any such Data Subject Requests. To the extent Customer is unable to access the relevant Customer Personal Data within the Service using such controls or otherwise, we shall (upon Customer’s written request and taking into account the nature of our Processing) provide commercially reasonable cooperation to assist Customer in responding to Data Subject Requests.

9.2. Data Protection Impact Assessments. We shall provide reasonably requested information regarding the Service to enable Customer to carry out data protection impact assessments or prior consultations with data protection authorities as required by Data Protection Laws, so long as Customer does not otherwise have access to the relevant information.

9.3 Ownership of Service Data. If we receive a demand to retain, disclose, or otherwise Process Customer Personal Data from law enforcement or any other government and/or public authority (“Third-Party Demand”), then we shall attempt to redirect the Third-Party Demand to Customer. Customer agrees that we can provide information to such third-party to the extent reasonably necessary to redirect the Third-Party Demand to Customer. If we cannot redirect the Third-Party Demand to Customer, then we shall, to the extent legally permitted to do so, provide Customer reasonable notice of the Third-Party Demand as promptly as feasible under the circumstances to allow Customer to seek a protective order or other appropriate remedy. This section does not diminish our obligations under any applicable Transfer Mechanisms with respect to access by public authorities.

Section 10. Relationship with the Agreement.

10.1. The Parties agree that this DPA shall replace and supersede any existing data processing addendum, attachment, exhibit or standard contractual clauses that the Parties may have previously entered into in connection with the Service. We may update this DPA from time to time, provided that no such update shall materially diminish the privacy or security of Customer Personal Data.

10.2. Except as provided by this DPA, the Agreement remains unchanged and in full force and effect. If there is any conflict between this DPA and the Agreement, this DPA shall prevail to the extent of that conflict in connection with the Processing of Customer Personal Data. Notwithstanding the foregoing, and solely to the extent applicable to any Customer Personal Data comprised of patient, medical or other protected health information regulated by HIPAA, if there is any conflict between this DPA and a business associate agreement between Customer and us, then the business associate agreement shall prevail solely with respect to such Customer Personal Data.

10.3. Notwithstanding anything to the contrary in the Agreement or this DPA, each Party’s and all of its Affiliates’ liability, taken together in the aggregate, arising out of or relating to this DPA, the Transfer Mechanisms, and any other data protection agreements in connection with the Agreement (if any), shall be subject to any aggregate limitations on liability set out in the Agreement. Without limiting the Parties’ obligations under the Agreement, each Party agrees that any regulatory penalties incurred by one Party (the “Incurring Party”) in relation to the Customer Personal Data that arise as a result of, or in connection with, the other Party’s failure to comply with its obligations under this DPA or any applicable Data Protection Laws shall count toward and reduce the Incurring Party’s liability under the Agreement as if it were liability to the other Party under the Agreement.

10.4. In no event shall this DPA benefit or create any right or cause of action on behalf of a third party (including a Third-Party Controller), but without prejudice to the rights or remedies available to Data Subjects under Data Protection Laws or this DPA (including the Transfer Mechanisms).

10.5. This DPA will be governed by and construed in accordance with governing law and jurisdiction provisions in the Agreement.

Last updated: April 19, 2024