Skip to main content

DATA PROCESSING ADDENDUM

This Data Processing Addendum (“DPA”) is incorporated by reference into the Atera Terms of Use (available at https://www.atera.com/terms-of-use/) and any other applicable Atera terms or agreement governing the use of the Services (collectively, the “Agreement”). Both parties shall be referred to as the “Parties” and each, a “Party”.

In order to provide the services provided under the Agreement (“Services”), Atera Networks Ltd. (together with its affiliated companies and subsidiaries worldwide) (“Atera”, “us”, “we”, “our” or “Processor”) may be required to Process Personal Data (as defined below).

To the extent Personal Data is Processed by Atera on Client’s behalf, Client acknowledges and agrees to abide to this DPA and further agrees that Atera will Process Personal Data as necessary to provide the Services and as further detailed herein. By using the Services, Client instructs Atera to process such Personal Data on its behalf pursuant to this DPA and you represent and warrant that you have full authority to bind the Client to this DPA. If you cannot, or do not agree to, comply with and be bound by this DPA, or do not have authority to bind the Client, please do not provide Personal Data to us.

  1. If any provision of this DPA is deemed by a court of competent jurisdiction to be invalid, unlawful, void, or for any reason unenforceable, then such provision shall be deemed severable and will not affect the validity and enforceability of the remaining provisions.
  2. Any questions regarding this DPA should be addressed to [email protected]. Atera will attempt to resolve any complaints regarding the use of Personal Data in accordance with this DPA and the Agreement.
  3. This DPA was written in English and may be translated into other languages for your convenience. If a translated (non-English) version of this DPA conflicts in any way with its English version, the provisions of the English version shall prevail.

SCHEDULE 1 – DETAILS OF THE PROCESSING

Subject Matter

Atera will Process Personal Data as necessary to provide the Services, perform and enforce the Agreement (or any other agreement between the parties), and as further instructed by Client in its use of the Services.

Nature and Purpose of Processing

Collection and Processing of Personal Data for providing the Service(s) to Client; for Atera to comply with documented reasonable instructions provided by Client where such instructions are consistent with the terms of the Agreement and/or pursuant to Client’s use of the Services (e.g., integrations between the Services and any services provided by third parties, as configured by or on behalf of Client to facilitate the sharing of Personal Data between the Services and such third party services); Complying with applicable laws and regulations; for performing the Agreement, this DPA and/or other contracts executed by the parties, and for all tasks related to any of the above.

Duration of Processing

Subject to any Section of the DPA and/or the Agreement dealing with the duration of the Processing and the consequences of the expiration or termination thereof, Atera will Process Personal Data for the duration of the Agreement, unless otherwise agreed upon in writing.

Types of Data

Client may submit Personal Data to the Services, the extent and nature of which is determined and controlled by Client in its sole discretion. This data may include: Client’s End-Users’ email addresses, credentials, physical addresses, phone numbers, roles, geolocation, photos, internet protocol (IP) addresses, hardware and software details, Personal Data in files or communications that Client transmits or receives through the Service (where applicable), operating system (OS), browser type, webpage titles (available on Robin only), in-Service activity, Windows or other operating systems’ logs and events, and online identifiers.

Categories of Data Subjects

  • Client’s Admins, Permitted Users and End-Users.
  • Any other individual whose Personal Data may be Processed through the Services, depending on Client’s use of the Services and the types of Personal Data Processed.

SCHEDULE 2 – TRANS BORDER TRANSFERS

PART 1 – EEA Trans-Border Transfers

  1. The parties agree that the terms of the EU SCCs are hereby incorporated by reference and shall apply to an EEA Transfer as set out in this Part 1.
  2. Module Two (Controller to Processor) of the EU SCCs shall apply where the EEA Transfer is effectuated by Client as the data controller of the Personal Data and Atera is the data processor of the Personal Data. Module Three (Processor to Processor) of the EU SCCs shall apply where the EEA Transfer is effectuated by Client as the data processor of the Personal Data and Atera is a sub-processor of the Personal Data. Module Four (Processor to Controller) of the EU SCCs shall apply where the EEA Transfer is effectuated by Atera as the data processor of the Personal Data and Client is the data controller of the Personal Data.
  3. Clause 7 of the EU SCCs (Docking Clause) shall not apply.
  4. Option 2: GENERAL WRITTEN AUTHORISATION in Clause 9 of the EU SCCs shall apply, and the time period for prior notice of Sub-processor changes shall be as set forth in Section 6 of the DPA.
  5. In Clause 11 of the EU SCCs, the optional language will not apply.
  6. In Clause 17 of the EU SCCs, Option 1 shall apply, and the Parties agree that the EU SCCs shall be governed by the laws of the Republic of Ireland. 
  7. In Clause 18(b) of the EU SCCs, disputes will be resolved before the courts of the Republic of Ireland.
  8. Annex I.A of the EU SCCs shall be completed as follows:

Module 2: 

Name: Client. Contact details: as detailed in the Agreement. Activities relevant to the data transferred: as detailed in Schedule 1 to this DPA. Signature and date: by entering into the Agreement and DPA, Data Exporter is deemed to have signed this Annex I to the EU SCCs. Role: data controller.

Module 3:

Name: Client. Contact details: as detailed in the Agreement. Activities relevant to the data transferred: as detailed in Schedule 1 to this DPA. Signature and date: by entering into the Agreement and DPA, Data Exporter is deemed to have signed this Annex I to the EU SCCs. Role: data processor.

Module 4:

Name: Atera. Contact details: as detailed in the Agreement. Activities relevant to the data transferred: as detailed in Schedule 1 to this DPA. Signature and date: by entering into the Agreement and DPA, Data Exporter is deemed to have signed this Annex I to the EU SCCs. Role: data processor.

Name: Client. Contact details: as detailed in the Agreement. Activities


Name: Atera. Contact details: as detailed in the Agreement. Activities relevant to the data transferred: as detailed in Schedule 1 to this DPA. Signature and date: by entering into the Agreement and DPA, Data Importer is deemed to have signed this Annex I to the EU SCCs. Role: data processor.


Name: Atera. Contact details: as detailed in the Agreement. Activities relevant to the data transferred: as detailed in Schedule 1 to this DPA. Signature and date: by entering into the Agreement and DPA, Data Importer is deemed to have signed this Annex I to the EU SCCs. Role: sub-processor.


relevant to the data transferred: as detailed in Schedule 1 to this DPA. relevant to the data transferred: as detailed in Schedule 1 to this DPA. Signature and date: by entering into the Agreement and DPA, Data Importer is deemed to have signed this Annex I to the EU SCCs. Role: data controller.

  1. Annex I.B of the EU SCCs shall be completed as follows: The categories of data subjects whose Personal Data is transferred, the categories of Personal Data transferred, the frequency of the transfer, the nature of the Processing, the purposes of the data transfer and further Processing, and the period for which the Personal Data will be retained are described in Schedule 1 to this DPA. In relation to transfers to Sub-processors, the subject matter, nature, and duration of the processing is set forth at the link detailed in Section 6 of this DPA.
  2. Annex I.C of the EU SCCs shall be completed as follows: The competent supervisory authority in accordance with Clause 13 is the supervisory authority in the Member State stipulated in Section 6 of this Part 1‎.
  3. The Security Documentation referred to in the DPA serves as Annex II of the EU SCCs.
  4. To the extent there is any conflict between the EU SCCs and any other terms in this DPA or the Agreement, the provisions of the EU SCCs will prevail.

PART 2 – UK Trans-Border Transfers

  1. Part 1 (tables) of the UK Addendum shall be completed as follows: The Parties agree that the UK Addendum is hereby incorporated by reference and shall apply to UK Transfers as set forth in this Part 2, together with the EU SCCs as set forth in Part 1 above.

Table 1: Parties: As stipulated in Section 8 of Part 1 of this Schedule 2.

Table 2: Selected SCCs, Modules and Selected Clauses: As stipulated in Part 1 of this Schedule 2.

Table 3: Appendix Information: Annex 1A: As stipulated in Section 8 of Part 1 of this Schedule 2; Annex 1B: As stipulated in Section 9 of Part 1 of this Schedule 2; Annex II: As stipulated in Section 11 of Part 1 of this Schedule 2; Annex III: As set forth at the link detailed in Section 6 of this DPA.

Table 4: Ending this Addendum when the Approved Addendum Changes: Neither Party may end this UK Addendum in the manner set out in Section 19 of the Mandatory Clauses of the UK Addendum.

  1. The Alternative Part 2 (Mandatory Clauses) of the UK Addendum shall apply, as follows:
    Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section ‎‎18 of those Mandatory Clauses.

PART 3 – Swiss Trans-Border Transfers

  1. The Parties agree that the EU SCCs as detailed in Part 1 of this Schedule 2, as adjusted below, shall apply where the FADP applies to Swiss Transfers:
  2. References to the Standard Contractual Clauses mean the EU SCCs as amended by this Part 3;
  3. The Swiss Federal Data Protection and Information Commissioner shall be the sole Supervisory Authority for Swiss Transfers exclusively subject to the FADP;
  4. The terms “General Data Protection Regulation” or “Regulation (EU) 2016/679” as utilized in the EU SCCs shall be interpreted to include the FADP with respect to Swiss Transfers;
  5. References to Regulation (EU) 2018/1725 are removed;
  6. Swiss Transfers subject to both the FADP and the GDPR, shall be dealt with by the Swiss Federal Data Protection and Information Commissioner insofar as the Swiss Transfer is governed by the FADP, and by the EU Supervisory Authority named in Part 1 of this Schedule 2, insofar as the Swiss Transfer is governed by the GDPR;
  7. References to the “Union”, “EU” and “EU Member State” shall not be interpreted in such a way as to exclude Data Subjects in Switzerland from the possibility of exercising their rights in their place of habitual residence (Switzerland) in accordance with Clause 18(c) of the EU SCCs; 
  8. Where Swiss Transfers are exclusively subject to the FADP, all references to the GDPR in the EU SCCs are to be understood to be references to the FADP;
  9. Where Swiss Transfers are subject to both the FDPA and the GDPR, all references to the GDPR in the EU SCCs are to be understood to be references to the FDPA insofar as the Swiss Transfer is subject to the FADP.

PART 4 – Additional Safeguards 

  1. In the event of an EEA Transfer, a UK Transfer or a Swiss Transfer, the Parties agree to supplement these with the following safeguards and representations, where appropriate: 
  1. The Processor shall have in place and maintain in accordance with good industry practice measures to protect the Personal Data from interception (including in transit from the Controller to the Processor and between different systems and services). This includes having in place and maintaining network protection intended to deny attackers the ability to intercept data and encryption of Personal Data whilst in transit and at rest intended to deny attackers the ability to read data.
  2. The Processor will make commercially reasonable efforts to resist, subject to applicable laws, any request for bulk surveillance relating to the Personal Data protected under GDPR or the UK GDPR, including under section 702 of the United States Foreign Intelligence Surveillance Act (“FISA”); 
  3. If the Processor becomes aware that any government authority (including law enforcement) wishes to obtain access to or a copy of some or all of the Personal Data, whether on a voluntary or a mandatory basis, then unless legally prohibited or under a mandatory legal compulsion that requires otherwise:
  1. The Processor shall inform the relevant government authority that the Processor is a processor of the Personal Data and that the Controller has not authorized the Processor to disclose the Personal Data to the government authority, and inform the relevant government authority that any and all requests or demands for access to the Personal Data should therefore be notified to or served upon the Controller in writing;
  2. The Processor will use commercially reasonable legal mechanisms to challenge any such demand for access to Personal Data that is under the Processor’s control. Notwithstanding the above, (a) the Controller acknowledges that such challenge may not always be reasonable or possible in light of the nature, scope, context and purposes of the intended government authority access, and (b) if, taking into account the nature, scope, context and purposes of the intended government authority access to Personal Data, the Processor has a reasonable and good-faith belief that urgent access is necessary to prevent an imminent risk of serious harm to any individual or entity, this subsection (c)(II) shall not apply. In such event, the Processor shall notify the Controller, as soon as possible, following the access by the government authority, and provide the Controller with relevant details of the same, unless and to the extent legally prohibited to do so.
  3. Once in every 12-month period, the Processor will inform the Controller, at the Controller’s written request, of the types of binding legal demands for Personal Data it has received and solely to the extent such demands have been received, including national security orders and directives, which shall encompass any process issued under section 702 of FISA.

SCHEDULE 3 – CCPA TERMS

  1. SCOPE, APPLICATION & INTERPRETATION
    1. This Schedule 3 shall apply and bind the Parties if and to the extent that (i) Client is a Business under the CCPA, and (ii) Atera Processes Personal Information (as defined below) that is subject to the CCPA in the course of providing the Services to Client pursuant to the Agreement. 
    2. This Schedule 3 prevails over any conflicting terms of the Agreement or the DPA but does not otherwise modify the Agreement or the DPA.
    3. This Schedule 3 shall be interpreted in favor of the Parties’ intent to comply with the CCPA, and therefore any ambiguity shall be resolved in favor of a meaning that complies and is consistent with the CCPA.
    4. Capitalized terms not specifically defined herein shall have the meanings ascribed to them in the DPA, as amended by this Schedule 3.
  2. DEFINITIONS

For the purposes of this Schedule 3:

  1. The terms “Business”, “Collects” (and “collected” and “collection”), “Consumer”, “Business Purpose”, “Sell” (and “selling”, “sale”, and “sold”), “Share” (and “shared”, or “sharing”), and “Service Provider” shall each have the same meaning as in the CCPA.
  2. Personal Information” means any information that identifies, relates to, describes, is capable of being associated with, or could reasonably be linked, directly or indirectly, to or with an identified or identifiable Consumer or household of a Consumer, which is processed by Atera solely on behalf of Client under this Schedule 3 and the Agreement.
  3. PROCESSING OF PERSONAL INFORMATION
    1. Client hereby appoints Atera as a Service Provider to Process Personal Information on behalf of Client. Client, in its use of the Services, and Client’s instructions to Atera, shall comply with the CCPA. Client represents and warrants that it has provided notice consistent with Section 1798.135 of the CCPA, and has obtained consents to the extent required under the CCPA for Atera to lawfully Collect and Process the Personal Information in pursuit of the Permitted Purposes (as defined in Section ‎3.2 below).
    2. Atera shall Process Personal Information solely for the purposes set forth in Section 2.3 of the DPA and as necessary to comply with this Schedule 3 and the CCPA. For the avoidance of doubt, such Processing shall include the pursuit of Business Purposes, including providing Client with Atera’s cloud-based IT management platform (collectively: the “Permitted Purposes“). 
    3. Sections 3-8 and 10-15 of the DPA shall apply to the Processing of Personal Information and the following terms shall be replaced as follows: “Data Protection Laws” shall mean the CCPA; “DPA” shall mean this Schedule 3; “Personal Data” shall mean “Personal Information”; “Data Subject” shall mean “Consumer”; “Controller” shall mean “Business”; “Processor” shall mean “Service Provider”; and Sub-processor shall refer to the concept of a Service Provider engaged by Atera to Process Personal Information.
    4. Atera shall Process Personal Information in accordance with the provisions of the CCPA, and in a manner that provides the same level of privacy protection to Personal Information as required by the CCPA. Atera certifies that it understands the rules, requirements, and definitions of the CCPA and this Schedule 3, and shall comply with them.
    5. Atera acknowledges and confirms that it does not receive or process any Personal Information as consideration for any services or other items that Atera provides to Client under the Agreement. Atera agrees to refrain from Selling and/or Sharing any Personal Information Processed hereunder without Client’s prior written consent, nor taking any action that would cause any transfer of Personal Information to or from Atera under the Agreement or this Schedule 3 to qualify as Selling and/or Sharing such Personal Information. Atera shall not have, derive, or exercise any rights or benefits regarding the Personal Information, and shall not retain, use, or disclose any Personal Information (i) for any purpose other than the Permitted Purposes, and/or (ii) outside of the direct business relationship between the Parties. 
    6. Atera shall not combine Personal Information with any other data if and to the extent that this would be inconsistent with the limitations on Service Providers under the CCPA. 
    7. Atera shall notify Client if Atera makes a determination that it can no longer meet its obligations under this Schedule 3 and/or the CCPA.

Last updated: December 30, 2025

This site is registered on wpml.org as a development site. Switch to a production site key to remove this banner.