This Data Processing Addendum (“Addendum”) is entered into between Amua, Inc. (“Amua”) and the individual or organization agreeing to the Terms (“Customer”) for use of the “Services” (each a “Party” and collectively, the “Parties”). This Addendum supplements and forms part of any existing, current, or future agreement between the Parties (any such agreement being individually or together referred to as the “Agreement”) and will terminate when the last Agreement in effect terminates unless extended by the Parties. This Addendum will be in effect as of the effective date of the Agreement (“Effective Date”); provided, however, the relevant obligations apply only to the extent that (i) Personal Data is subject to the Applicable Data Privacy Laws; and (ii) an Applicable Data Privacy Laws has taken effect. The terms of this Addendum will control to the extent inconsistent with the Agreement.

“Applicable Data Privacy Laws” means all state, federal, national, or international laws, rules, and regulations applicable to the Personal Data Processed under this Addendum. Applicable Data Privacy Laws may include, without limitation: EU Regulation 2016/679 (“EU GDPR”), EU Directive 2002/58/EC (the “ePrivacy Directive”), and any laws, regulations, or rules implementing the foregoing, or implemented in European Union Member States thereunder, and any successor directives or regulations thereof then in effect, the UK Data Protection Act 2018, the UK GDPR (as defined in the Data Protection Act 2018), the UK Privacy and Electronic Communications (EC Directive) Regulations 2003; the Swiss Data Protection Act 2020 (collectively “European Applicable Data Privacy Laws ”); and Cal. Civ. Code §§ 1798.80 et seq., 1798.100 et seq. and its implementing regulations (“CCPA”).

“Consent” means a Data Subject’s freely given, specific, informed, and unambiguous indication of the Data Subject’s wishes by which they, by a statement or by a clear affirmative action, signifies agreement to the Processing of Personal Data relating to them.

“Controller” means a person that, either alone or with another person, determines the purposes and means of Processing Personal Data, and includes a “Business” as defined by CCPA.

“Data Incident” means any unauthorized destruction, loss, alteration, disclosure, acquisition or use of, or access to, Personal Data Processed under this Addendum.

“Data Subject” means an identifiable natural person who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person

“Personal Data” means any information relating to a Data Subject.

“Processing” means any operation or set of operations which is performed on Personal Data or on sets of Personal Data, whether or not by automated means, such as collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure, transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.

“Processor” means a person, to the extent that person Processes Personal Data on behalf of a Controller, including persons defined as “Service Providers” or similar under analogous definitions under Applicable Data Privacy Laws.

“Sensitive Data” means (a) social security number, passport number, driver’s license number, or similar identifier (or any portion thereof); (b) credit or debit card number (other than the truncated (last four digits) of a credit or debit card), financial information, banking account numbers or passwords; (c) employment information (other than business contact information, such as name, employer, job title or position, and business contact details), financial, genetic, biometric or health information; (d) racial, ethnic, political or religious affiliation, trade union membership, or information about sexual life or sexual orientation; (e) account passwords, mother’s maiden name, or date of birth; (f) criminal history; or (g) any other information or combinations of information that falls within the definition of “special categories of data” or “sensitive personal information” or analogous definitions in Applicable Data Privacy Laws .

SCHEDULE 1 – DESCRIPTION OF PROCESSING

Processing ActivityStatus of the PartiesCategories of Personal Data ProcessedCategories of Sensitive Data ProcessedStatus of the Parties as Data Exporter or ImporterApplicable SCCs Module
Customer discloses Personal Data to Amua in connection with the Business Purpose(s) listed below.Customer is a Controller. Amua is a Processor/ Service Provider.Any Personal Data that Customer discloses to Amua.NoneCustomer is the Data Exporter, and exports data from the UK or EEA. Amua is the Data Importer, and imports data into the U.S.A.Module 2 Module 3, if Amua acts as a Processor to another Controller
Amua creates accounts for Customer and Customer’s end users, synchronizes accounts with the user’s Telegram account, and collects usage information from them.Amua is a Controller/Third Party. Customer is a Controller.Name, phone number, Telegram username. User ID. Usage/telemetry data about the end-user’s device, e.g., device and browser identifiers (e.g., IP address, MAC address, identifiers stored in cookies) and information connected to such identifiersNoneCustomer is the Data Exporter, and exports data from the UK or EEA. Amua is the Data Importer, and imports data into the U.S.A.Module 1
Customer contacts Amua for support.Customer is a Controller. Amua is a Controller/Third Party.Name, phone number, Telegram username. User ID.NoneCustomer is the Data Exporter, and exports data from the UK or EEA. Amua is the Data Importer, and imports data into the U.S.A.Module 1
The Parties Process Personal Data of each other’s representatives to, e.g., (a) administer and provide the Services; (b) manage invoices; (c) manage the Agreement and resolve any disputes relating to it; (d) respond and/or raise general queries; and (e) comply with their respective regulatory obligations.Amua is a Controller/Third Party. Customer is a Controller.Name, title, and contact information.NoneCustomer is the Data Exporter, and exports data from the UK or EEA. Amua is the Data Importer, and imports data into the U.S.A.

Business Purposes

  • Processing related to ensuring security and integrity, to the extent that the information is reasonably necessary for these purposes.
  • Debugging to identify and repair errors that impair existing intended functionality.
  • Performing services on behalf of the Business, such as maintaining or servicing accounts, providing customer service, processing or fulfilling orders and transactions, verifying customer information, processing payments, providing financing, providing analytic services, providing storage, or providing similar services on behalf of the Business.
  • Undertaking internal research for technological development and demonstration.
  • Undertaking activities to verify or maintain the quality or safety of a service or device that is owned, manufactured for, or controlled by the Business, and to improve, upgrade, or enhance such a service or device.

Frequency of Transfers

Continuous

Duration of Processing

Personal Data will be Processed for the Term of the Agreement, and will be retained pursuant to the records retention provisions set forth in the Agreement.

Sub-Processor Transfers

Amua may use Subprocessors as set forth in Section 6 of the Addendum. Amua’s current authorized subprocessors include the following:

  • Amazon Web Services (Hosting)
  • Stripe (Payment Processing)
  • Telegram

Technical and Organizational Measures

Amua will implement and maintain the technical and organizational measures set forth in Section 8 and Schedule 2 of this Addendum.

SCHEDULE 2 – TECHNICAL AND ORGANIZATIONAL MEASURES

In its capacity as a Processor, Amua has implemented an information security policy that addresses:

  • Data minimization
  • Purpose limitation
  • User rights management
  • Encryption in transit and at rest
  • Multi-factor authentication for all access to Customer data
  • Role-based access controls with least privilege
  • Access logging retained for minimum 12 months
  • Network segmentation and firewalls
  • Intrusion detection/prevention systems
  • Regular vulnerability scanning and penetration testing

SCHEDULE 3 - INTERNATIONAL TRANSFER PROVISIONS