HomeSecurityPrivacy

Data Processing Agreement

Version 1.0, 14 October 2026.

To sign: print this page or save it as PDF (Ctrl/Cmd + P), fill in your details at the end, sign, and email it to contact@kunads.ai. We countersign and send it back. Without a signed copy, this agreement applies as part of our Terms of service from the moment you connect an account.

1. Parties and roles

This agreement is between the customer named below (the Controller) and MB Kunis, Vilnius, Lithuania, which operates Kunads (the Processor). It applies to personal data the Processor handles for the Controller through Kunads, and follows Article 28 of the General Data Protection Regulation (EU) 2016/679 (GDPR). Where the Controller is an agency acting for its own clients, the agency is the Processor's customer and the Processor acts as its sub-processor; the agency remains responsible towards its clients.

2. What is processed

PurposeReporting on and managing the Controller's advertising: matching sales to ad clicks, measuring profit, proposing and — on approval — applying changes, and, if switched on, reporting confirmed sales back to the Controller's own ad accounts.
Data subjectsThe Controller's (or its clients') customers and leads; the Controller's own users of Kunads.
Personal dataOrder or deal identifiers, times and values; customer email addresses (stored as given; sent onwards only as one-way SHA-256 hashes); ad click identifiers (e.g. gclid, fbclid); campaign and channel tags; names and emails of Kunads users. No special categories of data are intended to be processed.
DurationFor as long as the Controller uses Kunads, then deletion as in section 9.

3. Instructions

The Processor processes personal data only on the Controller's documented instructions — this agreement, the Terms of service, and the settings the Controller chooses in Kunads — unless EU or Lithuanian law requires otherwise, in which case the Processor tells the Controller first unless the law forbids it. The Processor tells the Controller if it believes an instruction breaks the GDPR.

4. Confidentiality

Everyone the Processor allows to access the personal data is bound to confidentiality. Today that is the operator of MB Kunis only, and only when supporting the Controller, investigating a fault, or as the law requires.

5. Security

The Processor keeps appropriate technical and organisational measures under Article 32 GDPR, described on the Security page, including: hosting in the EU (Frankfurt), encryption in transit, encryption of access keys at rest (AES-256-GCM, key held apart from the database), two-step sign-in, server-side access checks for every read and change, approval before any change to an ad account, and a record of every change. The Processor may improve these measures but will not lower their overall level.

6. Sub-processors

The Controller authorises the sub-processors listed on the Security page (Supabase, Vercel, GitHub, Anthropic, fal.ai, Stripe, Resend). The Processor binds each to data-protection terms no less protective than these, and remains responsible for them. The Processor announces a new sub-processor by email at least 30 days before it starts; the Controller may object on reasonable grounds, and if no solution is found, may end the service and receive a pro-rata refund of prepaid fees.

7. Transfers outside the EU

Where a sub-processor handles data outside the European Economic Area, the transfer relies on an adequacy decision (including the EU–US Data Privacy Framework where the provider is certified) or on the European Commission's standard contractual clauses.

8. Helping the Controller

  • The Processor helps the Controller answer data-subject requests (access, correction, deletion, objection), and passes on any such request it receives directly.
  • The Processor helps with security, breach notification, impact assessments and prior consultation (Articles 32–36), taking into account what it can know.
  • The Processor tells the Controller of a personal-data breach without undue delay and in any case within 72 hours of becoming aware of it, with what is known and the steps taken.

9. End of the service

When the Controller disconnects a source or closes its account, the Processor stops processing and deletes the personal data within 30 days, unless the law requires it to be kept (for example accounting records). On request before closing, the Processor provides a copy of the Controller's data.

10. Audits

The Processor makes available the information needed to show compliance with this agreement, answers security questionnaires in writing, and allows audits by the Controller or an auditor it appoints, on 30 days' notice, at the Controller's cost, at most once a year unless a breach or a supervisory authority requires more.

11. Liability and law

Liability follows the Terms of service, subject to the GDPR. Lithuanian law applies, and disputes belong to the courts of Vilnius. If this agreement and the Terms of service conflict on data protection, this agreement wins.

Signatures

Controller

Company: ______________________________

Company code: _________________________

Address: ______________________________

Name, title: ___________________________

Signature: ____________________________

Date: ________________
Processor

MB Kunis (Kunads)

Vilnius, Lithuania

Arnoldas Kunigėlis, manager

Signature: ____________________________

Date: ________________
© 2026 Kunads Home Security Privacy policy contact@kunads.ai Cookie settings