Rocket Domains Hosting Ltd. and the Customer, collectively referred to as the “Parties,” are parties to this Data Processing Agreement (“DPA”). This DPA is part of the Terms of Service, Privacy Policy, and other applicable policies accessible on Rocket Domains’ website(s). Customers who accept these terms enter into this DPA on their own behalf to the extent required under applicable Data Protection Regulations and Laws, and to the extent Rocket Domains processes Customer Data as instructed by the Controller, defined in Section 1.
Rocket Domains may process Customer Data on behalf of the Customer in the course of providing Services to the Customer. The Parties agree to comply with the provisions outlined below regarding any Customer Data, and each will act in good faith and reasonably:
- Definitions.
1.1. Unless defined in this DPA, all capitalized terms are outlined below:
“Adequacy decision” refers to the formal decision of the EU and UK that recognizes that another country, territory, sector, or international organization provides an equivalent level of protection for personal data as the EU does.
“Adequate country or countries” means countries covered by an adequacy decision issued by the EU or UK, meaning data can flow freely between such countries.
“Additional Products” means any third-party software or content, features, products, software, programs, add-ons, plugins, or scripts that are accessible through the Rocket Domains Client Area or the control panel but are not part of the Services.
“Agreement” refers to the Terms of Service, other relevant documents published on the Rocket Domains website, along with the Order for the purchase/use of Services and the Order confirmation sent by Rocket Domains, if applicable.
“Controller” refers to the natural person or legal entity that determines the purposes and means of the processing of customer data, either alone or jointly with others. In this agreement, the Customer (you) is the Controller.
“Customer Data” refers to any “Personal Data” provided to Rocket Domains by or on behalf of the Customer through the use of the Services. Customer Data does not include Personal Data that is part of the Customer’s Order for purchase/use of the respective Service, subject to this DPA.
“Data Protection Losses” refers to all liabilities, including claims, demands, actions, settlements, charges, procedures, expenses, losses, and damages (whether material or non-material, including for emotional distress), to the extent permitted by Applicable Law. Data Protection Losses also include administrative fines, penalties, sanctions, liabilities, or other remedies imposed by a Data Protection Supervisory Authority, other relevant Regulatory Authority, or the respective competent court. Compensation to a Data Subject ordered by a Data Protection Supervisory Authority or the respective competent court is also considered Data Protection Losses, as are the reasonable costs of compliance with investigations by a Data Protection Supervisory Authority or any other relevant Regulatory Authority, such as the ICO. Additionally, Data Protection Losses include the costs of loading Customer Data and replacement of Customer materials and equipment to the extent that the same are lost or damaged, any loss or corruption of Customer Data, including the cost of rectification or restoration of Customer Data, and any other costs (including legal costs).
“Data Protection Regulations and Laws” or “Data Protection Regulations” refers to all applicable regulations and laws, including but not limited to laws and regulations of the European Union, the European Economic Area, their member states, Switzerland, and the United Kingdom, related to the Processing of Customer Data under this DPA. It includes both the EU and UK GDPR, together with the DPA 2018.
“Data Subject in the UK” refers to a person residing in the United Kingdom at the time their data is processed.
The “Effective date” of this DPA is either the date on which the Customer accepted the Agreement or 10 days after Rocket Domains publicly released the DPA and sent notice to the Customer.
The “GDPR” refers to the General Data Protection Regulation (EU) 2016/679, which provides protection for personal data and free movement of such data within the European Union.
The “International Data Transfer Agreement” (“IDTA”) is the standard data protection clauses for the transfer of customer data when the data subject is in the UK, incorporated in Annex 4 of this DPA.
“Notification Email Address” is the email address specified by the Customer in the ‘Owner Profile Details’ Section in the Client Area to receive certain notifications from Rocket Domains.
An “Order” is a purchase or use of a service by a Customer.
A “Partner” refers to any entity that directly or indirectly controls or is controlled by Rocket Domains. Control is defined as direct or indirect ownership or control of over 50% of the voting interests of the subject entity.
“Personal Data” is defined as per the applicable Data Protection Regulations.
“Processing” refers to the processing of personal data as per the applicable Data Protection Regulations.
The “Processor” is the entity that processes customer data on behalf of the Controller.
“Services” refer to any services provided by Rocket Domains which may involve the processing of personal data by Rocket Domains and its subcontractors.
“Rocket Domains” is the Rocket Domains entity that is party to this DPA, specifically Rocket Domains Ltd., a company registered in England and Wales (registration number: 11431904 ), with registered address at 201 Reservoir Rd, Birmingham B29 6SX.
“Standard Contractual Clauses” or “SCCs” means the standard data protection clauses for the transfer of Customer Data, as described in Article 46, p.2, c) of the GDPR, incorporated as Annex 1 to this DPA.
“Sub-processor” means any Processor engaged by Rocket Domains or a partner of Rocket Domains.
“Supervisory Authority” or “Data Protection Authority” means an independent public authority, which is established in the United Kingdom (the ICO) or in the EU.
“Term” means the period from the Effective Date until the end of Rocket Domains’s provisioning of the Services under the applicable Agreement, including, if applicable, any period during which the Services may have been suspended and any post-termination period during which Rocket Domains may continue providing Services for transitional purposes.
“UK GDPR” means the United Kingdom Data Protection Regulation applicable to Data Subjects in the UK.
2. Data Processing.
2.1 This DPA applies where and only to the extent that Rocket Domains processes Customer Data on behalf of the Customer in the course of providing the Services and such Customer Data is subject to the applicable Data Protection Regulations. If the Customer agreeing to this DPA is already a Customer, this DPA forms part of the Agreement, Privacy Policy and other relevant policies and documents announced on our website. This DPA including its annexes will be effective and replace any terms previously applicable to privacy, data processing and/or data security where Rocket Domains acts as a Data Processor. Annex 1 (Standard Contractual Clauses) will be applicable to Data Subjects which are located in the EU, whilst Annex 4 (International Data Transfer Agreement) will be applicable to Data Subjects which are located in the UK.
2.2 Compliance with Applicable Data Protection Regulations. If both the GDPR and the UK GDPR and DPA 2018 apply to this DPA, both parties shall comply with their respective obligations under the applicable Data Protection Regulations in relation to the processing of Customer Data.
2.3. Subject Matter, Duration, Nature, Purpose and Categories of Data Processing.
2.3.1. Subject Matter. Rocket Domains will process Customer Data as necessary to provide the Services and related technical and other support, including other inquiries pursuant to the Agreement and as instructed by the Customer in its use of the Services.
2.3.2. Duration of Processing. Except as provided under Section 11, Rocket Domains will process the Customer Data for the duration of the Term designated under the Order and the applicable Agreement.
2.3.3. Nature and Purpose of the Processing. Rocket Domains will process Customer Data to provide the Services and related technical and other support to the Customer in accordance with the Agreement, this DPA, and other relevant documents.
2.3.4. Categories of Data Subjects. We process Personal Data of the following categories of Data Subjects: • People who access and/or use the Services; • People whose data is provided to Rocket Domains via the Services by or at the direction of the Customer or by the Customer’s end-users/website visitors; • Employees, agents, freelancers, clients, and other contractors of the Customer, and any other individuals whose Personal Data is processed in connection with the provision of the Services; • People who transmit data via the Services, including people collaborating and communicating with the Customer or Customer’s end-users/website visitors.
2.3.5. Categories of Personal Data. Rocket Domains may process the following categories of Personal Data in the course of providing the Services: • Personal identification information (such as name, etc.); • Contact details (such as address, email address, phone number, etc.); • Any other type of Personal Data of Data Subjects transmitted in relation to the provision of the Services, including Personal Data processed in Customer’s logs or Customer’s content (such as IP address, etc.).
2.4. Roles of the Parties. The Parties acknowledge and agree that:
Rocket Domains acts as a Data Processor of the Customer Data under the applicable Data Protection Regulations in the EU and UK;
The Customer acts as a Data Controller or Data Processor, as applicable, of the Customer Data under the applicable Data Protection Regulations in the EU and UK; and relies on a lawful basis according to the applicable Data Protection Regulations in order for Rocket Domains to process Customer Data and to provide the Services pursuant to the Agreement and this DPA.
2.5. Data Processing Instructions Rocket Domains will process Customer Data solely according to this DPA, which constitutes the Customer’s final and comprehensive instructions to Rocket Domains for processing the Customer Data. Any processing beyond the scope of this DPA, if any, will require the prior written agreement between Rocket Domains and the Customer for additional instructions for processing. By entering into this DPA, the Customer instructs Rocket Domains to process Customer Data only in compliance with applicable legislation:
- to provide the Services and related technical and other support;
- as initiated by the Customer and its end users/website visitors in their usage of the Services;
- as specified in the Agreement, Terms of Service, Privacy Policy, and other relevant documents that govern the provision of the Services and related technical and other support.
2.6. Access and Use Rocket Domains will not access or use Customer Data except when it is necessary to provide the Services and related technical and other support to the Customer in compliance with the DPA, Agreement, and other relevant documents, and to comply with applicable legislation, including any valid and binding order (such as a court order or other binding documents) of a law enforcement agency and/or any other competent authority/state body.
2.6.1. Customer’s Processing The Customer shall process its Personal Data in compliance with the requirements of Data Protection Laws and Regulations applicable to it in its use of the Services. The Customer will have sole responsibility for the accuracy, quality, and legality of its Data and the means by which it acquired this Data.
2.6.2. Rocket Domains’ Processing of Customer Data Rocket Domains will only process Customer Data on behalf of and in compliance with the Customer’s documented instructions (this DPA) for the following purposes:
Processing to provide the Services and related technical and other support;
Processing initiated by Customer and/or its end users/website visitors in their usage of the Services;
Processing necessary to maintain and improve the Services.
2.6.3. Rocket Domains’ Compliance with Instructions From the Effective Date, Rocket Domains will comply with the instructions mentioned above, including with regard to data transfers unless the applicable UK or EU Member State law requires other processing of Customer Data by Rocket Domains, in which case Rocket Domains will inform the Customer (unless that law prohibits Rocket Domains from doing so on important grounds of public interest). Customer Data may be accessed and processed by Rocket Domains and Sub-processors to fulfill the obligations under this DPA, the respective Agreement or applicable legislation. Such processing will comply with the measures outlined in Sections 3, Section 7, and Annex 2 Security Measures.
2.7. Data Subject Rights
2.7.1. Access, Rectification, Restricted Processing, Portability Rocket Domains will enable the Customer to access, rectify and restrict processing of Customer Data, including via deletion of all or some of the Customer Data under its account or deletion of the whole account as described in Section 2.8 (Return and Deletion of Customer Data), and via export of Customer Data during the applicable Term, in a manner consistent with the functionality of the Services.
2.7.2. Data Subject Requests.
During the applicable Term, if Rocket Domains receives a request from a Data Subject to exercise their rights under the GDPR and UK GDPR/DPA 2018, including the right of access, right to rectification, restriction of Processing, erasure (“right to be forgotten”), data portability, objection to Processing, or the right not to be subject to automated individual decision-making (“Data Subject Request”), Rocket Domains will advise the Data Subject to submit their request to the Customer, and the Customer will be responsible for responding to such requests using the functionality of the Services, where necessary. Rocket Domains will take commercially reasonable steps to notify the Customer about such requests to the extent legally permitted.
2.7.2.1. Customer’s Responsibility for Requests.
Rocket Domains acknowledges the Customer’s responsibility for responding to Data Subject Requests during the applicable Term, and will provide appropriate technical and organizational assistance to the extent possible, considering the nature of the Processing. This assistance includes documentation resources in the form of tutorials and knowledge base articles, functionality and/or controls in the control panel, which the Customer can use to properly configure the Services and use them in a secure manner, and features, functionalities, and/or controls in the control panel that enable the Customer to retrieve, correct or delete Customer Data from the Services.
2.7.2.2. Rocket Domains Data Subject Request Assistance.
If the Customer is unable to address a Data Subject Request, Rocket Domains will provide commercially reasonable assistance upon the Customer’s request, to the extent legally obliged to do so and where the response to such Data Subject Request is required under the applicable Data Protection Laws and Regulations. Customer will be responsible for any costs arising from Rocket Domains’s provision of such assistance. Rocket Domains shall comply with the commitments set out in this DPA.
2.8. Return and Deletion of Customer Data.
Rocket Domains will enable the Customer to delete Customer Data during the applicable Term in a manner consistent with the functionality of the used Services and respective features. Retrieval or deletion of Customer Data by the Customer will constitute an instruction to Rocket Domains to delete the respective Customer Data archived on backup systems in accordance with applicable law and within a maximum period of 60 calendar days. Deactivation of the Services or expiry of the applicable Term will constitute an instruction to Rocket Domains to delete the Customer Data and the relevant Customer Data archived on backup systems within a maximum period of 60 calendar days. However, Rocket Domains may retain some or all Customer Data as necessary to comply with applicable legislation or a valid and binding order of a law enforcement agency and/or any other competent authority/state body.
2.9. Disclosure.
Rocket Domains shall not disclose Customer Data to any government, law enforcement agencies and other authorities, except as necessary to comply with applicable legislation or a valid and binding order of a law enforcement agency and/or any other competent authority/state body. Upon receipt of an order by the authorities of a third country, Rocket Domains will act in accordance with clause 15 of the Standard Contractual Clauses. Rocket Domains may also disclose Customer Data to third parties in the event of a sale, merger, acquisition, or partnership with other companies or businesses, or sale or purchase of some or all of its assets.
2.10. Rocket Domains’s Personnel.
Rocket Domains limits personnel access to Customer Data, only authorizing those personnel whose role and responsibilities are connected to the provision of Services. Rocket Domains imposes relevant contractual obligations regarding confidentiality, data protection, and data security upon its personnel, ensuring that these obligations survive the termination of the personnel engagement.
2.11. Data Protection Officer. Rocket Domains has appointed a Data Protection Officer in compliance with applicable Data Protection Legislation. You can reach the Data Protection Officer at legal@rocket.domains
3. Sub-processors.
3.1. Consent to Sub-processor Engagement/Appointment of Sub-processors. You acknowledge and agree that: (a) Rocket Domains Partners may be retained as Sub-processors; and (b) Rocket Domains and Rocket Domains Partners may engage Sub-processors in connection with the provisioning of the Services. Rocket Domains has entered into an agreement with each Sub-processor containing data protection obligations no less protective than those in this DPA with respect to the protection of Customer Data to the extent applicable to the nature of the Services provided by such Sub-processors. If you have entered into Standard Contractual Clauses (Annex 1) or the International Data Transfer Agreement (Annex 4) as described in Section 5, the above authorizations shall constitute your prior written consent to the subcontracting by Rocket Domains of the processing of Customer Data if such consent is required under the Standard Contractual Clauses.
3.2. Information about Sub-processors.
3.2.1. Rocket Domains may share information about you with Sub-processors such as the Rocket Domains partners who may be engaged with provisioning of Services subject to your Agreement and who are based within and/or outside the EU, EEA or UK. These Sub-processors shall process the provided Customer Data under instructions of Rocket Domains and in compliance with our Privacy Policy and this DPA. 3.2.2. A list of Rocket Domains’s Sub-processors can be disclosed upon request, according to Annex 3.
3.3. Requirements for Sub-processor engagement. When engaging any Sub-processor, Rocket Domains shall: (a) ensure via a written contract that: (i) the Sub-processor only accesses and uses Customer Data to the extent required to perform the obligations subcontracted to it, and does so in accordance with this Data Processing Agreement and any Standard Contractual Clauses or International Data Transfer Agreement entered into or Alternative Transfer Solution adopted by Rocket Domains as described in Section 5; and (ii) if the UK or EU GDPR apply to the processing of Customer data, the data protection obligations set out in the applicable Data Protection Regulation, as described in this Data Processing Agreement, are imposed on the Sub-processor; and (b) remain fully liable for all obligations subcontracted to it, and all acts and omissions of the Sub-processor.
3.4. Objection Right for Sub-processor(s).
3.4.1. You may object to any Sub-processor by terminating the applicable Agreement immediately upon written notice to Rocket Domains, on condition that you provide such notice within 10 calendar days of being informed of the engagement of the respective Sub-processor. This termination right is your sole and exclusive remedy if you object to any Sub-processor.
3.4.2. Rocket Domains shall refund you any prepaid fees covering the remainder of the term of such Order(s) following the effective date of termination with respect to such terminated Services, without imposing a penalty for such termination on you.
4. Data Protection Impact Assessments (DPIA) and Consultations.
Upon your request, Rocket Domains shall give you reasonable cooperation and assistance necessary to meet your obligation under the EU and UK GDPR to perform a data protection impact assessment (DPIA) related to your use of Services, to the extent you do not otherwise have access to the relevant information, and to the extent that such information is available to Rocket Domains. Rocket Domains shall provide reasonable assistance to the Customer in the cooperation or prior consultation with the Supervisory Authority in the performance of its tasks relating to this DPA, to the extent required under the Data Protection Regulations.
5. Transfers
Section 5 of Rocket Domains’ Data Processing Agreement outlines the provisions for transfers of Customer Data outside of the European Union (EU), European Economic Area (EEA), and the UK. Rocket Domains processes Customer Data in Data Centers located inside and outside the EU, EEA, and the UK. The locations of these Data Centers are available on Rocket Domains’ website, which may be updated from time to time. The Customer may specify the Data Center location where its hosting account content will be stored, but Rocket Domains reserves the right to change the locations of the Data Centers and move Customer’s hosting account to another Data Center at its sole discretion. If the change of the Data Center results in storing the Customer Data located in the Customer’s hosting account under a different jurisdiction, the Customer may object to such change by terminating the Agreement immediately and upon written notice to Rocket Domains, provided that the Customer provides such notice within 10 calendar days of being informed of the change of the Data Center. Customer can change its data center location by submitting a request from their client area dashboard with a ticket from their account after logging in and by paying the relevant fees that we ask the customer to pay so long as our Services’ functionality allows it.
Regarding the processing locations, to the extent the Customer Data is located in a Data Center outside the EEA or the UK, and to the extent Rocket Domains provides the Services and related technical and other support, the Customer agrees that Rocket Domains may transmit, access and process Customer Data in the EU, EEA, UK, Asia, Australia, and the United States and any other countries where Rocket Domains and/or its Partners and Sub-processors have Data Centers, facilities or maintain data processing operations. This type of international data transfer operations may occur upon provision of any of the Services provided by Rocket Domains, including Content Delivery Network (CDN) service. The geographical locations of the servers to which the above-mentioned data transfer may happen are listed on Rocket Domains’ website and are subject to changes at their sole discretion. If the storage and/or processing of Customer Data involves processing of Customer Data outside of the EEA and the EU GDPR applies, then this Data Processing Agreement and Annex 1, containing the Standard Contractual Clauses, will automatically apply as a contractual safeguard of the international data transfer. If the storage and/or processing of Customer Data involves processing of Customer Data outside of the UK, and the UK GDPR applies, then this Data Processing Agreement and Annex 4, containing the International Data Transfer Agreement, will automatically apply as a contractual safeguard of the international data transfer.
Rocket Domains and the Customer agree that appropriate and proportional technical and organizational data protection and cybersecurity risk mitigation measures will be provided, as well as appropriate risk assessments when transferring Customer Data outside of the UK, EU and EEA. Rocket Domains will also provide appropriate safeguards to protect Customer Data by virtue of making available Standard Contractual Clauses (Annex 1) and International Data Transfer Agreement (Annex 4) as a transfer mechanism. The Standard Contractual Clauses (Annex 1) will apply to Customer Data that is transferred when the Data Subject is in the EU or EEA, while the International Data Transfer Agreement (Annex 4) will apply to Customer Data that is transferred when the Data Subject is in the UK.
To the extent Rocket Domains processes or transfers (directly or via onward transfer) Customer Data under this DPA from the UK, EU, EEA to countries which do not provide an adequate level of data protection within the meaning of applicable Data Protection Laws of the foregoing territories, the Parties hereby agree as follows:
The Customer hereby authorizes any transfer or access to Customer Data from and to such destinations outside the EU, EEA and the UK;
Rocket Domains shall be deemed to provide appropriate and proportional technical and organisational data protection and cybersecurity risk mitigation measures, as well as to perform the appropriate risk assessments when transferring Customer Data outside of the UK, EU and EEA;
Rocket Domains shall be deemed to provide appropriate safeguards to protect Customer Data by virtue of making available Standard Contractual Clauses (Annex 1) and International Data Transfer Agreement (Annex 4) as a transfer mechanism;
The Standard Contractual Clauses (Annex 1) will apply to Customer Data that is transferred, when the Data Subject is in the EU or EEA;
The International Data Transfer Agreement (Annex 4) will apply to Customer Data that is transferred, when the Data Subject is in the UK.
6. Record processing
Rocket Domains is obligated under the UK and EU GDPR to collect and maintain records of certain information, such as the name and contact details of each processor and/or controller on behalf of whom Rocket Domains is acting. This also includes information on the local representative and data protection officer of such processor or controller. Rocket Domains is required to make this information available to the supervisory authorities. If the UK and EU GDPR applies to the processing of Customer data, the Customer must provide such information to Rocket Domains via the Rocket Domains website or other means provided by Rocket Domains, and ensure that all information provided is accurate and up-to-date.
7. Security Responsibilities
7.1. Security measures
Rocket Domains is responsible for implementing and maintaining technical and organizational measures to protect Customer Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access, as outlined in Annex 2. The Security Measures include encrypted transmission of Customer Data outside the Service environment, ensuring confidentiality, integrity, availability, and resilience of Rocket Domains’s systems and services, timely access to Customer Data from an available backup copy, and regular testing of effectiveness. Rocket Domains may update or modify the Security Measures from time to time, provided that such updates and modifications do not degrade the overall security of the Services.
7.2. Customer’s Security Responsibilities and Assessment
The Customer agrees that, without prejudice to Rocket Domains’s obligations under Section 7 (Security Responsibilities of Rocket Domains) and other relevant sections in this DPA:
7.2.1. The Customer is solely responsible for the use of the Services, including ensuring a level of security suitable to the risk in respect of the Customer Data and the content of its hosting account. The Customer is also responsible for securing the account authentication credentials, systems, and devices used to access the Services, as well as ensuring that all programs, scripts, add-ons, plugins, and other software installed on its hosting account are secure, properly configured, regularly maintained, and do not impose any security risks in respect to the Customer Data and the account itself.
7.2.2. Rocket Domains has no obligation to protect Customer Data stored or transferred outside of Rocket Domains’ and its sub-processors’ systems (e.g., offline or on-premise storage) or to provide additional paid security services unless Rocket Domains offers and the Customer orders and pays for such services.
7.2.3. The Customer is solely responsible for reviewing the documentation and evaluating whether the Services, the Security Measures, Rocket Domains’s commitments under this section, and the following meet the Customer’s needs, including any security obligations of the Customer under the European Data Protection Legislation and/or Non-European Data Protection Legislation, as applicable.
7.2.4. The Customer acknowledges and agrees that the Security Measures implemented and maintained by Rocket Domains, as outlined in Section 7.1, provide the necessary level of security appropriate to the risk in respect of the Customer Data, taking into account the costs of implementation and the nature, scope, context, and purpose of processing of Customer data, as well as the risks to individuals.
7.2.5. The Customer is responsible for backing up Customer Data and all data and content stored within its hosting account to prevent potential data loss. Rocket Domains Backup Services are provided “as-is” and are subject to all limitations of liability outlined in the applicable agreement. If there is partial or full data loss or corruption and the Customer is not satisfied with the outcome of the restore by Rocket Domains Backup Services, or Rocket Domains’s backup copy is not recent or suitable for restore, it is the Customer’s obligation to restore any and all data and content stored within its hosting account from its own backup.
8. Compliance Review
As per the Data Protection Regulations applicable, the Customer has the right to ensure that Rocket Domains is complying with its obligations under this DPA by conducting a review of the documentation or an audit. The audit can be conducted by the Customer or an independent auditor appointed by the Customer, and the request must be made in writing to Rocket Domains at the address mentioned in the respective Terms of Service. Rocket Domains will provide written responses to all reasonable requests made by the Customer and may charge a fee for any review or audit. Rocket Domains will inform the Customer of any applicable fee before the audit is conducted, and the Customer will be responsible for any fees charged by the auditor and any fees associated with executing an audit. The reports of any such audit will be made available to Rocket Domains without any restrictions on their further usage by Rocket Domains. Rocket Domains reserves the right to decline the request by the Customer or the auditor appointed by the Customer to conduct an audit if it feels that they are not qualified or independent, a competitor of Rocket Domains, or manifestly unsuitable. Rocket Domains will provide a written response if it decides to decline the request. If Rocket Domains declines to follow any instruction requested by the Customer or an auditor regarding a properly requested and scoped audit or review, the Customer has the right to terminate this DPA and the Agreement. This Section 8 (Review and Audits of compliance) does not affect or modify any rights or obligations of the Customer or Rocket Domains under the Standard Contractual Clauses and the International Data Transfer Agreement entered into as described in Section 5.
9. Security Breach Notification
Rocket Domains maintains security incident management policies and procedures and will notify the Customer without undue delay after becoming aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Customer data transmitted, stored or otherwise processed by Rocket Domains or its Sub-processors, which affects the rights and freedoms of any Data Subjects (“Customer Data Incident”). Rocket Domains will make reasonable efforts to identify the cause of such Customer Data Incidents and take necessary and reasonable steps to remediate the cause to the extent possible. However, the obligations herein do not apply to incidents caused by the Customer, Customer’s usage of the Services, Customer’s actions or activities, or Customer’s Users.
9.2. In accordance with this section, notifications must provide details of the Customer Data Incident to the extent possible, including the steps taken by Rocket Domains to mitigate the potential risks, and recommendations for actions that the Customer should take to address the incident. 9.3. Notification(s) regarding Customer Data Incidents will be sent to the Notification Email Address, or, at Rocket Domains’s discretion, through direct communication such as a phone call. The Customer is solely responsible for ensuring that the Notification Email Address and the contact information specified in the ‘Owner Profile Details’ Section of its Client Area are accurate and valid. 9.4. Rocket Domains will not examine the content of the Customer Data in order to identify information subject to specific legal requirements. The Customer is solely responsible for complying with incident notification laws that apply to them and fulfilling any third-party notification obligations related to any Customer Data Incidents. 9.5. Rocket Domains’s notification of or response to a Customer Data Incident under this Section 9 does not constitute an acknowledgement of any fault or liability with respect to the Customer Data Incident.
10. Liability and indemnification
10.1. The Customer is responsible for indemnifying and keeping Rocket Domains and its Partners and/or Sub processors indemnified against any data protection breaches and losses, including legal and other costs, incurred by Rocket Domains, its Partners, and/or Sub processors due to non-compliance by the Customer with data protection laws and regulations, or any breach by the Customer of its data protection and other obligations under this DPA and the Agreement as well other Rocket Domains’ Policies, Terms and Agreements published on our website(s).
10.2. Rocket Domains will be liable for data protection breaches and losses that result solely, directly and exclusively from Rocket Domains’ failure to comply with its obligations as Data Processor under Data Protection Laws and Regulations. Rocket Domains’ liability under the DPA is subject to the exclusions and limitations of liability set out in the Agreement and or other Rocket Domains’ Policies, Terms, and Agreements published on our websites. In any case, Rocket Domains’ liability will not exceed the payments received by Rocket Domains from the affected customer in the latest order or renewal.
11. Termination
This DPA is effective from the Effective Date until the end of Rocket Domains’s provisioning of the Services under the applicable Agreement. This includes any period during which the Services may have been suspended and any post-termination period (which is a maximum of 60 calendar days) during which Rocket Domains may continue processing Customer Data for transitional purposes (“Term”). Nothing in this Section 11 modifies Rocket Domains’s obligation to retain some or all Customer Data as necessary to comply with applicable legislation or with a valid and binding order (such as a subpoena or a court order) from a law enforcement agency and/or any other competent authority/state body. The DPA will automatically terminate upon termination of the Agreement and deletion of all Customer Data by Rocket Domains.
12. Legal Effect and Amendments
12.1. In case of any conflict or inconsistency between the terms of this DPA and those of the applicable Agreement regarding the Processing of Customer Data, the terms of this DPA shall take precedence.
It should be noted that if the Customer has entered into multiple Agreements, this DPA will amend each Agreement separately.
12.2. Rocket Domains reserves the right to modify the terms of this DPA at any time. In case of material changes to this DPA, we will notify you through this channel, by email, or by means of a notice on our website or via your Client Area, at least ten (10) calendar days before the changes become effective. Non-material changes to this DPA will have immediate effect.
Annex 1:
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 2016on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of 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.
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 2 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 2. 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 (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.
Clause 9
Use of sub-processors
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 10 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
(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.
Clause 10
Data subject rights
(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 2 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.
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.
(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.
Clause 12
Liability
(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
(a) 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.
(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
(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;
(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).
(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. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
Clause 15
Obligations of the data importer in case of access by public authorities
15.1 Notification
(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.
(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.).
(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.
(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 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) Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
(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
These Clauses shall be governed by the law of England (UK) provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the United Kingdom. If the law of the UK, including Northern Ireland, cannot govern these clauses as determined and agreed by the Parties, then the laws of Ireland will govern these Clauses.
Clause 18
Choice of forum and jurisdiction
(a) Any dispute arising from these Clauses shall be resolved by the courts of the UK and if that’s not legally possible, by the courts of Ireland.
(b) The Parties agree that those shall be the courts of thе UK and if that’s not legally possible, by the courts of Ireland.
(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.
Annex I.A. LIST OF PARTIES
Data exporter(s):
Name: [Customer name]
Address: [Customer address]
Contact person’s name, position and contact details: [Contact person for Customer]
Activities relevant to the data transferred under these Clauses: The Data importer provides the Services to the Data exporter in accordance with the Agreement.
Signature and date:
…………………………………………………………………………………………..
Role: Data Controller
Data importer(s):
Name: Rocket Domains Ltd.
Address: 201 Reservoir Road, Birmingham B29 6SX, United Kingdom
Contact person’s name, position and contact details: MF Sharif, Data Protection Officer, legal@rocket.domains
Activities relevant to the data transferred under these Clauses: hosting and other services
Signature and date:
…………………………………………………………………………………………..
Role: Data Processor
Annex I.B. DESCRIPTION OF TRANSFER
Categories of data subjects whose personal data is transferred
The personal data concerns the categories of data subjects as defined in Section 2.3.4. in the Data Processing Agreement.
Categories of personal data transferred
The personal data concerns the categories of data as defined in Section 2.3.5. in the Data Processing Agreement.
Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures.
Customer may submit Customer Data in the course of its use of the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include categories of sensitive data. To ensure its protection we have adopted various restrictions and safeguards such as security measures, systems and data access controls, and others. For more detailed information, see Annex 2.
The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis).
On a continuous basis.
Nature of the processing
The nature of the processing is determined according to Art. 2.3.3 of the DPA.
Purpose(s) of the data transfer and further processing
The purpose of the data transfer and further processing is to better utilise Rocket Domains’ server infrastructure, some of which is based outside the EEA.
The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period
The duration of the processing is determined according to Art. 2.3.2 of the DPA.
For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing
The subject matter, nature and duration of the processing is determined according to Art. 2.3.1, 2.3.2 and 2.3.3 of the DPA respectively.
Annex I.C. COMPETENT SUPERVISORY AUTHORITY
Competent supervisory authority is the UK ICO
Annex 2: TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA
Security Measures
Rocket Domains is committed to implementing and maintaining appropriate technical and organizational Security Measures to ensure the safe Processing of Personal Data. These measures are intended to protect Personal Data from accidental or unauthorized loss, destruction, alteration, disclosure, or access, and against all other unlawful forms of Processing. To achieve this, Rocket Domains has implemented the measures set out in Annex 2 to the Data Processing Agreement. Additionally, specific security measures and practices for the Services ordered by the Customer may be specified in the Agreement.
Rocket Domains may update or modify these Security Measures from time to time, provided that such updates and modifications do not result in the degradation of the overall security of the Services. Any such changes will be communicated to the Customer in a timely and transparent manner.
Please note that the technical and organizational security measures implemented by Rocket Domains are in accordance with the Standard Contractual Clauses. This ensures that the Processing of Personal Data is carried out in compliance with the relevant data protection laws and regulations.
Personnel and Confidentiality
Rocket Domains shall take reasonable steps to ensure that no person shall be appointed by us to process Personal Data unless that person:
- is competent and qualified to perform the specific tasks assigned to him by us;
- has been authorised by us; and
- has been instructed by us in the requirements relevant to the performance of the obligations of Rocket Domains under these Clauses, in particular the limited purpose of the data processing.
Rocket Domains maintains a set of guidelines regarding confidentiality, business ethics, appropriate usage, and professional standards, which all personnel are required to follow. Additionally, all personnel handling Customer Data are required to execute a confidentiality agreement and must acknowledge receipt of, and compliance with, Rocket Domains confidentiality and privacy policies.
Rocket Domains conducts reasonably appropriate background checks on personnel to the extent legally permissible and in accordance with applicable local labor law and statutory regulations.
Personnel handling Customer Data are provided with relevant information security and data protection training and are required to complete additional requirements appropriate to their role.
By implementing these measures, Rocket Domains aims to ensure that its personnel conduct themselves in a manner consistent with applicable laws and regulations, as well as the company’s policies, to protect the security and confidentiality of Customer Data.
Physical Security
Rocket Domains maintains geographically distributed data centers that ensure the physical security of production data. The company’s sub-processors employ various measures to secure access to data processing systems, including access control systems that permit only authorized personnel to enter secure areas. Data centers are designed to withstand adverse weather and natural conditions and are equipped with around-the-clock guards, CCTV monitoring, access screening, and escort-controlled access. On-site backup generators are available in case of power failures.
The electrical power systems in the data centers are redundant and maintainable without impacting continuous operations. Critical infrastructure components have a primary and alternate power source, and backup power is provided by uninterruptible power supplies or diesel generators. Infrastructure systems are designed to eliminate single points of failure and minimize the impact of anticipated environmental risks.
Rocket Domains’ sub-processors have documented preventative maintenance procedures for production equipment and facilities, which detail the process for and frequency of performance according to the manufacturer’s or internal specifications. Preventative and corrective maintenance is scheduled through a standard change process according to documented procedures.
System Access Control
Rocket Domains has implemented a customized Linux-based operating system for its servers that provides the Services. The company regularly reviews its operating systems and employs security measures to increase the protection of its production environments.
To maintain the security of its infrastructure and respond to security incidents, Rocket Domains has established information security policies for its personnel. Its infrastructure, development, and support teams are responsible for ongoing monitoring and review of the Services.
To prevent unauthorized access to systems used to process customer data, including personal data, Rocket Domains has implemented internal access control policies and processes. The company designs its systems to restrict access to authorized personnel only and to ensure that personal data cannot be read, copied, altered, or removed without authorization during processing and after recording. Access to production servers is controlled by an access management system and is restricted to authorized personnel only. Depending on the Services ordered, access controls may include authentication via passwords and/or two-factor authentication, SSH keys, authorization processes, change management processes, and logical access restrictions protected by firewall/VLAN. Access rights are granted or modified based on job responsibilities, job duty requirements, and strict need-to-know criteria, in accordance with Rocket Domains’ internal data access policies.
Services Access Control
o use the Services, customers are required to authenticate themselves through an authentication system, which verifies credentials before allowing access to the data. Additional controls may also be implemented based on the specific Services ordered, such as authentication through passwords and/or two-factor authentication, SSH keys, authorization processes, change management processes, and multi-level access logging.
Depending on the Services ordered, additional controls may include assigning unique identifiers to authorized personnel, mechanisms to revoke access after consecutive failed login attempts, lockout periods, password expiry and reset mechanisms, and password complexity requirements.
All of these measures are put in place to ensure the security of the Services and protect against unauthorized access to customer data.
Data Access Control
Rocket Domains uses a multi-tenant environment to store data, which allows multiple customers’ deployments to be stored on the same physical hardware. To prevent customers from accessing each other’s data, Rocket Domains employs logical isolation, which separates each customer’s data from others. This approach provides scalability while ensuring strict data privacy.
Customers have control over specific controls for sharing access to data with end-users for specific purposes, in line with the Services’ functionality. Customers can choose to make use of these controls. Rocket Domains offers certain logging capabilities to aid in tracking access to data.
To maintain data privacy, direct access to customer data is restricted. If such access is required, access rights are only granted to authorized staff in accordance with the access control rules outlined in the previous sections.
Transmission Control
Rocket Domains uses high-speed private links to connect its data centers, ensuring secure and fast data transfer between them. This prevents unauthorized access to data during electronic transfer or transport, as well as during recording onto data storage media or exchange within the data center.
Rocket Domains employs industry-standard transport protocols like SSL and TLS for data in transit between Customer devices and its Services, as well as within data centers. Data transmissions outside the Service environment are encrypted unless otherwise specified in the Order, the applicable Agreement, or the User documentation of the Services.
Some functionalities of the Services may allow the Customer to choose unencrypted communications. It’s the Customer’s sole responsibility to decide whether to use such unencrypted communications or transmissions, and to accept any risks associated with that decision.
Input Control
The integration of Personal Data into the system is managed by the Customer via secured file transfer, web services, or by entering data directly into the application. As stated in Section Transmission Control, some functionalities of the Services allow Customers to use unencrypted file transfer protocols. In such cases, Customers are solely responsible for their decision to use such protocols.
The Services are designed not to introduce viruses to Customer Data; however, the Services do not scan for viruses that may be included in attachments or other Personal Data uploaded into the Services by the Customer. These attachments will not be executed in the Services, ensuring that the Service remains uncompromised and free from damage.
Network Control
Rocket Domains implements various security measures to prevent unauthorized traffic to and within data centers. These measures include firewalls, NATs, partitioned Local Area Networks, and physical separation of back-end servers from public-facing interfaces. Multiple layers of network devices and intrusion detection systems are also employed to protect against external attacks. Additionally, Rocket Domains considers potential attack vectors and incorporates appropriate purpose-built technologies into external-facing systems.
Intrusion Detection and Response
Rocket Domains and authorized personnel continuously monitor the Services for unauthorized intrusions using network-based intrusion detection mechanisms. Incident response policies and procedures are in place, and Rocket Domains personnel will react promptly to known incidents and notify customers in the event of an actual or suspected unauthorized disclosure of Personal Data.
System Logs and Backups
Rocket Domains ensures that processing systems used to store Customer Data log information to their respective system log facility. Log entries are maintained and stored in case there is suspicion of inappropriate access and an analysis is required. Backups are taken regularly and secured using a combination of technical and physical controls. Rocket Domains also ensures that the systems where Customer Data is stored have a disaster recovery facility and are governed under a disaster recovery plan. In the event of a disaster, Rocket Domains will execute recovery plans to restore operation in a timely manner.
Data Destruction and Sub-processor Security
Rocket Domains ensures that data is deleted when customers delete data or leave the Service, and strict procedures are in place for the reuse, redeployment, data destruction, and decommission of disks and hardware. Before onboarding Sub-processors, Rocket Domains conducts due diligence of their security and privacy practices to ensure that they provide a level of security and privacy appropriate to their access to data and the scope of services they are engaged to provide. Sub-processors are required to enter into appropriate security, confidentiality, and privacy contract terms.
System Changes and Enhancements
Rocket Domains may enhance and implement changes in the Services during the term of the Agreement. Security controls, procedures, policies, and features may change or be added. Rocket Domains will provide security controls that deliver a level of security protection that is not materially lower than that provided as of the Effective Date.
In summary, Rocket Domains implements multiple security measures to protect customer data, including intrusion detection, incident response, system logs and backups, data destruction, sub-processor security, and system changes and enhancements. These measures are designed to prevent unauthorized access, protect data in transit, and ensure reliability and availability of the Services.
Annex 3: List of Sub-processors
Available upon request.
Annex 4: International Data Transfer Agreement
This International Data Transfer Agreement (IDTA) has been issued by the Information Commissioner for Parties making Restricted Transfers. The Information Commissioner considers that it provides Appropriate Safeguards for Restricted Transfers when it is entered into as a legally binding contract.
Part 1: Tables
Table 1: Parties and signatures
| Start date | From the moment the Exporter (Controller) enters a relationship with the Importer (Processor) | |
| The Parties | Exporter (who sends the Restricted Transfer) | Importer (who receives the Restricted Transfer) |
| Parties’ details | Rocket Domains Customer, resident of the United Kingdom | Rocket Domains Ltd. Registered address: 201 Reservoir Rd, Birmingham B29 6SX, United Kingdom |
| Key Contact | As described on our website | MF Sharif, Data Protection Officer, legal@rocket.domains |
| Importer Data Subject Contact | MF Sharif, Data Protection Officer, legal@rocket.domains | |
| Signatures confirming each Party agrees to be bound by this IDTA | Considered as signed upon acceptance of the Data Processing Agreement. | Considered as signed upon its publication on our website. |
Table 2: Transfer Details
| UK country’s law that governs the IDTA: | England and Wales |
| Primary place for legal claims to be made by the Parties | England and Wales |
| The status of the Exporter | In relation to the Processing of the Transferred Data: Exporter is a Controller, Processor or Sub-Processor |
| The status of the Importer | In relation to the Processing of the Transferred Data: Importer is the Exporter’s Processor or Sub-Processor |
| Whether UK GDPR applies to the Importer | UK GDPR applies to the Importer’s Processing of the Transferred Data when the data subjects are in the UK |
| Linked Agreement | If the Importer is the Exporter’s Processor or Sub-Processor – the agreement(s) between the Parties which sets out the Processor’s or Sub-Processor’s instructions for Processing the Transferred Data: Name of agreement: Data Processing Agreement Date of agreement: The Effective Date specified in the DPA Parties to the agreement: Rocket Domains’ customers and Rocket Domains |
| Term | The Importer may Process the Transferred Data for the following time period: the period for which the Linked Agreement is in force |
| Ending the IDTA before the end of the Term | The Parties cannot end the IDTA before the end of the Term unless there is a breach of the IDTA or the Parties agree in writing. |
| Ending the IDTA when the Approved IDTA changes | Which Parties may end the IDTA as set out in Section 29.2: Importer |
| Can the Importer make further transfers of the Transferred Data? | The Importer MAY transfer on the Transferred Data to another organisation or person (who is a different legal entity) in accordance with Section 16.1 (Transferring on the Transferred Data). |
| Specific restrictions when the Importer may transfer on the Transferred Data | There are no specific restrictions. |
| Review Dates | The Parties must review the Security Requirements at least once each year or each time there is a change to the Transferred Data, Purposes, Importer Information, TRA or risk assessment. |
Table 3: Transferred Data
| Transferred Data | The categories of Transferred Data will update automatically if the information is updated in the Linked Agreement referred to. The personal data concerns the categories of data as defined in Section 2.3.5. in the Linked Agreement. Customer may submit Customer Data in the course of its use of the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include categories of sensitive data. To ensure its protection we have adopted various restrictions and safeguards such as security measures, systems and data access controls, and others. For more detailed information, see Annex 2. |
| Special Categories of Personal Data and criminal convictions and offences | All types of sensitive data may be transferred by the Customer in its sole discretion when using the services, and the Importer will implement 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. |
| Relevant Data Subjects | The Data Subjects of the Transferred Data are: The categories of Data Subjects will update automatically if the information is updated in the Linked Agreement referred to. The personal data concerns the categories of data subjects as defined in Section 2.3.4. in the Linked Agreement. |
| Purpose | The Importer may Process the Transferred Data for the purposes set out in the Linked Agreement. The purposes will update automatically if the information is updated in the Linked Agreement referred to. |
Table 4: Security Requirements
| Security of Transmission | As set out in Annex 2 to the Linked Agreement. |
| Security of Storage | As set out in Annex 2 to the Linked Agreement. |
| Security of Processing | As set out in Annex 2 to the Linked Agreement. |
| Organisational security measures | As set out in Annex 2 to the Linked Agreement. |
| Technical security minimum requirements | As set out in Annex 2 to the Linked Agreement. |
| Updates to the Security Requirements | The Security Requirements will update automatically if the information is updated in the Linked Agreement referred to. |
Part 2: Extra Protection Clauses
| Extra Protection Clauses: | As set out in the Linked Agreement and Annex 2 thereto. |
| (i) Extra technical security protections | As set out in the Linked Agreement and Annex 2 thereto. |
| (ii) Extra organisational protections | As set out in the Linked Agreement and Annex 2 thereto. |
| (iii) Extra contractual protections | As set out in the Linked Agreement and Annex 2 thereto. |
Part 3: Commercial Clauses
| Commercial Clauses | As set out in the Linked Agreement. |
Part 4: Mandatory Clauses
Information that helps you to understand this IDTA
1. This IDTA and Linked Agreements
1.1 Each Party agrees to be bound by the terms and conditions set out in the IDTA, in exchange for the other Party also agreeing to be bound by the IDTA.
1.2 This IDTA is made up of:
1.2.1 Part one: Tables;
1.2.2 Part two: Extra Protection Clauses;
1.2.3 Part three: Commercial Clauses; and
1.2.4 Part four: Mandatory Clauses.
1.3 The IDTA starts on the Start Date and ends as set out in Sections 29 or 30.
1.4 If the Importer is a Processor or Sub-Processor instructed by the Exporter: the Exporter must ensure that, on or before the Start Date and during the Term, there is a Linked Agreement which is enforceable between the Parties and which complies with Article 28 UK GDPR (and which they will ensure continues to comply with Article 28 UK GDPR).
1.5 References to the Linked Agreement or to the Commercial Clauses are to that Linked Agreement or to those Commercial Clauses only in so far as they are consistent with the Mandatory Clauses.
2. Legal Meaning of Words
2.1 If a word starts with a capital letter it has the specific meaning set out in the Legal Glossary in Section 36.
2.2 To make it easier to read and understand, this IDTA contains headings and guidance notes. Those are not part of the binding contract which forms the IDTA.
3. You have provided all the information required
3.1 The Parties must ensure that the information contained in Part one: Tables is correct and complete at the Start Date and during the Term.
3.2 In Table 2: Transfer Details, if the selection that the Parties are Controllers, Processors or Sub-Processors is wrong (either as a matter of fact or as a result of applying the UK Data Protection Laws) then:
3.2.1 the terms and conditions of the Approved IDTA which apply to the correct option which was not selected will apply; and
3.2.2 the Parties and any Relevant Data Subjects are entitled to enforce the terms and conditions of the Approved IDTA which apply to that correct option.
3.3 In Table 2: Transfer Details, if the selection that the UK GDPR applies is wrong (either as a matter of fact or as a result of applying the UK Data Protection Laws), then the terms and conditions of the IDTA will still apply to the greatest extent possible.
4. How to sign the IDTA
4.1 The Parties may choose to each sign (or execute):
4.1.1 the same copy of this IDTA;
4.1.2 two copies of the IDTA. In that case, each identical copy is still an original of this IDTA, and together all those copies form one agreement;
4.1.3 a separate, identical copy of the IDTA. In that case, each identical copy is still an original of this IDTA, and together all those copies form one agreement,
unless signing (or executing) in this way would mean that the IDTA would not be binding on the Parties under Local Laws.
5. Changing this IDTA
5.1 Each Party must not change the Mandatory Clauses as set out in the Approved IDTA, except only:
5.1.1 to ensure correct cross-referencing: cross-references to Part one: Tables (or any Table), Part two: Extra Protections, and/or Part three: Commercial Clauses can be changed where the Parties have set out the information in a different format, so that the cross-reference is to the correct location of the same information, or where clauses have been removed as they do not apply, as set out below;
5.1.2 to remove those Sections which are expressly stated not to apply to the selections made by the Parties in Table 2: Transfer Details, that the Parties are Controllers, Processors or Sub-Processors and/or that the Importer is subject to, or not subject to, the UK GDPR. The Exporter and Importer understand and acknowledge that any removed Sections may still apply and form a part of this IDTA if they have been removed incorrectly, including because the wrong selection is made in Table 2: Transfer Details;
5.1.3 so the IDTA operates as a multi-party agreement if there are more than two Parties to the IDTA. This may include nominating a lead Party or lead Parties which can make decisions on behalf of some or all of the other Parties which relate to this IDTA (including reviewing Table 4: Security Requirements and Part two: Extra Protection Clauses, and making updates to Part one: Tables (or any Table), Part two: Extra Protection Clauses, and/or Part three: Commercial Clauses); and/or
5.1.4 to update the IDTA to set out in writing any changes made to the Approved IDTA under Section 5.4, if the Parties want to. The changes will apply automatically without updating them as described in Section 5.4;
provided that the changes do not reduce the Appropriate Safeguards.
5.2 If the Parties wish to change the format of the information included in Part one: Tables, Part two: Extra Protection Clauses or Part three: Commercial Clauses of the Approved IDTA, they may do so by agreeing to the change in writing, provided that the change does not reduce the Appropriate Safeguards.
5.3 If the Parties wish to change the information included in Part one: Tables, Part two: Extra Protection Clauses or Part three: Commercial Clauses of this IDTA (or the equivalent information), they may do so by agreeing to the change in writing, provided that the change does not reduce the Appropriate Safeguards.
5.4 From time to time, the ICO may publish a revised Approved IDTA which:
5.4.1 makes reasonable and proportionate changes to the Approved IDTA, including correcting errors in the Approved IDTA; and/or
5.4.2 reflects changes to UK Data Protection Laws.
The revised Approved IDTA will specify the start date from which the changes to the Approved IDTA are effective and whether an additional Review Date is required as a result of the changes. This IDTA is automatically amended as set out in the revised Approved IDTA from the start date specified.
6. Understanding this IDTA
6.1 This IDTA must always be interpreted in a manner that is consistent with UK Data Protection Laws and so that it fulfils the Parties’ obligation to provide the Appropriate Safeguards.
6.2 If there is any inconsistency or conflict between UK Data Protection Laws and this IDTA, the UK Data Protection Laws apply.
6.3 If the meaning of the IDTA is unclear or there is more than one meaning, the meaning which most closely aligns with the UK Data Protection Laws applies.
6.4 Nothing in the IDTA (including the Commercial Clauses or the Linked Agreement) limits or excludes either Party’s liability to Relevant Data Subjects or to the ICO under this IDTA or under UK Data Protection Laws.
6.5 If any wording in Parts one, two or three contradicts the Mandatory Clauses, and/or seeks to limit or exclude any liability to Relevant Data Subjects or to the ICO, then that wording will not apply.
6.6 The Parties may include provisions in the Linked Agreement which provide the Parties with enhanced rights otherwise covered by this IDTA. These enhanced rights may be subject to commercial terms, including payment, under the Linked Agreement, but this will not affect the rights granted under this IDTA.
6.7 If there is any inconsistency or conflict between this IDTA and a Linked Agreement or any other agreement, this IDTA overrides that Linked Agreement or any other agreements, even if those agreements have been negotiated by the Parties. The exceptions to this are where (and in so far as):
6.7.1 the inconsistent or conflicting terms of the Linked Agreement or other agreement provide greater protection for the Relevant Data Subject’s rights, in which case those terms will override the IDTA; and
6.7.2 a Party acts as Processor and the inconsistent or conflicting terms of the Linked Agreement are obligations on that Party expressly required by Article 28 UK GDPR, in which case those terms will override the inconsistent or conflicting terms of the IDTA in relation to Processing by that Party as Processor.
6.8 The words “include”, “includes”, “including”, “in particular” are used to set out examples and not to set out a finite list.
6.9 References to:
6.9.1 singular or plural words or people, also includes the plural or singular of those words or people;
6.9.2 legislation (or specific provisions of legislation) means that legislation (or specific provision) as it may change over time. This includes where that legislation (or specific provision) has been consolidated, re-enacted and/or replaced after this IDTA has been signed; and
6.9.3 any obligation not to do something, includes an obligation not to allow or cause that thing to be done by anyone else.
7. Which laws apply to this IDTA
7.1 This IDTA is governed by the laws of the UK country set out in Table 2: Transfer Details. If no selection has been made, it is the laws of England and Wales. This does not apply to Section 35 which is always governed by the laws of England and Wales.
How this IDTA provides Appropriate Safeguards
8. The Appropriate Safeguards
8.1 The purpose of this IDTA is to ensure that the Transferred Data has Appropriate Safeguards when Processed by the Importer during the Term. This standard is met when and for so long as:
8.1.1 both Parties comply with the IDTA, including the Security Requirements and any Extra Protection Clauses; and
8.1.2 the Security Requirements and any Extra Protection Clauses provide a level of security which is appropriate to the risk of a Personal Data Breach occurring and the impact on Relevant Data Subjects of such a Personal Data Breach, including considering any Special Category Data within the Transferred Data.
8.2 The Exporter must:
8.2.1 ensure and demonstrate that this IDTA (including any Security Requirements and Extra Protection Clauses) provides Appropriate Safeguards; and
8.2.2 (if the Importer reasonably requests) provide it with a copy of any TRA.
8.3 The Importer must:
8.3.1 before receiving any Transferred Data, provide the Exporter with all relevant information regarding Local Laws and practices and the protections and risks which apply to the Transferred Data when it is Processed by the Importer, including any information which may reasonably be required for the Exporter to carry out any TRA (the “Importer Information”);
8.3.2 co-operate with the Exporter to ensure compliance with the Exporter’s obligations under the UK Data Protection Laws;
8.3.3 review whether any Importer Information has changed, and whether any Local Laws contradict its obligations in this IDTA and take reasonable steps to verify this, on a regular basis. These reviews must be at least as frequent as the Review Dates; and
8.3.4 inform the Exporter as soon as it becomes aware of any Importer Information changing, and/or any Local Laws which may prevent or limit the Importer complying with its obligations in this IDTA. This information then forms part of the Importer Information.
8.4 The Importer must ensure that at the Start Date and during the Term:
8.4.1 the Importer Information is accurate;
8.4.2 it has taken reasonable steps to verify whether there are any Local Laws which contradict its obligations in this IDTA or any additional information regarding Local Laws which may be relevant to this IDTA.
8.5 Each Party must ensure that the Security Requirements and Extra Protection Clauses provide a level of security which is appropriate to the risk of a Personal Data Breach occurring and the impact on Relevant Data Subjects of such a Personal Data Breach.
9. Reviews to ensure the Appropriate Safeguards continue
9.1 Each Party must:
9.1.1 review this IDTA (including the Security Requirements and Extra Protection Clauses and the Importer Information) at regular intervals, to ensure that the IDTA remains accurate and up to date and continues to provide the Appropriate Safeguards. Each Party will carry out these reviews as frequently as the relevant Review Dates or sooner; and
9.1.2 inform the other party in writing as soon as it becomes aware if any information contained in either this IDTA, any TRA or Importer Information is no longer accurate and up to date.
9.2 If, at any time, the IDTA no longer provides Appropriate Safeguards the Parties must Without Undue Delay:
9.2.1 pause transfers and Processing of Transferred Data whilst a change to the Tables is agreed. The Importer may retain a copy of the Transferred Data during this pause, in which case the Importer must carry out any Processing required to maintain, so far as possible, the measures it was taking to achieve the Appropriate Safeguards prior to the time the IDTA no longer provided Appropriate Safeguards, but no other Processing;
9.2.2 agree a change to Part one: Tables or Part two: Extra Protection Clauses which will maintain the Appropriate Safeguards (in accordance with Section 5); and
9.2.3 where a change to Part one: Tables or Part two: Extra Protection Clauses which maintains the Appropriate Safeguards cannot be agreed, the Exporter must end this IDTA by written notice on the Importer.
10. The ICO
10.1 Each Party agrees to comply with any reasonable requests made by the ICO in relation to this IDTA or its Processing of the Transferred Data.
10.2 The Exporter will provide a copy of any TRA, the Importer Information and this IDTA to the ICO, if the ICO requests.
10.3 The Importer will provide a copy of any Importer Information and this IDTA to the ICO, if the ICO requests.
The Exporter
11. Exporter’s obligations
11.1 The Exporter agrees that UK Data Protection Laws apply to its Processing of the Transferred Data, including transferring it to the Importer.
11.2 The Exporter must:
11.2.1 comply with the UK Data Protection Laws in transferring the Transferred Data to the Importer;
11.2.2 comply with the Linked Agreement as it relates to its transferring the Transferred Data to the Importer; and
11.2.3 carry out reasonable checks on the Importer’s ability to comply with this IDTA, and take appropriate action including under Section 9.2, Section 29 or Section 30, if at any time it no longer considers that the Importer is able to comply with this IDTA or to provide Appropriate Safeguards.
11.3 The Exporter must comply with all its obligations in the IDTA, including any in the Security Requirements, and any Extra Protection Clauses and any Commercial Clauses.
11.4 The Exporter must co-operate with reasonable requests of the Importer to pass on notices or other information to and from Relevant Data Subjects or any Third Party Controller where it is not reasonably practical for the Importer to do so. The Exporter may pass these on via a third party if it is reasonable to do so.
11.5 The Exporter must co-operate with and provide reasonable assistance to the Importer, so that the Importer is able to comply with its obligations to the Relevant Data Subjects under Local Law and this IDTA.
The Importer
12. General Importer obligations
12.1 The Importer must:
12.1.1 only Process the Transferred Data for the Purpose;
12.1.2 comply with all its obligations in the IDTA, including in the Security Requirements, any Extra Protection Clauses and any Commercial Clauses;
12.1.3 comply with all its obligations in the Linked Agreement which relate to its Processing of the Transferred Data;
12.1.4 keep a written record of its Processing of the Transferred Data, which demonstrate its compliance with this IDTA, and provide this written record if asked to do so by the Exporter;
12.1.5 if the Linked Agreement includes rights for the Exporter to obtain information or carry out an audit, provide the Exporter with the same rights in relation to this IDTA; and
12.1.6 if the ICO requests, provide the ICO with the information it would be required on request to provide to the Exporter under this Section 12.1 (including the written record of its Processing, and the results of audits and inspections).
12.2 The Importer must co-operate with and provide reasonable assistance to the Exporter and any Third Party Controller, so that the Exporter and any Third Party Controller are able to comply with their obligations under UK Data Protection Laws and this IDTA.
13. Importer’s obligations if it is subject to the UK Data Protection Laws
13.1 If the Importer’s Processing of the Transferred Data is subject to UK Data Protection Laws, it agrees that:
13.1.1 UK Data Protection Laws apply to its Processing of the Transferred Data, and the ICO has jurisdiction over it in that respect; and
13.1.2 it has and will comply with the UK Data Protection Laws in relation to the Processing of the Transferred Data.
13.2 If Section 13.1 applies and the Importer complies with Section 13.1, it does not need to comply with:
· Section 14 (Importer’s obligations to comply with key data protection principles);
· Section 15 (What happens if there is an Importer Personal Data Breach);
· Section 15 (How Relevant Data Subjects can exercise their data subject rights); and
· Section 21 (How Relevant Data Subjects can exercise their data subject rights – if the Importer is the Exporter’s Processor or Sub-Processor).
14. Importer’s obligations to comply with key data protection principles
14.1 The Importer does not need to comply with this Section 14 if it is the Exporter’s Processor or Sub-Processor.
14.2 The Importer must:
14.2.1 ensure that the Transferred Data it Processes is adequate, relevant and limited to what is necessary for the Purpose;
14.2.2 ensure that the Transferred Data it Processes is accurate and (where necessary) kept up to date, and (where appropriate considering the Purposes) correct or delete any inaccurate Transferred Data it becomes aware of Without Undue Delay; and
14.2.3 ensure that it Processes the Transferred Data for no longer than is reasonably necessary for the Purpose.
15. What happens if there is an Importer Personal Data Breach
15.1 If there is an Importer Personal Data Breach, the Importer must:
15.1.1 take reasonable steps to fix it, including to minimise the harmful effects on Relevant Data Subjects, stop it from continuing, and prevent it happening again. If the Importer is the Exporter’s Processor or Sub-Processor: these steps must comply with the Exporter’s instructions and the Linked Agreement and be in co-operation with the Exporter and any Third Party Controller; and
15.1.2 ensure that the Security Requirements continue to provide (or are changed in accordance with this IDTA so they do provide) a level of security which is appropriate to the risk of a Personal Data Breach occurring and the impact on Relevant Data Subjects of such a Personal Data Breach.
15.2 If the Importer is a Processor or Sub-Processor: if there is an Importer Personal Data Breach, the Importer must:
15.2.1 notify the Exporter Without Undue Delay after becoming aware of the breach, providing the following information:
15.2.1.1 a description of the nature of the Importer Personal Data Breach;
15.2.1.2 (if and when possible) the categories and approximate number of Data Subjects and Transferred Data records concerned;
15.2.1.3 likely consequences of the Importer Personal Data Breach;
15.2.1.4 steps taken (or proposed to be taken) to fix the Importer Personal Data Breach (including to minimise the harmful effects on Relevant Data Subjects, stop it from continuing, and prevent it happening again) and to ensure that Appropriate Safeguards are in place;
15.2.1.5 contact point for more information; and
15.2.1.6 any other information reasonably requested by the Exporter,
15.2.2 if it is not possible for the Importer to provide all the above information at the same time, it may do so in phases, Without Undue Delay; and
15.2.3 assist the Exporter (and any Third Party Controller) so the Exporter (or any Third Party Controller) can inform Relevant Data Subjects or the ICO or any other relevant regulator or authority about the Importer Personal Data Breach Without Undue Delay.
15.3 If the Importer is a Controller: if the Importer Personal Data Breach is likely to result in a risk to the rights or freedoms of any Relevant Data Subject the Importer must notify the Exporter Without Undue Delay after becoming aware of the breach, providing the following information:
15.3.1 a description of the nature of the Importer Personal Data Breach;
15.3.2 (if and when possible) the categories and approximate number of Data Subjects and Transferred Data records concerned;
15.3.3 likely consequences of the Importer Personal Data Breach;
15.3.4 steps taken (or proposed to be taken) to fix the Importer Personal Data Breach (including to minimise the harmful effects on Relevant Data Subjects, stop it from continuing, and prevent it happening again) and to ensure that Appropriate Safeguards are in place;
15.3.5 contact point for more information; and
15.3.6 any other information reasonably requested by the Exporter.
If it is not possible for the Importer to provide all the above information at the same time, it may do so in phases, Without Undue Delay.
15.4 If the Importer is a Controller: if the Importer Personal Data Breach is likely to result in a high risk to the rights or freedoms of any Relevant Data Subject, the Importer must inform those Relevant Data Subjects Without Undue Delay, except in so far as it requires disproportionate effort, and provided the Importer ensures that there is a public communication or similar measures whereby Relevant Data Subjects are informed in an equally effective manner.
15.5 The Importer must keep a written record of all relevant facts relating to the Importer Personal Data Breach, which it will provide to the Exporter and the ICO on request.
This record must include the steps it takes to fix the Importer Personal Data Breach (including to minimise the harmful effects on Relevant Data Subjects, stop it from continuing, and prevent it happening again) and to ensure that Security Requirements continue to provide a level of security which is appropriate to the risk of a Personal Data Breach occurring and the impact on Relevant Data Subjects of such a Personal Data Breach.
16.Transferring on the Transferred Data
16.1 The Importer may only transfer on the Transferred Data to a third party if it is permitted to do so in Table 2: Transfer Details Table, the transfer is for the Purpose, the transfer does not breach the Linked Agreement, and one or more of the following apply:
16.1.1 the third party has entered into a written contract with the Importer containing the same level of protection for Data Subjects as contained in this IDTA (based on the role of the recipient as controller or processor), and the Importer has conducted a risk assessment to ensure that the Appropriate Safeguards will be protected by that contract; or
16.1.2 the third party has been added to this IDTA as a Party; or
16.1.3 if the Importer was in the UK, transferring on the Transferred Data would comply with Article 46 UK GDPR; or
16.1.4 if the Importer was in the UK transferring on the Transferred Data would comply with one of the exceptions in Article 49 UK GDPR; or
16.1.5 the transfer is to the UK or an Adequate Country.
16.2 The Importer does not need to comply with Section 16.1 if it is transferring on Transferred Data and/or allowing access to the Transferred Data in accordance with Section 23 (Access Requests and Direct Access).
17. Importer’s responsibility if it authorises others to perform its obligations
17.1 The Importer may sub-contract its obligations in this IDTA to a Processor or Sub-Processor (provided it complies with Section 16).
17.2 If the Importer is the Exporter’s Processor or Sub-Processor: it must also comply with the Linked Agreement or be with the written consent of the Exporter.
17.3 The Importer must ensure that any person or third party acting under its authority, including a Processor or Sub-Processor, must only Process the Transferred Data on its instructions.
17.4 The Importer remains fully liable to the Exporter, the ICO and Relevant Data Subjects for its obligations under this IDTA where it has sub-contracted any obligations to its Processors and Sub-Processors, or authorised an employee or other person to perform them (and references to the Importer in this context will include references to its Processors, Sub-Processors or authorised persons).
What rights do individuals have?
18. The right to a copy of the IDTA
18.1 If a Party receives a request from a Relevant Data Subject for a copy of this IDTA:
18.1.1 it will provide the IDTA to the Relevant Data Subject and inform the other Party, as soon as reasonably possible;
18.1.2 it does not need to provide copies of the Linked Agreement, but it must provide all the information from those Linked Agreements referenced in the Tables;
18.1.3 it may redact information in the Tables or the information provided from the Linked Agreement if it is reasonably necessary to protect business secrets or confidential information, so long as it provides the Relevant Data Subject with a summary of those redactions so that the Relevant Data Subject can understand the content of the Tables or the information provided from the Linked Agreement.
19. The right to Information about the Importer and its Processing
19.1 The Importer does not need to comply with this Section 19 if it is the Exporter’s Processor or Sub-Processor.
19.2 The Importer must ensure that each Relevant Data Subject is provided with details of:
· the Importer (including contact details and the Importer Data Subject Contact);
· the Purposes; and
· any recipients (or categories of recipients) of the Transferred Data;
The Importer can demonstrate it has complied with this Section 19.2 if the information is given (or has already been given) to the Relevant Data Subjects by the Exporter or another party.
The Importer does not need to comply with this Section 19.2 in so far as to do so would be impossible or involve a disproportionate effort, in which case, the Importer must make the information publicly available.
19.3 The Importer must keep the details of the Importer Data Subject Contact up to date and publicly available. This includes notifying the Exporter in writing of any such changes.
19.4 The Importer must make sure those contact details are always easy to access for all Relevant Data Subjects and be able to easily communicate with Data Subjects in the English language Without Undue Delay.
20. How Relevant Data Subjects can exercise their data subject rights
20.1 The Importer does not need to comply with this Section 20 if it is the Exporter’s Processor or Sub-Processor.
20.2 If an individual requests, the Importer must confirm whether it is Processing their Personal Data as part of the Transferred Data.
20.3 The following Sections of this Section 20, relate to a Relevant Data Subject’s Personal Data which forms part of the Transferred Data the Importer is Processing.
20.4 If the Relevant Data Subject requests, the Importer must provide them with a copy of their Transferred Data:
20.4.1 Without Undue Delay (and in any event within one month);
20.4.2 at no greater cost to the Relevant Data Subject than it would be able to charge if it were subject to the UK Data Protection Laws;
20.4.3 in clear and plain English that is easy to understand; and
20.4.4 in an easily accessible form
together with
20.4.5 (if needed) a clear and plain English explanation of the Transferred Data so that it is understandable to the Relevant Data Subject; and
20.4.6 information that the Relevant Data Subject has the right to bring a claim for compensation under this IDTA.
20.5 If a Relevant Data Subject requests, the Importer must:
20.5.1 rectify inaccurate or incomplete Transferred Data;
20.5.2 erase Transferred Data if it is being Processed in breach of this IDTA;
20.5.3 cease using it for direct marketing purposes; and
20.5.4 comply with any other reasonable request of the Relevant Data Subject, which the Importer would be required to comply with if it were subject to the UK Data Protection Laws.
20.6 The Importer must not use the Transferred Data to make decisions about the Relevant Data Subject based solely on automated processing, including profiling (the “Decision-Making”), which produce legal effects concerning the Relevant Data Subject or similarly significantly affects them, except if it is permitted by Local Law and:
20.6.1 the Relevant Data Subject has given their explicit consent to such Decision-Making; or
20.6.2 Local Law has safeguards which provide sufficiently similar protection for the Relevant Data Subjects in relation to such Decision-Making, as to the relevant protection the Relevant Data Subject would have if such Decision-Making was in the UK; or
20.6.3 the Extra Protection Clauses provide safeguards for the Decision-Making which provide sufficiently similar protection for the Relevant Data Subjects in relation to such Decision-Making, as to the relevant protection the Relevant Data Subject would have if such Decision-Making was in the UK.
21. How Relevant Data Subjects can exercise their data subject rights– if the Importer is the Exporter’s Processor or Sub-Processor
21.1 Where the Importer is the Exporter’s Processor or Sub-Processor: If the Importer receives a request directly from an individual which relates to the Transferred Data it must pass that request on to the Exporter Without Undue Delay. The Importer must only respond to that individual as authorised by the Exporter or any Third Party Controller.
22.Rights of Relevant Data Subjects are subject to the exemptions in the UK Data Protection Laws
22.1 The Importer is not required to respond to requests or provide information or notifications under Sections 18, 19, 20, 21 and 23 if:
22.1.1 it is unable to reasonably verify the identity of an individual making the request; or
22.1.2 the requests are manifestly unfounded or excessive, including where requests are repetitive. In that case the Importer may refuse the request or may charge the Relevant Data Subject a reasonable fee; or
22.1.3 a relevant exemption would be available under UK Data Protection Laws, were the Importer subject to the UK Data Protection Laws.
If the Importer refuses an individual’s request or charges a fee under Section 22.1.2 it will set out in writing the reasons for its refusal or charge, and inform the Relevant Data Subject that they are entitled to bring a claim for compensation under this IDTA in the case of any breach of this IDTA.
How to give third parties access to Transferred Data under Local Laws
23. Access requests and direct access
23.1 In this Section 23 an “Access Request” is a legally binding request (except for requests only binding by contract law) to access any Transferred Data and “Direct Access” means direct access to any Transferred Data by public authorities of which the Importer is aware.
23.2 The Importer may disclose any requested Transferred Data in so far as it receives an Access Request, unless in the circumstances it is reasonable for it to challenge that Access Request on the basis there are significant grounds to believe that it is unlawful.
23.3 In so far as Local Laws allow and it is reasonable to do so, the Importer will Without Undue Delay provide the following with relevant information about any Access Request or Direct Access: the Exporter; any Third Party Controller; and where the Importer is a Controller, any Relevant Data Subjects.
23.4 In so far as Local Laws allow, the Importer must:
23.4.1 make and keep a written record of Access Requests and Direct Access, including (if known): the dates, the identity of the requestor/accessor, the purpose of the Access Request or Direct Access, the type of data requested or accessed, whether it was challenged or appealed, and the outcome; and the Transferred Data which was provided or accessed; and
23.4.2 provide a copy of this written record to the Exporter on each Review Date and any time the Exporter or the ICO reasonably requests.
24. Giving notice
24.1 If a Party is required to notify any other Party in this IDTA it will be marked for the attention of the relevant Key Contact and sent by e-mail to the e-mail address given for the Key Contact.
24.2 If the notice is sent in accordance with Section 24.1, it will be deemed to have been delivered at the time the e-mail was sent, or if that time is outside of the receiving Party’s normal business hours, the receiving Party’s next normal business day, and provided no notice of non-delivery or bounceback is received.
24.3 The Parties agree that any Party can update their Key Contact details by giving 14 days’ (or more) notice in writing to the other Party.
25. General clauses
25.1 In relation to the transfer of the Transferred Data to the Importer and the Importer’s Processing of the Transferred Data, this IDTA and any Linked Agreement:
25.1.1 contain all the terms and conditions agreed by the Parties; and
25.1.2 override all previous contacts and arrangements, whether oral or in writing.
25.2 If one Party made any oral or written statements to the other before entering into this IDTA (which are not written in this IDTA) the other Party confirms that it has not relied on those statements and that it will not have a legal remedy if those statements are untrue or incorrect, unless the statement was made fraudulently.
25.3 Neither Party may novate, assign or obtain a legal charge over this IDTA (in whole or in part) without the written consent of the other Party, which may be set out in the Linked Agreement.
25.4 Except as set out in Section 17.1, neither Party may sub contract its obligations under this IDTA without the written consent of the other Party, which may be set out in the Linked Agreement.
25.5 This IDTA does not make the Parties a partnership, nor appoint one Party to act as the agent of the other Party.
25.6 If any Section (or part of a Section) of this IDTA is or becomes illegal, invalid or unenforceable, that will not affect the legality, validity and enforceability of any other Section (or the rest of that Section) of this IDTA.
25.7 If a Party does not enforce, or delays enforcing, its rights or remedies under or in relation to this IDTA, this will not be a waiver of those rights or remedies. In addition, it will not restrict that Party’s ability to enforce those or any other right or remedy in future.
25.8 If a Party chooses to waive enforcing a right or remedy under or in relation to this IDTA, then this waiver will only be effective if it is made in writing. Where a Party provides such a written waiver:
25.8.1 it only applies in so far as it explicitly waives specific rights or remedies;
25.8.2 it shall not prevent that Party from exercising those rights or remedies in the future (unless it has explicitly waived its ability to do so); and
25.8.3 it will not prevent that Party from enforcing any other right or remedy in future.
What happens if there is a breach of this IDTA?
26. Breaches of this IDTA
26.1 Each Party must notify the other Party in writing (and with all relevant details) if it:
26.1.1 has breached this IDTA; or
26.1.2 it should reasonably anticipate that it may breach this IDTA, and provide any information about this which the other Party reasonably requests.
26.2 In this IDTA “Significant Harmful Impact” means that there is more than a minimal risk of a breach of the IDTA causing (directly or indirectly) significant damage to any Relevant Data Subject or the other Party.
27. Breaches of this IDTA by the Importer
27.1 If the Importer has breached this IDTA, and this has a Significant Harmful Impact, the Importer must take steps Without Undue Delay to end the Significant Harmful Impact, and if that is not possible to reduce the Significant Harmful Impact as much as possible.
27.2 Until there is no ongoing Significant Harmful Impact on Relevant Data Subjects:
27.2.1 the Exporter must suspend sending Transferred Data to the Importer;
27.2.2 If the Importer is the Exporter’s Processor or Sub-Processor: if the Exporter requests, the importer must securely delete all Transferred Data or securely return it to the Exporter (or a third party named by the Exporter); and
27.2.3 if the Importer has transferred on the Transferred Data to a third party receiver under Section 16, and the breach has a Significant Harmful Impact on Relevant Data Subject when it is Processed by or on behalf of that third party receiver, the Importer must:
27.2.3.1 notify the third party receiver of the breach and suspend sending it Transferred Data; and
27.2.3.2 if the third party receiver is the Importer’s Processor or Sub-Processor: make the third party receiver securely delete all Transferred Data being Processed by it or on its behalf, or securely return it to the Importer (or a third party named by the Importer).
27.3 If the breach cannot be corrected Without Undue Delay, so there is no ongoing Significant Harmful Impact on Relevant Data Subjects, the Exporter must end this IDTA under Section 30.1.
28. Breaches of this IDTA by the Exporter
28.1 If the Exporter has breached this IDTA, and this has a Significant Harmful Impact, the Exporter must take steps Without Undue Delay to end the Significant Harmful Impact and if that is not possible to reduce the Significant Harmful Impact as much as possible.
28.2 Until there is no ongoing risk of a Significant Harmful Impact on Relevant Data Subjects, the Exporter must suspend sending Transferred Data to the Importer.
28.3 If the breach cannot be corrected Without Undue Delay, so there is no ongoing Significant Harmful Impact on Relevant Data Subjects, the Importer must end this IDTA under Section 30.1.
Ending the IDTA
29.How to end this IDTA without there being a breach
29.1 The IDTA will end:
29.1.1 at the end of the Term stated in Table 2: Transfer Details; or
29.1.2 if in Table 2: Transfer Details, the Parties can end this IDTA by providing written notice to the other: at the end of the notice period stated;
29.1.3 at any time that the Parties agree in writing that it will end; or
29.1.4 at the time set out in Section 29.2.
29.2 If the ICO issues a revised Approved IDTA under Section 5.4, if any Party selected in Table 2 “Ending the IDTA when the Approved IDTA changes”, will as a direct result of the changes in the Approved IDTA have a substantial, disproportionate and demonstrable increase in:
29.2.1 its direct costs of performing its obligations under the IDTA; and/or
29.2.2 its risk under the IDTA,
and in either case it has first taken reasonable steps to reduce that cost or risk so that it is not substantial and disproportionate, that Party may end the IDTA at the end of a reasonable notice period, by providing written notice for that period to the other Party before the start date of the revised Approved IDTA.
30. How to end this IDTA if there is a breach
30.1 A Party may end this IDTA immediately by giving the other Party written notice if:
30.1.1 the other Party has breached this IDTA and this has a Significant Harmful Impact. This includes repeated minor breaches which taken together have a Significant Harmful Impact, and
30.1.1.1 the breach can be corrected so there is no Significant Harmful Impact, and the other Party has failed to do so Without Undue Delay (which cannot be more than 14 days of being required to do so in writing); or
30.1.1.2 the breach and its Significant Harmful Impact cannot be corrected;
30.1.2 the Importer can no longer comply with Section 8.3, as there are Local Laws which mean it cannot comply with this IDTA and this has a Significant Harmful Impact.
31. What must the Parties do when the IDTA ends?
31.1 If the parties wish to bring this IDTA to an end or this IDTA ends in accordance with any provision in this IDTA, but the Importer must comply with a Local Law which requires it to continue to keep any Transferred Data then this IDTA will remain in force in respect of any retained Transferred Data for as long as the retained Transferred Data is retained, and the Importer must:
31.1.1 notify the Exporter Without Undue Delay, including details of the relevant Local Law and the required retention period;
31.1.2 retain only the minimum amount of Transferred Data it needs to comply with that Local Law, and the Parties must ensure they maintain the Appropriate Safeguards, and change the Tables and Extra Protection Clauses, together with any TRA to reflect this; and
31.1.3 stop Processing the Transferred Data as soon as permitted by that Local Law and the IDTA will then end and the rest of this Section 29 will apply.
31.2 When this IDTA ends (no matter what the reason is):
31.2.1 the Exporter must stop sending Transferred Data to the Importer; and
31.2.2 if the Importer is the Exporter’s Processor or Sub-Processor: the Importer must delete all Transferred Data or securely return it to the Exporter (or a third party named by the Exporter), as instructed by the Exporter;
31.2.3 if the Importer is a Controller and/or not the Exporter’s Processor or Sub-Processor: the Importer must securely delete all Transferred Data.
31.2.4 the following provisions will continue in force after this IDTA ends (no matter what the reason is):
· Section 1 (This IDTA and Linked Agreements);
· Section 2 (Legal Meaning of Words);
· Section 6 (Understanding this IDTA);
· Section 7 (Which laws apply to this IDTA);
· Section 10 (The ICO);
· Sections 11.1 and 11.4 (Exporter’s obligations);
· Sections 12.1.2, 12.1.3, 12.1.4, 12.1.5 and 12.1.6 (General Importer obligations);
· Section 13.1 (Importer’s obligations if it is subject to UK Data Protection Laws);
· Section 17 (Importer’s responsibility if it authorised others to perform its obligations);
· Section 24 (Giving notice);
· Section 25 (General clauses);
· Section 31 (What must the Parties do when the IDTA ends);
· Section 32 (Your liability);
· Section 33 (How Relevant Data Subjects and the ICO may bring legal claims);
· Section 34 (Courts legal claims can be brought in);
· Section 35 (Arbitration); and
· Section 36 (Legal Glossary).
How to bring a legal claim under this IDTA
32. Your liability
32.1 The Parties remain fully liable to Relevant Data Subjects for fulfilling their obligations under this IDTA and (if they apply) under UK Data Protection Laws.
32.2 Each Party (in this Section, “Party One”) agrees to be fully liable to Relevant Data Subjects for the entire damage suffered by the Relevant Data Subject, caused directly or indirectly by:
32.2.1 Party One’s breach of this IDTA; and/or
32.2.2 where Party One is a Processor, Party One’s breach of any provisions regarding its Processing of the Transferred Data in the Linked Agreement;
32.2.3 where Party One is a Controller, a breach of this IDTA by the other Party if it involves Party One’s Processing of the Transferred Data (no matter how minimal)
in each case unless Party One can prove it is not in any way responsible for the event giving rise to the damage.
32.3 If one Party has paid compensation to a Relevant Data Subject under Section 32.2, it is entitled to claim back from the other Party that part of the compensation corresponding to the other Party’s responsibility for the damage, so that the compensation is fairly divided between the Parties.
32.4 The Parties do not exclude or restrict their liability under this IDTA or UK Data Protection Laws, on the basis that they have authorised anyone who is not a Party (including a Processor) to perform any of their obligations, and they will remain responsible for performing those obligations.
33. How Relevant Data Subjects and the ICO may bring legal claims
33.1 The Relevant Data Subjects are entitled to bring claims against the Exporter and/or Importer for breach of the following (including where their Processing of the Transferred Data is involved in a breach of the following by either Party):
· Section 1 (This IDTA and Linked Agreements);
· Section 3 (You have provided all the information required by Part one: Tables and Part two: Extra Protection Clauses);
· Section 8 (The Appropriate Safeguards);
· Section 9 (Reviews to ensure the Appropriate Safeguards continue);
· Section 11 (Exporter’s obligations);
· Section 12 (General Importer Obligations);
· Section 13 (Importer’s obligations if it is subject to UK Data Protection Laws);
· Section 14 (Importer’s obligations to comply with key data protection laws);
· Section 15 (What happens if there is an Importer Personal Data Breach);
· Section 16 (Transferring on the Transferred Data);
· Section 17 (Importer’s responsibility if it authorises others to perform its obligations);
· Section 18 (The right to a copy of the IDTA);
· Section 19 (The Importer’s contact details for the Relevant Data Subjects);
· Section 20 (How Relevant Data Subjects can exercise their data subject rights);
· Section 21 (How Relevant Data Subjects can exercise their data subject rights– if the Importer is the Exporter’s Processor or Sub-Processor);
· Section 23 (Access Requests and Direct Access);
· Section 26 (Breaches of this IDTA);
· Section 27 (Breaches of this IDTA by the Importer);
· Section 28 (Breaches of this IDTA by the Exporter);
· Section 30 (How to end this IDTA if there is a breach);
· Section 31 (What must the Parties do when the IDTA ends); and
· any other provision of the IDTA which expressly or by implication benefits the Relevant Data Subjects.
33.2 The ICO is entitled to bring claims against the Exporter and/or Importer for breach of the following Sections: Section 10 (The ICO), Sections 11.1 and 11.2 (Exporter’s obligations), Section 12.1.6 (General Importer obligations) and Section 13 (Importer’s obligations if it is subject to UK Data Protection Laws).
33.3 No one else (who is not a Party) can enforce any part of this IDTA (including under the Contracts (Rights of Third Parties) Act 1999).
33.4 The Parties do not need the consent of any Relevant Data Subject or the ICO to make changes to this IDTA, but any changes must be made in accordance with its terms.
33.5 In bringing a claim under this IDTA, a Relevant Data Subject may be represented by a not-for-profit body, organisation or association under the same conditions set out in Article 80(1) UK GDPR and sections 187 to 190 of the Data Protection Act 2018.
34. Courts legal claims can be brought in
34.1 The courts of the UK country set out in Table 2: Transfer Details have non-exclusive jurisdiction over any claim in connection with this IDTA (including non-contractual claims).
34.2 The Exporter may bring a claim against the Importer in connection with this IDTA (including non-contractual claims) in any court in any country with jurisdiction to hear the claim.
34.3 The Importer may only bring a claim against the Exporter in connection with this IDTA (including non-contractual claims) in the courts of the UK country set out in the Table 2: Transfer Details
34.4 Relevant Data Subjects and the ICO may bring a claim against the Exporter and/or the Importer in connection with this IDTA (including non-contractual claims) in any court in any country with jurisdiction to hear the claim.
34.5 Each Party agrees to provide to the other Party reasonable updates about any claims or complaints brought against it by a Relevant Data Subject or the ICO in connection with the Transferred Data (including claims in arbitration).
35. Arbitration
35.1 Instead of bringing a claim in a court under Section 34, any Party, or a Relevant Data Subject may elect to refer any dispute arising out of or in connection with this IDTA (including non-contractual claims) to final resolution by arbitration under the Rules of the London Court of International Arbitration, and those Rules are deemed to be incorporated by reference into this Section 35.
35.2 The Parties agree to submit to any arbitration started by another Party or by a Relevant Data Subject in accordance with this Section 35.
35.3 There must be only one arbitrator. The arbitrator (1) must be a lawyer qualified to practice law in one or more of England and Wales, or Scotland, or Northern Ireland and (2) must have experience of acting or advising on disputes relating to UK Data Protection Laws.
35.4 London shall be the seat or legal place of arbitration. It does not matter if the Parties selected a different UK country as the ‘primary place for legal claims to be made’ in Table 2: Transfer Details.
35.5 The English language must be used in the arbitral proceedings.
35.6 English law governs this Section 35. This applies regardless of whether or not the parties selected a different UK country’s law as the ‘UK country’s law that governs the IDTA’ in Table 2: Transfer Details.
36. Legal Glossary
| Word or Phrase | Legal definition(this is how this word or phrase must be interpreted in the IDTA) |
| Access Request | As defined in Section 23, as a legally binding request (except for requests only binding by contract law) to access any Transferred Data. |
| Adequate Country | A third country, or:· a territory;· one or more sectors or organisations within a third country;· an international organisation;which the Secretary of State has specified by regulations provides an adequate level of protection of Personal Data in accordance with Section 17A of the Data Protection Act 2018. |
| Appropriate Safeguards | The standard of protection over the Transferred Data and of the Relevant Data Subject’s rights, which is required by UK Data Protection Laws when you are making a Restricted Transfer relying on standard data protection clauses under Article 46(2)(d) UK GDPR. |
| Approved IDTA | The template IDTA A1.0 issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 5.4. |
| Commercial Clauses | The commercial clauses set out in Part three. |
| Controller | As defined in the UK GDPR. |
| Damage | All material and non-material loss and damage. |
| Data Subject | As defined in the UK GDPR. |
| Decision-Making | As defined in Section 20.6, as decisions about the Relevant Data Subjects based solely on automated processing, including profiling, using the Transferred Data. |
| Direct Access | As defined in Section 23 as direct access to any Transferred Data by public authorities of which the Importer is aware. |
| Exporter | The exporter identified in Table 1: Parties & Signature. |
| Extra Protection Clauses | The clauses set out in Part two: Extra Protection Clauses. |
| ICO | The Information Commissioner. |
| Importer | The importer identified in Table 1: Parties & Signature. |
| Importer Data Subject Contact | The Importer Data Subject Contact identified in Table 1: Parties & Signature, which may be updated in accordance with Section 19. |
| Importer Information | As defined in Section 8.3.1, as all relevant information regarding Local Laws and practices and the protections and risks which apply to the Transferred Data when it is Processed by the Importer, including for the Exporter to carry out any TRA. |
| Importer Personal Data Breach | A ‘personal data breach’ as defined in UK GDPR, in relation to the Transferred Data when Processed by the Importer. |
| Linked Agreement | The linked agreement set out in Table 2: Transfer Details. |
| Local Laws | Laws which are not the laws of the UK and which bind the Importer. |
| Mandatory Clauses | Part four: Mandatory Clauses of this IDTA. |
| Notice Period | As set out in Table 2: Transfer Details. |
| Party/Parties | The parties to this IDTA as set out in Table 1: Parties & Signature. |
| Personal Data | As defined in the UK GDPR. |
| Personal Data Breach | As defined in the UK GDPR. |
| Processing | As defined in the UK GDPR.When the IDTA refers to Processing by the Importer, this includes where a third party Sub-Processor of the Importer is Processing on the Importer’s behalf. |
| Processor | As defined in the UK GDPR. |
| Purpose | The ‘Purpose’ set out in Table 2: Transfer Details, including any purposes which are not incompatible with the purposes stated or referred to. |
| Relevant Data Subject | A Data Subject of the Transferred Data. |
| Restricted Transfer | A transfer which is covered by Chapter V of the UK GDPR |
| Review Dates | The review dates or period for the Security Requirements set out in Table 2: Transfer Details, and any review dates set out in any revised Approved IDTA. |
| Significant Harmful Impact | As defined in Section 26.2 as where there is more than a minimal risk of the breach causing (directly or indirectly) significant harm to any Relevant Data Subject or the other Party. |
| Special Category Data | As described in the UK GDPR, together with criminal conviction or criminal offence data. |
| Start Date | As set out in Table 1: Parties and signature. |
| Sub-Processor | A Processor appointed by another Processor to Process Personal Data on its behalf.This includes Sub-Processors of any level, for example a Sub-Sub-Processor. |
| Tables | The Tables set out in Part one of this IDTA. |
| Term | As set out in Table 2: Transfer Details. |
| Third Party Controller | The Controller of the Transferred Data where the Exporter is a Processor or Sub-ProcessorIf there is not a Third Party Controller this can be disregarded. |
| Transfer Risk Assessment or TRA | A risk assessment in so far as it is required by UK Data Protection Laws to demonstrate that the IDTA provides the Appropriate Safeguards |
| Transferred Data | Any Personal Data which the Parties transfer, or intend to transfer under this IDTA, as described in Table 2: Transfer Details |
| UK Data Protection Laws | All laws relating to data protection, the processing of personal data, privacy and/or electronic communications in force from time to time in the UK, including the UK GDPR and the Data Protection Act 2018. |
| UK GDPR | As defined in Section 3 of the Data Protection Act 2018. |
| Without Undue Delay | Without undue delay, as that phase is interpreted in the UK GDPR. |