Technical logs are not an ad graph

Oernoe runs a search engine and a publisher website. They share an operator, Anoepal, and they must not share an advertising file of your queries. Search queries and Google ads states the split in public. How Oernoe Search works describes ranking without a search-history advertising profile. The Privacy Policy says we do not sell account information or search history, and that Oernoe does not use search history to create advertising profiles. This essay takes one easy confusion and slows it down: ordinary technical logs that Search needs to return a page and fight abuse are not an ad graph.

If we cannot keep those apart in code, we should not keep the sentence on the site. The journal’s job here is to make the distinction readable before anyone has to read a header trace.

## What Search is allowed to see

When you type a query on Search, the product still sees ordinary request data needed to return a page: the query, the fact that a browser asked, technical logs for abuse and uptime. That sentence appears on Search queries and Google ads for a reason. Denying request data entirely would be a fairy tale about how HTTP works. Pretending request data is automatically an advertising profile would be a different fairy tale, useful only to people who want every log file to sound like a dossier.

Ordinary request data, in the Privacy Policy’s broader language, can include technical and security information such as IP address, browser and device type, request time, requested page, referring page, and diagnostic events. The stated uses are delivering pages, protecting accounts, preventing abuse, investigating failures, and maintaining service reliability. Those uses are operational. They are not a license to build an interest map for sale.

How Search works adds the product promise in ranking clothes. The algorithm is described as treating searches without attaching a personal advertising profile. Notice what is not on the primary ranking-signal list: your search history as an ad interest file, your age, your marketed interests, and the rest of the dossier vocabulary. Ranking signals are about pages and aggregated quality, not about assembling a person-shaped advertising object from the query stream.

Saved preferences are a separate, explicit lane. When you are logged in, you can save searches, bookmark sources, set language and region preferences, and create filters. That personalization is under your control. It is not the system secretly inferring a marketing persona from every keystroke. Conflating saved preferences with an ad profile is how careful product language gets flattened into slogans.

## What an ad graph would be

An ad graph, in the sense this essay refuses, is a structure that connects identifiers, interests, and inventory so advertisers can target people. It is the thing Search is not allowed to build from query history. It is also the thing we are not allowed to sell as account or search data for someone else’s marketing.

Publisher AdSense on selected www.oernoe.com pages is a different system. When ads load on eligible finished documents, Google may process page context, cookies or similar identifiers, IP address, browser and device data, and ad interaction data under Google’s own policies. Oernoe does not receive a copy of a visitor’s complete browsing history from Google. Ads are requested as non-personalized by default on this site. That still is not “no processing.” Search queries and Google ads and Privacy both refuse the lazy claim that non-personalized means invisible.

The important boundary is operator-level, not vibes-level. Search’s technical logs exist to keep Search up and safe. AdSense on the publisher hostname exists to fund selected finished writing. The operator must not mash them into one sentence about privacy theater. We already had to correct homepage copy that sounded like the whole network had no ads, no cookies, and no third parties while this publisher site was applying for AdSense. Corrections records that failure. The current rule is both sentences at once: Search does not use queries as an advertising file; selected finished publisher pages may show Google ads with the processing Privacy describes.

## Retention without turning logs into product

Privacy’s retention section is deliberately unsensational. We keep information as long as needed to provide services, protect security, meet legal obligations, resolve disputes, and enforce agreements. Retention periods vary by data type and service. That is not a promise that every query lives forever, and it is not a promise that every query is deleted at the speed of a marketing slogan.

How Search works states the companion line: your search queries are not used to build an advertising profile; we may keep technical and security logs needed to run Search, as described in the Privacy Policy; those logs are not a license to sell query history to advertisers. Retention for security and reliability is allowed to exist. Sale of query history as advertising fuel is not. The existence of the first does not smuggle in the second.

Technical logs for abuse and uptime have boring jobs. They help answer whether a spike is an outage or an attack. They help tell whether a client is scraping in a way that harms the service. They help diagnose why a result page failed. None of those jobs require building a marketing graph. If a future design started feeding the same logs into an interest model for ads, that would be a product change that violates the public deal, not a natural reading of “we keep technical logs.”

## Publisher ads are not Search monetizing queries

