Start free

Last updated 6 November 2026

Privacy policy

This policy explains what personal data AdCtrl handles, why, who receives it, where it is kept and for how long. It covers the website adctrl.ai and the AdCtrl service at app.adctrl.ai. AdCtrl connects the Google Ads, Meta Ads, Google Analytics 4, Google Tag Manager and Google Search Console accounts you select to the AI app you choose, such as Claude or ChatGPT.

Who we are

AdCtrl is operated by mondaybrew ApS, CVR 45217779, Vesterbrogade 74, 3. sal, 1620 København V, Denmark. Contact hello@adctrl.ai with any privacy question or request.

How AdCtrl works

You sign in to app.adctrl.ai, connect Google and/or Meta, and choose which accounts your AI app may use. You then add AdCtrl to your AI app and approve its access. When you ask your AI app something, it calls AdCtrl's tools. AdCtrl reads only from the accounts you selected and returns the result to your AI app. For changes, AdCtrl first saves a preview with the exact account, items and values before and after. The change is sent to Google or Meta only after it is approved, and AdCtrl then reads the result back. AdCtrl only acts when your AI app calls it. It doesn't read or change your accounts in the background, and it doesn't call any AI model itself.

What we collect and why

We don't sell personal data, use data from your connected accounts for our own advertising, or use it to train AI models.

Customer data you send to Google or Meta

Some features handle personal data about your own customers. AdCtrl processes it only to send it to the Google or Meta account you chose, after you approve the exact upload.

You decide whether to use these features and are responsible for having a lawful basis and giving your customers the required notices. Google and Meta process the data under your own agreements with them, including Google's Customer Match policy and Meta's Custom Audience and Business Tools terms.

Legal basis

For data we process as your processor, you as controller determine the legal basis.

Google user data

AdCtrl's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

AdCtrl requests access to Google Ads, Google Analytics, Tag Manager and Search Console only so that your AI app can read and change the accounts you select at your request. In practice:

Meta platform data

We process data from Meta's platform only to provide the features you request in AdCtrl and in line with Meta's Platform Terms and Developer Policies. We don't sell or license it, give it to data brokers, use it for our own advertising, use it to make decisions about anyone's eligibility for credit, housing, employment or insurance, or use it to train AI models. We keep it only as long as described below, and we delete it when you ask, when Meta asks, or when we no longer need it to provide AdCtrl. To remove AdCtrl's access to Meta and ask for deletion, see disconnect and deletion.

Your AI app

Tool results, including advertising, analytics, search and tracking data, previews, change results and any approved lead fields, are returned to the AI app you connected, such as Anthropic's Claude or OpenAI's ChatGPT. That AI app receives the data because you asked for it, under your own account and agreement with Anthropic or OpenAI, and keeps it in your conversations according to its own terms and settings. Anthropic and OpenAI are not our sub-processors. Access tokens for Google and Meta are never included in tool results. We can't delete data held by your AI app; use its own controls for that.

Who processes data for us

If you accept marketing cookies, Google (Google Ads) and Meta (Meta Pixel and Conversions API) also receive the measurement events above to measure and improve our own ads and to show our ads to people who visited adctrl.ai (remarketing), and use them for their own purposes under their own terms: Google, Meta. For the Meta Pixel and Conversions API we and Meta Platforms Ireland Ltd are joint controllers for collecting and sending the data; Meta is responsible for what it does with it afterwards. Before you choose, Google Analytics and Google Ads receive only cookieless signals (Google Consent Mode): no cookies are set, no identifier is stored and Google uses them only to model totals.

Google and Meta receive data because you instruct AdCtrl to read or change your own accounts there. They act under your agreements with them, not as our sub-processors. We disclose data to authorities only where the law requires it.

Some of these providers may process data outside the EU and EEA. Where they do, the transfer is protected by the EU–US Data Privacy Framework or the European Commission's standard contractual clauses.

How long we keep data

