Sign Up
Star us on Github

Star

2403

Yosemite Crew License and
Subscription Terms (SaaS)

1. DEFINITIONS

In addition to terms defined elsewhere in this Agreement, the following terms have the following meanings:

  • 1.1. Admin Account means the Account that the Customer registers with signing up to the service and that has the most comprehensive rights including creating new Users.
  • 1.2. Agreement means the contract concluded with the Customer under theseYosemite CrewLicense and Subscription Terms and its Appendices.
  • 1.3. Business Owner means a Customer registering as a Business Owner who can interact with Pet Owners
  • 1.4. Customer means any company having entered or about to enter into a contractual relationship with DuneXploration in order to allow Users (typically its employees) the use of the SaaS Service and/or the Software.
  • 1.5. Customer Data means all content and data, including but not limited to personal data, either provided by the Customer or entered on its behalf, through use of the SaaS Services or collected or generated by the SaaS Services on behalf of the Customer, and which remains in DuneXploration’s possession and control as part of the SaaS Services.
  • 1.6. Data Subject means any identified or identifiable natural person in accordance with the definitions of the GDPR.
  • 1.7. Developer means a Customer registering as a Developer to sell plugins on the Digital Marketplace to Business Owners.
  • 1.8. Digital Marketplace means the online platform that allows Developers the selling of plugins to Business Owners.
  • 1.9. Documentation means any technical specification documentation, technical product descriptions, user guides and technical integration guides relating to the SaaS Services.
  • 1.10. DPA means DuneXploration’s data processing agreement agreed between DuneXploration and Customers as attached in Exhibit B.
  • 1.11. DuneXploration means the DuneXploration UG (haftungsbeschränkt), Am Finther Weg 7, 55127 Mainz.
  • 1.12. Intellectual Property means all rights of intellectual property, such as copyrights, trademark rights, patents, model rights, trade name rights, database rights and neighbouring rights, as well as domain names and know-how and any related rights.
  • 1.13. Mobile App means the application for Pet Owners, Customer and Users that gives Customer access to the SaaS Services from a mobile device and provides Pet Owners access to services of Business Owners and certain functions such as booking appointments.
  • 1.14. Pet Owner means a person using the Mobile App to manage their pets and book appointments or services at a Business Owner.
  • 1.15. SaaS Access Rights means type and quantity of SaaS access rights granted to the Customer for use during the applicable Subscription Term.
  • 1.15. SaaS Services means the online service Yosemite Crew, a Practice Management Software (“PMS”) for Business Owners and a platform for Developers to offer plugins to Business Owners including all its functions and all SaaS Access Rights offered by DuneXploration.
  • 1.17. Services means the SaaS Services and the Additional Services (if any) together.
  • 1.18. Software means the Self Hosting Version of the PMS provided under an Open Source Software License.
  • 1.19. Subscription Term means the Initial Subscription Term plus any Renewal Term(s).
  • 1.20. Support Services means the Services provided under the Support Services and Service Levels Policy.
  • 1.21. These Terms means these Yosemite Crew License and Subscription Terms.
  • 1.22. User means any user that is created by the Customer in the Admin Account irrespective of his or her role.tore it.

2. SCOPE

  • 2.1. These Terms shall apply to and control solely with respect to the Services. In the event of a conflict between these Terms and any other terms and conditions and/or Appendices of the Agreement, these Terms shall prevail with respect to the SaaS Services, unless explicitly provided otherwise.
  • 2.2. Licensing of the Software is not covered by these Terms but only governed by the applicable Open Source Software license.
  • 2.3. DuneXploration rejects any and all terms and conditions of Customers. Only these Terms apply to the respective contractual relationships with DuneXploration.
  • 2.4. In the event of a conflict between these Terms and an individual agreement between DuneXploration and a Customer, the individual agreement shall prevail, unless explicitly provided otherwise in these Terms.

3.OVERVIEW OF THE SAAS SERVICES

  • 3.1. DuneXploration operates a SaaS Service that provides Business Owners with a flexible and scalable PMS. The PMS is able to provide Business Owne rs with functions to manage their professional veterinary practice and services. For Developers the SaaS Service provides the necessary tools to offer plugins on a Digital Marketplace to Business Owners.
  • 3.2. A separate Mobile App is available to Pet Owners, Customer and Users that gives Customer access to the SaaS Services on a mobile device and provides Pet Owners access to services of Business Owners and certain functions such as booking appointments. The Mobile App is provided by DuneXploration separately and guided by separate terms and conditions.
  • 3.3. The SaaS Service can be used in different countries and languages. The SaaS Service is available anywhere with a good internet connection.

4. CONCLUSION OF THE AGREEMENT AND REGISTERING FOR AN ACCOUNT

  • 4.1. The Customer has to register to use the SaaS Service. Registering is free of charge for the Customer.
  • 4.2. The Customer can register directly by visiting the website www.yosemitecrew.com by creating an Admin Account. The person registering the Admin Account for the Customer confirms that he or she has the necessary legal power and capacity to act on Customer’s behalf and conclude the Agreement.
  • 4.3. By clicking on “Sign Up”, the Customer asks DuneXploration to create an Admin Account on the Platform and DuneXploration will send an email with a legally binding offer to open the Admin Account and to confirm the Customer’s email address. By clicking on “confirm email”, the Customer accepts the offer, concludes the contract with DuneXploration and opens the Admin Account.
  • 4.4. After the sign up, Customer has to provide certain basic information, including its place of business, business registration number and an address and further information depending on if the Customer is a Business Owner or a Developer. The Customer can rectify all and any information at any time during sign up and later in the settings of the Admin Account.
  • 4.5. Customer shall keep all account information, and especially the chosen password, confidential and not disclose it to any third party. Any abuse or suspected abuse shall be reported to DuneXploration immediately.
  • 4.6. The User can access these terms anytime on the SaaS Service in the most recent version. The Agreement is concluded in English and These Terms are available in English exclusively.

5. FUNCTIONS OF THE PMS

  • 5.1. The PMS provides Business Owners with the necessary functions to manage their veterinary practice or other veterinary professional services. The functions of the PMS include, depending on the chosen type of business:
    • 5.1.1. An overview of all relevant metrics of their business
    • 5.1.2. The ability to manage Users
    • 5.1.3. Options regarding the visibility of the clinic
    • 5.1.4. The ability to manage appointments
    • 5.1.5. Role and permission management
    • 5.1.6. Inventory and procedure management
    • 5.1.7. Billing and invoicing
  • 5.2. DuneXploration reserves the right to add, remove or modify functions from the PMS in the future but will ensure that the core functions of the PMS mentioned above will be available to Customer. It will notify Customer of changes.

6. FUNCTIONS FOR DEVELOPERS

  • 6.1. Developers can use the SaaS Service to develop plugins for the PMS and sell them to Business Owners on the Digital Marketplace.
  • 6.2. The Digital Marketplace is still under development and details will be added in the future.

