Skip to content
Ad Radar
How it works Features Pricing FAQ
Log in

Legal

Privacy Policy

What Ad Radar collects when you use the website, the web app and the Chrome extension, why we collect it, who helps us process it, and what you can ask us to do with it.

Last updated October 8, 2026
Privacy Terms
On this page
  1. The short version
  2. Who we are and what this covers
  3. Information we collect
  4. The Chrome extension
  5. API tokens and AI assistants
  6. Public ad data
  7. How we use information
  8. Cookies and local storage
  9. Advertising and measurement
  10. How we share information
  11. Service providers
  12. Retention and deletion
  13. Security
  14. Your choices and rights
  15. California residents
  16. Other US states
  17. Visitors from the EEA and UK
  18. International transfers
  19. Children
  20. Changes to this policy
  21. Contact

01The short version

In plain terms

  • We collect what we need to run your account: your email, your name if you give it, your workspace, and what you do in the app.
  • Payments are handled by Stripe. We never see or store your full card number.
  • The Chrome extension reads an ad only when you click Save on it, and nothing else on Facebook.
  • We don't sell your personal information for money.
  • To measure and improve our own ads, this website, the checkout and the page you see after checkout use the Meta Pixel and the Meta Conversions API. What you do inside the app (boards, searches, saved ads) is never sent to Meta. How to opt out.
  • You can ask us for a copy of your data or to delete it at privacy@ad-radar.dev.

02Who we are and what this covers

Ad Radar ("Ad Radar", "we", "us", "our") provides a subscription service that tracks publicly available Meta ads, analyzes them and helps marketing teams find the ones that are working. This policy applies to:

  • the website at ad-radar.dev (the "Site");
  • the web app at app.ad-radar.dev, including shared boards, in-app alerts, the API and the MCP server (the "App");
  • the Ad Radar Chrome extension (the "Extension").

Together we call these the "Service". For personal information about you as a user, Ad Radar is the business (under US state privacy laws) and the controller (under the GDPR) responsible for it. Your use of the Service is also governed by our Terms of Service.

03Information we collect

Information you give us

  • Account data. Your email address and, if you provide it, your name. We don't use passwords: you sign in with a link we email to you.
  • Workspace and team data. Your workspace name, the email addresses of people you invite, their role and whether they accepted.
  • Content you create. Boards, ads you save to them, brands you ask us to track, alert and notification settings, and the share links you create.
  • Billing data. When you subscribe, Stripe collects your payment details. We receive from Stripe a customer and subscription identifier, your billing email, plan, payment status and billing country or postal code where needed for tax. We do not receive or store full card numbers or security codes. Apple Pay and Google Pay payments are also processed by Stripe.
  • Messages. What you send us when you email us, and our replies.

Information collected automatically

  • Usage data. The features and pages you use in the App, the searches you run, the ads and boards you open, the ads you save, and when you do so. We use it to operate the Service, enforce plan limits and improve the product.
  • API and MCP usage. Which token made a request, the endpoint or tool called, and when.
  • Technical data. IP address, browser and device type, and request logs recorded by our hosting provider when you load the Site or the App.
  • Advertising measurement. On the Site, at checkout and on the page shown after checkout, the Meta Pixel and the Meta Conversions API record page visits and checkout events, as described in Advertising and measurement.
  • Campaign attribution. If you arrive on the Site from a link that carries campaign parameters (for example utm_source, utm_campaign, fbclid, gclid or msclkid), the Site keeps those parameters, the page you landed on, the referring page and the date of your first visit in your browser for up to 90 days. If you subscribe, they are passed to checkout and stored with your subscription record, so we can tell which channels bring customers. We don't use these parameters to build a profile of you. What the Meta Pixel collects is described in Advertising and measurement.

We don't collect precise geolocation, and we don't ask for sensitive information such as government IDs, health data or financial account credentials.

04The Chrome extension

The Extension works only on the Meta Ad Library (facebook.com/ads/library) and on the Ad Radar settings page in the App.

  • What it reads. When, and only when, you click Save on an ad, the Extension reads the public information shown on that ad card: Library ID, advertiser page name and link, ad text, headline, description, call to action, landing page link, start date and the image or video links. It does not read anything else on Facebook: not your feed, your messages, your profile, or ads you don't save.
  • What it sends. That ad data, plus the board you picked, goes to Ad Radar's servers (app.ad-radar.dev) over HTTPS, authenticated with your personal API token. We then download the ad's images and video and store copies, so they remain viewable after Facebook's links expire.
  • What it stores in your browser. Your API token, your account email, name and workspace name, and the list of ads you saved with the board each went to (so the button can show "Saved"). To place the Save button the Extension looks for the Library ID on each ad card; this stays in your browser. This stays in the Extension's local storage on your device and is deleted when you disconnect or remove the Extension.
  • What it doesn't do. It does not track your browsing, does not include analytics or advertising code, does not run remote code, and does not send data to anyone other than Ad Radar.

