Data Processing Agreement

To download a copy of this Data Processing Agreement, click here.

This Data Processing Agreement (“Agreement“) forms part of the Agreement for the Service (“Principal Agreement“) between Stormly (as a “Data Processor”) and the Client (as a “Data Controller”) (and together as the “Parties”).

This Data Processing Agreement applies to all data sent from Client to Stormly; not only that part of data that would fall under the GDPR. While implemented with the GDPR in mind, it should be compatible with other potential data legislation as well, such as the new CCPA (California Consumer Privacy Act) that goes into effect on the 1st of January 2020.

Stormly has a dedicated Data Protection Officer: Maurice Sikkink, which can be reached by email at dpo@stormly.com.

Effective date: 21 November 2019

WHEREAS:

  1. The Client acts as a Data Controller.
  2. The Client wishes to subcontract certain Services, which imply the processing of personal data, to Stormly.
  3. The Parties seek to implement a data processing agreement that complies with the requirements of the current legal framework in relation to data processing and with the 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, and repealing Directive 95/46/EC (General Data Protection Regulation).
  4. The Parties wish to lay down their rights and obligations.


IT IS AGREED AS FOLLOWS:
Article 1. Definitions and Interpretation

  1. Unless otherwise defined herein, capitalized terms and expressions used in this Agreement shall have the following meaning:
    1. Agreement: this Data Processing Agreement.
    2. Client Personal Data: any Personal Data Processed by a Contracted Processor on behalf of Client pursuant to or in connection with the Principal Agreement.
    3. Contracted Processor: a Subprocessor.
    4. Data Protection Laws: means EU Data Protection Laws and, to the extent applicable, the data protection or privacy laws of any other country.
    5. EEA: means the European Economic Area.
    6. EU Data Protection Laws: means EU Directive 95/46/EC, as transposed into domestic legislation of each Member State and as amended, replaced or superseded from time to time, including by the GDPR and laws implementing or supplementing the GDPR.
    7. GDPR: EU General Data Protection Regulation 2016/679.
    8. Data Transfer: (i) a transfer of Client Personal Data from the Client to a Contracted Processor; or (ii) an onward transfer of Client Personal Data from a Contracted Processor to a Subcontracted Processor, or between two establishments of a Contracted Processor, in each case, where such transfer would be prohibited by Data Protection Laws (or by the terms of data transfer agreements put in place to address the data transfer restrictions of Data Protection Laws).
    9. Services: the SaaS services the Client provides.
    10. Subprocessor: any person appointed by or on behalf of Stormly to process Personal Data on behalf of the Client in connection with the Agreement.
    11. Sensitive Data: (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); (c) employment, 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; or (f) other information that falls within the definition of "special categories of data" under the GDPR or any other applicable Data Protection Laws.
    12. The terms, “Commission”, “Controller”, “Data Subject”, “Member State”, “Personal Data”, “Personal Data Breach”, “Processing” and “Supervisory Authority” shall have the same meaning as in the GDPR, and their cognate terms shall be construed accordingly.

Article 2. Processing of Client Personal Data

  1. Stormly shall:
    1. comply with all applicable Data Protection Laws in the Processing of Client Personal Data; and
    2. not Process Client Personal Data other than on the relevant Client’s documented instructions.
  2. The Client instructs Stormly to process Client Personal Data.

Article 3. Details of Data Processing

  1. Stormly processes data of Client to provide Services to the Client as agreed upon in the Principal Agreement.
  2. Information is processed which is sent by Clients’ end-user to Stormly, via different programmatic integrations, such as, but not limited to: Stormly’s Javascript website integration library, import functionality, custom tracking end-points and 3rd party data sources. The following is a list of Personal Data properties that may be processed due to integrations as described above.

    Automatically tracked general properties for all integrations:

    • Timestamp of action
    • User created timestamp
    • User last active at
    • Previous user id (in case of identifying an anonymous user)
    • Referred by user id (in case share codes are used to track invites)
    • IP (not stored and anonymized by removing the last octet. Only used temporarily to generate other properties like Geolocation and timezone)
    • The timezone of request, based on anonymized IP
    • Anonymized Geo coordinates, country, city and connection type, based on IP anonymized address

    For Web integrations the following is tracked automatically:

    • User Identifier (using a first-party cookie)
    • Browser User Agent, version and name
    • Page URL and title
    • HTTP referrer
    • UTM campaign properties
    • Screen width and height
    • Operating System name and version
    • Locale
    • Share code

    For App integrations the following properties are tracked only if set by the developer of the App, or using 3rd party data sources like Segment.com:

    • User Identifier (implementation is up to Client or 3rd party data source used)
    • Screen width, height and density
    • App name, version and build
    • Device id, name, model, manufacturer
    • Device advertising id, and if ad is tracking enabled
    • If device network is using bluetooth, cellular, wifi, and the network in case of cellular
    • Referrer id, name and type
    • Custom Campaign properties
    • Operating System name and version
    • Locale
    • Share code

Article 4. Categories of Data Subjects

The categories of Data Subject are Clients’ End-User, such as but not limited to users of web and mobile applications, or any custom imported data containing users and their actions.

Article 5. Processor Personnel

