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.
- We are the controller for your account, sign-in, billing, support, security and website data, and for the record of changes we keep to protect the service.
- We are your processor for personal data inside the accounts you connect and for personal data you send through AdCtrl, such as customer lists, conversion uploads, audience members, lead answers and Page posts. We process it only on your instructions. The data processing agreement in our terms covers this.
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
- Account details. Your name, email address and, if you sign in with Google, your Google account identifier. If you sign in by email, we send you a one-time code. On the Agency plan, we store your team members' email addresses. We use this to create and secure your workspace and to send service emails, such as sign-in codes and notices when an AI app is connected or a provider connection is about to expire.
- Billing details. When you subscribe, Stripe collects your payment card, billing name and address, and VAT number if you give one. We give Stripe your email and workspace reference, and we store your Stripe customer and subscription references, plan, status and billing period. We never see or store your full card number.
- Trial records. To give each customer one free trial, we keep the workspace reference, a one-way hash of the sign-in email and the IDs of the ad accounts that used a trial.
- Provider connections. When you connect Google or Meta, we receive an access token and the details needed to check it: for Google, your account email and the permissions you granted; for Meta, the business that authorized AdCtrl, a system-user identifier, the permissions granted and when they expire. We use these only to make the requests you ask for.
- AI app connections. Which AI app you approved, for which workspace, and its short-lived access tokens.
- Data from your connected accounts. AdCtrl reads and changes only what your AI app asks for, in the accounts you selected. This can include account settings, campaigns, ad groups and ad sets, ads and creatives, budgets and bids, targeting and audiences, performance reports, images and videos, Facebook Page and Instagram details used for ads and posts, lead forms, product catalogs, conversion settings, keyword data, Google Analytics 4 reports and property settings, Search Console queries, pages and sitemaps, and Tag Manager tags, triggers, variables and versions. Most of this passes through: it is returned to your AI app and not stored, except in short caches (see below).
- Previews and change history. For each change, we store the preview, the values before the change, the confirmation from Google or Meta and the readback. These records can contain names, ad and post text, targeting and account IDs. We keep them so you can check what was changed and so AdCtrl never sends the same change twice.
- Customer data you send to Google or Meta. See the next section.
- Feedback and support. If you send feedback through your AI app, we store only the message you wrote. If you email us, we keep the correspondence as long as needed to help you.
- Website and sign-up measurement, only if you agree. If you accept cookies on adctrl.ai, we measure how the website is used and whether our own ads work: pages viewed, how far you scroll, which sections you see and for how long, the links, buttons, pricing options, questions and videos you use, page load speed and errors, and which ad or link brought you (campaign tags and ad click IDs). With your choice, app.adctrl.ai also reports these steps: joined the early-access list by email, signed in, created a workspace, started or finished connecting Google or Meta (with the product, such as Google Ads or GA4), connected an AI app and first used AdCtrl from it. These measurement events contain no email address, name, workspace name, ad account, advertising data or anything you type. Events sent to Meta also carry your IP address and browser type, as Meta requires, and a sign-up carries a one-way hash of your workspace reference. Microsoft Clarity records how pages are scrolled and clicked on adctrl.ai with all text and form fields masked; it does not run on app.adctrl.ai. See Cookies for the tools, cookies and retention.
- Security and technical data. Our servers process standard request data such as IP address and browser type to deliver the service and protect it from misuse. Error alerts contain only an error code and the software version, never account data or conversation content.
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.
- Customer Match and Meta audience members (adding or removing people from an audience) and conversion uploads (Google offline conversion imports and adjustments, Meta Conversions API events). AdCtrl accepts email addresses, phone numbers and external customer IDs only as SHA-256 hashes and rejects them in plain text. Click IDs, Meta lead IDs, order IDs and event details are sent as given. The upload is held encrypted with its own key, which exists only in the running service's memory and is never written to the database or to backups. The key is destroyed as soon as the upload has been sent, cancelled or has expired, and always within 1 hour. After that the upload can't be read again, even from a backup.
- What we keep after an upload. A short record so you can see what was sent and so nothing is sent twice: the number of entries, the identifier and event types, a fingerprint of the batch and the provider's response. For Google conversion imports, this record also holds the hashed identifiers and a fingerprint of each order ID.
- Lead answers from Meta lead forms are read only for the form, fields and time period you approve (at most 24 hours). They are filtered on our server, returned to your AI app and not stored. The approval itself (Page, form, field names and expiry) is kept until it expires.
- Images and videos you upload for ads are held for at most 1 hour, sent to Google or Meta and then discarded. We keep the file's name, size and fingerprint in the change record.
- Facebook Page posts you publish or delete through AdCtrl are sent to Meta. The post text and Meta's post ID stay in the change history.
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
- Contract: to provide AdCtrl, run your workspace, process payments and carry out your requests.
- Legal obligation: to keep accounting records as Danish bookkeeping law requires.
- Consent: for website and sign-up measurement and our ad measurement (Google Analytics, Microsoft Clarity, Google Ads, Meta). You can withdraw it at any time in cookie settings.
- Legitimate interests: to keep the service secure, prevent abuse of free trials, keep a reliable record of changes, prevent duplicate uploads, answer support requests and improve AdCtrl from feedback.
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:
- We use Google user data only to provide and improve the user-facing features you use in AdCtrl.
- We transfer it only to provide those features: to your chosen AI app when you ask for it, and to the service providers listed below. We also transfer it where the law requires, for security, or as part of a merger or acquisition with your notice.
- We don't use it for advertising, including retargeting, personalized or interest-based ads.
- We don't sell it, and we don't use it to develop, improve or train generalized AI or machine-learning models.
- Our staff don't read it unless you give us permission (for example in a support request), it is needed for security or to investigate abuse, the law requires it, or it is aggregated and anonymized for internal operations.
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
- Hetzner Online GmbH (Germany) hosts the AdCtrl service and its database on a server in Helsinki, Finland.
- Stripe processes payments, subscriptions and invoices. Stripe also processes some payment data for its own purposes, such as fraud prevention and legal compliance, under its own privacy policy.
- Google Workspace sends our email, including sign-in codes, service notices and internal error alerts.
- Vercel hosts the public website adctrl.ai. It processes no AdCtrl account data.
- Google (Google Tag Manager and Google Analytics) processes website and sign-up measurement for us, only after your consent.
- Microsoft (Clarity) processes masked session recordings and heatmaps of adctrl.ai for us, only after your consent.
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
- Minutes: sign-in codes (10 minutes), AI app access tokens (15 minutes), report caches (10 minutes) and account and keyword caches (1 hour).
- At most 1 hour: uploaded customer lists, conversion events, images and videos. After that they can't be read by anyone, including us.
- Never stored: lead answers.
- Up to 30 days: AI app refresh tokens, and feedback you send through your AI app.
- Up to 90 days: records of Meta conversion uploads and Google conversion imports, so the same events aren't sent twice. Records of uploads that were never sent are deleted after 7 days.
- Website and sign-up measurement: if you accepted cookies, app.adctrl.ai keeps the Google Analytics and Meta browser identifiers, browser type, campaign tags and ad click IDs from your sign-up for up to 90 days, only to report your first use of AdCtrl from your AI app; if you withdraw consent, they are deleted the next time you sign in or connect an account, and otherwise expire after 90 days. Google Analytics 14 months; Microsoft Clarity recordings 30 days and heatmaps 13 months; Google Ads and Meta under their own terms. Cookie lifetimes are listed under Cookies.
- While your workspace exists: your account, team, connections, account selections, previews and change history, including records of sent audience changes and Google conversion adjustments. Disconnecting a provider deletes its connection. Cancelling your plan deletes nothing, so you can come back; ask us and we delete it all (see disconnect and deletion).
- After deletion: invoices for 5 years, as Danish bookkeeping law requires, and a trial record (hashed email, workspace reference and ad account IDs) so the free trial can be used only once. We may also keep the record of a change whose outcome Google or Meta never confirmed until it has been checked, so it can't be sent twice.
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.
| Cookie | Set by | Purpose | Lifetime | Needs consent |
|---|---|---|---|---|
| adctrl_consent | AdCtrl | Remembers your cookie choice | 6 months | No, strictly necessary |
| adctrl_attr | AdCtrl | Which campaign or ad link brought you, so a later sign-up can be credited to it | 90 days | Analytics or marketing |
| _ga, _ga_D17LFWTPGE | Google Analytics | Tell visits and sessions apart | 13 months | Analytics |
| _clck, _clsk | Microsoft Clarity | Connect page views of one visit for masked recordings and heatmaps | 1 year; 1 day | Analytics |
| _gcl_au, _gcl_aw, _gcl_gb | Google Ads | Link a visit to the Google ad that was clicked | 90 days | Marketing |
| _fbp, _fbc | Meta | Link a visit to a Meta ad click and measure our ads | 90 days | Marketing |
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.