05API tokens and AI assistants

Personal API tokens let the Extension, an AI assistant connected through our MCP server, or your own scripts access your Ad Radar account. We store only a cryptographic hash of each token, plus when and how it was last used. You can revoke a token at any time in Settings โ†’ API.

When you connect an AI assistant or another third-party tool to Ad Radar, the data that tool retrieves with your token is handled by that tool under its own terms and privacy policy. You choose what to connect, and you can revoke access at any time.

06Public ad data

Most of what you see in Ad Radar is advertising that businesses have chosen to publish and that Meta makes publicly available in its Ad Library: ad copy, creatives, advertiser page names, dates and similar details. We collect it, store copies of the media, and add our own analysis on top, such as transcripts, tags, scores and spend estimates.

  • If an ad you save is not yet in Ad Radar, we store it, with its media, privately in your workspace and analyze it (transcript and tags) for you. It becomes part of our public database only if our own collection later finds the same ad from a brand we track. Your boards, and the fact that you saved it, are never shown outside your workspace.
  • Public ads can include the name, image or voice of people who appear in them, or the name of an advertiser who is an individual. We process this information because it is part of published advertising, for the purpose of advertising research and analysis. If you appear in an ad shown in Ad Radar and want to ask about it, or object to its processing, write to privacy@ad-radar.dev.

07How we use information

  • To create and secure your account, sign you in and keep you signed in.
  • To provide the Service: boards, brand tracking, search, shared boards, alerts, the API, the MCP server and the Extension.
  • To process payments, manage your subscription and meet tax and accounting obligations.
  • To send you the emails the Service depends on: sign-in links, team and client invitations, and billing notices.
  • To answer your requests and provide support.
  • To measure which marketing channels bring customers, using the attribution data described above.
  • To measure and optimize our advertising on Meta's platforms (Facebook and Instagram), as described in Advertising and measurement.
  • To understand how the Service is used and improve it, and to enforce plan limits and fair use.
  • To prevent fraud and abuse, protect the Service and its users, and comply with the law.

We don't use your personal information, or the content of your workspace, to train third-party AI models.

08Cookies and local storage

We use a small number of first-party cookies and browser storage entries. Most are needed for the Service to work. The two Meta cookies below are for advertising measurement: they are set by the Meta Pixel on the Site and can be read by the App's post-checkout page. The App itself loads no other third-party analytics or tracking code.

NameWhereWhat it doesHow long
ar_sessionApp (cookie)Keeps you signed in. Signed and HTTP-only, so scripts on the page can't read it.3 days, renewed while you use the App
ad-radar-langApp (cookie)Remembers the interface language you picked.Until you change it or clear cookies
ar_attributionSite (local storage)Keeps the campaign parameters of your first visit so they can be passed to checkout.90 days
_fbpSite and App (cookie on ad-radar.dev)Set by the Meta Pixel. A random browser identifier Meta uses to connect visits and checkouts to our ads.90 days, renewed on each visit
_fbcSite and App (cookie on ad-radar.dev)Set by the Meta Pixel only when you arrive from a Meta ad. Stores the ad click identifier (fbclid).90 days
Stripe cookiesCheckout and billing portalSet by Stripe on its own pages for payment processing and fraud prevention.See Stripe's cookie policy

The Site loads its icon set from a public content delivery network, which, like any web server, receives your IP address when your browser requests the file. You can block or delete cookies in your browser settings; if you block the session cookie, you won't be able to sign in. Blocking or deleting the Meta cookies doesn't affect the Service. The Site and the App may set the Meta cookies _fbp and _fbc on ad-radar.dev and app.ad-radar.dev. The Site doesn't respond to browser signals such as Global Privacy Control or "Do Not Track"; see Advertising and measurement for how to opt out.

09Advertising and measurement

We advertise Ad Radar on Facebook and Instagram. To know which ads bring customers, and to let Meta show our ads to people more likely to find Ad Radar useful, we use two tools from Meta Platforms, Inc. ("Meta"):

  • The Meta Pixel, a script that runs on the Site (ad-radar.dev) and on the page shown after you complete checkout in the App.
  • The Meta Conversions API, which sends checkout events from our servers to Meta, so they're counted even when the browser blocks the Pixel.

What is shared with Meta

  • The pages you visit on the Site, and when you view the pricing section.
  • That you started a checkout (the plan and its price) and, if you subscribe, that you completed it.
  • If you are signed in when you start a checkout, and when you subscribe: your email address, your name and an identifier of your account, in hashed form (SHA-256), so Meta can match the checkout to an ad you saw. We never send them in readable form.
  • When you subscribe, the name, phone number and billing location (city, state, ZIP code, country) you give at checkout, if any, in hashed form (SHA-256).
  • Your IP address and your browser's user agent.
  • The Meta cookies _fbp and _fbc, and the ad click identifier (fbclid) if you arrived from a Meta ad.

