Publisher and Search share an operator

Oernoe runs a search engine and a publisher website. That sentence is true, short, and dangerous. It is true because both products exist under one operator. It is dangerous because the same sentence is where people — including us — once mashed two different systems into one privacy claim. The mash is how a homepage ends up promising “zero tracking” while the publisher hostname is applying for AdSense. We are not doing that anymore. This essay is about the shared operator, the line that has to stay between Search and advertising, and why naming Anoepal once does not license a single advertising file of your queries.

## Two products, one company

Anoepal operates Oernoe. The About page says so in plain language: five months after Oernoe launched, Angel founded Anoepal as the company that operates and funds the platform. Hostnames make the product split concrete. search.oernoe.com is the search engine. www.oernoe.com is the public publisher site: journal, guides, How-To, company pages, and legal. account.oernoe.com is login and signup. Those hosts share branding and an operator. They do not share a right to pool query text into an ad graph.

The Search and ads guide exists because reviewers, privacy readers, and people who land from a Search result keep asking the same question in different words: if one company runs both, do ads on the publisher site mean Search sold my queries? The answer we will stand behind is no. Selected finished pages on www.oernoe.com may load Google AdSense. Queries typed at search.oernoe.com are not an input file for that system. Ordinary request data still exists so Search can return a page and fight abuse. That is not the same thing as an advertising profile built from what you typed.

## How the mash happens

It is easy to write one privacy sentence that covers “the network.” The sentence feels efficient. It also lies by compression. Search’s product promise is that we do not use query history to build an advertising profile, and we do not sell account or search data to advertisers for their own marketing. The publisher site’s disclosure is different: when ads load on eligible pages, Google may process page context, cookies or similar identifiers, IP address, browser and device data, and ad interaction data. Those are Google’s words, required in Privacy in the same form Google expects, including Ads Settings and the industry opt-outs.

If you glue those into “we never track anyone anywhere,” you have a slogan that cannot survive view-source. How-To and several finished guides include the AdSense client. About does not. Home does not. Login, signup, Account, Search, Health, Chat, AI, Docs, Drive, and Tracker do not load that script. The honest check is mechanical: look at the source on an eligible article and on About. If they disagree with the caption, the caption is wrong.

We already failed the mash test once — not as a clever strategy, but as sloppy language that tried to sound absolute while the publisher was seeking ad funding. The Search and ads page says that mash is how you get a homepage that says “zero tracking” while the same company is applying for AdSense, and that we are not doing that anymore. This journal piece exists to keep that correction public, not to re-run the old line under a softer title.

## What “share an operator” does and does not mean

Sharing an operator means shared legal responsibility, shared funding decisions, and a shared name on Contact and Privacy. It means Angel still sets product direction under a standing test: whether a feature gives people more control over their data, or less. It means Anoepal’s holding structure exists so free accounts, labeled paid features, and a refusal to sell account or search data can stay the basic deal.

Sharing an operator does not mean every hostname is one product surface. It does not mean a query on Search can be read as consent for a publisher ad unit. It does not mean technical logs from Search are a license to profile interests for ads. It does not mean Health notes, Chat threads, Drive files, or account settings become fair game for page-context advertising. Those are not publisher pages. Ads stay off the apps themselves.

The Hostnames guide is the map we use when we write. Look at the hostname in the address bar, not the logo. The logo is shared. The host is not. If you are reading an article, you should be on www.oernoe.com. If you are typing a query, you should be on search.oernoe.com. If you are signing in, you should be on account.oernoe.com. If an ad unit appears inside Chat or Drive, that is a bug to report to support, not a privacy setting you failed to toggle.

## Publisher rules that stay on www

www.oernoe.com is allowed to be three things under What we publish: original writing about search, privacy, and the products we actually run; help pages for those products; and a legal and company record. It is not allowed to be a pile of launch notes or generic ranking essays. Google’s publisher network wants unique content and a usable site. Webmaster quality guidelines say the same thing differently: do not publish thin pages whose only job is to rank or to hold an ad.

Placement rules matter as much as the script tag. We keep a site-wide navigation bar. Ads are not the menu. Ads are not download buttons. Ads are not mixed into login fields. We do not run pop-ups that cover the article before you can read it. The cookie bar on www is a notice with Privacy, Cookies, Ads Settings, and OK. Dismissing it with OK only hides the bar; it is not consent. This website does not include a consent management platform. We have not wired Google Privacy & messaging or another Google-certified TCF v2.3 CMP. That limitation is stated in the guides and in Privacy. It is not something we hide behind softer copy.