www.oernoe.com is the public publisher site. Selected finished pages may load Google AdSense. Search queries and Google ads lists eligible document types and the surfaces that stay off inventory: Home, About, Team, Contact, editorial standards, guides index, legal pages, login flows, the journal listing, error pages, and the apps themselves. The honest check offered there is view-source: finished guides can include the AdSense client; About should not.

That placement map matters because reviewers and readers often collapse “Oernoe has ads somewhere” into “Search sells my queries.” Those are not the same claim. Funding on the publisher hostname through contextual units on finished writing is disclosed. Selling account or search data is denied. Optional labeled premium features are a third funding lane described on About. If an ad unit appears inside Search, Health, Chat, AI, Docs, Drive, Tracker, or Account, that is a bug for support, not a privacy setting you toggle. Bugs do not redefine the architecture. They get fixed.

## What this essay is not arguing

It is not arguing that Search queries are sold as a downloadable file. They are not. Here the job is the subtler mistake: treating necessary technical logs as if they were already an ad graph. It is not a restatement of “no sale of account or search data is the deal,” except as boundary context. It is not about saved preferences becoming an ad profile. It is not a ranking-signals essay: ranking signals are about pages, not people-shaped advertising objects. It is not privacy-export-as-diary. It is not about publisher funding beyond the needed split: publisher AdSense and Search query handling are different systems that must not share an advertising file of queries.

## How the confusion starts, and the cure

The confusion usually starts with a true sentence spoken too fast. “We log requests.” Someone hears “they profile you.” Or: “Google ads appear on some Oernoe pages.” Someone hears “Search is monetizing your searches.” Or: “Privacy mentions IP addresses.” Someone hears “they built a dossier.”

Each leap skips a category distinction. Request logs are not interest graphs. Publisher ads are not query auctions inside Search. IP addresses used to defend a service are not the same processing story as advertising identifiers on eligible publisher pages, even when both can appear in a broad privacy document.

The cure is slower sentences. Search sees ordinary request data. That is not an ad graph. Queries are not sold and are not used to build advertising profiles. Publisher AdSense is a different system with its own disclosures. Retention for security and reliability is described in Privacy and is not a sale license. If any of those links break in the product, the public sentence should come down the same day.

When we write about Search privacy, we should be able to point at How Search works, Search queries and Google ads, and Privacy without hand-waving. Product claims get checked against live hostnames on the homepage. Policy claims get checked against Privacy, Cookies, and Terms. We should not claim the publisher site is free of advertising. Selected finished pages may show Google ads. We should not claim Google’s non-personalized request means nothing is processed. We should not claim technical logs do not exist. We should not claim logs are an ad graph. We should also avoid fake scale stories. The deal does not depend on inflating how many people search. It depends on whether the systems stay apart.

You open Search, type a query, and receive results. Search necessarily learns that a browser asked for that query string at a time, from a network location, with a user agent, and that the response was generated. Abuse systems may retain enough technical detail to notice a flood. Uptime systems may retain enough to notice an error rate. None of that, under the public rules, is allowed to become a marketed profile of your interests, and none of it is sold as account or search data to advertisers for their own marketing.

Separately, you might later read a finished guide on www.oernoe.com that is eligible for AdSense. Google may process page context and related advertising data under its policies and under our Privacy disclosures. That processing is not Search inserting your earlier query into an ad graph. It is the publisher hostname doing what we say it may do on selected finished pages. If you never visit an eligible publisher page, you still are not entitled to a fantasy in which Search runs without request data. You are entitled to the promise that Search’s operational data is not reimagined as advertising identity.

Repetition is not laziness when the failure mode is expensive. We already shipped purity language that could not survive AdSense on the publisher site. We already had to teach reviewers that old promotional URLs are not the site. We already had to say that non-personalized is not invisible. Search still sees ordinary request data: the query, the fact that a browser asked, technical logs for abuse and uptime. That is not an ad graph. Queries are not sold and are not turned into advertising profiles. Publisher AdSense is a different system. Retention language in Privacy explains how long operational data can remain for security and service reasons without converting those logs into a product we denied. Keep those sentences stacked. If the stack breaks, fix the product or fix the sentence. Do not blur them into a comforting mush that collapses under view-source.