This Data Processing Addendum and its appendixes ("DPA") form part of the Terms of Service available at www.hihello.com/legal/terms, or, if applicable, any other separate written agreement (the "Agreement" or “Services Agreement”), by and between HiHello, Inc., a Delaware corporation ("HiHello") and the Customer named in the Agreement, pursuant to which Customer has purchased a subscription to access and use the Service (as defined in the Agreement). The parties intend this DPA to be an extension of the Agreement governing certain requirements for HiHello’s Processing of Personal Data provided or made available by Customer, or collected or otherwise obtained by HiHello, in the course of providing the Service to Customer. Except for the changes made by this DPA, the Agreement remains unchanged and in full force and effect. If there is any conflict between the terms of this DPA and the Agreement, the terms of this DPA shall prevail.
Customer enters into this DPA on behalf of itself and, to the extent required under Data Protection Legislation, in the name and on behalf of its Affiliates. For the purposes of this DPA only, and except where indicated otherwise, the term “Customer” shall include Customer and such Affiliates.
If HiHello becomes aware of a Security Breach affecting Personal Data that is Processed by HiHello in the course of providing the Service under the Agreement:
it shall within 72 hours and without undue delay notify Customer and provide Customer with: a detailed description of the Security Breach; the type of data that was the subject of the Security Breach; and the steps HiHello has or will take in order to mitigate and remediate such Security Breach, in each case as soon as such information can be collected or otherwise becomes available (as well as periodic updates to this information and any other information Customer may reasonably request relating to the Security Breach); and
it shall within 72 hours and without undue delay notify Customer and provide Customer with: a detailed description of the Security Breach; the type of data that was the subject of the Security Breach; and the steps HiHello has or will take in order to mitigate and remediate such Security Breach, in each case as soon as such information can be collected or otherwise becomes available (as well as periodic updates to this information and any other information Customer may reasonably request relating to the Security Breach); and
HiHello will notify Customer immediately if, in HiHello's reasonable opinion, an instruction for the Processing of Personal Data given by Customer infringes applicable Data Protection Legislation.
HiHello as data exporter.
Subject to complying with the terms of this Section 4.1, Customer acknowledges and agrees that HiHello may transfer or disclose Personal Data to and in the United States and other locations in which HiHello or its Subprocessors maintain Processing operations (as more particularly described in the Subprocessors List).
HiHello shall at all times ensure that such transfers, including Restricted Transfers, are made in compliance with the requirements of Data Protection Legislation and this DPA. If HiHello engages in a Restricted Transfer, such measures may include (without limitation) transferring the Personal Data to a recipient that: (i) is covered by a suitable framework or other legally adequate transfer mechanism recognized by the relevant authorities or courts as providing an adequate level of protection for Personal Data, including the DPF; (ii) has achieved binding corporate rules authorization; or (iii) has executed SCCs; in each case as adopted or approved in accordance with Data Protection Legislation.
HiHello as data importer. The parties agree that, when the transfer of Personal Data from Customer to HiHello is a Restricted Transfer, HiHello shall comply with the following:
Data Privacy Framework: HiHello shall use the DPF to lawfully receive Personal Data in the United States and HiHello shall ensure that it provides at least the same level of protection to such Personal Data as is required by the DPF Principles.
SCCs: If the DPF does not cover the Restricted Transfer and/or it is invalidated, the SCCs shall automatically be incorporated into this DPA and apply to the Restricted Transfers as follows:
EU Transfers: In relation to Personal Data that is protected by the EU GDPR, the SCCs will apply completed as follows:
Module Two (Controller to Processor) will apply;
in Clause 7, the optional docking clause will not apply;
in Clause 9, Option 2 will apply, and the time period for prior notice of Subprocessor changes shall be as set out in Section 3.3 of this DPA;
in Clause 11, the optional language will not apply;
in Clause 17, Option 1 will apply, and the SCCs will be governed by the laws of the Republic of Ireland;
in Clause 18(b), disputes shall be resolved before the courts of the Republic of Ireland;
Annex I of the SCCs shall be deemed completed with the information set out in Appendix 1 of this DPA; and
Annex II of the SCCs shall be deemed completed with the information set out in Appendix 2 of this DPA.
UK Transfers: In relation to Personal Data that is protected by UK Data Protection Legislation, the SCCs: (i) shall apply as completed in accordance paragraph a.(i)-(viii) above; and (ii) shall be deemed amended as specified by the UK Addendum, which shall deemed executed by the parties and incorporated into and form an integral part of this DPA. In addition, Tables 1 to 3 in Part 1 of the UK Addendum shall be completed respectively with the information set out in Appendixes 1 and 2 of this DPA and Table 4 in Part 1 shall be deemed completed by selecting "neither party".
Swiss Transfers: In relation to Personal Data that is protected by the Swiss FADP, the SCCs will apply in accordance with paragraph a.(i)-(viii) above with the following modifications:
references to "Regulation (EU) 2016/679" shall be interpreted as references to the Swiss FADP;
references to specific Articles of "Regulation (EU) 2016/679" shall be replaced with the equivalent article or section of the Swiss FADP;
references to "EU", "Union", "Member State" and "Member State law" shall be replaced with references to "Switzerland" or "Swiss law";
the term "member state" shall not be interpreted in such a way as to exclude data subjects in Switzerland from the possibility of suing for their rights in their place of habitual residence (i.e., Switzerland);
Clause 13(a) and Part C of Annex I are not used and the "competent supervisory authority" is the Swiss Federal Data Protection Information Commissioner;
references to the "competent supervisory authority" and "competent courts" shall be replaced with references to the "Swiss Federal Data Protection Information Commissioner" and "applicable courts of Switzerland";
in Clause 17, the SCCs shall be governed by the laws of Switzerland; and
Clause 18(b) shall state that disputes shall be resolved before the applicable courts of Switzerland.
It is not the intention of either party to contradict or restrict any of the provisions set forth in the SCCs and, accordingly, if and to the extent the SCCs conflict with any provision of the Agreement (including this DPA) the SCCs shall prevail to the extent of such conflict.
This Appendix 1 forms part of the DPA and describes the Processing that HiHello (as the Processor) will perform on behalf of Customer (as the Controller).
HiHello adopts an Information Security Management Systems (ISMS) as a framework for continuous improvement of security.
This ISMS includes (but is not limited to):
Policies
HiHello has and periodic reviews the Information Security Policies as the major guidelines for security practices. This includes Risk Management, Data Classification, Access Control, Software Development and Data Breaches.
Awareness
Awareness on security and compliance is fundamental and provided to all users. Some users may have additional specific awareness, relevant for their function.
Access control
Access is granted on a need-to-know basis and only a small number of users can access production systems where information from Customers is stored. Authentication to production systems is made with 2-factor Authentication as a standard.
Audit logging
Relevant audit logs are maintained, including access to sensitive information (including personal data). The logs are kept in separate infrastructure and only accessed by Security team.
Data Breaches
Processes are defined to handle Data Breaches. These processes include notification to relevant stakeholders, according to type of incident and applicable legislation.
Network security
HiHello implemented several security measures to protect our infrastructure from external and internal threats. This includes encryption, firewalls, IDS and other cloud provider specific. Access to production systems is made in secure mode and encryption in transit is a default. Sensitive information is also encrypted at rest.
Physical Security
HiHello uses data centers managed by cloud providers and delegates all physical security to them, after a due diligence.
Business Continuity
HiHello has several technical implementations to assure business continuity of its service. Those include backups, resilient and redundant infrastructure and a Disaster Recovery Plan.
Development
Development is made using a secure development methodology that includes peer review and secure coding and testing.
Continuous improvement and review
HiHello security posture is based on a continuous improvement process that includes periodic review of security controls effectiveness.