Legal pages never carry AdSense

Privacy and Cookies both say legal pages are outside AdSense inventory. About’s funding section agrees in company voice: ads do not appear on Home, About, legal pages, or the journal listing. Hostnames says the ads script stays off legal pages and that the split is enforced in code, not as a caption. This essay is privacy writing about that exclusion as its own job. It is not a remake of short-posts-and-listings gates, not a full eligible-inventory tour, and not a claim that a page without units is a page without any Google-related markup. Notice is still not a consent management platform. The exclusion still has to mean something a reviewer can check.

## What the legal documents actually exclude

Privacy Policy section 4 lists where Google AdSense may appear on www.oernoe.com: selected substantial publisher pages, including named guides, How-To, and substantial journal articles. The same section lists where AdSense is not loaded: the homepage, About, login or signup screens, protected application pages, legal pages, error pages, the journal index, short or promotional journal posts, the guides index, editorial standards, or Oernoe service subdomains.

Cookie Policy section 3 repeats the exclusion list with Team and Contact named beside legal pages, indexes, login screens, application pages, error pages, and service subdomains such as Search, Chat, Drive, Docs, Health, Tracker, and Account. Application shells such as /mail, /console, and /dashboard send a noindex header and do not load ads. Cookie Policy section 3a then names eligible inventory: How-To; finished guides including How Search works, Search queries and Google ads, Using an account, What we publish, Which hostname does what, Corrections, and How a privacy request is handled; and journal articles that still pass originality and length checks.

Legal pages sit on the excluded side on purpose. Privacy, Cookies, and Terms are the documents that disclose the advertising system. Putting units on the disclosure itself would turn the policy into inventory. The publisher chose the opposite shape: finished guides and substantial journal articles may carry contextual units; the legal set explains those units without becoming one.

## Meta tags are not units

Cookie Policy is careful about publisher verification. ads.txt at the site root names pub-9477175344230263. Pages can carry a google-adsense-account meta tag so Google can verify the publisher even when a given URL has no unit. That sentence matters for reading view-source without inventing a contradiction.

A guest check of /legal/privacy and /legal/cookies on 8 September 2026 showed the google-adsense-account meta tag with ca-pub-9477175344230263 and did not load the pagead2.googlesyndication.com adsbygoogle script. A guest check of the eligible How Search works guide showed both the meta tag and the AdSense client script. About and Team matched the legal pattern: verification meta present, unit script absent. Search’s homepage showed neither.

So “legal pages never carry AdSense” means units and the ads script stay off those URLs. It does not mean every Google string is scrubbed from HTML. It does not mean Privacy cannot mention AdSense in prose. The policy has to name the product it is disclosing. Naming is not loading. Meta verification is not a unit. Reviewers who collapse those three into one panic sentence recreate the zero-tracking failure mode from the other direction: demanding a purity the documents never promised, then missing the exclusion the documents did promise.

## Why legal stays out

First, trust. A privacy policy that hosts the same ad network it describes asks the reader to trust a disclosure while the disclosure page itself is inventory. Keeping legal pages clean of units is a readability and integrity choice, not a claim that Google never processes anything anywhere on www.

Second, reviewer clarity. Hostnames tells reviewers that Home, About, the journal listing, the guides listing, editorial standards, and legal pages do not load the ads script, and that the split is enforced in code. A reviewer who opens Privacy should see policy text, not a unit competing with the rights section. A reviewer who opens an eligible guide should expect possible units and should find the disclosure in Privacy and Cookies rather than reverse-engineering intent from a blank legal URL.

Third, category discipline on the publisher host. Earlier essays already covered why short posts, listing pages, and thin teasers stay out of inventory. Legal exclusion is adjacent but not identical. Listing pages are excluded because they are indexes and thin surfaces. Legal pages are excluded because they are the rules. Both exclusions shrink inventory. Only one of them is about not monetizing the contract language.

Fourth, product-host hygiene travels with the same map. Privacy section 1 warns that advertising disclosures apply to selected publisher pages on www and do not mean advertising is enabled on Chat, Drive, Docs, Health, Tracker, Account, login screens, or other application surfaces. Legal exclusion and product-host exclusion are sibling sentences. Confusing them produces bad tickets: people ask support@ why Privacy has no unit as if that proved Search sells queries, or ask privacy@ to remove a guide unit as if legal exclusion had to propagate to every eligible URL.

## Notice is not a CMP, and that still applies on legal URLs

Privacy section 4 and Cookie Policy section 4 say the same hard thing. This website does not include a consent management platform. The cookie bar on www.oernoe.com is a notice. Dismissing it with OK only hides the bar; it is not consent. Ads on eligible pages are requested as non-personalized by default. Google and its advertising partners may still process page context, cookies or similar identifiers, IP address, browser and device information, and ad interaction data to serve, secure, limit, and measure advertisements. Readers can limit cookies in the browser and manage advertising choices through Google Ads Settings, the Network Advertising Initiative opt-out, and the Digital Advertising Alliance opt-out.