ads.txt at the site root names publisher ID pub-9477175344230263. Pages also carry a google-adsense-account meta tag so Google can verify the site even when the homepage has no ad units. robots.txt allows Mediapartners-Google and Google-Display-Ads-Bot so an ads crawler can see the same writing a person sees. Those are publisher mechanics on www. They are not Search ranking knobs, and they are not a claim that every Oernoe hostname is monetized.

## What Search is allowed to mean

Oernoe Search is at search.oernoe.com. You type a query. You get links. People can also submit public people and company listings, with an approval step you can see in the product. That is an index of the public web and of listings people chose to submit. It is not a way to open private product objects. Ranking and crawling belong on How Oernoe Search works. Advertising boundaries belong on Search and ads. Mixing those jobs in one paragraph is how readers walk away thinking crawl signals are personal profiles, or that AdSense on a How-To page means Search sold the phrase they typed yesterday.

Search still sees ordinary request data needed to return a page: the query, the fact that a browser asked, technical logs for abuse and uptime. Privacy and the Search and ads guide both insist that this is not an ad graph. If we cannot keep those apart in code, we should not keep the sentence on the site. That is the operational test, not a slogan.

## Claims we will not make

We will not say the whole Oernoe network has no ads, no cookies, and no third parties. We will not say Google ads on this site are “not tracking” just because they are requested as non-personalized. Non-personalized is a request default; Google may still process the categories Privacy lists. We will not put ads on Chat, Drive, Docs, Health, or other private product surfaces. We will not dress ads up as navigation, or run ads on pages that are only a teaser or a slogan. Optional labeled premium features are not the same funding story as publisher ads. This essay stays narrow: one operator, two systems, one hard line against turning Search queries into an advertising file.

## Funding on www is not Search selling queries

Account creation is free. Some products have optional paid tiers, and those are labeled in the product. Selected finished pages on this publisher hostname may show Google ads. About says we do not sell account or search data, and we do not sell journal articles, links, or reviews. Pitches for sponsored posts are declined. Ads do not appear on Search, Health, Chat, AI, Docs, Drive, Tracker, or Account. They do not appear on Home, About, legal pages, or the journal listing. That funding split is a publisher story on www. It is not a Search monetization story, and it is not proof that queries become an advertising file.

When ads load, we ask for non-personalized ads by default. That request does not erase Google’s processing of the categories Privacy lists. Saying “non-personalized” is not the same as saying “not tracking.” The Search and ads guide refuses that soft lie. The honest network answer is not that everything is free of ads — selected www documents may carry them, and the apps do not.

## What failure would look like

Failure would look like shipping query text, or derived interest labels from queries, into a system that decides which ads to show, or selling that file to advertisers for their own marketing. Failure would also look like using Search request logs as quiet input to publisher targeting while the copy still says queries are not sold. Technical logs for abuse and uptime remain. If those logs ever become the ad graph under another name, the sentence should leave the site until the systems are separated again. Public people and company listings with an approval step stay public-index work, not a side door into Health notes, Chat threads, Drive files, or account settings.

## Why the journal keeps saying it

Public writing is issued as Oernoe Editorial Team unless a person is named. Product claims get checked against live hostnames on the homepage. Policy claims get checked against Privacy, Cookies, and Terms. If those sources disagree, the article is wrong. The recovery rule after templated journal URLs and promotional stubs is to keep documents that add a fact, a method, or a correction you cannot get by swapping a logo onto a template.

The correction here is simple enough to state and hard enough to keep: Anoepal operates both Search and the publisher website; that shared operator does not authorize a shared advertising file of your queries; easy privacy mash once produced a “zero tracking” line while AdSense was in play; we are not doing that anymore. Readers who need the map should open Search and ads, Hostnames, How Search works, and Privacy. Readers who need this journal piece should leave with the operator named and the line between products intact.

If a future page on www talks as if Search queries fund AdSense, that page is out of date and should be corrected. If a future homepage sentence tries to cover every hostname with one absolute privacy claim while eligible articles still load adsbygoogle.js, that sentence is the mash again. The work is to keep the systems distinct in code, in disclosure, and in the writing people actually find.