Moka

Data processing agreement

Last updated:

Contents

This agreement (the “Agreement”) supplements the terms of use and sale (the “Terms”) of Moka. In accordance with article 28 of Regulation (EU) 2016/679 (“GDPR”), it sets out the conditions under which Tharshan Vishnukumar EI (the “Processor”) processes personal data on behalf of the User (the “Controller”) when the latter installs the Moka script on their website. It is accepted together with the Terms and applies for the whole duration of the subscription, then until the data is deleted. In the event of a conflict, the Agreement prevails over the Terms as regards personal data.

1. Description of the processing

  • Subject matter and purpose: audience measurement of the Controller's website and attribution of its revenue to traffic sources, presented in its dashboard.
  • Nature of the operations: collection by the script, enrichment (channel, approximate location, device), storage, aggregation, consultation by the Controller, erasure.
  • Data subjects: visitors to the Controller's website and, when it connects its payments, its buyers.
  • Data processed: in exempt mode, an audience measurement identifier (moka_aid cookie, 13 months from when it is first set, never extended); in full mode, after the visitor's consent, a visitor identifier (moka_visitor_id and moka_consent cookies, 13 months from when they are first set, never extended, set only after the visitor's consent); in both modes, a session identifier (moka_session_id cookie, 30 minutes, extended with each page view); pages viewed, referrer, campaign parameters, goals and outbound links; device type, browser, operating system, screen size; country, region, city and approximate position of the city (rounded to about ten kilometres) derived from the IP address, which is not stored; for visitors in full mode, payments: amount, currency, date, Stripe customer identifier and buyer's email address.
  • Excluded data: the Service is not designed to process special categories of data (art. 9 of the GDPR) or direct identifiers in page addresses or goal properties; the Controller undertakes not to send any.
  • Retention period: 25 months from collection, then deleted automatically; linked payments (amount, currency, date, Stripe customer identifier, buyer's email address, visitor identifier and acquisition channel of the first visit: source, campaign, landing page, device, country, region, city) are kept for as long as the site exists; everything is deleted along with the site concerned, or with the customer's account at their request.

2. Obligations of the Controller

The Controller:

  • determines the purposes of the processing and configures the Service (domains, exclusions, goals);
  • informs its visitors of the processing and has a legal basis for it;
  • enables the Service's full mode (individual journeys, linking to payments) only for visitors who have consented to it, by calling moka.consent(), and withdraws it with moka.revoke(); gives them the means to object to measurement (moka.optOut()); only loads the script after consent where the regulations applicable to its visitors do not allow the consent exemption for audience measurement (article 82 of the French Data Protection Act);
  • chooses the people it gives read-only access to a site, ensures they are bound by confidentiality and removes their access when it is no longer needed; the Processor only grants them access on its invitation;
  • answers its visitors' requests to exercise their rights;
  • documents its instructions in writing, the Terms and this Agreement constituting its initial instructions.

3. Obligations of the Processor

The Processor undertakes to:

  • process the data only for the purpose described and on documented instructions from the Controller, including with regard to transfers outside the European Union; it immediately informs the Controller if an instruction appears to infringe the regulations;
  • not use the data for its own purposes, not sell it and not combine it with other customers' data;
  • ensure the confidentiality of the data and ensure that persons authorised to process it are bound by a duty of confidentiality;
  • implement the security measures described in article 6;
  • assist the Controller, insofar as possible, in answering requests to exercise rights, carrying out an impact assessment and meeting its security and notification obligations; any request received directly from a data subject is forwarded to it without delay;
  • make available to the Controller the information needed to demonstrate compliance with this Agreement and allow reasonable audits, at the Controller's expense, with 30 days' notice and while respecting the confidentiality of other customers.

4. Sub-processors

The Controller gives general authorisation for the use of the following sub-processors, bound to the Processor by a contract imposing obligations equivalent to those of this Agreement:

  • Vercel: Application hosting and reception of the tracking script's events. Location: United States and global points of presence.
  • Railway: Database hosting. Location: United States.
  • Upstash: Rate limiting of sign-in attempts (IP address, temporary counters). Location: United Kingdom (AWS, London).
  • Stripe: Payment processing and billing. Location: European Union and United States.
  • Resend: Sending transactional emails (address confirmation, password reset, sign-in link, billing). Location: United States.

The Processor informs the Controller, by email or in the Service, of any addition or replacement at least 30 days in advance. The Controller may object on legitimate grounds relating to data protection; failing agreement, it may cancel its subscription at no cost. The Processor remains liable to the Controller for the performance of their obligations by its sub-processors.

5. Transfers outside the European Union

Some sub-processors process data outside the European Economic Area. These transfers are covered by the following safeguards (chapter V of the GDPR):

  • Vercel: EU–US Data Privacy Framework and standard contractual clauses.
  • Railway: European Commission standard contractual clauses (and the Data Privacy Framework where applicable).
  • Upstash: European Commission adequacy decision for the United Kingdom, and standard contractual clauses for access from the United States (Upstash Inc.).
  • Stripe: EU–US Data Privacy Framework and standard contractual clauses.
  • Resend: European Commission standard contractual clauses.

6. Security

The Processor implements technical and organisational measures appropriate to the risk, including:

  • encrypted connections (HTTPS) between the script, the Service and its providers;
  • random visitor identifiers, unrelated to people's identity; IP address not stored;
  • data partitioned by website and access control: only the account holder can access it;
  • restricted, encrypted Stripe API keys and webhook signature verification;
  • protected authentication (hashed passwords, email verification, rate limiting of attempts).

7. Personal data breach

The Processor notifies the Controller of any personal data breach within 48 hours at most of becoming aware of it, by email to the account's address, with the information referred to in article 33.3 of the GDPR that it has, so that the Controller can notify the supervisory authority within 72 hours where applicable.

8. Return and deletion of data

The Controller may delete a website's data at any time by deleting that website in the Service. At the end of the subscription, and at the Controller's request, the Processor deletes the data collected on its behalf, unless a legal obligation requires it to be kept. Backups are erased according to their rotation cycle.

9. Contact

For any question about this Agreement or to exercise an audit right: hello@koumastudio.com. See also our privacy policy.