7. OFFERING SERVICES TO PET OWNERS

  • 7.1. If Business Owners decide to make their services visible for all Pet Owners on the Mobile App (for example booking appointments but also to provide other services such as diabetes assessments), the following provisions to fulfil our obligations from the REGULATION (EU) 2019/1150 on promoting fairness and transparency for business users of online intermediation services (“P2B Regulation”) applies. With regard to the obligations from the P2B Regulations DuneXploration gives Customer the following information:
  • 7.2. Access to Data
    • 7.2.1. Access to Customer Data by DuneXploration
      Since DuneXploration operates the SaaS Service it can access any Customer Data (including User and Pet Owner data). This includes, in particular, the following categories of data:
      • Contact Details
      • Pet data
      • Accounting data
      • Booked appointments or services rendered and any related data and
      • Usage data.
      A comprehensive List of data processed for Customer can be found in Appendix 1 Annex 2 of the DPA. Access to such data is granted solely for the purposes of operating, improving, and securing the SaaS Services, ensuring compliance with applicable law, and supporting Business Owners in the provision of their services.
    • 7.2.2. Access to Customer Data by Business Owners Each Business Owner has access to all Customer Data they have provided to DuneXploration in the context of using the SaaS Service and to the data that is generated through the provision of the SaaS Service. Access is granted via the functions of the SaaS Service. With regard to the services offered to all Pet Owners this includes, in particular, the following categories of data:
      • Contact Details
      • Booked appointments or services rendered and any related data
      • Pet data
      • Billing information.
      A comprehensive List of data processed for Customer can be found in Appendix 1 Annex 2 of the DPA.
    • 7.2.3. Access to Data provided by or generated by other Customers or Pet Owners: Business Owners do not access data of other Customers or Pet Owners.
    • 7.2.4. Disclosure of Data to Third Parties: Other than Customer Data made public to Pet Owners or Developers, DuneXploration only shares Customer Data with technical service providers listed in the Data Processing Agreement.
  • 7.3.1 Main Parameters Used for Ranking:
    • Services offered by Customer
    • If relevant for the Service (for example for booking appointments the Customer’s Location (e.g., proximity to the Pet Owner’s search location);
    • Service hours
    • User ratings
    • Business Name (e.g., alphabetical order or match with search terms). These parameters are considered to ensure relevant, (where applicable) localized, and easily identifiable results for Pet Owners.
    • Pet Owners have at the moment the following filters to modify their search for services:
      • Previous
      • Vet New Vet
  • 7.3.2.Relative Weighting of Parameters:Among the above parameters, (if relevant) location is typically given higher weight than name, as geographic preference plays a more significant role for Pet Owner. If location is not relevant the service hours are the most relevant factor.
  • 7.3.3. Influence of Payments on Ranking: Customers cannot influence their ranking through direct or indirect payments to DuneXploration. No payment-based ranking advantages are offered or applied.
  • 7.3.4. Product or Service Characteristics and Consumer Relevance: The ranking mechanism may also take into account certain characteristics of the services offered, including relevance to consumer preferences based on prior search behaviour or explicitly provided filters. However, these aspects play a secondary role in the default ranking logic.
  • 7.4.Retention of Data
    • 7.4.1. After termination of the Agreement, DuneXploration does not retain any identifiable Customer Data.
    • 7.4.2. However, DuneXploration may retain Customer Data in aggregated and anonymized form, provided such data cannot be traced back to a Customer or Data Subject. This aggregated data may be used for statistical analysis, service improvement, or market research purposes.
    • 7.4.3. Customer Access: The Customer has no access to any data after termination of the Agreement.

8. DUNEXPLORATION’S RESPONSIBILITIES

  • 8.1. Subject to any other individual agreement with the Customer, DuneXploration provides the technical resources for the SaaS Service and allows Users to use the Yosemite Crew Platform as described in these Terms.
  • 8.2. DuneXploration provides the SaaS Services on servers up to the access point of DuneXploration's data center (“Service Delivery Point”). The Customer is responsible for maintaining its own internet access to reach the Service Delivery Point.
  • 8.3. Service levels are specified in Exhibit A – Support Services and Service Level Policy.
  • 8.4. As part of the SaaS Services, DuneXploration will provide Support Services. In addition to establishing and maintaining the hosted environment of the SaaS Services, DuneXploration will maintain the components of the SaaS Services with all current updates that DuneXploration deems necessary for the SaaS Services. DuneXploration will use commercially reasonable efforts to implement any required error corrections or other necessary fixes for the SaaS Services.
  • 8.5. As a part of the SaaS Services, DuneXploration will also maintain a backup of all Customer Data that DuneXploration is required to retain as a part of the SaaS Services. In the event the Customer Data becomes destroyed or corrupt, DuneXploration shall use commercially reasonable efforts to restore all available data from backup, and to remediate and recover such corrupt data.

9. SAAS ACCESS RIGHTS AND LICENSES

  • 9.1. During the Subscription Term, DuneXploration grants to the Customer, solely for the Customer’s internal business use and subject to the limitations and restrictions set in these Terms, a non-exclusive, non-transferable, non-sublicensable right to use the SaaS Services. With respect to the Documentation applicable to the SaaS Services, the Customer may make a reasonable number of copies of the Documentation solely as needed for the Customer’s and its Affiliates’ internal business purposes.
  • 9.2. The Customer acknowledges and agrees that the use rights provided hereunder do not grant any rights not explicitly expressed. All other such rights and interests in DuneXploration’s Intellectual Property (including any derivatives thereto) are expressly reserved and remain vested in DuneXploration.
  • 9.3. Except as otherwise specified in an Addendum, expressly permitted in writing by DuneXploration, or otherwise cannot be precluded under mandatory applicable law, Customer shall not, and shall not permit any other party to:
  • 9.4. Disassemble, decompile, decrypt, or reverse engineer, or attempt to discover or reproduce source code for any part of the SaaS Services or on-premise components; adapt, modify, or prepare derivative works based on any of DuneXploration’s Intellectual Property; or use any of DuneXploration’s Intellectual Property to create any program or material that performs, replicates, or utilizes the same or substantially similar functions as the SaaS Service.
  • 9.5. Alter, remove, or suppress any copyright, confidentiality, or other proprietary notices, marks, or legends placed on or embedded in DuneXploration Intellectual Property, or fail to ensure that such notices and legends appear on all full or partial copies of DuneXploration Intellectual Property or any related material.
  • 9.6. Sell, sublicense, lease, assign, delegate, transfer, distribute, encumber, or otherwise transform any DuneXploration Intellectual Property or any of the rights or obligations granted to or imposed on the Customer hereunder.

10. CUSTOMER’S OBLIGATIONS

  • 10.1. Customer allocates User Accounts to its employees in accordance with the license purchased.
  • 10.2. Customer must ensure that their use of the SaaS Service fulfills all applicable statutory requirements, such as maintaining a proper license, compliance with consumer protection law, data protection law, and statutory information obligations (e.g., maintaining an imprint). DuneXploration is not responsible for any breach of such statutory provisions by the Customer.
  • 10.3. If the SaaS Services have an error or malfunction, the Customer shall immediately notify DuneXploration thereof in accordance with the provisions of Exhibit A — SUPPORT SERVICES AND SERVICE LEVEL POLICY.
  • 10.4. The Customer is responsible for ensuring that all Users comply with these Terms by monitoring and instructing its Users accordingly. In particular, the Customer shall:
    • explicitly inform its Users that the SaaS Services may only be used in a professional context and only for professional matters;
    • instruct its Users not to use the SaaS Services for illegal purposes, in particular not to harm third parties or DuneXploration. Customer will also not carry out any such actions itself;on.
    • not use the SaaS Services in a way that compromises the security, proper functioning and integrity of DuneXploration's systems or that circumvents or compromises security measures. In particular, the Customer will instruct their Users not to generate malicious, harmful prompts or to carry out prompt injection attacks in order to manipulate the behavior of the SaaS Services, or to carry out vulnerability, penetration or similar tests;
    • not to pass off output generated by means of the SaaS Services as having been created by a human, and not to use the output if there is reason to believe that the use of the output could infringe the rights of third parties.
  • 10.5. The Customer shall ensure and inform Users about the acceptable use of the SaaS Services as specified in these Terms.

11. TECHNICAL DEPENDENCIES AND LIMITATIONS

  • In order to use the SaaS Services, Users need to meet the following technical requirements:
    • Current versions of Windowsand MacOS Xare fully supported (“Supported Operating Systems”).
    • Current versions of Chrome, Firefox, Safari, or Edgeare fully supported (“Supported Browsers”).
    • A sufficient network broadband connectionis required.

12. ACCEPTABLE USE POLICY

  • 12.2. The Customer may not use the SaaS Services in a way that unnecessarily interferes with the normal operation of the SaaS Services generally.
  • 12.3. The Customer is responsible for maintaining the confidentiality and security of all passwords issued, and for ensuring that each password is only used by the individual(s) authorised. To the extent DuneXploration enables the Customer with administrative rights to create passwords for its personnel, the Customer shall be responsible for issuing such passwords.
  • 12.4. If the Customer violates the acceptable use policy set forth in this Section, DuneXploration may require the Customer to immediately abstain from any such action or behaviour, provided that DuneXploration may also terminate this Agreement for cause with or without notice if the violation(s) of the acceptable use policy are, decided in DuneXploration’s sole discretion, of such gravity as to justify such termination. In such case DuneXploration will give Customer sufficient time (at least 30 days) to
    • The Customer may not use the SaaS Services in a way that unnecessarily interferes with the normal operation of the SaaS Services generally.
    • The Customer is responsible for maintaining the confidentiality and security of all passwords issued, and for ensuring that each password is only used by the individual(s) authorised. To the extent DuneXploration enables the Customer with administrative rights to create passwords for its personnel, the Customer shall be responsible for issuing such passwords.
    • If the Customer violates the acceptable use policy set forth in this Section, DuneXploration may require the Customer to immediately abstain from any such action or behaviour, provided that DuneXploration may also terminate this Agreement for cause with or without notice if the violation(s) of the acceptable use policy are, decided in DuneXploration’s sole discretion, of such gravity as to justify such termination. In such case DuneXploration will give Customer sufficient time (at least 30 days) to

13. FEES

  • 13.1. The Customer shall pay DuneXploration a fee for rendering the Services. The calculation depends on several factors and is described on the website.
  • 13.2. DuneXploration shall invoice the Customer according to the criteria in Section 13.1 to Section 13.3 at the end of each month.
  • 13.3. Customer shall pay all Subscription Fees with the payment method specified in the Admin Account.
  • 13.4. All amounts due to DuneXploration hereunder are net amounts, exclusive of, and the Customer is responsible for paying, all value added taxes or other similar taxes. DuneXploration will issue its invoices in accordance with the applicable laws and may thus, as the case may be, also invoice the payable value added taxes.
  • 13.5. DuneXploration is entitled to increase the prices the fee is calculated on for the first time after the expiry of 12 months following the start of the contract provided that DuneXploration’s costs for the provision of the SaaS Service have increased by at least 20% compared to the same month of the previous year. DuneXploration shall communicate the increase in writing (email to suffice) at least 2 months before the increase shall come into force. The Customer has the right to terminate the Agreement within a period of 30 days after receiving the notice. DuneXploration shall inform the customer of the termination right together with each notification of a price increase. CUSTOMER DATA
  • 13.6. DuneXploration acknowledges it receives no ownership or, except to the extent specified herein and in Section 10.2, other rights in any Customer Data, and all rights, title and interest in such Customer Data remain with Customer. DuneXploration shall not, and shall not permit its Personnel to use or disclose Customer Data, unless authorized by the terms and conditions of this Addendum, by the Customer in writing, or if DuneXploration is required to do so by law or court order.
  • 13.7. Customer agrees that DuneXploration may:
    • (a) use and disclose in aggregate, anonymous and de-identified form, information derived from Customer Data where the resulting information does not in any way identify or allow the identification of Customer or any Personal Data, and
    • (b) access, use in accordance with the terms and conditions of this Addendum, but not otherwise use or disclose, Customer Data for DuneXploration’s internal business purposes, including for purposes of planning, support, administration and invoicing related to Customer’s use of the SaaS Services, improving or creating new offerings related to the SaaS Services.
    Customer acknowledges that DuneXploration owns all right, title and interest in and to the aggregated data. The Customer instructs DuneXploration within the framework of the DPA to anonymize the personal data for the aforementioned use.
  • 13.8. Customer agrees that Customer is solely responsible for:
    • (i) obtaining any Customer Data and other information Customer provides while using the SaaS Services,
    • (ii) obtaining all rights and consents necessary to collect, retain, use and disclose the Customer Data,
    • (iii) ensuring the Processing, collection, retention and any other processing of Personal Data in connection with the use and delivery of the SaaS Services does not violate the rights of Data Subjects or the Privacy Laws,
    • (iv) establishing and complying with a retention schedule and destruction guidelines related to Customer Data where required by law,
    • (v) the accuracy, completeness, quality, integrity, legality, reliability, appropriateness and copyright of all Customer Data.
    By providing any Customer Data or other information, Customer represents and warrants that such information does not:
    • (a) violate any intellectual property rights, publicity rights, confidentiality or trade secret rights, or any other legal or equitable rights;
    • (b) violate any law, rule, order, judgment or regulation to which Customer or the Customer Data may be subject; and
    • (c) violate in any way Customer’s obligations.
  • 13.9. Customer acknowledges and agrees that DuneXploration is not responsible or liable for any unlawful, harassing, defamatory, privacy invasive, abusive, threatening, offensive, harmful, vulgar, obscene, tortuous, hateful, racially, ethnically or otherwise objectionable information contained in Customer Data, or content, or information or content contained in Customer Data that infringes or may infringe any copyright, patent, moral right, trade secret, confidential information, trademark right or any other right of a third party. DuneXploration may remove any violating content posted on the SaaS Services or transmitted through the SaaS Services, without notice to Customer.
  • 13.10. In addition to all other obligations in this Addendum with respect to Customer Data, each party agrees to comply with its obligations under Privacy Laws, and in the context of any Processing of Personal Data through the provision of the SaaS Services, the Parties shall comply with the DPA in Exhibit 2, which is hereby incorporated into the Agreement.

14. WARRANTY

  • 14.1. DuneXploration will meet warranty claims and rights that the Customer may have against DuneXploration in accordance with the applicable statutory provisions, subject only to Sections 15.2 and 15.3.
  • 14.2. Claims to reduce the Subscription Fees shall fall under the statute of limitations one year after the end of the calendar year during which the claims came into existence and the Customer knew or should have reasonably known the factual circumstances that gave rise to the claim.
  • 14.3. Damage claims are subject to the provision of Section 16.
  • 14.4. DuneXploration may temporarily restrict access to the SaaS Service in order to carry out maintenance work in accordance with the provision of the Exhibit A SUPPORT SERVICES AND SERVICE LEVEL POLICY.

15. LIMITATION OF LIABILITY

  • 15.1. DuneXploration shall be liable in accordance with the applicable statutory provisions (whether in contract, tort or otherwise) for damages suffered by the Customer that (i) have been caused as a result of DuneXploration, its legal representatives, its agents or auxiliaries having acted, or having failed to act where there was a duty for DuneXploration to act, in gross negligence or with wilful or malicious intent; (ii) have occurred as a result of a breach of a guarantee (the term “guarantee” in accordance with the applicable statutory meaning); (iii) are a result of a culpably caused injury to life, limb or health; and/or (iv) are subject to product liability under the German Product Liability Act.
  • 15.2. In cases of negligence other than gross negligence, DuneXploration shall only be liable for damages that result from breaches of material contractual obligations. This limitation of liability shall not apply, however, where the damages result from culpably caused injuries to life, limb or health or a breach of a guarantee (as defined in Section 15.1). “Material contractual obligations” are such contractual obligations that, if breached, jeopardize the aim and purpose of the contract, and are such that the other contractual party may generally rely on.
  • 15.3. In cases of negligence other than gross negligence, DuneXploration’s liability shall also be limited to damages that are typically foreseeable in the context of an agreement such as this Agreement. This limitation of liability shall, however, likewise not apply where the damages result from culpably caused injuries to life, limb or health or a breach of a guarantee (as defined in Section 15.1).
  • 15.4. Other than in cases that fall under Section 15.1 and (other) cases where the damages result from culpably caused injuries to life, limb or health or a breach of a guarantee (as defined above):
    • 15.4.1. DuneXploration shall not be liable for indirect, consequential or special damages.
    • 15.4.2. DuneXploration’s aggregate liability under this Agreement shall not exceed the greater of: (a) the aggregate Fees paid or payable by the Customer to DuneXploration in the twelve (12) calendar months prior to the event giving rise to the liability; or (b) 5,000 EUR.
  • 15.5. Any liability other or beyond the liability provided in Sections 15.1 to 15.3 is excluded.
  • 15.6. The Customer is responsible for ensuring the routine backup of its data. Irrespective of Sections 15.1 to 15.3, if the Customer suffers damages that result from the loss of data, DuneXploration shall in each case only be liable for such damages insofar as the damages could not have been avoided by the Customer carrying out data backups of all relevant data in regular intervals according to good industry practice.
  • Damage claims, irrespective of their legal origin and nature (contract, tort or other), shall fall under the statute of limitations one year after the end of the calendar year during which the claims came into existence and the Customer knew or should have reasonably known the factual circumstances that gave rise to the claim. The foregoing sentence shall, however, not apply where the damage has been caused by, or has not been remedied with or because of, DuneXploration’s wilful intent, where DuneXploration had maliciously concealed a defect in the Products, in cases of injuries to life, limb or health, and/or where the corresponding claims result from the German Product Liability Act.

16. CONFIDENTIALITY

  • 16.1. Each Party (the “Receiving Party”) understands that the other Party (the “Disclosing Party”) has disclosed or may disclose information relating to the Disclosing Party’s business (hereinafter referred to as “Confidential Information” of the Disclosing Party). The Receiving Party agrees:

    (i) to take reasonable precautions to protect such Confidential Information, and

    (ii) not to use (except as expressly permitted herein) or divulge to any third person any such Confidential Information.

  • 16.2. The Disclosing Party agrees that the foregoing shall not apply with respect to any information after ten years following the disclosure thereof (except Confidential Information that is identified as trade secrets, in which case the foregoing obligations are ongoing) or any information that the Receiving Party can document: (a) is or becomes generally available to the public, (b) was in its possession or known by it prior to receipt from the Disclosing Party, (c) was rightfully disclosed to it without restriction by a third party, (d) was independently developed without use of any Confidential Information of the Disclosing Party, or (e) is required by law to be disclosed, provided that the Receiving Party first provides the Disclosing Party with reasonable prior notice and obtains, or provides the Disclosing Party with an opportunity to obtain, a protective order or confidential treatment of the Proprietary Information.

17. USE OF CUSTOMER NAME AND LOGO

  • Customer grants DuneXploration a non-exclusive, non-transferable, royalty-free, worldwide license to use, distribute, reproduce and display Customer’s trade name(s), trademarks, and logos (collectively, “Marks”) for use by DuneXploration on its website, in marketing materials and for similar marketing purposes.

18. TERM AND TERMINATION

  • 18.1. This Agreement shall commence on the Order Effective Date and shall continue for the Initial Subscription Term. The Agreement automatically renews for subsequent Renewal Terms except where a Party provides the other with no less than thirty (30) days’ notice prior to the expiry of the Initial Subscription Term or, as the case may be, the then-current Renewal Term of its intent to not renew.
  • 18.2. The rights of the Parties to terminate this Agreement for cause remains unaffected.
  • 18.3. Reasons to terminate for cause are specifically (but not exclusively):
    • 18.3.1. A breach of Sections 10 and 12 by Customer; or
    • 18.3.2. By either party a material breach which has not been cured within thirty (30) days after written notice of such breach; or
    • 18.3.3. By either party at any time if the other party makes an assignment for the benefit of creditors, or commences or has commenced against it any proceeding in bankruptcy or insolvency;
  • 18.4. Notices of non-renewal as well as termination notices must be made in writing (email to suffice).

20. MISCELLANEOUS

  • 20.1. This Agreement is governed by, and shall be interpreted in accordance with, the laws of, and directly applicable in, the Federal Republic of Germany, excluding, however, the provisions of the United Nations Convention on Contracts for the International Sale of Goods and any conflict of law provisions that would require the application of the material law of another country.
  • 20.2. Unless otherwise expressly set forth in this Agreement, any provision of this Agreement (including this Section 20.2) may only be amended or waived by a written agreement executed by both Parties.
  • 20.3. Neither Party is entitled to assign, delegate or otherwise transfer any rights, claims or obligations under this Agreement, in whole or in part, without the prior written consent of the other Party except that DuneXploration is entitled to assign this Agreement as a whole, as well as individual rights and claims under this Agreement to an Affiliate of DuneXploration. Section 354a of the German Commercial Code remains unaffected.
  • 20.4. The Parties hereby irrevocably submit to the exclusive jurisdiction of the courts of Mainz, Germany, for all disputes or claims arising out of or in connection with this Agreement made hereunder.

Updated: June 2025

EXHIBIT A

SUPPORT SERVICES AND SERVICE LEVEL POLICY

1. DEFINITIONS

1.1. Emergency Downtime means such time as the SaaS Service is offline due to a short-term emergency condition, provided that: (a) the incident lasts less than three (3) hours; and (b) there have been no prior Emergency Downtime incidents within 90 days before the incident.

1.2. Excused Downtime means any downtime that is Maintenance Downtime or Emergency Downtime or that is caused by the failure of any third party vendors, the Internet in general, or any event beyond the reasonable control of the party, including force of nature, war, riot, civil action, terrorism, labor dispute, malicious acts or denial of service by a third party, or failure of telecommunication systems or utilities (“Force Majeure Event”).

1.3. Error means a failure of the SaaS Service to conform to the specifications set forth in the Documentation, resulting in the inability to use, or material restriction in the use of the SaaS Service.

1.4. Maintenance Downtime means such time as the SaaS Service is offline for maintenance or backup purposes, provided that the incident is scheduled with Customer at least 24 hours in advance.

1.5. Monthly Availability Percentagemeans the percentage of time over the course of each calendar month during the Subscription Term, excluding Excused Downtime, that the SaaS Service is available for use by Customer.

1.6. Start Time means the time at which DuneXploration first becomes aware of an Error.

1.7. Update is a SaaS Service release that DuneXploration makes generally available to all DuneXploration customers, along with any corresponding changes to Documentation. An Update may be an error correction or bug fix; or it may be enhancement, new feature, or new functionality.

2. SUPPORT SERVICES

DuneXploration will provide Support Services to Customer through an online form (support@yosemitecrew.com) and a discord chat (https://discord.gg/YVzMq97Bk) or through other customer support center contacts, set forth below (the“Customer Support Center”). Customer will receive Updates, other software modifications or additions, procedures, or routine or configuration changes that may solve, bypass or eliminate the practical adverse effect of the Error. Customer will designate a certain number of employees or agents that will interface with the Customer Support Center, and submit Errors, requests or support tickets (the “Technical Support Contacts”). Customer is permitted to name as many Technical Contacts as allowed pursuant to the purchased Support Service Subscription. Customer’s non-named Technical Contacts may contact the Customer Support Center only in case of an emergency or on an exception basis, and DuneXploration will respond to such Error submission and cooperate with the non-named Technical Contact, subject to later verification and involvement of a named Technical Support Contact. Additional named Technical Support Contacts may be permitted upon mutual agreement of the parties.

3. SUPPORT SERVICES SUBSCRIPTIONS

Customer will have access to the Customer Support Center, Monday through Friday, 9 a.m. to 5 p.m. (DuneXploration’s local time). Submitted Errors will be classNameified by severity as set forth in the table below. Customer may assign two (2) Technical Support Contacts, which may contact the Customer Support Center through any of the Customer Support Center Contacts, as set forth below.

4. SAAS SERVICE AVAILABILITY

DuneXploration will use its commercially reasonable efforts to ensure a Monthly Availability Percentage of the SaaS Service is equal to or greater than 99.99% excluding any Excused Downtime.

5. SERVICE LEVEL CREDITS

5.1. If DuneXploration does not meet the Uptime levels specified below, Customer will be entitled, upon written request, to a service level credit (“Service Level Credit”) to be calculated as follows:

  • If Uptime Percentage is at least 99.995% of the month’s minutes, no Service Level Credits are provided; or
  • If Uptime Percentage is 99.75% to 99.94% (inclusive) of the month’s minutes, Customer will be eligible for a credit of 5% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to DuneXploration; or
  • If Uptime Percentage is 99.50% to 99.74% (inclusive) of the month’s minutes, Customer will be eligible for a credit of 7.5% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to DuneXploration; or
  • If Uptime Percentage is less than 99.50% of the month’s minutes, Customer will be eligible for a credit of 10.0% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to DuneXploration.

5.2. Customer shall only be eligible to request Service Level Credits if it notifies DuneXploration in writing within thirty (30) days from the end of the month for which Service Level Credits are due. All claims will be verified against DuneXploration’s system records. In the event after such notification DuneXploration determines that Service Level Credits are not due, or that different Service Level Credits are due, DuneXploration shall notify Customer in writing on that finding. Service Level Credits will be applied to the next invoice following Customer’s request and DuneXploration’s confirmation of available credits. Service Level Credits shall be Customer’s sole and exclusive remedy in the event of any failure to meet the Service Levels. DuneXploration will only provide records of system availability in response to good faith Customer claims.

6. CUSTOMER SUPPORT CENTER CONTACT

Phone SupportEnglish
Support PhoneNone
Support Mailsupport@yosemitecrew.com
Support Chathttps://discord.gg/YVzMq97Bk

7. ERROR RESPONSE SERVICE LEVELS

Customer shall submit each ticket with a severity level designation based on the definitions in the table below. Severity response times do not vary, whether Customer contacts the Customer Support Center via phone or email. DuneXploration shall respond to such ticket in accordance with the severity designation and validate Customer’s severity level designation or notify Customer of a proposed change in the severity level designation with justification for the change. DuneXploration will provide continuous efforts to resolve Severity 1 issues until a workaround or resolution can be provided or until the incident can be downgraded to a lower severity. DuneXploration will use reasonable efforts to meet the target response times for the Errors stated in the table below.

Severity LevelDescriptionResponse Time
Severity 1 (Critical)Any Error in the SaaS Service causing the SaaS Service to be unusable, resulting in a critical impact on the operation of the SaaS Service and there is no workaround DuneXploration will promptly: (i) assign a specialist to correct the Error; (ii) provide ongoing communication on the status of an Update; and (iii) begin to provide a temporary workaround or fix.Within 2 hours.
Severity 2 (Serious)An Error in a SaaS Service where the SaaS Service will operate but its operation is severely restricted. No workaround is available, and performance may be degraded, or functions are limited. DuneXploration will promptly: (i) assign a specialist to correct the Error; and (ii) provide additional escalated Support Services as determined necessary by DuneXploration.Within 4 hours.
Severity 3 (Moderate)An Error in the SaaS Service where the SaaS Service will operate with limitations that are not critical to the overall operation, such as a workaround forces user and or a systems operator to use a time-consuming procedure to operate the system; or removes a non -essential feature. DuneXploration will triage the request and may include a resolution in the next Update.Within 8 hours.
Severity 4 (Low)An Error in the SaaS Service where the SaaS Service can be used with only slight inconvenience. All SaaS Service feature requests fall into this severity level. DuneXploration will triage the request and may include a resolution in the next Update.Next business day.

EXHIBIT A

SUPPORT SERVICES AND SERVICE LEVEL POLICY

1. DEFINITIONS

1.1. Emergency Downtime means such time as the SaaS Service is offline due to a short-term emergency condition, provided that: (a) the incident lasts less than three (3) hours; and (b) there have been no prior Emergency Downtime incidents within 90 days before the incident.

1.2. Excused Downtime means any downtime that is Maintenance Downtime or Emergency Downtime or that is caused by the failure of any third party vendors, the Internet in general, or any event beyond the reasonable control of the party, including force of nature, war, riot, civil action, terrorism, labor dispute, malicious acts or denial of service by a third party, or failure of telecommunication systems or utilities (“Force Majeure Event”).

1.3. Error means a failure of the SaaS Service to conform to the specifications set forth in the Documentation, resulting in the inability to use, or material restriction in the use of the SaaS Service.

1.4. Maintenance Downtime means such time as the SaaS Service is offline for maintenance or backup purposes, provided that the incident is scheduled with Customer at least 24 hours in advance.

1.5. Monthly Availability Percentage means the percentage of time over the course of each calendar month during the Subscription Term, excluding Excused Downtime, that the SaaS Service is available for use by Customer.

1.6. Start Time means the time at which DuneXploration first becomes aware of an Error.

1.7. Update is a SaaS Service release that DuneXploration makes generally available to all DuneXploration customers, along with any corresponding changes to Documentation. An Update may be an error correction or bug fix; or it may be enhancement, new feature, or new functionality.

Exhibit B
Data Processing Agreement

The Customer as defined in the Yosemite Crew License and Subscription Terms (SaaS) – hereinafter referred to as the Controller/Data Importer – and DuneXploration as defined in the Yosemite Crew License and Subscription Terms (SaaS) – hereinafter referred to as the Processor/Data Exporter – each a ‘party’; together ‘the parties’ –

HAVE AGREED on the following Data Processing Agreement (the “DPA”) in order to fulfil their obligation according to Art. 28 (3) GDPR.

Preamble

The Parties have concluded the “Yosemite Crew License and Subscription Terms (SaaS)” under which the Processor performs services for the Customer. For the performance of the services, it is necessary that the Processor processes personal data for and on behalf of the Controller. The purpose of this agreement is to stipulate the obligations of the parties in connection with any processing of personal data by Processor as data processor on behalf of Controller as data controller.

1. Application of the Standard Contractual Clauses

  1. The Parties conclude the Standard Contractual Clauses between controllers and processors as agreed upon by the European Commission in its Commission Implementing Decision (EU) 2021/915 of June 4 2021 and attached to this DPA as APPENDIX 1 (the “EU-Standard Contractual Clauses”). For clarity, Processor’s obligations and Controller’s rights concerning Personal Data apply even if the Personal Data relates to a data subject outside the European Union.
  2. The Parties agree upon including Clause 5 of the Standard Contractual Clauses and use OPTION 2 of Clause 7.7 regarding the general authorization of sub processors, whereas the time period in Clause 7.7 shall be 2 weeks. Regarding any other OPTIONS to choose from in the Clauses of the Standard Contractual Clauses, the Parties in each case agree upon OPTION 1.
  3. The Parties conclude the Standard Contractual Clauses, MODULE 4 (Processor to Controller) for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 as agreed upon by the European Commission in its Commission Implementing Decision (EU) 2021/914 of 4 June 2021 and attached to this DPA as APPENDIX 2 (the “International Standard Contractual Clauses”). Regarding Clause 17 and Clause 18 (applicable law and jurisdiction) Germany is chosen each time. ANNEX 1 and 2 of APPENDIX 1 apply accordingly to describe the roles and the processing of personal data.
  4. The EU-Standard Contractual Clauses and International Standard Contractual Clauses will be supplemented by the provisions of this DPA.
  5. If any clause from this DPA or the Yosemite Crew License and Subscription Terms (SaaS) or any other related agreement between the Parties directly or indirectly contradicts the EU-Standard Contractual Clauses or International Standard Contractual Clauses, the respective Standard Contractual Clauses shall prevail. If any clause from the EU-Standard Contractual Clauses directly or indirectly contradicts the International Standard Contractual Clauses, the International Standard Contractual Clauses shall prevail.

2. Instructions of the Controller

  1. The Controller’s initial instructions shall be set out by the provisions of the Yosemite Crew License and Subscription Terms (SaaS), its Annexes and Appendices and any related agreement.
  2. The Controller shall be entitled to modify, amend or replace such individual instructions by issuing new instructions to the point of contact designated by the Processor. The instruction shall be given either in written form (email to suffice). In case of an oral instruction, the Controller shall immediately confirm this instruction in written form (email to suffice).
  3. Instructions not foreseen in or covered by the Yosemite Crew License and Subscription Terms (SaaS) shall be treated as requests for change in performance. The Controller shall immediately confirm in writing or in text form any instruction issued orally.

3. Technical and Organisational Measures

In Cases where the EU-Standard Contractual Clauses apply, the Processor has the right to amend or modify the technical and organisational measures that are set out in the DPA and its APPENDICES and ANNEXES at any time, provided, however, that the level of security shall not fall below the level initially agreed upon.

4. Obligations of the Controller

  1. The Controller shall notify the Processor without undue delay of any defect or irregularity of the services with regard to the processing of personal data detected by the Controller.
  2. The Controller shall notify the Processor’s point of contract for any issue related to data protection arising out of or in connection with the Yosemite Crew License and Subscription Terms (SaaS).

5. Inspections

  1. In cases where the EU-Standard Contractual Clauses apply, the Controller shall give the Processor reasonable notice before conducting an audit according to Clause 7.6 of the EU-Standard Contractual Clauses unless such notice is impossible to provide or would defeat the purpose of the audit.
  2. In cases where the EU-Standard Contractual Clauses apply, Processor shall be entitled to request a remuneration for Processor’s support in conducting audits in accordance with the then current price list of Processor.

6. Remuneration for Supporting Obligations

In cases where the EU-Standard Contractual Clauses apply and Insofar as Processor may claim compensation to the Controller for support services which are not included in the description of the services and which are not attributable to failures on the part of the Processor, the parties may agree in writing in advance to additional remuneration for Processor’s supporting obligations in connection with non-standard data protection requests.

Appendix I
Standard Contractual Clauses
Clause 1 - Purpose and scope

a. The purpose of these Standard Contractual Clauses (the Clauses) is to ensure compliance with [choose relevant option: OPTION 1: Article 28(3) and (4) of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data] / [OPTION 2: Article 29(3) and (4) of Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data].

b. The controllers and processors listed in Annex I have agreed to these Clauses in order to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 and/or Article 29 (3) and (4) Regulation (EU) 2018/1725.

c. These Clauses apply to the processing of personal data as specified in Annex II.

d. Annexes I to IV are an integral part of the Clauses.

e. These Clauses are without prejudice to obligations to which the controller is subject by virtue of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

f. These Clauses do not by themselves ensure compliance with obligations related to international transfers in accordance with Chapter V of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

Clause 2 - Invariability of the Clauses

a. The Parties undertake not to modify the Clauses, except for adding information to the Annexes or updating information in them.

b. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a broader contract, or from adding other clauses or additional safeguards provided that they do not directly or indirectly contradict the Clauses or detract from the fundamental rights or freedoms of data subjects.

Clause 3 - Interpretation

a. Where these Clauses use the terms defined in Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively, those terms shall have the same meaning as in that Regulation.

b. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively.

c. These Clauses shall not be interpreted in a way that runs counter to the rights and obligations provided for in Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or in a way that prejudices the fundamental rights or freedoms of the data subjects.

Clause 4 - Hierarchy

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

Clause 5 - Optional
Docking clause

a. Any entity that is not a Party to these Clauses may, with the agreement of all the Parties, accede to these Clauses at any time as a controller or a processor by completing the Annexes and signing Annex I.

b. Once the Annexes in (a) are completed and signed, the acceding entity shall be treated as a Party to these Clauses and have the rights and obligations of a controller or a processor, in accordance with its designation in Annex I.

c. The acceding entity shall have no rights or obligations resulting from these Clauses from the period prior to becoming a Party.

SECTION II – OBLIGATIONS OF THE PARTIES
Clause 6 - Description of processing(s)

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

Clause 7 - Obligations of the Parties
7.1. Instructions

a. The processor shall process personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. In this case, the processor shall inform the controller of that legal requirement before processing, unless the law prohibits this on important grounds of public interest. Subsequent instructions may also be given by the controller throughout the duration of the processing of personal data. These instructions shall always be documented.

b. The processor shall immediately inform the controller if, in the processor’s opinion, instructions given by the controller infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the applicable Union or Member State data protection provisions.

7.2. Purpose limitation

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

7.3. Duration of the processing of personal data

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

7.4. Security of processing

a. The processor shall at least implement the technical and organisational measures specified in Annex III to ensure the security of the personal data. This includes protecting the data against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to the data (personal data breach). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risks involved for the data subjects.

b. The processor shall grant access to the personal data undergoing processing to members of its personnel only to the extent strictly necessary for implementing, managing and monitoring of the contract. The processor shall ensure that persons authorised to process the personal data received have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

7.5. Sensitive data

If the processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (“sensitive data”), the processor shall apply specific restrictions and/or additional safeguards.

7.6. Documentation and compliance

a. The Parties shall be able to demonstrate compliance with these Clauses.

b. The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with these Clauses.

c. The processor shall make available to the controller all information necessary to demonstrate compliance with the obligations that are set out in these Clauses and stem directly from Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. At the controller’s request, the processor shall also permit and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or an audit, the controller may take into account relevant certifications held by the processor.

d. The controller may choose to conduct the audit by itself or mandate an independent auditor. Audits may also include inspections at the premises or physical facilities of the processor and shall, where appropriate, be carried out with reasonable notice.

e. The Parties shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority/ies on request.

7.7. Use of sub-processors

a. OPTION 1: PRIOR SPECIFIC AUTHORISATION: The processor shall not subcontract any of its processing operations performed on behalf of the controller in accordance with these Clauses to a sub-processor, without the controller’s prior specific written authorisation. The processor shall submit the request for specific authorisation at least [SPECIFY TIME PERIOD] prior to the engagement of the sub-processor in question, together with the information necessary to enable the controller to decide on the authorisation. The list of sub-processors authorised by the controller can be found in Annex IV. The Parties shall keep Annex IV up to date.

OPTION 2: GENERAL WRITTEN AUTHORISATION: The processor has the controller’s general authorisation for the engagement of sub-processors from an agreed list. The processor shall specifically inform in writing the controller of any intended changes of that list through the addition or replacement of sub-processors at least [SPECIFY TIME PERIOD] in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the concerned sub-processor(s). The processor shall provide the controller with the information necessary to enable the controller to exercise the right to object.

b. Where the processor engages a sub-processor for carrying out specific processing activities (on behalf of the controller), it shall do so by way of a contract which imposes on the sub-processor, in substance, the same data protection obligations as the ones imposed on the data processor in accordance with these Clauses. The processor shall ensure that the sub-processor complies with the obligations to which the processor is subject pursuant to these Clauses and to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

c. At the controller’s request, the processor shall provide a copy of such a sub-processor agreement and any subsequent amendments to the controller. To the extent necessary to protect business secrets or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.

d. The processor shall remain fully responsible to the controller for the performance of the sub-processor’s obligations in accordance with its contract with the processor. The processor shall notify the controller of any failure by the sub-processor to fulfil its contractual obligations.

e. The processor shall agree a third party beneficiary clause with the sub-processor whereby - in the event the processor has factually disappeared, ceased to exist in law or has become insolvent - the controller shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

7.8. International transfers

a. Any transfer of data to a third country or an international organisation by the processor shall be done only on the basis of documented instructions from the controller or in order to fulfil a specific requirement under Union or Member State law to which the processor is subject and shall take place in compliance with Chapter V of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725.

b. The controller agrees that where the processor engages a sub-processor in accordance with Clause 7.7. for carrying out specific processing activities (on behalf of the controller) and those processing activities involve a transfer of personal data within the meaning of Chapter V of Regulation (EU) 2016/679, the processor and the sub-processor can ensure compliance with Chapter V of Regulation (EU) 2016/679 by using standard contractual clauses adopted by the Commission in accordance with of Article 46(2) of Regulation (EU) 2016/679, provided the conditions for the use of those standard contractual clauses are met.

Clause 8 - Assistance to the controller

a. The processor shall promptly notify the controller of any request it has received from the data subject. It shall not respond to the request itself, unless authorised to do so by the controller.

b. The processor shall assist the controller in fulfilling its obligations to respond to data subjects’ requests to exercise their rights, taking into account the nature of the processing. In fulfilling its obligations in accordance with (a) and (b), the processor shall comply with the controller’s instructions.

c. In addition to the processor’s obligation to assist the controller pursuant to Clause 8(b), the processor shall furthermore assist the controller in ensuring compliance with the following obligations, taking into account the nature of the data processing and the information available to the processor:

  1. the obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a ‘data protection impact assessment’) where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons;
  2. the obligation to consult the competent supervisory authority/ies prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk;
  3. the obligation to ensure that personal data is accurate and up to date, by informing the controller without delay if the processor becomes aware that the personal data it is processing is inaccurate or has become outdated;
  4. the obligations in [OPTION 1] Article 32 Regulation (EU) 2016/679/ [OPTION 2] Articles 33, 36 to 38 Regulation (EU) 2018/1725.

d. The Parties shall set out in Annex III the appropriate technical and organisational measures by which the processor is required to assist the controller in the application of this Clause as well as the scope and the extent of the assistance required.

Clause 9 - Notification of personal data breach

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

9.1. Data breach concerning data processed by the controller

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

  1. in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the controller has become aware of it, where relevant/(unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons);
  2. in obtaining the following information which, pursuant to [OPTION 1] Article 33(3) Regulation (EU) 2016/679/ [OPTION 2] Article 34(3) Regulation (EU) 2018/1725, shall be stated in the controller’s notification, and must at least include:
    1. the nature of the personal data including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
    2. the likely consequences of the personal data breach;
    3. the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.
    Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
  3. in complying, pursuant to [OPTION 1] Article 34 Regulation (EU) 2016/679 / [OPTION 2] Article 35 Regulation (EU) 2018/1725, with the obligation to communicate without undue delay the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons.
9.2. Data breach concerning data processed by the processor

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

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

Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.

The Parties shall set out in Annex III all other elements to be provided by the processor when assisting the controller in the compliance with the controller’s obligations under [OPTION 1] Articles 33 and 34 of Regulation (EU) 2016/679 / [OPTION 2] Articles 34 and 35 of Regulation (EU) 2018/1725.

SECTION III – FINAL PROVISIONS
Clause 10 - Non-compliance with the Clauses and termination

a. Without prejudice to any provisions of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725, in the event that the processor is in breach of its obligations under these Clauses, the controller may instruct the processor to suspend the processing of personal data until the latter complies with these Clauses or the contract is terminated. The processor shall promptly inform the controller in case it is unable to comply with these Clauses, for whatever reason.

b. The controller shall be entitled to terminate the contract insofar as it concerns processing of personal data in accordance with these Clauses if:

  1. The processing of personal data by the processor has been suspended by the controller pursuant to point (a) and if compliance with these Clauses is not restored within a reasonable time and in any event within one month following suspension;
  2. the processor is in substantial or persistent breach of these Clauses or its obligations under Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725;
  3. the processor fails to comply with a binding decision of a competent court or the competent supervisory authority/ies regarding its obligations pursuant to these Clauses or to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

c. The processor shall be entitled to terminate the contract insofar as it concerns processing of personal data under these Clauses where, after having informed the controller that its instructions infringe applicable legal requirements in accordance with Clause 7.1 (b), the controller insists on compliance with the instructions.

d. Following termination of the contract, the processor shall, at the choice of the controller, delete all personal data processed on behalf of the controller and certify to the controller that it has done so, or, return all the personal data to the controller and delete existing copies unless Union or Member State law requires storage of the personal data. Until the data is deleted or returned, the processor shall continue to ensure compliance with these Clauses.

ANNEX I LIST OF PARTIES

Controller(s): [Identity and contact details of the controller(s), and, where applicable, of the controller’s data protection officer] The Controller as defined in the DPA.

Processor(s): [Identity and contact details of the processor(s) and, where applicable, of the processor’s data protection officer] The Processor as defined in the DPA

Data Protection Officer of Processor: Anna Upadhyay. She can be reached at security@yosemitecrew.com.

ANNEX II: DESCRIPTION OF THE PROCESSING

ModuleCategories of Personal DataCategories of Data SubjectsPurpose
Sign UpEmailCustomer/Employees of CustomerTo register and onboard veterinary businesses onto the Yosemite Crew platform, create accounts, and establish secure access for managing their practice's information and activities.
Password
Business Type
Business Logo
Business name
Registration Number
Year of establishment
Registration Number
Country Code
Phone Number
Website
Address along with:
Address Line 1
Street
City
ZipCode
Specialised department
Add Services
Brochures, Photos
Add a vetProfile PictureCustomer/Employees of CustomerTo register and onboard veterinarians to the veterinary business’s profile on the Yosemite Crew platform, allowing them to provide services through the platform.
Last name
First name
Gender (Male/Female/Others)
Date of Birth
Email address
Phone Number
Country Code
Address along with:
Address Line 1
Phone Number
Street
City
State
ZipCode
Professional background with:
Specialization
Qualification
Medical License Number
Year of experience
Language Spoken
Biography/Short Description
CV/Resume
Appointment Duration:
Days
From time
To Time
Consultation Mode(In-person/Online/Both)
Consultation Fee
Username
Password
Confirm password
Authorisation Settings with:
Take Assessments
Appointments (Chat or In-person)
View Medical Records
Prescribe Medications
Privacy Policy and Terms&conditions Agreement
Contact usFull nameCustomer/Employees of CustomerTo receive and respond to user inquiries, provide customer support, and address feedback or issues related to the Yosemite Crew platform.
Email Address
Phone Number
Type of Enquiry Such as:
General Enquiry
Feature Request
Data Service Access Request
Message
Add DepartmentNameCustomer/Employees of CustomerTo register and manage different departments or services within the veterinary business for streamlined operations and organisation.
Department Name
Description
Email
Country Code
Phone Number
Services such as:
Cardiac Health Screenings
Echocardiograms
Electrocardiograms (ECG)
Blood Pressure Monitoring
Holter Monitoring
Cardiac Catheterisation
Congenital Heart Disease Management
Department Head
Conditions Treated
Congestive Heart Failure
Arrhythmias
Heart Murmurs
Dilated Cardiomyopathy
Valvular Heart Disease
Pericardial Effusion
Myocarditis
Developer Sign upNameCustomer/Employees of CustomerTo register and onboard developers for API access and potential collaborations within the Yosemite Crew platform's marketplace, allowing them to create and integrate third-party apps and services.
Full name
Last Name
Company Name
Email Address
Password
Privacy Policy and Terms& conditions Agreement
Create an AppointmentNameCustomer/Employees of CustomerTo facilitate appointment scheduling for pet owners with veterinarians registered on the Yosemite Crew platform, improving convenience and accessibility to veterinary services.
Owner Details with:
Pet Owner
Pet Owner’s Name
Phone number
Address Line 1
Street
City
State
ZIP Code
Pet Details
Pet’s Name
Age
Pet Type (Cat/Dog/Horse)
Gender (Male/Female)
Breed
Appointment Details
Purpose of Visit
Appointment Type
Appointment Source (In-Hospital/App)Pet Owner Customer/Employees of Customer
Select Department
Select Veterinarian
Appointment date
Appoint Time (with time selection)
Add New Discount CouponNameCustomer/Employees of CustomerTo create and manage discount coupons, enhancing marketing efforts and attracting more clients to the veterinary business through the Yosemite Crew platform.
Discount Code Name
Discount Code
Select Services
Coupon Type
Percentage Rate
Min Order Value
Valid Till
Offer Description. Eg - 20% OFF on Grooming Services
Add Procedure estimateNameCustomer/Employees of CustomerProvide pet owners with estimations related to procedures their pets may need to undergo based on veterinarian information input.
Procedure Name
Estimate
Department
Add a description
Add Items with:
Name
Description
Qty
Unit Price(USD)
Gross Total (USD)
Discount(%)
Tax (%)
Add a PrescriptionDetails Such as:Customer/Employees of CustomerTo manage and track pet prescriptions, ensuring accurate medication administration and compliance, and providing pet owners with access to their pet's medication history.
Appointment ID
Prescription Date
Doctor’s Name
Pet’s Name
Age
Pet’s Weight
Temperature
Blood Pressure
SPO2
Heart Rate
Prescription Notes:
History (Subjective)
Clinical examination/Physical exam (Objective)
Differentials (Assessment)
Plan
Or Upload Document
Medication:
Name
Category
Strength
Dosage
Freq
Duration
Checkbox for the consent form.
Procedures
Surgical Notes (optional)
Add Procedure Package
Minor Procedure for surgeries
Generate New BillNameCustomer/Employees of CustomerTo generate and manage invoices for veterinary services, ensuring accurate billing and payment records for the veterinary business and pet owners, and integrating financial data with the platform.
Bill Number
Pet Owner
Bill Date
Animal Name
Doctor's Name
Itemised Billing Details:
Item name
Item Type
Quantity
Unit Price
Gross Total
Discount
Tax
Payment Information:
Payment Method
Payment Status

Categories of data subjects whose personal data is processed
See the table above.

Categories of personal data processed
See the table above.

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

Nature of the processing
Processor provides SaaS to Controller and the nature of the processing of personal data includes any processing that is required for Processor to render these services to Controller. It specifically includes the collection, organisation, structuring, storage and making available of personal data but may also include any other operation such as the adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination, alignment or combination, restriction, erasure or destruction of personal data.

Purpose(s) for which the personal data is processed on behalf of the controller
See the table above.

Duration of the processing
The processing endures as long as Processor renders its services to Controller and ends with the termination of the Yosemite Crew License and Subscription Terms.

Subject matter, nature and duration of the processing with regard to sub processors:
Please see below in ANNEX IV.

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

EXPLANATORY NOTE:
The technical and organisational measures need to be described concretely and not in a generic manner.

Technical and organisational measures of Processor

EXPLANATORY NOTE:
The technical and organisational measures must be described in specific (and not generic) terms. See also the general comment on the first page of the Appendix, in particular on the need to clearly indicate which measures apply to each transfer/set of transfers.
Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons.

The following specific measures are implemented:

  • Measures of pseudonymisation and encryption of personal data
    Our data is Encrypted both way at rest and in transit too. 
    We use strong encryption: data and volumes are encrypted at rest (AES-256) using AWS KMS, and in transit (TLS 1.3) across all services:
    • Encryption at rest our dev and prod instances, databases, snapshots and file stores are encrypted with AES-256 Encryption. Keys live in AWS KMS and rotate automatically every 12 months.
    • Encryption in transit – External traffic is forced over TLS 1.3 with Perfect-Forward Secrecy. Internal service-to-service calls use mTLS.
    • Pseudonymisation – We use salted bcrypt hashing for lookup tables for password store
  • Measures for ensuring ongoing confidentiality, integrity, availability and resilience of processing systems and services
    Our systems are built on AWS using secure, highly available cloud architecture. We use encryption (TLS & AES-256), least-privilege IAM roles RBAC methodology, and network isolation to protect data. We use GitHub for secure source control, with enforced code reviews, signed commits, and audit logging to ensure code integrity: All changes are version-controlled, tested, and logged via CloudTrail to maintain integrity. Backups, regular disaster recovery tests, and alignment with AWS Well-Architected Framework ensure we stay resilient under pressure or failure. Continuous vulnerability management, container scans, weekly patched AMIs backup, annual VAPT penetration test.
  • Measures for user identification and authorisation
    (RBAC) Role based access control: We use role-based access control (RBAC) to make sure each person only sees the data they need for their job – right down to individual rows in the database if needed. We don’t allow shared logins, so every action can be clearly traced to a specific user. Session management – We manage user sessions securely using encrypted tokens. If someone’s inactive for 15 minutes, they’re logged out automatically, and all sessions end after 12 hours no matter what — this helps reduce the risk from forgotten or unattended logins.
  • Measures for the protection of data during transmission
    All data on AWS cloud instances volumes are encrypted using the latest and most secure standard. We’ve disabled older, weaker encryption methods to keep communications safe. For our mobile apps, we use certificate pinning to make sure the app only talks to our real servers — this helps prevent man-in-the-middle attacks. In sensitive industries like healthcare or legal, we offer full end-to-end encryption so that even we can’t see the data in transit. When it comes to file transfers, we use secure methods like SFTP with strong SSH keys or short-lived HTTPS download links that session ends after 30 minutes to prevent unauthorized access.
  • Measures for ensuring events logging
    We track all key activities across our systems using AWS CloudWatch and GitHub audit logs. In AWS, CloudWatch logs cover everything from API calls and network activity to system performance and security events. Combined with services like CloudTrail and GuardDuty, this helps us detect and respond to threats quickly. On the development side, GitHub audit logs let us monitor actions like code pushes, permission changes, and access to repositories — ensuring we have full traceability of who did what, and when. All logs are stored securely, protected from tampering, and kept according to our retention policy. We review them regularly and have automated alerts for anything suspicious, so our security team can act fast if something’s not right.
  • Measures for ensuring system configuration, including default configuration
    Our systems are built with security in mind from the ground up. We use infrastructure a -code tools (like Terraform and Ansible) to ensure all environments are configured consistently and securely. Servers and containers are based on hardened images that follow industry standards (like CIS Benchmarks), with only the necessary services and ports enabled. Encryption is turned on by default, and insecure protocols are disabled. We regularly apply security updates and critical API patches, so we don’t fall behind. System settings are continuously monitored to catch any drift from our secure baseline.
  • Measures for internal IT and IT security governance and management
    We follow IT Security & Compliance standards like ISO 27001:2022 and SOC 2 to keep our systems and data secure. Our Information Security Management System (ISMS) is aligned with ISO 27001:2022, and we have a dedicated Data Protection Officer (DPO) and a Security Steering Committee that reports quarterly to senior leadership. We carry out regular risk assessments, including a Data Protection Impact Assessment (DPIA) at project launch and updates after any major technical or architectural changes. All team members complete mandatory cyber security and privacy training during onboarding and annually thereafter.
  • Measures for certification/assurance of processes and products
    • We're actively working toward completing our ISO 27001:2022 and SOC 2 Type II certifications to demonstrate our commitment to strong security and compliance practices.
    • As part of this process, we’ve already implemented many of the required controls across our infrastructure, development, and data handling processes. We’re also working closely with external auditors to ensure everything meets or exceeds industry expectations.
  • Measures for ensuring data minimisation
    We generally do not store personal data unless it’s strictly necessary for the functionality of our application. When personal data is required, we collect only what’s needed — no more, no less. Every feature goes through a privacy-by-design review to ensure we’re limiting the type, amount, and duration of personal data used. Where possible, we replace identifiers with pseudonyms or anonymised values, and we use aggregated data for analytics and reporting.
  • Measures for ensuring accountability
    We take accountability seriously and have put processes in place to make sure data protection and security responsibilities are clear, monitored, and auditable. All roles and responsibilities related to data handling and security are formally defined, with oversight from our Data Protection Officer (DPO) and Security Steering Committee. We maintain detailed records of processing activities (RoPA) and conduct regular internal audits to ensure we’re following our policies and meeting legal requirements.

Transfers to (Sub-)Processors

We carefully vet all sub-processors before working with them, especially when they handle personal data on our behalf. Each sub-processor must sign a Data Processing Agreement (DPA) that clearly sets out their responsibilities, including support for the controller’s obligations under GDPR. Sub-processors are required to implement equivalent technical and organisational measures as we do — including encryption of data in transit and at rest, access controls, security logging, and staff training. We also require that they only process data under documented instructions and never for their own purposes. To ensure transparency and compliance: Sub-processors must promptly assist us (and therefore the controller) with requests from data subjects, such as access, rectification, or deletion. They must notify us of any data breach without undue delay, allowing us to meet the 72-hour GDPR notification window. They are required to undergo regular security audits (ISO 27001 or SOC 2) and provide evidence on request.

Technical and organisational measures of sub processors

Supplier uses sub processors for rendering its services (see Annex IV). All sub processors implement appropriate technical and organisational measures. Please find more information under:
Amazon Web Services: https://d1.awsstatic.com/legal/aws-gdpr/AWS_GDPR_DPA.pdf; https://aws.amazon.com/de/security/
MongoDB: https://www.mongodb.com/technical-and-organizational-security-measures
Google Cloud: https://cloud.google.com/terms/data-processing-addendum, https://cloud.google.com/trust-center/security

ANNEX IV: LIST OF SUB-PROCESSORS

The controller has authorised the use of the following sub-processors:

S.No.Third Party ProviderAddressPurpose
1Amazon Web Services EMEA SARL38 Avenue John F. Kennedy, L-1855 LuxembourgAWS cloud server for Hosting
Provides the cloud infrastructure for hosting the Yosemite Crew platform and storing application data, ensuring accessibility and scalability.
2Amazon Web Services EMEA SARL38 Avenue John F. Kennedy, L-1855 LuxembourgAmazon Simple Email service
Facilitates the sending of automated email notifications, alerts, and transactional emails to users of the Yosemite Crew platform.
3Amazon Web Services EMEA SARL38 Avenue John F. Kennedy, L-1855 LuxembourgAWS S3 Bucket
Stores files and documents, such as images, uploaded documents, and other digital assets, for the Yosemite Crew platform.
4Google Ireland LimitedGordon House, Barrow Street Dublin 4, IrelandGoogle Cloud Services for map APIs
Enables the integration of mapping functionalities within the Yosemite Crew platform, such as displaying addresses, and location-based searches.
5MongoDB LimitedBuilding Two, Number One Ballsbridge, Dublin 4, Ballsbridge, Dublin, IrelandStores and manages the application's data, including user information, business data, pet records, and other relevant information for the Yosemite Crew platform.

APPENDIX 2 ANNEX STANDARD CONTRACTUAL CLAUSES

SECTION I

Clause 1 Purpose and scope

a. 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) (1) for the transfer of personal data to a third country.
b. The Parties: (i) the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and (ii) the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’) have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
c. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
d. 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