What you do inside the App is not shared with Meta: your boards, searches, saved ads, tracked brands, workspace, team and API activity stay with us. The Extension sends nothing to Meta.

Why

To measure how our ads perform, count the customers they bring, and let Meta optimize the delivery of our ads. Meta receives this data under its own terms and may also use it as described in the Meta Privacy Policy, for example to improve its ad delivery. If you are signed in to Facebook or Instagram, Meta may also read its own cookies on its domains when the Pixel loads.

How to opt out

  • Meta's settings. Control how Meta uses activity from other websites to show you ads in your Meta ad preferences.
  • Your browser. Block or delete third-party and advertising cookies in your browser settings, or use an ad or tracker blocker. The Site and the App keep working normally.
  • Ask us. Email privacy@ad-radar.dev and we'll stop sending your checkout events to Meta.

10How we share information

We don't sell your personal information for money. We share it only in these cases:

  • Service providers that host, store, bill, email or compute for us, under contracts that limit their use of the data to providing services to us. They're listed in the next section.
  • Meta, for advertising measurement on the Site and after checkout, as described in Advertising and measurement. Some US state laws call this "sharing" for cross-context behavioral advertising or "targeted advertising".
  • Your workspace. Members of your workspace see the boards, saved ads, tracked brands and settings of that workspace, and the names and emails of the other members.
  • Share links. Anyone who has a share link you created can see the board it points to, until you turn the link off.
  • Tools you connect. Data retrieved with your API token by the Extension, an AI assistant or your own scripts.
  • Legal reasons. When we believe in good faith that disclosure is required by law, a court order or a valid legal request, or is needed to protect the rights, property or safety of Ad Radar, our users or others.
  • Business transfers. If Ad Radar is involved in a merger, acquisition, financing or sale of assets, information may be transferred as part of that transaction, subject to this policy.
  • With your consent, or at your direction.

11Service providers

These are the providers that process data to run the Service and to measure our advertising.

ProviderWhat they do for usData involved
VercelHosting of the Site and the AppRequest logs, IP address, all data served by the App
SupabaseDatabaseAccount, workspace, billing status and usage data
Cloudflare (R2)File and media storageCopies of public ad media and files the Service stores
StripePayments, subscriptions, invoices and taxBilling and payment details, attribution parameters
ResendSending emailEmail address, name, email content (sign-in links, invitations)
OpenAIAI features: transcription and analysis of ad content, and searchPublic ad content and the text of searches you run; never your account details
Other AI model providersTranscription, tagging and scoring of adsPublic ad content only
Meta PlatformsAdvertising measurement: Meta Pixel and Conversions APIPages visited on the Site, checkout started and completed, hashed email, account identifier, name, phone and billing location, IP address, user agent, Meta cookies
ApifyCollecting public ad data from the Meta Ad LibraryAdvertiser identifiers and public ad content only

We may change providers as the Service evolves. You can ask for the current list at privacy@ad-radar.dev.

12Retention and deletion

  • Account and workspace data is kept while your account exists. If you cancel your subscription, your account is kept so you can come back, unless you ask us to delete it.
  • Deletion requests. Email privacy@ad-radar.dev from the address on your account and we'll delete your account and your workspace data within 30 days. Copies in backups are removed on the normal backup cycle.
  • Billing records are kept for as long as tax and accounting laws require, even after your account is deleted.
  • Request logs are kept for a short period for security and troubleshooting, then deleted.
  • Data sent to Meta is kept by Meta under its own terms. The _fbp and _fbc cookies expire after 90 days unless renewed by a new visit.
  • Extension data stored in your browser is deleted when you disconnect or remove the Extension.
  • Public ad data and our analysis of it are not tied to you and may be kept after your account is deleted.

We may keep information longer where needed to resolve disputes, enforce our agreements or comply with a legal obligation.

13Security

Traffic to the Site, the App and the API is encrypted with HTTPS. Session cookies are signed and HTTP-only. API tokens are stored as hashes, and access to production systems is limited to the people who operate Ad Radar. No system is completely secure, so we can't guarantee absolute security. If we learn of a breach that affects your personal information, we'll notify you as required by law.

14Your choices and rights

  • Access and export. Ask for a copy of the personal information we hold about you.
  • Correction. Ask us to fix inaccurate information.
  • Deletion. Ask us to delete your account and personal information.
  • Alerts. Alerts show up only in the App, never by email. Turn them off in Settings โ†’ Notifications. Service emails such as sign-in links and billing notices can't be turned off while you have an account.
  • Advertising measurement. Opt out with your Meta ad preferences, your browser settings or by email, as described in Advertising and measurement.
  • Tokens and integrations. Revoke API tokens in Settings โ†’ API, and remove the Extension at any time.