That notice-not-CMP rule does not flip when the URL is /legal/privacy. Legal pages still show the publisher’s cookie notice behavior like other www documents. Dismissing the bar still only hides the bar. The difference is inventory: eligible guides may request non-personalized ads; legal pages do not load the ads script. Absence of units is not a silent CMP. Presence of a notice is not consent. Both sentences remain true on the legal set.

Privacy section 8 repeats the rights path. Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to certain processing. Contact privacy@oernoe.com with enough information to verify and respond. Rejecting optional advertising cookies does not prevent essential site functions. Dismissing the cookie notice is not a consent choice. Those lines belong on a page that is not trying to monetize the paragraph.

## What Google may still process, without pretending legal is inventory

On eligible pages, Privacy is explicit that non-personalized default still allows Google and partners to process page context and technical signals for serving, security, limiting, and measurement. Oernoe does not receive a copy of a visitor’s complete browsing history from Google. How Google uses information from sites that use its services is linked from the policy.

On legal pages, the ads script stays off, so the unit path described for eligible inventory is not the path those URLs take. Ordinary request and security data for delivering the page can still exist. Privacy section 2 already describes IP address, browser and device type, request time, requested page, referring page, and diagnostic events for delivery, abuse prevention, and reliability. Essential cookies for authentication, security, preferences, and core operation may still apply site-wide as Cookie Policy section 2 describes. Essential is not AdSense. Legal exclusion is not a claim of a blank network log.

Cookie Policy also says dismissing the cookie notice stores a first-party flag so the bar stays down, and that flag is not an ad identifier. That sentence is useful on legal URLs because readers often land on Privacy or Cookies specifically to understand the bar they just saw. The legal page should explain the notice without turning the explanation into a second ad slot.

## Corrections already punished the opposite slogan

About’s corrections class and the Corrections guide both name the failure: homepage and product copy that sounded like the whole network had no tracking, cookies, or third parties, while this publisher hostname was applying for AdSense. Search still does not use queries as an advertising file. Selected finished pages on www may show Google ads, and Google may process page context, cookies, IP address, and device data on those pages. Both sentences have to be true at once.

Legal-page exclusion is part of making the true pair readable. If Privacy carried units while promising a careful map, the map would look like theatre. If Privacy stayed clean but marketing still shouted zero tracking across Search and www, the clean legal URL would not save the slogan. Corrections chose to name the slogan failure and keep the map. This essay keeps the map’s legal corner from being treated as optional decoration.

## How to use the exclusion without inventing a fourth funding story

If you are reading Privacy or Cookies, you are on excluded legal inventory. Expect disclosure text, rights addresses, and links to Google’s partner-sites explanation and industry opt-outs. Do not expect a unit. Do not treat the verification meta tag as a broken exclusion.

If you are reading an eligible guide or a substantial journal article, you may see Google ads requested as non-personalized. That is the funding door About and Privacy describe beside free accounts and labeled paid features. It is not Search selling queries. Cookie Policy says Search queries typed at search.oernoe.com are not an input to those units.

If a unit appears on Privacy, Cookies, Terms, or another legal URL, that is a publisher bug relative to the published map. Write support@oernoe.com with the URL. If your complaint is Google’s advertising choices on an eligible page, use Ads Settings and the linked opt-outs. If your complaint is a rights request, use privacy@oernoe.com. If your complaint is a factual error in policy prose, use legal@ or hello@ with the sentence, following Contact and Corrections practice. Wrong inbox, wrong theory.

This essay will not invent CMP screens the site does not run, will not invent click-through rates for legal URLs, will not treat unreleased homepage products as shipped, and will not pretend essential logs vanish on /legal/*. The verified facts are Privacy §4 and Cookies §3 exclusions naming legal pages; Cookies §3a and Privacy eligible lists that do not put legal in inventory; notice≠CMP language on both policies; ads.txt / meta verification language; guest checks showing meta without ads script on legal pages and script present on How Search works; About and Hostnames agreeing that legal stays off units.

## The privacy sentence worth keeping

Legal pages disclose AdSense. They do not carry AdSense units. Verification meta can exist without a script. The cookie bar remains a notice, not a CMP, including on legal URLs. Eligible finished publisher documents may still request non-personalized ads under the policies legal pages publish. Search still does not feed those units with queries. Keep those sentences separate, and privacy reading stays checkable. Collapse them, and you get either a purity myth or an inventory myth — both of which Corrections already showed are expensive to unwind.