Processor shall take reasonable steps to ensure the reliability of any employee, agent or contractor of any Contracted Processor who may have access to the Client Personal Data, ensuring in each case that access is strictly limited to those individuals who need to know / access the relevant Client Personal Data, as strictly necessary for the purposes of the Principal Agreement, and to comply with Applicable Laws in the context of that individual’s duties to the Contracted Processor, ensuring that all such individuals are subject to confidentiality undertakings or professional or statutory obligations of confidentiality.

Article 6. Security

  1. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of Processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Stormly shall in relation to the Client Personal Data implement appropriate technical and organizational measures to ensure a level of security appropriate to that risk, including, as appropriate, the measures referred to in Article 32(1) of the GDPR.
  2. In assessing the appropriate level of security, Stormly shall take account in particular of the risks that are presented by Processing, in particular from a Personal Data Breach.
  3. To see what third-party service providers Stormly uses and that may be used to process Personal Data and their compatibility with the GDPR and other data regulation frameworks, see “Security Architecture Document”.

Article 7. Subprocessing

  1. Stormly shall not appoint (or disclose any Client Personal Data to) any Subprocessor unless required or authorized by the Client. Stormly will notify the Client immediately in case of changes in appointed Subprocessors. For a list of Subprocessors appointed by Stormly see: “Security Architecture Document”.
  2. Stormly only works with 3rd parties that are GDPR compliant and use the data only to the agreed purpose. Stormly publishes any new Subprocessors in the “Security Architecture Document” under "Subprocessors". Client is responsible for keeping up to date with any changes, and can cancel its Agreement within 10 days of publication if a valid reason for objection is provided, and Stormly has a chance to establish that the objections towards using a specific Subcontractor are correct and can’t find an alternative.

Article 8. Data Subject Rights

  1. Taking into account the nature of the Processing, Stormly shall assist the Client by implementing appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Client obligations, as reasonably understood by Client, to respond to requests to exercise Data Subject rights under the Data Protection Laws.
  2. Stormly shall:
    1. promptly notify Client if it receives a request from a Data Subject under any Data Protection Law in respect of Client Personal Data; and
    2. ensure that it does not respond to that request except on the documented instructions of Client or as required by Applicable Laws to which Stormly is subject, in which case Stormly shall to the extent permitted by Applicable Laws inform Client of that legal requirement before the Contracted Processor responds to the request.
  3. Stormly provides programmatic and online tools so that Client can comply with user removal and user data retrieval requests. See “Data Processing Terms” for more information.

Article 9. Personal Data Breach

  1. Stormly shall notify Client without undue delay upon Stormly becoming aware of a Personal Data Breach affecting Client Personal Data, providing Client with sufficient information to allow the Client to meet any obligations to report or inform Data Subjects of the Personal Data Breach under the Data Protection Laws.
  2. Stormly shall co-operate with the Client and take reasonable commercial steps as are directed by Client to assist in the investigation, mitigation and remediation of each such Personal Data Breach.

Article 10. Data Protection Impact Assessment and Prior Consultation

Stormly shall provide reasonable assistance to the Client with any data protection impact assessments, and prior consultations with Supervising Authorities or other competent data privacy authorities, which Client reasonably considers to be required by article 35 or 36 of the GDPR or equivalent provisions of any other Data Protection Law, in each case solely in relation to Processing of Client Personal Data by, and taking into account the nature of the Processing and information available to, the Contracted Processors.

Article 11. Deletion or return of Client Personal Data

Subject to this section 9, Stormly shall promptly and in any event within 10 business days of the date of cessation of any Services involving the Processing of Client Personal Data (the “Cessation Date”), delete and procure the deletion of all copies of those Client Personal Data.

Article 12. Audit rights

  1. Subject to this section 10, Stormly shall make available to the Client on request all information necessary to demonstrate compliance with this Agreement, and shall allow for and contribute to audits, including inspections, by the Client or an auditor mandated by the Client in relation to the Processing of the Client Personal Data by the Contracted Processors.
  2. Information and audit rights of the Client only arise under section 10.1 to the extent that the Agreement does not otherwise give them information and audit rights meeting the relevant requirements of Data Protection Law.

Article 13. Data Transfer

Stormly may not transfer or authorize the transfer of Data to countries outside the EU and/or the European Economic Area (EEA) without the prior written consent of the Client. If personal data processed under this Agreement is transferred from a country within the European Economic Area to a country outside the European Economic Area, the Parties shall ensure that the personal data are adequately protected. To achieve this, the Parties shall, unless agreed otherwise, rely on EU approved standard contractual clauses for the transfer of personal data.

Article 14. Confidentiality

Each Party must keep this Agreement and information it receives about the other Party and its business in connection with this Agreement (“Confidential Information”) confidential and must not use or disclose that Confidential Information without the prior written consent of the other Party except to the extent that: (i) disclosure is required by law; (ii) the relevant information is already in the public domain.

Article 15. Notices

All notices and communications given under this Agreement must be in writing and will be delivered personally, sent by post or sent by email to the address or email address set out in the heading of this Agreement at such other address as notified from time to time by the Parties changing address.

Article 16. Governing Law and Jurisdiction

  1. This Agreement is governed by the laws of the Netherlands.
  2. Any dispute arising in connection with this Agreement, which the Parties will not be able to resolve amicably, will be submitted to the exclusive jurisdiction of the courts of Amsterdam.