Last updated 16 November 2026
Privacy policy
1. Controller
Benjamin Will, trading as AdLibAPI.com, c/o MDC#1996, Welserstraße 3, 87463 Dietmannsried, Germany. Email: [email protected]. We have not appointed a data protection officer, as we are not required to.
2. Visiting the website
Hosting. The website, API and database run on servers of Hetzner Online GmbH in Germany, which processes data on our behalf. To deliver pages and keep the service secure, the servers process your IP address, the requested page, time, browser type and referring page. Legal basis: Art. 6(1)(f) GDPR (secure and stable operation). These access data are kept only briefly for troubleshooting and abuse prevention and are not combined with other data.
Domain and storage. Cloudflare, Inc. provides our DNS and stores archived ad images (Cloudflare R2, EU jurisdiction) that are served from media.adlibapi.com; when your browser loads such an image, Cloudflare processes your IP address to deliver it.
Free tools. When you use a free tool (for example the ad library link generator or the “is this brand running ads?” checker), we process the domain or page you enter and your IP address for a per-hour limit, held in memory only. Some tools use Cloudflare Turnstile to tell people from bots; Turnstile processes your IP address and browser signals for this check. Legal basis: Art. 6(1)(f) GDPR (preventing abuse of free tools).
3. Analytics
We use PostHog (PostHog Inc., data stored in the EU in Frankfurt) as our processor to understand how the website and dashboard are used: page views, clicks on buttons and links, the campaign parameters and referring site of the link you came from (utm_*, the referring domain and the first page of your visit), use of the price calculator, copied code samples, search terms in the documentation (shortened, with email addresses and keys removed), scroll depth, page load times and script errors, use of the demo and free tools (the company domain you look up and how many results it found), and in the dashboard which pages you open (overview, keys, usage, billing, playground), playground requests (endpoint, status, credits), copied keys (that you copied one, not the key) and the start and outcome of a checkout. If you came from an AI assistant (for example ChatGPT, Perplexity or Claude, recognised from the referring site or the link’s utm_source), we note which one. We never record what else you type into form fields, API keys or email addresses. Session replays are made only with your consent (below). Requests go through this website’s own domain (path /ingest); our server removes cookies and replaces your IP address with a pseudonym that changes every day before forwarding them, so PostHog never receives your IP address. PostHog’s own location lookup is switched off; instead our server adds the country your visit comes from, as Cloudflare determines it from your IP address (only the country, never a region, city or the address itself).
- Without your consent (default): nothing is stored on or read from your device. PostHog counts visits from the daily pseudonym, your browser type and our domain; the next day the same visitor counts as a new one. Legal basis: Art. 6(1)(f) GDPR (understanding and improving the website). You can object at any time (Art. 21 GDPR), for example by email.
- With your consent: if you accept in the consent bar, PostHog stores a random ID in a cookie (
ph_<project key>_posthog, for adlibapi.com and its subdomains, 1 year) and in local storage, so we can see which pages lead to sign-up and first use. After you sign in, the dashboard links this ID to a pseudonymous account ID, never your email address. We also record replays of your visits to the website and dashboard (the page layout, mouse movements, clicks and scrolling, as in a screen recording): everything you type into form fields is masked, API keys and your email address are left out of the recording entirely, and no console output, request headers or request contents are recorded; operator pages are never recorded. Replays help us find where pages are confusing or broken; PostHog keeps them for at most 30 days. Legal basis: § 25(1) TDDDG and Art. 6(1)(a) GDPR. You can withdraw at any time in the cookie settings at the bottom of every page; a running recording stops at once. - Browser privacy signals: if your browser sends Global Privacy Control or Do Not Track, we do not load PostHog at all.
- Product analytics for accounts: our servers record the main steps of the customer journey and send them to PostHog under a pseudonymous ID (
acct_plus a value derived from your internal account number with a secret key; no email address, no IP address, no API keys, no request contents): sign-up and login, API key created or disabled, first API request, each day with API use, API calls that failed (status and error code, endpoint, platform filter) or came back empty (endpoint, platform filter), at most ten of each per day and never what you searched for, 80 % and 100 % of the monthly credits used, checkout opened, completed or failed, credit packs bought, plan changes and failed renewals, watchlists created, changed (which setting, not its value) or deleted, Studio onboarding steps (the role and tools you picked), Studio searches (tool, platform, country, number of results, not the search terms) and switches between Studio and the API dashboard, webhook tests and webhook deliveries that failed for good, and AI apps connected via OAuth (the app’s name). With the account ID we store your plan, your sign-up date and the domain part of your email address (for exampleexample.com), never the full address. When you request a sign-in link, the first touch of your visit (campaign parameters, referring domain, first page, the AI assistant you came from, if any) is sent along (from our website to the sign-in page it travels in the link’s address, not in storage on your device); if the link creates your account, we keep it with the account and add it to the sign-up event. Nothing is stored on your device for this. Purpose: understanding where customers get stuck and improving sign-up, onboarding and payment. Legal basis: Art. 6(1)(f) GDPR; you can object at any time (Art. 21 GDPR), for example by email.
PostHog Inc. is based in the USA; access from there is covered by the EU standard contractual clauses.
4. Cookies
adlib_consent: your analytics choice, 180 days. Necessary to remember the choice (§ 25(2) TDDDG).adlib_session: keeps you signed in to the dashboard, 30 days, not readable by scripts;adlib_signed_inonly tells our pages that a session exists. Both are necessary for the service you request.adlib_flash_key: shows a newly created API key once, then is deleted.adl_did(cookie and local storage): a random device ID, set when you request a sign-in link, 1 year. Used only to prevent repeated free-plan sign-ups (section 5).- Only with your consent: PostHog’s cookie and local storage entry (section 3).
5. Account and sign-in
To create an account you give us your email address. We send sign-in links by email through Resend (Resend, Inc., USA) as our processor; a link is valid for 15 minutes. We store your email address, plan, credit balance, the dates you signed up and last used the service, and hashes (not the plain text) of your API keys and sessions. Legal basis: Art. 6(1)(b) GDPR (providing the service you signed up for). Resend processes data in the USA on the basis of the EU-U.S. Data Privacy Framework and standard contractual clauses.
Preventing repeated free sign-ups. The free credits are meant once per person. When you request a sign-in link, we therefore process your IP address and, from the sign-in form, a random device ID stored in your browser (adl_did) and a fingerprint of your browser (a hash over technical properties such as screen size, time zone, languages and how your browser draws a test graphic). Our server stores the device ID and fingerprint only as keyed hashes, and your IP address as a keyed hash plus, for 30 days, in plain text; it compares the hashes with earlier sign-ups. To review a match by hand, we also store the country your sign-up came from (as Cloudflare determines it from your IP address; only the country) and your browser and operating system with its main version (for example “Chrome 131 · macOS”, not the full user agent). We also check whether the email address belongs to a disposable-email service or its domain can receive email, and treat aliases of one mailbox (for example dots or a + suffix in Gmail addresses) as one address. If a new account matches an earlier one, it is created without the free credits; paid plans and credit packs are unaffected, and you can ask us to review the decision at any time. There is no other automated decision. Purpose: preventing abuse of the free plan. Legal basis: Art. 6(1)(f) GDPR; reading and storing the device ID and fingerprint on your device is strictly necessary for the sign-up you request (§ 25(2) no. 2 TDDDG). The plain IP address is deleted 30 days after sign-up; the hashes, country and browser are kept with the account for as long as it exists.
We send you emails about your account, security and billing, and about changes to these documents or the service that affect you. We do not send newsletters without your consent.
We also email you a short note with a first request if you have not used the API a day after signing up, a short question a few days after you tried the API on the free plan and then stopped (what you were looking for and what got in the way, with a few tips), and a reminder when you have used 80% or all of your monthly credits, with your options to continue. For this we use your email address, plan, sign-up date and usage. Legal basis: Art. 6(1)(f) GDPR (our and your interest in you being able to use the service without interruption). You can object at any time, free of charge, with the unsubscribe link in each of these emails or by writing to us; sign-in links and watchlist alerts you turned on are not affected.
6. Using the API
When you use the API, MCP server or dashboard, we process:
- Usage records: credits used per day and endpoint, for billing and quotas (kept 90 days in detail, monthly totals as long as your account exists).
- Request log: the newest 1,000 requests across all customers (method, path and query, status, the error message of a failed request, duration, account), for troubleshooting and support. For the newest 3,000 requests we also keep the request body and the answer for at most 3 hours, with API keys and webhook signing secrets masked. It contains no IP addresses and is overwritten continuously.
- Your configuration: watchlists, webhook URLs and signing secrets, batch jobs; webhook deliveries and batch results are deleted after 30 days. In AdLib Studio also your answers from onboarding (what you do, which tools you picked, an optional note), the brands and competitors you add, boards with the ads you save (a copy of the ad card: advertiser, image link, copy), saved searches and the history of your tool runs (tool, search terms, credits), which is deleted after 90 days. Onboarding answers and picked tools also go to product analytics (see above).
- Which advertisers you ask for: we count which advertisers customers request, per account and day, to decide which advertisers we archive daily. These counts are deleted after 90 days.
Legal basis: Art. 6(1)(b) GDPR, and Art. 6(1)(f) GDPR for troubleshooting and improving coverage.
7. Payments
Purchases are processed by Stripe through Stripe Managed Payments. Stripe acts as reseller and processes your payment and billing data as an independent controller under its own privacy policy, shown at checkout. We receive from Stripe your customer ID, plan, subscription status and purchase amounts, but never your card or bank details. Legal basis: Art. 6(1)(b) GDPR.
8. AI features
Some features are written by AdLib AI, which runs on language models of external providers. What goes to which provider depends on whether it contains your own words:
- Your own words, on paid plans: briefs, rewritten ad copy and the assistant send what you enter (a goal, notes, your questions) together with the ad data they draw on to Anthropic (Anthropic PBC, USA) as our processor. Under its commercial terms Anthropic does not use these inputs to train its models. Legal basis: Art. 6(1)(b) GDPR. Transfers to the USA are covered by the EU standard contractual clauses.
- Public data, and the assistant on the free plan: the analysis of an ad (its text, image and the text on it), suggestions of a brand’s competitors (from its public website and ads), and the free plan’s assistant (your questions and the data it looks up) go through OpenRouter (OpenRouter, Inc., USA) to freely available models. The providers of these models may store the inputs and use them to improve their models. Please do not enter personal or confidential information, such as details of your clients, into the assistant on the free plan. Legal basis: Art. 6(1)(b) GDPR for the assistant, Art. 6(1)(f) GDPR for analysing public ad data. Transfers to the USA are covered by the EU standard contractual clauses.
9. Support and internal notifications
When you email us, we process your message and contact details to answer it (Art. 6(1)(b) or (f) GDPR). For new sign-ups, purchases and reports submitted through the website, we send a short notification including the email address to a private Telegram chat used only by us (Telegram FZ-LLC, Dubai). Legal basis: Art. 6(1)(f) GDPR (reacting quickly to sign-ups, payments and issues).
10. People and companies in archived ads (Art. 14 GDPR)
Our archive contains ads from the public ad libraries of Meta, Google, YouTube, Google Play, TikTok, LinkedIn, Pinterest, X, Snapchat, the Apple App Store, Amazon and Microsoft Bing. Ads mostly concern companies, but they can contain personal data: the name of an advertiser who is a natural person, the names of payers and beneficiaries that EU law requires the platforms to publish, and people shown in ad images or videos. We collect only what the platforms publish without login, keep it as published with first and last seen dates, and do not combine it with other sources to build profiles of individuals.
Purpose and legal basis: making advertising transparent and searchable over time for research, journalism, compliance and market analysis, Art. 6(1)(f) GDPR. The data was made public by the platforms for exactly this kind of transparency. We keep archived ads without a fixed deletion date because the history is the purpose of the archive.
If you appear in an archived ad, you can object to the processing or ask for erasure at any time by emailing [email protected] with a link to the ad or the advertiser. We delete the ad or advertiser from our database and storage, including archived images and videos, unless overriding legitimate grounds apply, and we keep a short record of the deletion so the item is not collected again. So that customers can remove their own copies, we show the id of the deleted ad or advertiser and the hashes of deleted files to customers, without saying who asked or why.
11. Recipients and transfers
We share personal data only with the providers named above (Hetzner, Cloudflare, PostHog, Resend, Stripe, Anthropic, OpenRouter, Telegram) and with authorities where we are legally required to. We do not sell personal data. Where providers process data outside the EU/EEA, this happens on the basis of an adequacy decision (including the EU-U.S. Data Privacy Framework) or the EU standard contractual clauses.
12. Retention
We keep personal data only as long as needed for the purposes above. When you close your account, we delete or anonymise your account data within 30 days, except where commercial or tax law requires us to keep records (up to 10 years for booking records). Periods for specific data are given in the sections above.
13. Your rights
You have the right to access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and to object to processing based on Art. 6(1)(f) (Art. 21). You can withdraw consent at any time with effect for the future. Email us at [email protected]. You can also complain to a data protection supervisory authority, for example the Bavarian authority responsible for us: Bayerisches Landesamt für Datenschutzaufsicht, Promenade 18, 91522 Ansbach, Germany.
We do not make decisions based solely on automated processing that have legal or similarly significant effects on you (Art. 22 GDPR).