We make encrypted copies of the service database on the same server in Finland, for example before an update. We delete these copies after 30 days, so deleted records are gone from them within 30 days. Uploaded customer lists and conversion events can't be read from these copies, because their keys are never stored.

Deleting AdCtrl data doesn't delete campaigns, ads, posts, forms, leads, audiences, catalogs, conversions or anything else held by Google or Meta, or conversations held by your AI app.

Security

All traffic to AdCtrl uses HTTPS. Provider tokens and all stored records are encrypted with AES-256-GCM, using a key kept in the server configuration rather than in the database. Uploaded customer data uses separate per-upload keys that exist only in memory, as described above. AI apps connect through OAuth with short-lived tokens bound to your workspace, and every request is checked against the accounts you selected, so an AI app can't reach an account you haven't turned on. No system is completely secure. If a breach affects your personal data, we will tell you and the authorities as the law requires.

Cookies

On adctrl.ai we ask before setting any cookie that isn't strictly necessary. Choose Reject all, Accept all or pick analytics and marketing separately. You can change your choice at any time in cookie settings; withdrawing removes our measurement cookies from your browser. Your choice applies to adctrl.ai and app.adctrl.ai.

CookieSet byPurposeLifetimeNeeds consent
adctrl_consentAdCtrlRemembers your cookie choice6 monthsNo, strictly necessary
adctrl_attrAdCtrlWhich campaign or ad link brought you, so a later sign-up can be credited to it90 daysAnalytics or marketing
_ga, _ga_D17LFWTPGEGoogle AnalyticsTell visits and sessions apart13 monthsAnalytics
_clck, _clskMicrosoft ClarityConnect page views of one visit for masked recordings and heatmaps1 year; 1 dayAnalytics
_gcl_au, _gcl_aw, _gcl_gbGoogle AdsLink a visit to the Google ad that was clicked90 daysMarketing
_fbp, _fbcMetaLink a visit to a Meta ad click and measure our ads90 daysMarketing

Google, Microsoft and Meta may also set their own cookies on their domains (for example google.com, clarity.ms or facebook.com) when their tools load after your consent; see their policies above. All tags on adctrl.ai are managed in one Google Tag Manager container. The pages for reviewers of our Google and Meta app reviews load none of these tools.

The AdCtrl service at app.adctrl.ai loads Google Tag Manager with Google Analytics only, under the same cookie choice as adctrl.ai: before you choose or after Reject, Google gets only cookieless signals; after Accept, Google Analytics may set its cookies. It records which kind of page was viewed with a cleaned address (no account, workspace or other identifiers and no query strings) and never anything you type. It loads no advertising or recording scripts (no Google Ads, Meta Pixel or Microsoft Clarity), and none of these tools load on the pages for Google and Meta reviewers or on sign-in callbacks. The service uses two strictly necessary cookies: a session cookie that keeps you signed in and protects forms (up to 8 hours, deleted when you sign out) and a connection cookie used only while you connect Google or Meta (10 minutes). Both are secure and HTTP-only. Because they are strictly necessary, we don't ask for consent for them. If you accepted cookies on adctrl.ai, app.adctrl.ai reads that choice and the Google Analytics and Meta cookies listed above to send the sign-up steps described in What we collect and why, without adding cookies of its own.

Your rights

Under the GDPR you can ask for access to your personal data, a copy of it in a portable format, correction, deletion or restriction of its use, and you can object to processing based on our legitimate interests. Email hello@adctrl.ai. We may need to confirm that the request comes from you, and we answer within one month. Never send passwords, tokens or customer lists by email.

If you are one of our customers' customers, for example someone in a customer list or a lead, the business that uploaded your data is the controller. Contact them first; we will help them answer you.

You can complain to the Danish Data Protection Agency, Datatilsynet, or the data protection authority where you live.

Children

AdCtrl is for businesses and adults. It is not meant for anyone under 18, and we don't knowingly collect their data.

Changes

We will update this page and its date when our data handling changes, and tell customers by email or in AdCtrl about material changes.