Privacy Policy
Ad Launch (https://adlaunch.klarodata.com) is an internal tool operated by Goverlo Media sp. z o.o., Poland for launching Meta (Facebook / Instagram) ads from prepared videos and images into advertising accounts that an organization has connected. This page says exactly what the service stores, why, for how long, and how it is deleted.
1. Who we are
The data controller is Goverlo Media sp. z o.o., Poland. Questions and requests: adlaunch@klarodata.com.
2. What we collect and why
| Data | Source | Purpose |
|---|---|---|
| Member accounts: e-mail, display name, a scrypt hash of the password, role and the ad accounts a member may see; session records (random token hash, creation and expiry time, browser user-agent); the client IP address of sign-in attempts (kept in memory only, for rate limiting). | Entered by the member or by the person who invited them. | Signing in and deciding who may see or launch what. |
| Meta access token of the person who connected Meta, with what Meta reports about it (app, token type, permissions, expiry dates, Facebook user id and name). The permissions requested are ads_management, pages_show_list and pages_read_engagement. | Facebook Login for Business, or pasted by an administrator. | Reading the connected ad accounts and creating ads in them on the organization's instruction. The token is stored encrypted at rest on our server and is never shown again in the interface. |
| Ad account data read through the Meta Marketing API: ad account name, currency and time zone; campaigns, ad sets, ads, creatives, videos and images (ids, names, settings, thumbnails, preview links); Facebook Pages and Instagram accounts the ad account may advertise from; pixels; EU advertiser/payer names; delivery statuses and review feedback; performance figures (spend, impressions, clicks, CTR, video plays); the account's activity log. | Meta Graph API, on behalf of the connected token. | Showing the state of the ad account, choosing where a new ad goes, reporting results of the ads the platform created. |
| Records of what the platform did: ids of every ad set, creative and ad it created, every write it sent to Meta, every launch plan and result, an audit log of member actions. | Generated by the platform. | Making sure nothing is created twice, showing who did what, and proving that the platform never modified anything it did not create. |
| Upload reports: names of videos, task names and reactions in the organization's own Slack channels (only when the organization switches Slack sync on). | The organization's Slack workspace. | Marking which uploaded video is queued or launched. |
3. What we do not do
We do not sell or share data with advertisers or data brokers. We do not build profiles of people who see ads: audience data of ads is read only as aggregated performance figures. The platform never pauses, edits or deletes an ad, ad set or campaign it did not create, and it never changes an object it created except its own name, status (switching it on) and EU advertiser/payer fields.
4. Processors
Hosting: a server in the European Union operated by us. Transactional e-mail (invitations, password resets): Resend. Operational alerts to the operator (failed launches, token expiry — no personal data beyond task names): Telegram. Meta Platforms is an independent controller of everything inside Facebook and Instagram; its terms and policies apply to the ad accounts themselves.
5. Retention
- Member accounts and audit log: while the organization uses the service; the audit log keeps the last 500 entries.
- Sessions: 30 days after the last visit, or at once when the member signs out, changes the password, or is deactivated.
- Meta access token: until the person disconnects Meta, re-authenticates (the old token is replaced) or Meta reports it invalid.
- Ad account data read from Meta: cached for minutes to hours and re-read; the per-account discovery (campaigns, pages, pixels) until the ad account is removed from the platform.
- Records of created objects and launch results: while the organization uses the service (they are the proof of what was done).
- Encrypted database backups on the same server: 14 daily copies, then deleted.
6. Deleting your data
- Disconnect Meta in Connect → Ad Channels deletes the stored access token and every cached read from Meta immediately.
- A data deletion request from Facebook (Settings → Apps and Websites → remove the app → «Send request») reaches our callback, deletes the connection authorised by that Facebook user and gives a confirmation code you can check at /data-deletion.
- Members: an administrator deactivates the account, or write to adlaunch@klarodata.com; we delete the account within 30 days unless the law requires us to keep a record.
- Anything else, including a copy of the data we hold about you: adlaunch@klarodata.com.
7. Your rights
Under the GDPR you may ask for access, rectification, erasure, restriction, portability and object to processing, and you may complain to your supervisory authority (in Poland: Urząd Ochrony Danych Osobowych). Write to adlaunch@klarodata.com.
8. Changes
When this policy changes, the date at the bottom changes and signed-in members see the new text here. Material changes are announced to the organization's administrators by e-mail.
Operator: Goverlo Media sp. z o.o., Poland · Contact: adlaunch@klarodata.com · Last updated 7 November 2026