FREE TRIAL
GET STARTED{$showtopbar$}Version Date: June 1, 2023
This Data Protection Agreement (“Agreement”) is incorporated by reference into the SaaS Services Agreement (“SaaS Agreement”) under which Mitsogo Inc. (“Company”) has agreed to provide Services (“Service”) to you (“Customer”). This Agreement sets out the additional terms, requirements, and conditions on which the Company will process personal data when providing Services to the Customer under the SaaS Agreement and contains mandatory clauses under the GDPR for contracts between controllers and processors.
This Agreement will be effective and replace any terms previously applicable to the processing of Personal Data, from the Effective Date (defined below).
The Company and the Customer are individually referred to as a “Party” and collectively as “Parties”.
IT IS AGREED:
IN WITNESS WHEREOF, this Agreement is entered into with effect from the Effective Date.
LIST OF SUB-PROCESSORS: https://www.hexnode.com/mobile-device-management/help/list-of-hexnode-subprocessors/
have agreed to these standard contractual clauses (hereinafter: “Clauses”).
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.
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.
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.
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.
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.
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.
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).
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.
The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (in the same country as the data importer or in another third country, hereinafter “onward transfer”) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:
Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.
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.
The data importer agrees that data subjects may also lodge a complaint with an independent dispute resolution body at no cost to the data subject. It shall inform the data subjects, in the manner set out in paragraph (a), of such redress mechanism and that they are not required to use it, or follow a particular sequence in seeking redress.
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.
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.
These Clauses shall be governed by the law of the EU Member State in which the data exporter is established. Where such law does not allow for third-party beneficiary rights, they shall be governed by the law of another EU Member State that does allow for third-party beneficiary rights. The Parties agree that this shall be the law of Austria.
APPENDIX
ANNEX Ⅰ
Name:
Address:
Contact person’s name, position and contact details:
Activities relevant to the data transferred under these Clauses:
Signature and date:
Role (controller/processor): Controller
Name: Mitsogo, Inc.
Address: 111 Pine St #1225, San Francisco, CA 94111, United States of America
Contact person’s name, position and contact details: Rachana Vijayan, CMO & Privacy Officer Email- legal@hexnode.com
Activities relevant to the data transferred under these Clauses: Provision of the Hexnode UEM
Signature and date:
Role (controller/processor): Processor
Mitsogo, Inc. will process persona data related to the Customer and Personal Data related to Customer’s users.
Device hardware and software details, location data, network information, user details, communication details, Customer’s billing details and any other data provided by Customer in course of using Hexnode.
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.
N/A
The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis).
Continuous Transfer
The Personal Data processed will be subject to the basic processing activities required for the provision of the Hexnode UEM to the Customer. These activities primarily include the gathering of device-related information, which is made accessible to the Customer through an easy-to-understand and manageable interface, empowering the Customer to supervise their enterprise device usage effectively. Hexnode does not perform any active monitoring or analysis of this data; the data processing is carried out solely to support the Customer's own use and management.
Personal Data will be processed for purposes of providing Hexnode UEM as set out in the SaaS Agreement, as further instructed by Customer in its use of Hexnode UEM, and otherwise agreed to in the Hexnode Terms of Use, Privacy Policy and any applicable order form.
The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period.
Data transferred will be stored for a period of 3 months from the date on which the Customer terminates its Hexnode UEM subscription.
For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing
Identify the competent supervisory authority/ies in accordance with Clause 13
-
ANNEX Ⅱ
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.
Hexnode exercises a set of layered security services and cryptographic framework that is in accordance with industry standard. Hexnode’s data security architecture is designed to implement preventative, detective, and remediation policies ensuring robust architectural security.
Mitsogo Inc. (“Our”, “us”) provides a multi-tenant SaaS solution where the customer data is logically segmented. Dedicated sub-domains are assigned per tenant. Each user has a unique ID and all the data and objects specific to the user are stored in it. Our application log consists of log details, IP details and security related administrative and configuration settings. Individual customer data can be recovered, changed, and removed upon request. We require that all Customers warrant that any data collected by Hexnode UEM is in accordance with local law related to monitoring of employees and other personnel.
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:
ANNEX III
LIST OF SUB-PROCESSORS: https://www.hexnode.com/mobile-device-management/help/list-of-hexnode-subprocessors/
PART 2
This Addendum has been issued by the Information Commissioner for Parties making Restricted Transfers. The Information Commissioner considers that it provides Appropriate Safeguards for Restricted Transfers when it is entered into as a legally binding contract.
DATE: Last date of signature of the EU SCCs to which this Addendum is appended and incorporated into the above DPA.
The Parties | Exporter (who sends the Restricted Transfer) | Importer (who receives the Restricted Transfer) |
---|---|---|
Parties' details | Full legal name: See Annex I.A of EU SCCs above | Full legal name: Mitsogo Inc |
Trading name (if different): See Annex I.A of EU SCCs above | Trading name (if different): dba Hexnode | |
Main address (if a company registered address): See Annex I.A of EU SCCs above | Main address (if a company registered address): 111 Pine St. 1225, San Francisco, CA 94111 | |
Official registration number (if any) (company number or similar identifier): See Annex I.A of EU SCCs above | Official registration number (if any) (company number or similar identifier): Delaware Corporate file number- 5983194 | |
Key contacts | Full name (optional): See Annex I.A of EU SCCs above | Full name (optional): Rachana Vijayan |
Job title: See Annex I.A of EU SCCs above | Job title: CMO, Privacy Officer | |
Contact details including email: See Annex I.A of EU SCCs above | Contact details including email: legal@hexnode.com 415-676-7575 | |
Signature (if required for the purposes of Section 2) |
Addendum EU SCCs | The Approved EU SCCs, which this Addendum is appended to, detailed below, including the Appendix Information. | |||||
Module | Module in operation | Clause 7 (Docking Clause) | Clause 11 (Option) | Clause 9a (Prior Authorisation or General Authorisation) | Clause 9a (Time period) | Is personal data received from the Importer combined with personal data collected by the Exporter? |
1 | - | - | - | |||
2 | X | X | X | General | 14 Days | - |
3 | - | |||||
4 | - | - |
"Appendix Information" means the information which must be provided for the selected modules as set out in the Appendix of the Approved EU SCCs (other than the Parties), and which for this Addendum is set out in:
Annex 1A: List of Parties: As set out in Approved EU SCCs to which this Addendum is appended |
Annex 1B: Description of Transfer: As set out in Approved EU SCCs to which this Addendum is appended |
Annex II: Technical and organisational measures including technical and organisational measures to ensure the security of the data: As set out in Approved EU SCCs to which this Addendum is appended |
Annex III: List of Sub processors (Modules 2 and 3 only): As set out in Approved EU SCCs to which this Addendum is appended |
Ending this Addendum when the Approved Addendum changes | Which Parties may end this Addendum as set out in Section 19:
Importer
Exporter
Neither Party
|
Entering into this Addendum
Although Annex 1A and Clause 7 of the Approved EU SCCs require signature by the Parties, for the purpose of making Restricted Transfers, the Parties may enter into this Addendum in any way that makes them legally binding on the Parties and allows data subjects to enforce their rights as set out in this Addendum. Entering into this Addendum will have the same effect as signing the Approved EU SCCs and any part of the Approved EU SCCs.
Interpretation of this Addendum
Where this Addendum uses terms that are defined in the Approved EU SCCs, those terms shall have the same meaning as in the Approved EU SCCs. In addition, the following terms have the following meanings:
Addendum: This International Data Transfer Addendum which is made up of this Addendum incorporating the Addendum EU SCCs.
Addendum EU SCCS: The version(s) of the Approved EU SCCs which this Addendum is appended to, as set out in Table 2, including the Appendix Information.
Appendix Information: As set out in Table 3.
Appropriate Safeguards: The standard of protection over the personal data and of data subjects' rights, which is required by UK Data Protection Laws when you are making a Restricted Transfer relying on standard data protection clauses under Article 46(2)(d) of the UK GDPR.
Approved Addendum: The template Addendum issued by the ICO and laid before Parliament in accordance with section 119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18.
Approved EU SCCs: The Standard Contractual Clauses set out in the Annex of Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
ICO: The Information Commissioner.
Restricted Transfer: A transfer which is covered by Chapter V of the UK GDPR.
UK: The United Kingdom of Great Britain and Northern Ireland.
UK Data Protection Laws: All laws relating to data protection, the processing of personal data, privacy and/or electronic communications in force from time to time in the UK, including the UK GDPR and the Data Protection Act 2018.
UK GDPR: As defined in section 3 of the Data Protection Act 2018.
Hierarchy
Incorporation of and changes to the EU SCCs
"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";
"The details of the transfers(s) and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred) are those specified in Annex I.B where UK Data Protection Laws apply to the data exporter's processing when making that transfer.";
"it is to a country benefitting from adequacy regulations pursuant to Section 17A of the UK GDPR that covers the onward transfer";
"the onward transfer is to a country benefitting from adequacy regulations pursuant to Section 17A of the UK GDPR that covers the onward transfer;"
"the Secretary of State makes regulations pursuant to Section 17A of the Data Protection Act 2018 that cover the transfer of personal data to which these clauses apply;";
"These Clauses are governed by the laws of England and Wales.";
"Any dispute arising from these Clauses shall be resolved by the courts of England and Wales. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of any country in the UK. The Parties agree to submit themselves to the jurisdiction of such courts."; and
The revised Approved Addendum will specify the start date from which the changes to the Approved Addendum are effective and whether the Parties need to review this Addendum including the Appendix Information. This Addendum is automatically amended as set out in the revised Approved Addendum from the start date specified.
and in either case it has first taken reasonable steps to reduce those costs or risks so that it is not substantial and disproportionate, then that Party may end this Addendum at the end of a reasonable notice period, by providing written notice for that period to the other Party before the start date of the revised Approved Addendum.
Alternative Part 2 Mandatory Clauses
Mandatory Clauses | Part 2: Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the ICO and laid before Parliament in accordance with section 119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18 of those Mandatory Clauses. |
This agreement has been entered into on the date stated at the beginning of it.
We'll personalize this session so you can gain deeper insights and get started quickly.
Hexnode year-end sale* ends in...
Copyright © 2024 Mitsogo Inc. All Rights Reserved.
Choose language