To make a request, email privacy@ad-radar.dev. We'll verify your request by confirming it from the email address on your account, and we won't discriminate against you for exercising any of these rights.

15California residents

This section applies to California residents under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, the "CCPA").

What we collected in the last 12 months

  • Identifiers: name, email address, IP address, account and token identifiers.
  • Commercial information: subscription plan, payment status and billing history.
  • Internet or other electronic network activity: usage of the Service, searches, API and MCP requests, campaign attribution parameters, pages visited on the Site and Meta cookie identifiers.
  • Professional or employment-related information: the workspace you belong to and your role in it.
  • Inferences: none. We don't build profiles about you. Meta may draw its own inferences from the data it receives, under its own policy.

We collect this information from you, from your use of the Service, from Stripe and from Meta's measurement tools. We use it for the business purposes described in How we use information, and disclose it for those purposes to the service providers listed above. We keep it for the periods described in Retention and deletion. We don't collect sensitive personal information as defined by the CCPA, apart from account sign-in credentials, which we use only to let you sign in.

Sale and sharing

We do not sell personal information for money. Through the Meta Pixel and the Meta Conversions API, we disclose identifiers (IP address, cookie identifiers, and hashed email, account identifier, name, phone and billing location), internet activity on the Site, and checkout events to Meta for advertising measurement. This may count as "sharing" for cross-context behavioral advertising under the CCPA. We have no actual knowledge of selling or sharing the personal information of consumers under 16. You can opt out of this sharing by emailing privacy@ad-radar.dev. See Advertising and measurement for the other options.

Your rights

You have the right to know what personal information we collect, use and disclose; to access it; to correct it; to delete it; to opt out of its sale or sharing; to limit the use of sensitive personal information; and not to be discriminated against for exercising these rights. To exercise them, email privacy@ad-radar.dev. We'll confirm receipt within 10 business days and respond within 45 days, which the law allows us to extend once by another 45 days if we tell you why. You can use an authorized agent; we'll ask the agent for proof of authorization and may ask you to confirm your identity directly.

16Other US states

Depending on where you live, including Colorado, Connecticut, Virginia, Utah, Texas, Oregon and other states with comprehensive privacy laws, you may have the right to confirm whether we process your personal information, to access, correct and delete it, to get a portable copy, and to opt out of targeted advertising, sale or profiling with significant effects. We don't sell personal information for money or profile you in that way. Our use of the Meta Pixel and Conversions API to measure and optimize our ads may count as targeted advertising under some of these laws; you can opt out by email, as described in Advertising and measurement. To make a request, email privacy@ad-radar.dev. If we decline your request, you can appeal by replying to our decision with "Appeal" in the subject line; we'll answer within the time your state's law requires, and if you're not satisfied you can contact your state attorney general.

17Visitors from the EEA and UK

Ad Radar is built for the US market, but if you use it from the European Economic Area, the United Kingdom or Switzerland, the GDPR (or the UK GDPR) gives you additional protections.

Legal bases

  • Contract: to provide the Service you subscribed to, including your account, billing and service emails.
  • Legitimate interests: to secure and improve the Service, measure marketing channels and our advertising, prevent abuse, and analyze publicly available advertising. We balance these interests against your rights, and you can object at any time.
  • Legal obligation: to keep billing records and respond to lawful requests.
  • Consent: where we ask for it. You can withdraw consent at any time.

Your rights

You can ask to access, correct, delete or port your personal data, to restrict its processing, and to object to processing based on legitimate interests. Email privacy@ad-radar.dev; we answer within one month. You also have the right to lodge a complaint with your local data protection authority.

18International transfers

Ad Radar and its service providers operate mainly in the United States. If you use the Service from outside the US, your information will be transferred to and processed in the US, where privacy laws may differ from those in your country. Where the law requires it, we rely on appropriate safeguards for these transfers, such as the European Commission's Standard Contractual Clauses included in our providers' data processing terms.

19Children

Ad Radar is a business tool for adults. It is not directed to children, and we don't knowingly collect personal information from anyone under 16. If you believe a child has given us personal information, contact us and we'll delete it.

20Changes to this policy

We'll post any change to this policy on this page and update the date at the top. If a change is material, we'll also tell you by email or in the App before it takes effect.

21Contact

Questions about this policy or your data go to the privacy address. Everything else goes to the general one.

Privacy requestsprivacy@ad-radar.dev Everything elsehello@ad-radar.dev

© 2026 Ad Radar

Privacy Terms Contact Log in