a. 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.
b. 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

a. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions: (i) Clause 1, Clause 2, Clause 3, Clause 6, Clause 7; (ii) Clause 8 – Module One: Clause 8.5 (e) and Clause 8.9(b); Module Two: Clause 8.1(b), 8.9(a), (c), (d) and (e); Module Three: Clause 8.1(a), (c) and (d) and Clause 8.9(a), (c), (d), (e), (f) and (g); Module Four: Clause 8.1 (b) and Clause 8.3(b); (iii) Clause 9 – Module Two: Clause 9(a), (c), (d) and (e); Module Three: Clause 9(a), (c), (d) and (e); (iv) Clause 12 – Module One: Clause 12(a) and (d); Modules Two and Three: Clause 12(a), (d) and (f); (v) Clause 13; (vi) Clause 15.1(c), (d) and (e); (vii) Clause 16(e); (viii) Clause 18 – Modules One, Two and Three: Clause 18(a) and (b); Module Four:Clause 18.
b. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4 Interpretation

a. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
b. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
c. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.

Clause 5 Hierarchy

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

Clause 6 Description of the transfer(s)

The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.

Clause 7 – Optional Docking clause

a. 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.
b. 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.
c. 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.
MODULE ONE: Transfer controller to controller
8.1 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. It may only process the personal data for another purpose: (i) where it has obtained the data subject’s prior consent; (ii) where necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or (iii) where necessary in order to protect the vital interests of the data subject or of another natural person.
8.2 Transparency
a. In order to enable data subjects to effectively exercise their rights pursuant to Clause 10, the data importer shall inform them, either directly or through the data exporter: (i) of its identity and contact details; (ii) of the categories of personal data processed; (iii) of the right to obtain a copy of these Clauses; (iv) where it intends to onward transfer the personal data to any third party/ies, of the recipient or categories of recipients (as appropriate with a view to providing meaningful information), the purpose of such onward transfer and the ground therefore pursuant to Clause 8.7.
b. Paragraph (a) shall not apply where the data subject already has the information, including when such information has already been provided by the data exporter, or providing the information proves impossible or would involve a disproportionate effort for the data importer. In the latter case, the data importer shall, to the extent possible, make the information publicly available.
c. On request, the Parties shall make a copy of these Clauses, including the Appendix as completed by them, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including personal data, the Parties may redact part of the text of the Appendix prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand 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.
d. Paragraphs (a) to (c) are without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679.
8.3 Accuracy and data minimisation
a. Each Party shall ensure that the personal data is accurate and, where necessary, kept up to date. The data importer shall take every reasonable step to ensure that personal data that is inaccurate, having regard to the purpose(s) of processing, is erased or rectified without delay.
b. If one of the Parties becomes aware that the personal data it has transferred or received is inaccurate, or has become outdated, it shall inform the other Party without undue delay.
c. The data importer shall ensure that the personal data is adequate, relevant and limited to what is necessary in relation to the purpose(s) of processing.
8.4 Storage limitation
The data importer shall retain the personal data for no longer than necessary for the purpose(s) for which it is processed. It shall put in place appropriate technical or organisational measures to ensure compliance with this obligation, including erasure or anonymisation (2) of the data and all back-ups at the end of the retention period.
8.5 Security of processing
a. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the personal data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access (hereinafter ‘personal data breach’). In assessing the appropriate level of security, they 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 subject. 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.
b. The Parties have agreed on the technical and organisational measures set out in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
c. The data importer shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
d. 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 personal data breach, including measures to mitigate its possible adverse effects.
e. In case of a personal data breach that is likely to result in a risk to the rights and freedoms of natural persons, the data importer shall without undue delay notify both the data exporter and the competent supervisory authority pursuant to Clause 13. Such notification shall contain i) a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), ii) its likely consequences, iii) the measures taken or proposed to address the breach, and iv) the details of a contact point from whom more information can be obtained. To the extent it is not possible for the data importer to provide all the information at the same time, it may do so in phases without undue further delay.
f. In case of a personal data breach that is likely to result in a high risk to the rights and freedoms of natural persons, the data importer shall also notify without undue delay the data subjects concerned of the personal data breach and its nature, if necessary in cooperation with the data exporter, together with the information referred to in paragraph (e), points ii) to iv), unless the data importer has implemented measures to significantly reduce the risk to the rights or freedoms of natural persons, or notification would involve disproportionate efforts. In the latter case, the data importer shall instead issue a public communication or take a similar measure to inform the public of the personal data breach.
g. The data importer shall document all relevant facts relating to the personal data breach, including its effects and any remedial action taken, and keep a record thereof.
8.6 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 or offences (hereinafter ‘sensitive data’), the data importer shall apply specific restrictions and/or additional safeguards adapted to the specific nature of the data and the risks involved. This may include restricting the personnel permitted to access the personal data, additional security measures (such as pseudonymisation) and/or additional restrictions with respect to further disclosure.
8.7 Onward transfers
The data importer shall not disclose the personal data to a third party located outside the European Union (3) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) unless the third party is or agrees to be bound by these Clauses, under the appropriate Module. Otherwise, an onward transfer by the data importer may only take place if: (i) it is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer; (ii) the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 of Regulation (EU) 2016/679 with respect to the processing in question; (iii) the third party enters into a binding instrument with the data importer ensuring the same level of data protection as under these Clauses, and the data importer provides a copy of these safeguards to the data exporter; iv) it is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; (v) it is necessary in order to protect the vital interests of the data subject or of another natural person; or (vi) where none of the other conditions apply, the data importer has obtained the explicit consent of the data subject for an onward transfer in a specific situation, after having informed him/her of its purpose(s), the identity of the recipient and the possible risks of such transfer to him/her due to the lack of appropriate data protection safeguards. In this case, the data importer shall inform the data exporter and, at the request of the latter, shall transmit to it a copy of the information provided to the data subject. Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.


