Data Processing Agreement
Version 2026-11-07 · effective 7 November 2026 · concluded under Article 28 of Regulation (EU) 2016/679 (GDPR)
This agreement is between the organization that uses Ad Launch (an agency or an advertiser — «the Organization», the controller) and Goverlo Media sp. z o.o., Poland («the Processor»). An owner or administrator of the Organization accepts it in Ad Launch on the Organization's behalf; the record of who accepted which version and when is kept by the platform. Where the Organization itself works for clients and acts as their processor, the Processor is its sub-processor (Art. 28(4)) and the Organization makes sure its agreements with those clients allow this.
1. Subject matter and duration (Art. 28(3))
The Processor runs Ad Launch for the Organization: it reads the Meta advertising accounts the Organization connects and creates ads in them on the Organization's instruction. The agreement lasts as long as the Organization uses the service and ends with the deletion described in §10.
2. Nature and purpose of the processing
- Reading campaigns, ad sets, ads, creatives, videos, images, Pages, Instagram accounts, pixels, delivery statuses, review feedback and aggregated performance figures through the Meta Marketing API, to show the state of the account and to choose where a new ad goes.
- Creating ad sets (as a duplicate of an existing one), creatives and ads from the files and texts the Organization prepared, and switching them on with a scheduled start.
- Keeping records of what the platform created and wrote, for the Organization's own control and to never create anything twice.
- When the Organization switches it on: reading upload reports in its own Slack channels and marking them queued/launched.
3. Types of personal data and categories of data subjects
- People appearing in the Organization's ad material: names, faces and voices in videos and images (passed to Meta as files, never analysed), names in ad texts, file names and task names.
- People behind Facebook Pages and Instagram accounts the ads run from (names, ids, profile pictures as Meta returns them).
- Advertiser / payer names declared for the EU Digital Services Act on ad sets.
- The person who connected Meta: Facebook user id and name, and the access token (encrypted at rest).
- The Organization's team in upload reports (Slack names), when Slack sync is on.
No special categories of data (Art. 9) are intended. People who see the ads are not processed individually: audience results are read only as aggregated figures (spend, impressions, clicks, plays). Member accounts of the Organization's team (e-mail, name, password hash, sessions) are covered by the Privacy Policy.
4. Obligations of the Processor
- Documented instructions (Art. 28(3)(a)): the Processor processes the data only to provide the service as configured by the Organization (which ad accounts, who may launch, whether writing to Meta and Slack sync are on) and on its members' actions in the platform, unless EU or Polish law requires otherwise — then it informs the Organization first unless the law forbids that.
- Confidentiality (Art. 28(3)(b)): only the Processor's staff who run the service have access, bound by confidentiality.
- Security (Art. 28(3)(c), Art. 32): TLS for every connection; the Meta token encrypted at rest (AES-GCM) and signed with appsecret_proof on every call; passwords stored as scrypt hashes; sessions revocable, ended on password change and deactivation; sign-in rate limiting; CSRF protection; role- and ad-account-based access for every member; an audit log of member actions; writing to Meta off per ad account until an administrator switches it on; daily database backups on the same EU server (14 copies, the token inside stays encrypted).
- Sub-processors (Art. 28(2), (4); (3)(d)): only those listed in §5. A new or replaced sub-processor is announced to the Organization's administrators by e-mail at least 30 days before it starts; the Organization may object, and if no solution is found it may end the agreement. Each sub-processor is bound by data-protection obligations no weaker than these.
- Data subject requests (Art. 28(3)(e)): the Processor forwards to the Organization any request it receives about the Organization's data and helps it answer (export, correction, deletion) within reasonable time.
- Assistance (Art. 28(3)(f)): with security, breach notification, data protection impact assessments and prior consultation (Art. 32–36), as far as the Processor's part of the processing goes.
- Deletion or return (Art. 28(3)(g)): see §10.
- Information and audits (Art. 28(3)(h)): the Processor gives the Organization the information needed to show compliance and allows audits, including inspections by an auditor the Organization appoints, with reasonable notice and at the Organization's cost.
5. Sub-processors
| Sub-processor | What for | Where |
|---|---|---|
| Hetzner Online GmbH | Server hosting of the platform and its database | European Union |
| Resend | Transactional e-mail to members (invitations, password resets) | See §6 |
| Telegram | Operational alerts to the Processor about failed launches and token expiry (task names only) | See §6 |
Meta Platforms is not a sub-processor: it is an independent controller of everything inside Facebook and Instagram, under the terms the Organization accepted with Meta. The Organization's Slack workspace is the Organization's own tool.
6. Transfers outside the EEA (Chapter V)
The database stays in the EU. Where a sub-processor processes data outside the EEA, the transfer relies on an adequacy decision or on the Standard Contractual Clauses (Art. 46(2)(c)) with that sub-processor.
7. Personal data breaches (Art. 33)
The Processor notifies the Organization without undue delay, and in any case within 48 hours of becoming aware of a breach affecting the Organization's data, with what is known (nature, categories and approximate number of records, likely consequences, measures taken), and completes the information as it becomes available.
8. The Organization's obligations
The Organization has a lawful basis for the data in its ad accounts and material, is entitled to connect the ad accounts it adds, and gives its instructions through the platform's settings or in writing to adlaunch@klarodata.com.
9. Liability
Liability follows Art. 82 GDPR and the Terms of Service. In a conflict between this agreement and the Terms on personal data, this agreement prevails.
10. End of the agreement: deletion
When the Organization stops using the service, or on its written request, the Processor deletes the Meta connection and cached reads at once (Disconnect Meta does the same at any time), and deletes the rest of the Organization's data within 30 days, unless the law requires it to be kept; backups roll over within 14 days after that. On request before deletion, the Processor returns the Organization's records (settings, created objects, launch results, audit log) in a machine-readable form.
11. Law and changes
Polish law applies; the courts of the Processor's seat are competent. A new version of this agreement is published here with a new version date, and owners/administrators are asked to accept it in Ad Launch. Contact: adlaunch@klarodata.com.
Operator: Goverlo Media sp. z o.o., Poland · Contact: adlaunch@klarodata.com · Last updated 7 November 2026