Effective March 30th 2026
ATHINIA TERMS OF SERVICE
These Athinia Technologies LLC (“Athinia”) Terms of Service (collectively with any attachments, addenda, or exhibits referenced herein and any Order Forms (as defined below) that reference these Terms of Service, the “Agreement”) apply to any Order Form(s) between Customer and Athinia (each a “Party” and collectively the “Parties”) and are effective as of the Effective Date of the first Athinia Order Form between the Parties.
ANNEX A
Customer’s use of AIP may leverage the following Models hosted in a third party environment (each a “Third Party Model Service”).
|
Third Party Model Service |
Additional Terms |
|
Anthropic Models hosted in Athinia’s Anthropic Environment (“Anthropic Model Service”) |
Customer’s use of AIP leveraging Anthropic Model Service (a) shall comply with the Anthropic Usage Policy (available at https://www.anthropic.com/legal/aup); and (b) shall not facilitate or engage in the following: (i) design, market, help distribute or utilize weapons, explosives, dangerous materials or other systems designed to cause harm to or loss of human life; (ii) covertly tracking, targeting, or surveilling individuals, i.e., searching for or gathering information on an individual or group in order to track, target or report on their identity, including using the product for facial recognition, covert tracking, battlefield management applications or predictive policing; (iii) automated determination of financing eligibility of individuals, i.e., making automated decisions about the eligibility of individuals for financial products and creditworthiness; (iv) automated determination of employment and housing decisions, i.e., making automated decisions about the employability of individuals or other employment determinations or decisions regarding eligibility for housing, including leases and home loans; (v) any law enforcement application, except for the following permitted applications by U.S. law enforcement organizations: back office uses including call center support, document summarization, and accounting; (vi) analysis of data for the location of missing persons and other applications, provided that such applications do not otherwise violate or impair the liberty, civil liberties, or human rights of natural persons; (vii) shall not be for the purpose of building a product or service to the Anthropic Model Service (including to train competing Models or to resell the Models); and (viii) shall not involve reverse engineering or duplicating the Anthropic Model Service. Customer acknowledges that Anthropic, PBC may collect and temporarily retain pseudonymized security classifier metadata related to Customer’s use of AIP leveraging the Anthropic Model Service (which metadata, for the avoidance of doubt, shall not include the contents of Customer’s prompts provided to or output received from the Anthropic Model Service). |
|
OpenAI Models hosted in Athinia’s Microsoft Azure Environment (“Azure OpenAI Model Service”) |
(a) Customer’s use of AIP leveraging the Azure OpenAI Model Service shall comply with the Azure OpenAI Code of Conduct (https://learn.microsoft.com/en-us/legal/cognitive-services/openai/code-of-conduct?context=%2Fazure%2Fcognitive- services%2Fopenai%2Fcontext%2Fcontext); (b) Customer shall only use AIP leveraging the Azure OpenAI Model Service to (i) submit content to be summarized for pre-defined topics built into AIP and cannot use AIP as an open-ended summarizer (examples of such permitted use include but are not limited to summarization of call center transcripts, technical reports, and product reviews); (ii) analyze inputs using classification, sentiment analysis of text, or entity extraction (examples of such permitted use include but are not limited to analyzing product feedback sentiment, analyzing support calls and transcripts, and refining text-based search with embeddings); (iii) search trusted source documents such as internal Customer documentation; (iv) ask questions and receive answers from trusted source documents such as internal Customer documentation; or (v) code generation or transformation scenarios (examples of such permitted use include but are not limited to converting one programming language to another, generating docstrings for functions, or converting natural language to SQL); and (c) Customer shall not use AIP leveraging the Azure OpenAI Model Service (i) to generate, distribute, or modify any output from the Azure OpenAI Model Service that the Customer knew or should have known was infringing or likely to infringe a third party’s intellectual property or other proprietary rights (including if such infringement is caused by Customer’s combination of such output with third party products or services); or (ii) while disabling, ignoring, or otherwise circumventing, without authorization, any relevant citation, filtering, or safety features or restrictions provided by Azure or Athinia applicable to the Azure OpenAI Model Service. |
|
Models hosted in Athinia’s Amazon Web Services Environment (“AWS Model Service”) |
Customer’s use of AIP leveraging Anthropic Models through the AWS Model Service (a) shall comply with the Anthropic Code of Conduct (https://console.anthropic.com/legal/aup), (b) shall comply with the Anthropic Bedrock AI Services Agreement (available at https://s3.amazonaws.com/EULA/Anthropic-EULA-1023.pdf), and (c) shall not facilitate or engage in the following: (i) design, market, help distribute or utilize weapons, explosives, dangerous materials or other systems designed to cause harm to or loss of human life; (ii) covertly tracking, targeting, or surveilling individuals, i.e., searching for or gathering information on an individual or group in order to track, target or report on their identity, including using the product for facial recognition, covert tracking, battlefield management applications or predictive policing; (iii) automated determination of financing eligibility of individuals, i.e., making automated decisions about the eligibility of individuals for financial products and creditworthiness; (iv) automated determination of employment and housing decisions, i.e., making automated decisions about the employability of individuals or other employment determinations or decisions regarding eligibility for housing, including leases and home loans; (v) any law enforcement application, except for the following permitted applications by U.S. law enforcement organizations: back office uses including call center support, document summarization, and accounting; or (vi) analysis of data for the location of missing persons and other applications, provided that such applications do not otherwise violate or impair the liberty, civil liberties, or human rights of natural persons. |
|
Google Provided Models hosted in Athinia’s Google Cloud Services Environment (“Google Model Service”) |
Customer’s use of AIP leveraging the Google Model Service (a) shall comply with the Google Generative AI Prohibited Use Policy (https://policies.google.com/terms/generative-ai/use-policy); (b) shall comply with the Google Cloud Platform Acceptable Use Policy (https://cloud.google.com/terms/aup); (c) shall comply with the Anthropic on Vertex - Commercial Terms of Service (available at https://www-cdn.anthropic.com/471bd07290603ee509a5ea0d5ccf131ea5897232/anthropic-vertex-commercial-terms-march-2024.pdf), with respect to any Anthropic models used or accessed via the Google Model Service; (d) shall not reasonably be expected to lead to death, personal injury, or environmental damage, including operation of nuclear facilities, air traffic control, life support systems, or weaponry; and (e) shall, with respect to Customer’s use of applicable models that meet the definition of “Pre-GA Offerings” in the Google Model Service Pre-GA Offerings Terms (defined below) made available via the Google Model Service, comply with Google’s “Pre-GA Offerings Terms” subsection in the “General Service Terms” section of the Google Cloud Platform Service Specific Terms, available at https://cloud.google.com/terms/service-terms (the “Google Model Service Pre-GA Offerings Terms”). |
|
OpenAI Models hosted by OpenAI (“OpenAI Model Service”) |
Customer’s use of AIP leveraging the OpenAI Model Service (a) shall comply with the OpenAI Usage Policies (https://openai.com/policies/usage-policies); (b) if and only as applicable, shall comply with the applicable OpenAI Service Terms (https://openai.com/policies/service-terms); (c) Customer shall only use AIP leveraging the OpenAI Model Service to (i) submit content to be summarized for pre-defined topics built into AIP and cannot use AIP as an open-ended summarizer (examples of such permitted use include but are not limited to summarization of call center transcripts, technical reports, and product reviews); (ii) analyze inputs using classification, sentiment analysis of text, or entity extraction (examples of such permitted use include but are not limited to analyzing product feedback sentiment, analyzing support calls and transcripts, and refining text-based search with embeddings; (iii) search trusted source documents such as internal Customer documentation; (iv) ask questions and receive answers from trusted source documents such as internal Customer documentation; (v) code generation or transformation scenarios (examples of such permitted use include but are not limited to converting one programming language to another, generating docstrings for functions, or converting natural language to SQL); or (vi) fine-tune Models as provided as part of AIP and the OpenAI Model Service; and (d) Customer shall not use AIP leveraging the OpenAI Model Service (i) to generate, distribute, or modify any output from the OpenAI Model Service that the Customer knew or should have known was infringing or likely to infringe a third party’s intellectual property or other proprietary rights (including if such infringement is caused by Customer’s combination of such output with third party products or services); or (ii) while disabling, ignoring, or otherwise circumventing, without authorization, any relevant citation, filtering, or safety features or restrictions provided by OpenAI applicable to the OpenAI Model Service. |
|
Meta’s Llama 4 Model, Meta's Llama 3.3 Model, Meta's Llama 3.2 Model, and Meta's Llama 3.1 Model (and Meta’s Llama Models now existing or released in the future) hosted in Athinia's model hub environment(s) (“Llama Model Service”) |
Customer’s use of AIP leveraging the Llama Model Service shall comply with (a) the Llama 4 Community License Agreement (https://www.llama.com/llama4/license/), which includes the Llama 4 Acceptable Use Policy incorporated by reference (https://www.llama.com/llama4/use-policy/); (b) the Llama 3.3 Community License Agreement (https://www.llama.com/llama3_3/license/), which includes the Llama 3.3 Acceptable Use Policy incorporated by reference (https://www.llama.com/llama3_3/use- policy/); (c) the Llama 3.2 Community License Agreement (https://github.com/meta-llama/llama-models/blob/main/models/llama3_2/LICENSE), which includes the Llama 3.2 Acceptable Use Policy (https://www.llama.com/llama3_2/use-policy/); (d) the Llama 3.1 Community License Agreement (https://github.com/meta-llama/llama-models/blob/main/models/llama3_1/LICENSE), which includes the Llama 3.1 Acceptable Use Policy (https://llama.meta.com/llama3_1/use-policy/); and (e) any license terms and/or acceptable use policies applicable to any other Llama Model(s) (now existing or released in the future) made available as part of the Llama Model Service. |
|
X.AI LLC’s Grok Models hosted by X.AI LLC (“xAI Model Service”) |
Customer’s use of AIP leveraging the xAI Model Service shall (a) comply with applicable law (this includes not taking unlawful action on behalf of others); (b) not promote or engage in (i) the sexualization or exploitation of children, (ii) violating copyright, trademark, or other intellectual property law, (iii) compromising others’ privacy, (iv) violating a person’s right to publicity, (v) operating in a regulated industry without complying with those regulations, or (vi) defrauding, defaming, scamming, or spamming; (c) not harm people or property (this includes but is not limited to not perpetrating hacking, doxing, phishing or other malicious attacks, and not developing any kind of weapon); (d) not mislead or circumvent technical safeguards or other technical guardrails; (e) not represent that output of the xAI Model Service is human generated; and (f) not use output of the xAI Model Service to train generative artificial intelligence models similar to or competitive with the xAI Model Service. |
ATHINIA TERMS OF SERVICE
These Athinia Technologies LLC (“Athinia”) Terms of Service (collectively with any attachments, addenda, or exhibits referenced herein and any Order Forms (as defined below) that reference these Terms of Service, the “Agreement”) apply to any Order Form(s) between Customer and Athinia (each a “Party” and collectively the “Parties”) and are effective as of the Effective Date of the first Athinia Order Form between the Parties.
Third Party Model Service | Additional Terms |
OpenAI Models hosted in Microsoft Azure Environment (“Azure OpenAI Model Service”) | (a) Customer’s use of AIP leveraging the Azure OpenAI Model Service shall comply with the Azure OpenAI Code of Conduct (https://learn.microsoft.com/en-us/legal/cognitive-services/openai/code-of-conduct?context=%2Fazure%2Fcognitive- services%2Fopenai%2Fcontext%2Fcontext); (b) Customer shall only use AIP leveraging the Azure OpenAI Model Service to (i) submit content to be summarized for pre-defined topics built into AIP and cannot use AIP as an open-ended summarizer (examples of such permitted use include but are not limited to summarization of call center transcripts, technical reports, and product reviews); (ii) analyze inputs using classification, sentiment analysis of text, or entity extraction (examples of such permitted use include but are not limited to analyzing product feedback sentiment, analyzing support calls and transcripts, and refining text-based search with embeddings; (iii) search trusted source documents such as internal Customer documentation; (iv) ask questions and receive answers from trusted source documents such as internal Customer documentation; or (v) code generation or transformation scenarios (examples of such permitted use include but are not limited to converting one programming language to another, generating docstrings for functions, or converting natural language to SQL); and (c) Customer shall not use AIP leveraging the Azure OpenAI Model Service (i) to generate, distribute, or modify any output from the Azure OpenAI Model Service that the Customer knew or should have known was infringing or likely to infringe a third party’s intellectual property or other proprietary rights (including if such infringement is caused by Customer’s combination of such output with third party products or services); or (ii) while disabling, ignoring, or otherwise circumventing, without authorization, any relevant citation, filtering, or safety features or restrictions provided by Azure or Athinia applicable to the Azure OpenAI Model Service. |
Models hosted in Amazon Web Services Environment (“AWS Model Service”) | Customer’s use of AIP leveraging Anthropic Models through the AWS Model Service (a) shall comply with the Anthropic Code of Conduct (https://console.anthropic.com/legal/aup), and (b) shall not facilitate or engage in the following: (i) design, market, help distribute or utilize weapons, explosives, dangerous materials or other systems designed to cause harm to or loss of human life; (ii) covertly tracking, targeting, or surveilling individuals, i.e., searching for or gathering information on an individual or group in order to track, target or report on their identity, including using the product for facial recognition, covert tracking, battlefield management applications or predictive policing; (iii) automated determination of financing eligibility of individuals, i.e., making automated decisions about the eligibility of individuals for financial products and creditworthiness; (iv) automated determination of employment and housing decisions, i.e., making automated decisions about the employability of individuals or other employment determinations or decisions regarding eligibility for housing, including leases and home loans; (v) any law enforcement application, except for the following permitted applications by U.S. law enforcement organizations: back office uses including call center support, document summarization, and accounting; or (vi) analysis of data for the location of missing persons and other applications, provided that such applications do not otherwise violate or impair the liberty, civil liberties, or human rights of natural persons. Customer hereby agrees that its use of AIP leveraging Models (other than Anthropic Models) through the AWS Model Service shall comply with any acceptable use policies or codes of conduct applicable to such Models, as made available to Customer through AIP or the Documentation. Customer acknowledges that Amazon Web Services, Inc. may collect and temporarily retain pseudonymized security classifier metadata related to Customer’s use of AIP leveraging the AWS Model Service (which metadata, for the avoidance of doubt, shall not include the contents of Customer’s prompts provided to or output received from the AWS Model Service). |
Google Models hosted in Google Cloud Services Environment (“Google Model Service”) | Customer’s use of AIP leveraging the Google Model Service (a) shall comply with the Google Generative AI Prohibited Use Policy (https://policies.google.com/terms/generative-ai/use-policy); (b) shall comply with the Google Cloud Platform Acceptable Use Policy (https://cloud.google.com/terms/aup); and (c) shall not reasonably be expected to lead to death, personal injury, or environmental damage, including operation of nuclear facilities, air traffic control, life support systems, or weaponry. Customer acknowledges that Google LLC may collect and temporarily retain pseudonymized security classifier metadata related to Customer’s use of AIP leveraging the Google Model Service (which metadata, for the avoidance of doubt, shall not include the contents of Customer’s prompts provided to or output received from the Google Model Service). |
OpenAI Models hosted by OpenAI (“OpenAI Model Service”) | Customer’s use of AIP leveraging the OpenAI Model Service (a) shall comply with the OpenAI Usage Policies (https://openai.com/policies/usage-policies); (b) if and only as applicable, shall comply with the applicable OpenAI Service Terms (https://openai.com/policies/service-terms); (c) Customer shall only use AIP leveraging the OpenAI Model Service to (i) submit content to be summarized for pre-defined topics built into AIP and cannot use AIP as an open-ended summarizer (examples of such permitted use include but are not limited to summarization of call center transcripts, technical reports, and product reviews); (ii) analyze inputs using classification, sentiment analysis of text, or entity extraction (examples of such permitted use include but are not limited to analyzing product feedback sentiment, analyzing support calls and transcripts, and refining text-based search with embeddings; (iii) search trusted source documents such as internal Customer documentation; (iv) ask questions and receive answers from trusted source documents such as internal Customer documentation; (v) code generation or transformation scenarios (examples of such permitted use include but are not limited to converting one programming language to another, generating docstrings for functions, or converting natural language to SQL); or (vi) fine-tune Models as provided as part of AIP and the OpenAI Model Service; and (d) Customer shall not use AIP leveraging the OpenAI Model Service (i) to generate, distribute, or modify any output from the OpenAI Model Service that the Customer knew or should have known was infringing or likely to infringe a third party’s intellectual property or other proprietary rights (including if such infringement is caused by Customer’s combination of such output with third party products or services); or (ii) while disabling, ignoring, or otherwise circumventing, without authorization, any relevant citation, filtering, or safety features or restrictions provided by OpenAI applicable to the OpenAI Model Service. Customer acknowledges that OpenAI, LLC may collect and temporarily retain pseudonymized security classifier metadata related to Customer’s use of AIP leveraging the OpenAI Model Service (which metadata, for the avoidance of doubt, shall not include the contents of Customer’s prompts provided to or output received from the OpenAI Model Service). |
ATHINIA TERMS OF SERVICE
These Athinia Technologies LLC (“Athinia”) Terms of Service (collectively with any attachments, addenda, or exhibits referenced herein and any Order Forms (as defined below) that reference these Terms of Service, the “Agreement”) apply to any Order Form(s) between Customer and Athinia (each a “Party” and collectively the “Parties”) and are effective as of the Effective Date of the first Athinia Order Form between the Parties.
Effective March 30th 2026
Customer and Athinia Technologies LLC (“Athinia” each of Customer and Athinia a “Party” and collectively the “Parties”), have entered into an agreement (including the Athinia Order Form and the Athinia Terms of Service) governing Customer’s use of Athinia Technology, including the Service, and the provision of related Professional Services to Customer by Athinia, including any attachments, order forms, exhibits, and appendices thereto (collectively, the “Agreement”). This DPA supplements, is incorporated into, and forms part of the Agreement and establishes the rights and obligations of Athinia and Customer with respect to any Customer Personal Data Processed by Athinia on behalf of Customer under the Agreement. Any capitalized terms used but not defined in this DPA shall have the meaning provided in the Agreement. To the extent there is any conflict in meaning between any provisions of the Agreement and this DPA, the terms and conditions in this DPA shall prevail and control.
EXHIBIT A
LIST OF APPROVED SUBPROCESSORS
Part I - Subprocessors
To perform its obligations under the Athinia Terms of Service and Athinia DPA (or the alternative written agreement between Customer and Athinia, if applicable), Athinia Technologies LLC and its Affiliates may use third-party data processors (“Third-Party Subprocessors”) and Athinia Affiliates to process Customer Personal Data. Capitalized terms used but not defined here shall have the meanings provided in the Agreement.
The following third parties are hereby specifically authorized by Customer to carry out work as Third-Party Subprocessors for purposes of the Agreement.
|
Authorized Third-Party Subprocessors |
||||
|
Subprocessor |
Purpose |
Registered Address |
Location |
Transfer Mechanism |
|
Amazon Web Services, Inc. |
Cloud hosting and infrastructure, alerting and encrypted notification services and AI services. |
410 Terry Avenue North, Seattle, WA 98109 USA |
As selected by Customer in the Order Form or, as applicable, other parts of the Agreement |
Standard Contractual Clauses |
|
Microsoft Corporation |
Cloud hosting and infrastructure and AI services (Microsoft Azure). |
One Microsoft Way Redmond, WA 98052 USA |
The location for the purpose of providing the cloud hosting service is as selected by Customer in the Order Form or, as applicable, other parts of the Agreement. The location for the purpose of providing the AI service is East US, South Central US, West Europe and other Azure regions as they become available. |
Standard Contractual Clauses |
|
Google LLC |
Cloud hosting and infrastructure (Google Cloud Platform) and AI services. |
1600 Amphitheatre Parkway Mountain View, CA 94043 USA |
The location for the purpose of providing the cloud hosting service is as selected by Customer in the Order Form or, as applicable, other parts of the Agreement. The location for the purpose of providing the AI services are all regions available for features of Generative AI on Google Vertex AI and other regions as they become available. |
Standard Contractual Clauses |
|
Proofpoint, Inc. |
Alerting and encrypted notification service. |
892 Ross Drive, Sunnyvale, CA 94089 USA |
As selected by Customer in the Order Form or, as applicable, other parts of the Agreement |
Standard Contractual Clauses |
|
Microsoft Corporation |
User authentication as an identity provider (where selected as chosen identity provider by Customer). |
One Microsoft Way Redmond, WA 98052, USA
|
United States |
Standard Contractual Clauses |
|
OpenAI LLC |
AI services. |
3180 18th Street, San Francisco, CA 94110 USA |
The location for the purpose of providing the AI service can be the United States and other regions as they become available. |
Standard Contractual Clauses |
|
X.AI LLC |
AI services. |
1450 Page Mill Rd. Palo Alto, CA 94034 USA |
The location for the purpose of providing the AI service can be the United States and other regions as they become available. |
Standard Contractual Clauses |
|
Oracle America, Inc. |
Cloud hosting and infrastructure. |
500 Oracle Parkway, Redwood Shores, CA 94065 USA |
As selected by Customer in the Order Form or, as applicable, other parts of the Agreement. |
Standard Contractual Clauses |
|
Anthropic, PBC |
AI Services |
548 Market Street, PMB 90375, San Francisco, CA 94104-5401
|
The location for the purpose of providing the AI service can be the United States and other regions as they become available. |
Standard Contractual Clauses |
PART II – Athinia Affiliates
Provided that an adequate level of data protection consistent with the Data Protection Laws and this Agreement is ensured by Athinia, Customer specifically authorizes Athinia Affiliates as listed below to act as Athinia’s Subprocessor(s) including by Processing Customer Personal Data for the purposes of the Agreement for the delivery of Service and/or Professional Services to Customer. Where required, Athinia and its respective Affiliate have entered into the Standard Contractual Clauses. Such Processing, where applicable, shall occur under the control and direction of Athinia and shall occur on systems managed or otherwise controlled by Athinia.
|
Athinia Affiliates |
||||
|
Subprocessor |
Purpose |
Registered Address |
Location |
Transfer Mechanism |
|
Palantir Technologies Inc. |
Providing the Service and Professional Services to Customer |
1200 17th Street, Floor 15, Denver, CO 80202 USA |
United States |
Standard Contractual Clauses |
|
EMD Digital Technologies Inc. |
Providing the Service and Professional Services to Customer |
400 Summit Dr. Burlington, MA 01803 USA |
United States |
Standard Contractual Clauses |
EXHIBIT B
Subject Matter and Details of Customer Personal Data Processing
Categories of Data Subject Whose Personal Data May be Subject to Processing
Data Subjects include the individuals about whom Personal Data is provided to Athinia via the Service (as applicable) or otherwise by (or at the direction of) Customer or Customer’s Users.
Categories of Customer Personal Data
Customer Personal Data provided to Athinia for Processing (including via the Service) by or at the direction of Customer or Customer’s Users.
Subject Matter of Processing
Athinia’s provision of the Service and Professional Services and performance of its obligations under the Agreement.
Nature and Purpose of Processing
Athinia will Process Customer Personal Data in accordance with the terms of this DPA for the purpose of providing the Service and Professional Services to Customer, or as otherwise compelled by applicable law.
Duration of Processing
Continuous for duration of the Agreement, plus the period from the expiry of the Agreement until the return or deletion of all Customer Personal Data by Athinia in accordance with the Agreement (including this DPA), Customer Instructions and applicable law.
Subject matter, nature and duration of processing by sub-processors
As set out in Exhibit A. The duration of sub-processing is as set out immediately above.
EXHIBIT C
Additions to the Standard Contractual Clauses
Each Party agrees to abide by and transfer Customer Personal Data subject to European Data Protection Law solely in accordance with the Standard Contractual Clauses, which are incorporated into this DPA. Each Party is deemed to have executed the Standard Contractual Clauses by entering into this DPA.
The Module 2 (Controller to Processor) terms, as provided below in Annex 1 to Exhibit C, shall apply to the extent Customer is a Controller of Customer Personal Data. The Module 3 (Processor to Processor) terms, as provided below in Annex 2 to Exhibit C, shall apply to the extent Customer is a Processor (or subprocessor) of Customer Personal Data. For both Module 2 and Module 3 of the Standard Contractual Clauses, the election of specific terms and/or addition of required information shall apply as follows:
ANNEX 1 TO EXHIBIT C
STANDARD CONTRACTUAL CLAUSES
Module 2: Controller to Processor
SECTION I
Clause 1
Purpose and scope
(a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) ([1]) for the transfer of data to a third country.
(b) The Parties:
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:
(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
Docking clause
[intentionally left blank]
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 II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679.
8.4 Accuracy
If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data.
8.5 Duration of processing and erasure or return of data
Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).
8.6 Security of processing
(a) The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
(b) The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
(c) In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
(d) The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
8.7 Sensitive data
Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.
8.8 Onward transfers
The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union ([2]) (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
(a) OPTION 2 GENERAL WRITTEN AUTHORISATION: The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 14 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. ([3]) 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 II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
(c) In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
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:
(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) [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.
[Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.
[Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.
(b) The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES
Clause 14
Local laws and practices affecting compliance with the Clauses
(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:
(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:
(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:
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 one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of Ireland.
Clause 18
Choice of forum and jurisdiction
(a) Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
(b) The Parties agree that those shall be the courts of 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.
APPENDIX
ANNEX I
A. LIST OF PARTIES
Data exporter(s):
Name: Name of Customer as stated in the Agreement.
Address: Address of Customer as stated in the Agreement.
Contact person’s name, position and contact details: Point of contact for Customer as stated in the Agreement.
Activities relevant to the data transferred under these Clauses: Customer under the Agreement
Role (controller/processor): Controller
Data importer(s):
Name: Name of Athinia as stated in the Agreement.
Address: Address of Athinia as stated in the Agreement.
Contact person’s name, position and contact details: Data Protection Officer, privacy@syntropy.com
Activities relevant to the data transferred under these Clauses: Supplier under the Agreement
Role (controller/processor): Processor
B. DESCRIPTION OF TRANSFER
Categories of data subjects whose personal data is transferred
As described under "Categories of Data Subject Whose Personal Data May be Subject to Processing" in Exhibit B.
Categories of personal data transferred
As described under "Categories of Customer Personal Data" in Exhibit B.
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.
Personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, biometric data, health data, data concerning a natural person's sex life or sexual orientation to the extent that Customer Personal Data includes such sensitive data and is provided to Athinia for Processing (including via the Service) by or at the direction of Customer or Customer’s Users. In that case Customer shall clearly identify such sensitive data to Athinia in writing before providing such sensitive data. The applied safeguards and restrictions are described in Annex II.
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
As described under "Nature and Purpose of Processing" in Exhibit B.
Purpose(s) of the data transfer and further processing
As described under "Nature and Purpose of Processing" in Exhibit B.
The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period
As described under "Duration of Processing" in Exhibit B.
For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing
As described under "Subject matter, nature and duration of processing by sub-processors" in Exhibit B.
C. COMPETENT SUPERVISORY AUTHORITY
Identify the competent supervisory authority/ies in accordance with Clause 13
The supervisory authority as determined in accordance with Clause 13 and as further specified at https://edpb.europa.eu/about-edpb/about-edpb/members_en (as updated from time to time).
ANNEX II
TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA
Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons.
The security features and functionalities available to Customer described in clause 4.1 of the DPA, as further documented in the Security Documentation, and the technical and organisational measures described in clause 4.3(c) of the DPA.
For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter.
The controls available to Customer described in clause 4.1 of the DPA, as further documented in the Security Documentation.
ANNEX 2 TO EXHIBIT C
STANDARD CONTRACTUAL CLAUSES
Module 3: Processor to Processor
SECTION I
Clause 1
Purpose and scope
(a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) ([5]) for the transfer of personal data to a third country.
(b) The Parties:
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:
(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
Docking clause
[Intentionally left blank]
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 exporter has informed the data importer that it acts as processor under the instructions of its controller(s), which the data exporter shall make available to the data importer prior to processing.
(b) The data importer shall process the personal data only on documented instructions from the controller, as communicated to the data importer by the data exporter, and any additional documented instructions from the data exporter. Such additional instructions shall not conflict with the instructions from the controller. The controller or data exporter may give further documented instructions regarding the data processing throughout the duration of the contract.
(c) The data importer shall immediately inform the data exporter if it is unable to follow those instructions. Where the data importer is unable to follow the instructions from the controller, the data exporter shall immediately notify the controller.
(d) The data exporter warrants that it has imposed the same data protection obligations on the data importer as set out in the contract or other legal act under Union or Member State law between the controller and the data exporter ().
8.2 Purpose limitation
The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B., unless on further instructions from the controller, as communicated to the data importer by the data exporter, or from the data exporter.
8.3 Transparency
On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including personal data, the data exporter may redact part of the text of the Appendix prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information.
8.4 Accuracy
If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to rectify or erase the data.
8.5 Duration of processing and erasure or return of data
Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the controller and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).
8.6 Security of processing
(a) The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, they shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subject. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter or the controller. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
(b) The data importer shall grant access to the data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
(c) In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify, without undue delay, the data exporter and, where appropriate and feasible, the controller after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the data breach, including measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
(d) The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify its controller so that the latter may in turn notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
8.7 Sensitive data
Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards set out in Annex I.B.
8.8 Onward transfers
The data importer shall only disclose the personal data to a third party on documented instructions from the controller, as communicated to the data importer by the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union ([6]) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:
(i) the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
(ii) the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 of Regulation (EU) 2016/679;
(iii) the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
(iv) the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.
Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.
8.9 Documentation and compliance
(a) The data importer shall promptly and adequately deal with enquiries from the data exporter or the controller that relate to the processing under these Clauses.
(b) The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the controller.
(c) The data importer shall make all information necessary to demonstrate compliance with the obligations set out in these Clauses available to the data exporter, which shall provide it to the controller.
(d) The data importer shall allow for and contribute to audits by the data exporter of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. The same shall apply where the data exporter requests an audit on instructions of the controller. In deciding on an audit, the data exporter may take into account relevant certifications held by the data importer.
(e) Where the audit is carried out on the instructions of the controller, the data exporter shall make the results available to the controller.
(f) The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
(g) The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
Clause 9
Use of sub-processors
(a) OPTION 2 GENERAL WRITTEN AUTHORISATION: The data importer has the controller’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the controller in writing of any intended changes to that list through the addition or replacement of sub-processors at least 14 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the controller with the information necessary to enable the controller to exercise its right to object. The data importer shall inform the data exporter of the engagement of the sub-processor(s).
(b) Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the controller), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects. ([7]) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
(c) The data importer shall provide, at the data exporter’s or controller’s request, a copy of such a sub-processor agreement and any subsequent amendments. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
(d) The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
(e) The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
Clause 10
Data subject rights
(a) The data importer shall promptly notify the data exporter and, where appropriate, the controller of any request it has received from a data subject, without responding to that request unless it has been authorised to do so by the controller.
(b) The data importer shall assist, where appropriate in cooperation with the data exporter, the controller in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
(c) In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the controller, as communicated by the data exporter.
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:
(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) [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.
[Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.
[Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.
(b) The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES
Clause 14
Local laws and practices affecting compliance with the Clauses
(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:
(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). The data exporter shall forward the notification to the controller.
(f) Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation, if appropriate in consultation with the controller. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the controller or the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
Clause 15
Obligations of the data importer in case of access by public authorities
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:
The data exporter shall forward the notification to the controller.
(b) If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
(c) Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.). The data exporter shall forward the information to the controller.
(d) The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
(e) Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
15.2 Review of legality and data minimization
(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. The data exporter shall make the assessment available to the controller.
(c) The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
SECTION IV – FINAL PROVISIONS
Clause 16
Non-compliance with the Clauses and termination
(a) The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
(b) In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
(c) The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
In these cases, it shall inform the competent supervisory authority and the controller of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.
(d) 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 one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of Ireland.
Clause 18
Choice of forum and jurisdiction
(a) Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
(b) The Parties agree that those shall be the courts of 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.
APPENDIX
ANNEX I
A. LIST OF PARTIES
Data exporter(s):
Name: Name of Customer as stated in the Agreement.
Address: Address of Customer as stated in the Agreement.
Contact person’s name, position and contact details: Point of contact for Customer as stated in the Agreement.
Activities relevant to the data transferred under these Clauses: Customer under the Agreement
Role (controller/processor): Processor
Data importer(s):
Name: Name of Athinia as stated in the Agreement.
Address: Address of Athinia as stated in the Agreement.
Contact person’s name, position and contact details: Data Protection Officer, dpo@athinia.com
Activities relevant to the data transferred under these Clauses: Supplier under the Agreement
Role (controller/processor): Processor
B. DESCRIPTION OF TRANSFER
Categories of data subjects whose personal data is transferred
As described under "Categories of Data Subject Whose Personal Data May be Subject to Processing" in Exhibit B.
Categories of personal data transferred
As described under "Categories of Customer Personal Data" in Exhibit B.
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.
Personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, biometric data, health data, data concerning a natural person's sex life or sexual orientation to the extent that Customer Personal Data includes such sensitive data and is provided to Athinia for Processing (including via the Service) by or at the direction of Customer or Customer’s Users. In that case, Customer shall clearly identify such sensitive data to Athinia in writing before providing such sensitive data. The applied safeguards and restrictions are described in Annex II.
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
As described under "Nature and Purpose of Processing" in Exhibit B.
Purpose(s) of the data transfer and further processing
As described under "Nature and Purpose of Processing" in Exhibit B.
The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period
As described under "Duration of Processing" in Exhibit B.
For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing
As described under "Subject matter, nature and duration of processing by sub-processors" in Exhibit B.
C. COMPETENT SUPERVISORY AUTHORITY
Identify the competent supervisory authority/ies in accordance with Clause 13
The supervisory authority as determined in accordance with Clause 13 and as further specified at https://edpb.europa.eu/about-edpb/about-edpb/members_en (as updated from time to time).
ANNEX II
TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA
Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons.
The security features and functionalities available to Customer described in clause 4.1 of the DPA, as further documented in the Security Documentation, and the technical and organisational measures described in clause 4.3(c) of the DPA.
For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter
The controls available to Customer described in clause 4.1 of the DPA, as further documented in the Security Documentation.
FOOTNOTES
[1] Where the data exporter is a processor subject to Regulation (EU) 2016/679 acting on behalf of a Union institution or body as controller, reliance on these Clauses when engaging another processor (sub-processing) not subject to Regulation (EU) 2016/679 also ensures compliance with Article 29(4) of Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No 1247/2002/EC (OJ L 295, 21.11.2018, p. 39), to the extent these Clauses and the data protection obligations as set out in the contract or other legal act between the controller and the processor pursuant to Article 29(3) of Regulation (EU) 2018/1725 are aligned. This will in particular be the case where the controller and processor rely on the standard contractual clauses included in Decision 2021/915.
[2] The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.
[3] This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.
[4] As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.
[5] Where the data exporter is a processor subject to Regulation (EU) 2016/679 acting on behalf of a Union institution or body as controller, reliance on these Clauses when engaging another processor (sub-processing) not subject to Regulation (EU) 2016/679 also ensures compliance with Article 29(4) of Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No 1247/2002/EC (OJ L 295, 21.11.2018, p. 39), to the extent these Clauses and the data protection obligations as set out in the contract or other legal act between the controller and the processor pursuant to Article 29(3) of Regulation (EU) 2018/1725 are aligned. This will in particular be the case where the controller and processor rely on the standard contractual clauses included in Decision 2021/915.
[6] The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.
[7] This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.
[8] As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.
| Authorized Third-Party Subprocessors | ||||
| Subprocessor | Purpose | Registered Address | Location | Transfer Mechanism |
| Amazon Web Services, Inc. | Cloud hosting and infrastructure, alerting and encrypted notification services and AI services | 410 Terry Avenue North, Seattle, WA 98109, USA | As selected by Customer in the Order Form or, as applicable, other parts of the Agreement | Standard Contractual Clauses |
| Microsoft Corporation | Cloud hosting and infrastructure and AI services (Microsoft Azure) | One Microsoft Way Redmond, WA 98052, USA |
The location for the purpose of providing the cloud hosting service is as selected by Customer in the Order Form or, as applicable, other parts of the Agreement. The location for the purpose of providing the AI service is East US, South Central US, West Europe and other Azure regions as they become available. | Standard Contractual Clauses |
| Google LLC | Cloud hosting and infrastructure (Google Cloud Platform) and AI services | 1600 Amphitheatre Parkway Mountain View, CA 94043, USA |
As selected by Customer in the Order Form or, as applicable, other parts of the Agreement | Standard Contractual Clauses |
| Proofpoint, Inc. | Alerting and encrypted notification service | 892 Ross Drive, Sunnyvale, CA 94089, USA | As selected by Customer in the Order Form or, as applicable, other parts of the Agreement | Standard Contractual Clauses |
| Microsoft Corporation | User authentication as an identity provider (where selected as chosen identity provider by Customer). | One Microsoft Way Redmond, WA 98052, USA |
United States | Standard Contractual Clauses |
| Athinia Affiliates | ||||
| Subprocessor | Purpose | Registered Address | Location | Transfer Mechanism |
| Palantir Technologies Inc. | Providing the Service and Professional Services to Customer | 1200 17th Street, Floor 15, Denver, CO 80202, USA | United States | Standard Contractual Clauses |
| EMD Digital Technologies Inc. | Providing the Service and Professional Services to Customer | 400 Summit Dr. Burlington, 01803, MA USA | United States | Standard Contractual Clauses |
| Authorized Third-Party Subprocessors | ||||
| Subprocessor | Purpose | Registered Address | Location | Transfer Mechanism |
| Amazon Web Services, Inc. | Cloud hosting and infrastructure | 410 Terry Avenue North, Seattle, WA 98109, USA | As selected by Customer in the Order Form or, as applicable, other parts of the Agreement | Standard Contractual Clauses |
| Microsoft Corporation | Cloud hosting and infrastructure (Microsoft Azure) and | One Microsoft Way Redmond, WA 98052, USA |
As selected by Customer in the Order Form or, as applicable, other parts of the Agreement | Standard Contractual Clauses |
| Google LLC | Cloud hosting and infrastructure (Google Cloud Platform) | 1600 Amphitheatre Parkway Mountain View, CA 94043, USA |
As selected by Customer in the Order Form or, as applicable, other parts of the Agreement | Standard Contractual Clauses |
| Proofpoint, Inc. | Alerting and encrypted notification service | 892 Ross Drive, Sunnyvale, CA 94089, USA | As selected by Customer in the Order Form or, as applicable, other parts of the Agreement | Standard Contractual Clauses |
| Microsoft Corporation | User authentication as an identity provider (where selected as chosen identity provider by Customer). | One Microsoft Way Redmond, WA 98052, USA |
United States | Standard Contractual Clauses |
| Athinia Affiliates | ||||
| Subprocessor | Purpose | Registered Address | Location | Transfer Mechanism |
| Palantir Technologies Inc. | Providing the Service and Professional Services to Customer | 1555 Blake Street Suite 250 Denver, CO 80202, USA | United States | Standard Contractual Clauses |
| EMD Digital Technologies Inc. | Providing the Service and Professional Services to Customer | 400 Summit Dr. Burlington, 01803, MA USA | United States | Standard Contractual Clauses |