Privacy Policy for Ad-Supported Sites: What to Include
Why Ad Networks Care About Your Privacy Policy
When you put ads on a site, you're inviting other companies to set cookies and collect data from your visitors. Google, the ad exchanges it works with, and any other network you run all read and write identifiers in your readers' browsers. Your privacy policy is where you tell readers that's happening. Ad networks want to see it because their own legal position depends on publishers disclosing what their ad code does.
That's why a missing or broken privacy policy is one of the easiest ways to get turned down. It isn't a judgment call like "content quality". Either the page exists and says the right things, or it doesn't. The good news is that it's also one of the easiest things to fix, as long as you know what the policy actually has to say for an ad-supported site. A generic template often doesn't say it.
One note before going further: this is a practical guide to what ad networks ask for, not legal advice. Privacy law varies by country and by state, and if you collect sensitive data, sell products, or run a membership site, it's worth having a lawyer look at your policy.
What AdSense Specifically Requires
Google is unusually clear about this. The AdSense Program policies require publishers to have a privacy policy that tells users third parties may be placing and reading cookies on their browsers, or using web beacons, as a result of ad serving. Google's help article Required content spells out what that policy should cover. In plain terms, your policy needs to say:
- Third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to your website or other websites.
- Google's use of advertising cookies lets it and its partners serve ads to your users based on their visits to your site and/or other sites on the internet.
- Users can opt out of personalized advertising by visiting Google's Ads Settings. As an alternative, they can opt out of some third-party vendors' cookies for personalized advertising at aboutads.info.
- Other vendors and ad networks that serve ads on your site, if you haven't opted out of third-party ad serving in AdSense. You're expected to name them, link to their websites, and tell users they can opt out with those vendors.
The last point is the one most people miss. AdSense isn't just Google's own ads. Unless you've changed the setting, certified third-party ad networks can also bid on your inventory through AdSense, so Google expects your policy to acknowledge them. The Required content page links to its own help articles on that list and on opting out of third-party ad serving. Read those rather than guessing which companies to name.
You don't have to copy Google's wording word for word. You do need to cover each of those points in language a reader can understand, and the opt-out instructions have to point somewhere real. A sentence like "we may use cookies" doesn't meet the requirement. It doesn't mention third-party vendors, it doesn't mention Google, and it doesn't tell anyone how to opt out.
Clause → why it's needed
| Clause | Why it's needed |
|---|---|
| Third-party vendors, including Google, use cookies | Named in AdSense's Required content page |
| Google's use of advertising cookies | Tells readers Google and partners target ads across sites |
| Opt-out via Ads Settings or aboutads.info | Readers need a working way to turn off personalized ads |
| List of other ad networks and vendors | Required if third-party ad serving is on; reviewers check it matches your tags |
| What you collect and why | Expected by privacy laws such as GDPR and California's |
| Contact details | Readers and regulators need a way to reach you |
| Last updated date | Shows the policy is maintained, not abandoned |
What Else a Good Policy Covers
The AdSense disclosures are the floor. A policy that only contains those four bullet points will look thin, and it won't cover the other things your site probably does. Walk through your own setup and write down everything that touches visitor data:
- Analytics. If you run Google Analytics or a similar tool, say so, say what it measures, and link to the provider's own privacy information.
- Forms and email. Contact forms, comment systems and newsletter sign-ups collect names and email addresses. Say what you collect, where it's stored (for example, your email service provider), and how someone can unsubscribe or ask for deletion.
- Embeds. YouTube videos, social media posts and maps can set their own cookies when they load. A short line acknowledging that is better than pretending they don't.
- Affiliate links. Affiliate programs often track clicks with cookies. If you use them, mention it.
- Retention. How long do you keep comments, form submissions and email lists? "Until you ask us to delete it" is a valid answer if it's true.
- Reader rights. Depending on where your visitors are, they may have rights to access, correct or delete their data, or to opt out of the sale or sharing of personal information. Explain how to make a request.
- Contact. A real email address or contact form. Not just a name.
Write it in the same voice as the rest of your site. A policy written in plain English that accurately describes your setup reads as more trustworthy than three thousand words of boilerplate that could belong to anyone.
What Ad Networks Look At During Review
No network publishes a full checklist of how its reviewers assess a privacy policy, so it's best to think about what a reviewer can actually see when they open your site. Most of it comes down to a few questions:
- Can I find it? The policy should be linked from every page, usually in the footer. A policy that exists at a URL nobody links to might as well not exist.
- Does it load? A 404, a placeholder page, or a policy that only appears after a cookie banner is dismissed is a problem.
- Does it mention advertising? For AdSense, the cookie, Google, and opt-out disclosures above. Other networks generally expect the same idea: a clear statement that third parties serve ads and use cookies to do it.
- Does it match what the site does? If the policy lists networks that aren't on the site, or the site loads ad tags the policy never mentions, that tells a reviewer nobody is maintaining it.
- Does it look like the rest of a real site? Privacy policy, contact page, and about page together signal that a real person or business stands behind the site. Our AdSense approval guide covers the other pages reviewers expect.
The managed networks and higher-tier platforms tend to go further. Some supply their own privacy text or an embeddable list of their demand partners and ask you to include it. If your network gives you that, use it. They know their partner list better than you do, and their version updates when the list changes.
If you want a quick check, AdGateScore's site scan looks for a linked privacy policy among its policy checks, alongside things like SSL, ads.txt and a cookie banner. It can tell you whether a policy is linked. It can't tell you whether your wording is right. That part is on you.
Cookie Consent Is a Separate Requirement
A privacy policy describes what happens. Consent is about getting permission before it happens. They're related, and people often mix them up, but having one doesn't cover you for the other.
If you have visitors in the EEA or the UK, Google's EU user consent policy applies on top of the privacy policy requirement, and Google requires a certified consent management platform for those visitors. A good privacy policy won't satisfy that. A consent banner won't replace a privacy policy either. The details are in our guide to consent management for GDPR-compliant ad serving, so this post won't repeat them. What matters here is that your policy should describe your consent setup accurately: which tool you use, what readers are asked, and how they can change their choice later. A link from the policy back to your consent settings makes that easy.
US state privacy laws work differently. California, for example, centres on a right to opt out of the sale or sharing of personal information, and ad cookies can count as sharing. If you have meaningful US traffic, check whether you need an opt-out link and say how it works in your policy.
Common Mistakes That Get Flagged
Generator text that names the wrong networks
Free privacy policy generators are fine as a starting point. The problem is that people tick every box, or none, and publish whatever comes out. You end up with a policy that mentions three ad networks you've never used and leaves out the one you actually run. Edit the output against what's really on your pages. If it says "we use Mediavine" and you're applying to Ezoic, a reviewer will notice.
An outdated vendor list
Your policy was accurate when you wrote it. Then you added a second network, switched analytics tools and installed a newsletter pop-up. A year later, half of it is wrong. This is the most common way a policy drifts, and it's why the update process below matters more than the first draft.
No way to contact you
A privacy policy that tells readers they have rights but gives them no way to use them is incomplete. Add an email address or link your contact page. If you use a contact form, make sure it actually delivers.
Not linked in the footer
Some themes drop the footer menu on certain templates, or the policy is linked on the homepage only. Check a blog post, a category page and a mobile view. The link should be on all of them.
No date
A "last updated" line costs nothing and tells readers and reviewers that the policy is current. Change it only when you actually change the policy.
Keeping the Policy Current When You Change Networks
Most publishers don't stay with one ad setup forever. You start with AdSense, add a second network for extra fill, then move to a managed platform once traffic grows. Each change affects the companies loading code on your pages, which means each change should touch your privacy policy. Make it part of the switch, not something you remember later.
When you add, remove or change an ad network
- Read the network's requirementsLook for required privacy text or a partner list embed
- Update the vendor sectionAdd the new network, remove any you've dropped
- Check opt-out linksEvery named vendor should have a working opt-out or privacy link
- Update ads.txt and consent settingsSame vendors, same change, same day
- Change the "last updated" dateOnly after the content actually changes
- Spot-check the live siteFooter link on several page types, tags match the policy
The highlighted step is the one that saves trouble later. Your ads.txt file lists who's authorized to sell your inventory, your consent tool lists the vendors readers can accept or reject, and your privacy policy tells readers who those vendors are. If you update one and not the others, they disagree, and a reviewer comparing them will see it. Our ad network switching guide covers the rest of the move, from running networks side by side to removing old tags.
It's also worth reviewing the policy on a schedule even if nothing has changed on purpose. Plugins and themes add scripts quietly. Once or twice a year, open your site with the browser's developer tools, look at which third-party domains load, and compare that list with your policy.
A Practical Way to Write or Fix Yours
If you're starting from scratch, or your current policy came from a generator you've never reread, here's an order of work that keeps it accurate:
- List what's on the site. Ad networks, analytics, forms, email tools, embeds, affiliate programs, and your consent tool. Check the live pages, not your memory.
- Write the advertising section first. Cover each AdSense required point, then name every other ad vendor with a link and an opt-out route.
- Add the rest. What you collect, why, how long you keep it, who it's shared with, reader rights, and how to contact you.
- Link it everywhere. Footer on every template, plus your contact and about pages.
- Read it as a stranger would. Would someone who's never heard of your site understand who you are, what's being collected, and how to opt out?
If you've already been rejected and aren't sure the policy was the reason, paste the rejection message into the rejection decoder to see what it usually points to. A missing or incomplete privacy policy is a quick fix compared with most rejection reasons, so make sure it's not the thing holding you back before you spend weeks rewriting content.
We build AdGateScore, the ad network readiness scanner. Our articles draw on the requirements each network publishes and on what our scans find.