8.8 Processing under the authority of the data importer
The data importer shall ensure that any person acting under its authority, including a processor, processes the data only on its instructions.
8.9 Documentation and compliance
a. Each Party shall be able to demonstrate compliance with its obligations under these Clauses. In particular, the data importer shall keep appropriate documentation of the processing activities carried out under its responsibility.
b. The data importer shall make such documentation available to the competent supervisory authority on request.


MODULE TWO: Transfer controller to processor
8.1. Instructions
(a) 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.
(b) 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
a. 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.
b. 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.
c. 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.
d. 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 (4) (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: (i) 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; (ii) 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; (iii) 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 (iv) 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
a. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
b. 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.
c. 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.
d. 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.
e. 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.
MODULE THREE: Transfer processor to processor
8.1. Instructions
a. The data exporter has informed the data importer that it acts as processor under the instructions of its controller(s), which the data exporter shall make available to the data importer prior to processing.
b. The data importer shall process the personal data only on documented instructions from the controller, as communicated to the data importer by the data exporter, and any additional documented instructions from the data exporter. Such additional instructions shall not conflict with the instructions from the controller. The controller or data exporter may give further documented instructions regarding the data processing throughout the duration of the contract.
c. The data importer shall immediately inform the data exporter if it is unable to follow those instructions. Where the data importer is unable to follow the instructions from the controller, the data exporter shall immediately notify the controller.
d. The data exporter warrants that it has imposed the same data protection obligations on the data importer as set out in the contract or other legal act under Union or Member State law between the controller and the data exporter (5).
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 controller, as communicated to the data importer by the data exporter, or 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 personal data, the data exporter may redact part of the text of the Appendix prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand 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.
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 rectify or erase 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 controller 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
a. 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, they 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 subject. 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 or the controller. 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.
b. The data importer shall grant access to the 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.
c. 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, without undue delay, the data exporter and, where appropriate and feasible, the controller 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 data breach, including 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.
d. 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 its controller so that the latter may in turn 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 set out 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 controller, as communicated to the data importer by the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (6) (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: (i) 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; (ii) the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 of Regulation (EU) 2016/679; (iii) 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 (iv) 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
a. The data importer shall promptly and adequately deal with enquiries from the data exporter or the controller that relate to the processing under these Clauses.
b. 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 controller.
c. The data importer shall make all information necessary to demonstrate compliance with the obligations set out in these Clauses available to the data exporter, which shall provide it to the controller.
d. The data importer shall allow for and contribute to audits by the data exporter of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. The same shall apply where the data exporter requests an audit on instructions of the controller. In deciding on an audit, the data exporter may take into account relevant certifications held by the data importer.
e. Where the audit is carried out on the instructions of the controller, the data exporter shall make the results available to the controller.
f. 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.
g. 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.
MODULE FOUR: Transfer processor to controller
8.1 Instructions
a. The data exporter shall process the personal data only on documented instructions from the data importer acting as its controller.
b. The data exporter shall immediately inform the data importer if it is unable to follow those instructions, including if such instructions infringe Regulation (EU) 2016/679 or other Union or Member State data protection law.
c. The data importer shall refrain from any action that would prevent the data exporter from fulfilling its obligations under Regulation (EU) 2016/679, including in the context of sub-processing or as regards cooperation with competent supervisory authorities.
d. After the end of the provision of the processing services, the data exporter shall, at the choice of the data importer, delete all personal data processed on behalf of the data importer and certify to the data importer that it has done so, or return to the data importer all personal data processed on its behalf and delete existing copies.
8.2 Security of processing
a. The Parties shall implement appropriate technical and organisational measures to ensure the security of the data, including during transmission, and protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access (hereinafter ‘personal data breach’). In assessing the appropriate level of security, they shall take due account of the state of the art, the costs of implementation, the nature of the personal data (7), the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects, and in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner.
b. The data exporter shall assist the data importer in ensuring appropriate security of the data in accordance with paragraph (a). In case of a personal data breach concerning the personal data processed by the data exporter under these Clauses, the data exporter shall notify the data importer without undue delay after becoming aware of it and assist the data importer in addressing the breach.
c. The data exporter shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
8.3 Documentation and compliance
a. The Parties shall be able to demonstrate compliance with these Clauses.
b. The data exporter shall make available to the data importer all information necessary to demonstrate compliance with its obligations under these Clauses and allow for and contribute to audits.

Clause 9 Use of sub-processors

MODULE TWO: Transfer controller to processor
a. OPTION 1: SPECIFIC PRIOR AUTHORISATION The data importer shall not sub-contract any of its processing activities performed on behalf of the data exporter under these Clauses to a sub-processor without the data exporter’s prior specific written authorisation. The data importer shall submit the request for specific authorisation at least [Specify time period] prior to the engagement of the sub-processor, together with the information necessary to enable the data exporter to decide on the authorisation. The list of sub-processors already authorised by the data exporter can be found in Annex III. The Parties shall keep Annex III up to date.
OPTION 2: GENERAL WRITTEN AUTHORISATION 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 [Specify time period] 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.
b. 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. (8) 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.
c. 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.
d. 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.
e. 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.
MODULE THREE: Transfer processor to processor
a. OPTION 1: SPECIFIC PRIOR AUTHORISATION The data importer shall not sub-contract any of its processing activities performed on behalf of the data exporter under these Clauses to a sub-processor without the prior specific written authorisation of the controller. The data importer shall submit the request for specific authorisation at least [Specify time period] prior to the engagement of the sub-processor, together with the information necessary to enable the controller to decide on the authorisation. It shall inform the data exporter of such engagement. The list of sub-processors already authorised by the controller can be found in Annex III. The Parties shall keep Annex III up to date.
OPTION 2: GENERAL WRITTEN AUTHORISATION The data importer has the controller’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the controller in writing of any intended changes to that list through the addition or replacement of sub-processors at least [Specify time period] in advance, thereby giving the controller 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 controller with the information necessary to enable the controller to exercise its right to object. The data importer shall inform the data exporter of the engagement of the sub-processor(s).
b. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the controller), 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. (9) 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.
c. The data importer shall provide, at the data exporter’s or controller’s request, a copy of such a sub-processor agreement and any subsequent amendments. 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.
d. 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.
e. 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

MODULE ONE: Transfer controller to controller
a. The data importer, where relevant with the assistance of the data exporter, shall deal with any enquiries and requests it receives from a data subject relating to the processing of his/her personal data and the exercise of his/her rights under these Clauses without undue delay and at the latest within one month of the receipt of the enquiry or request. (10) The data importer shall take appropriate measures to facilitate such enquiries, requests and the exercise of data subject rights. Any information provided to the data subject shall be in an intelligible and easily accessible form, using clear and plain language.
b. In particular, upon request by the data subject the data importer shall, free of charge: (i) provide confirmation to the data subject as to whether personal data concerning him/her is being processed and, where this is the case, a copy of the data relating to him/her and the information in Annex I; if personal data has been or will be onward transferred, provide information on recipients or categories of recipients (as appropriate with a view to providing meaningful information) to which the personal data has been or will be onward transferred, the purpose of such onward transfers and their ground pursuant to Clause 8.7; and provide information on the right to lodge a complaint with a supervisory authority in accordance with Clause 12(c)(i); (ii) rectify inaccurate or incomplete data concerning the data subject; (iii) erase personal data concerning the data subject if such data is being or has been processed in violation of any of these Clauses ensuring third-party beneficiary rights, or if the data subject withdraws the consent on which the processing is based.
c. Where the data importer processes the personal data for direct marketing purposes, it shall cease processing for such purposes if the data subject objects to it.
d. The data importer shall not make a decision based solely on the automated processing of the personal data transferred (hereinafter ‘automated decision’), which would produce legal effects concerning the data subject or similarly significantly affect him/her, unless with the explicit consent of the data subject or if authorised to do so under the laws of the country of destination, provided that such laws lays down suitable measures to safeguard the data subject’s rights and legitimate interests. In this case, the data importer shall, where necessary in cooperation with the data exporter: (i) inform the data subject about the envisaged automated decision, the envisaged consequences and the logic involved; and (ii) implement suitable safeguards, at least by enabling the data subject to contest the decision, express his/her point of view and obtain review by a human being.
e. Where requests from a data subject are excessive, in particular because of their repetitive character, the data importer may either charge a reasonable fee taking into account the administrative costs of granting the request or refuse to act on the request.
f. The data importer may refuse a data subject’s request if such refusal is allowed under the laws of the country of destination and is necessary and proportionate in a democratic society to protect one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679.
g. If the data importer intends to refuse a data subject’s request, it shall inform the data subject of the reasons for the refusal and the possibility of lodging a complaint with the competent supervisory authority and/or seeking judicial redress.
MODULE TWO: Transfer controller to processor
a. 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.
b. 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.
c. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
MODULE THREE: Transfer processor to processor
a. The data importer shall promptly notify the data exporter and, where appropriate, the controller of any request it has received from a data subject, without responding to that request unless it has been authorised to do so by the controller.
b. The data importer shall assist, where appropriate in cooperation with the data exporter, the controller in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable. 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.
c. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the controller, as communicated by the data exporter.
MODULE FOUR: Transfer processor to controller
The Parties shall assist each other in responding to enquiries and requests made by data subjects under the local law applicable to the data importer or, for data processing by the data exporter in the EU, under Regulation (EU) 2016/679.

Clause 11 Redress

a. 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. [OPTION: The data importer agrees that data subjects may also lodge a complaint with an independent dispute resolution body (11) at no cost to the data subject. It shall inform the data subjects, in the manner set out in paragraph (a), of such redress mechanism and that they are not required to use it, or follow a particular sequence in seeking redress.]
MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
b. 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.
c. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to: (i) lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13; (ii) refer the dispute to the competent courts within the meaning of Clause 18.
d. 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.
e. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
f. 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. 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. (c) Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to: (i) lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13; (ii) refer the dispute to the competent courts within the meaning of Clause 18. (d) 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. (e) The data importer shall abide by a decision that is binding under the applicable EU or Member State law. (f) 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

MODULE ONE: Transfer controller to controller
MODULE FOUR: Transfer processor to controller
a. 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.
b. Each Party shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages that the Party 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 under Regulation (EU) 2016/679.
c. 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.
d. The Parties agree that if one Party is held liable under paragraph (c), 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.
e. The data importer may not invoke the conduct of a processor or sub-processor to avoid its own liability.
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
a. 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.
b. 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.
c. 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.
d. 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.
e. 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.
f. 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.
g. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.

Clause 13 Supervision

MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
a. [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.
b. 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

MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
MODULE FOUR: Transfer processor to controller (where the EU processor combines the personal data received from the third country-controller with personal data collected by the processor in the EU)
a. 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.
b. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements: (i) the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred; (ii) the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (12); (iii) any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
c. 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.
d. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
e. 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). [For Module Three: The data exporter shall forward the notification to the controller.]
f. 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 [for Module Three:, if appropriate in consultation with the controller]. 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 [for Module Three: the controller or] 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

MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
MODULE FOUR: Transfer processor to controller (where the EU processor combines the personal data received from the third country-controller with personal data collected by the processor in the EU)
15.1 Notification
a. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it: (i) receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or (ii) becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer. [For Module Three: The data exporter shall forward the notification to the controller.]
b. 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.
c. 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.). [For Module Three: The data exporter shall forward the information to the controller.]
d. 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.
e. 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
a. 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).
b. 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. [For Module Three: The data exporter shall make the assessment available to the controller.]
c. 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

a. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
b. 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).
c. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where: (i) the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension; (ii) the data importer is in substantial or persistent breach of these Clauses; or (iii) the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses. In these cases, it shall inform the competent supervisory authority [for Module Three: and the controller] 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.
d. [For Modules One, Two and Three: 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.] [For Module Four: Personal data collected by the data exporter in the EU that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall immediately be deleted in its entirety, including any copy thereof.] 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.
e. 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

MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor

[OPTION 1: 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 Germany. [OPTION 2 (for Modules Two and Three): These Clauses shall be governed by the law of the EU Member State in which the data exporter is established. Where such law does not allow for third-party beneficiary rights, they shall be governed by the law of another EU Member State that does allow for third-party beneficiary rights. The Parties agree that this shall be the law of Germany.]


MODULE FOUR: Transfer processor to controller

These Clauses shall be governed by the law of a country allowing for third-party beneficiary rights. The Parties agree that this shall be the law of Germany.

Clause 18 Choice of forum and jurisdiction

MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
a. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
b. The Parties agree that those shall be the courts of Germany.
c. 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.
d. The Parties agree to submit themselves to the jurisdiction of such courts.
MODULE FOUR: Transfer processor to controller
Any dispute arising from these Clauses shall be resolved by the courts of Germany.

  1. Where the data exporter is a processor subject to Regulation (EU) 2016/679 acting on behalf of a Union institution or body as controller, reliance on these Clauses when engaging another processor (sub-processing) not subject to Regulation (EU) 2016/679 also ensures compliance with Article 29(4) of Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No 1247/2002/EC (OJ L 295, 21.11.2018, p. 39), to the extent these Clauses and the data protection obligations as set out in the contract or other legal act between the controller and the processor pursuant to Article 29(3) of Regulation (EU) 2018/1725 are aligned. This will in particular be the case where the controller and processor rely on the standard contractual clauses included in Decision 2021/915.
  2. This requires rendering the data anonymous in such a way that the individual is no longer identifiable by anyone, in line with recital 26 of Regulation (EU) 2016/679, and that this process is irreversible.
  3. The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.
  4. The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.
  5. See Article 28(4) of Regulation (EU) 2016/679 and, where the controller is an EU institution or body, Article 29(4) of Regulation (EU) 2018/1725.
  6. The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purposes of these Clauses.
  7. This includes whether the transfer and further processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions or offences.
  8. This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.
  9. That period may be extended by a maximum of two more months, to the extent necessary taking into account the complexity and number of requests. The data importer shall duly and promptly inform the data subject of any such extension.
  10. The data importer may offer independent dispute resolution through an arbitration body only if it is established in a country that has ratified the New York Convention on Enforcement of Arbitration Awards.
  11. As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

Need Help? We’re All Ears!

Got questions or need assistance? Just reach out! Our team is here to help.

Dog