Click-through does not hand over your query

How Oernoe Search works answers a blunt FAQ in plain language: when you click through to a website from Oernoe results, that website sees a generic referrer that does not reveal what you searched for. The guide names the mechanism stripping referrer information. This Privacy essay stays on that claim and pairs it with HTTPS encryption in transit. It is not a promise that destination sites never log anything else on their own servers. It is a narrower statement about what Oernoe sends with the click, and why that matters when people confuse a search engine’s privacy story with the privacy story of every page they open afterward.

## What the FAQ actually says

The Common Questions section on How Oernoe Search works asks whether websites can see that you searched using Oernoe, and whether they can see the query. The published answer is no on the query point: the destination receives a generic referrer that does not include the search string. That is referrer stripping as the product describes it today. The sentence is short on purpose. It does not expand into a marketing claim that nobody on the internet ever learns anything about you after you leave the results page. It says what Oernoe controls on the way out: the referrer header that would otherwise carry the search URL and, with it, the words you typed.

A referrer is ordinary browser plumbing. When you move from one page to another, browsers often tell the new host which URL you came from. On a results page, that URL can include the query. If the engine forwards that full URL as the referrer, the destination can reconstruct what you searched for without asking you. Stripping means Oernoe does not hand that string over in the referrer. The destination may still see that traffic arrived somehow; it does not get the query from Oernoe’s referrer design as the guide states it.

That distinction is the whole essay. People often want a larger guarantee. They want to hear that clicking a result is private end to end. Oernoe’s guide does not sell that. It sells a specific cut: the query stays out of the referrer that accompanies the click.

## HTTPS is a different layer

The same guide’s privacy-during-search section describes encryption in transit. All communication between your device and Oernoe’s servers uses HTTPS. The claim there is about the path to Search itself: your ISP, a network administrator, or someone watching the connection should not be able to read the query off the wire while it travels to Oernoe. That is transport security. It is not referrer stripping, and it is not a rule about what the destination site does after you land.

Keeping those layers separate is editorial hygiene. HTTPS protects the session with Search. Referrer stripping protects the query from riding along in the header when you leave Search for a third-party page. Neither layer rewrites the destination’s own logging, analytics, cookies, or account systems. If you create an account on the site you clicked, fill a form, or load their scripts, that site’s privacy policy takes over for what it collects. Oernoe’s FAQ does not erase that.

The Privacy Policy on this publisher site is honest about ordinary technical receipt on Oernoe’s side too: systems may receive IP address, browser and device type, request time, requested page, referring page, and diagnostic events to deliver pages, protect accounts, prevent abuse, and keep services reliable. That is Oernoe’s own operational logging language. It does not convert into a claim that destination hosts are silent. It does remind readers that “privacy” on the open web is a stack of partial protections, not a single switch.

## What click-through privacy is not

It is not the same essay as “search queries are not sold as a file.” Non-sale is about Oernoe’s commercial posture toward account and search data. Referrer stripping is about what a third-party host can infer from the HTTP referrer on a single click. You can refuse to sell query files and still leak the query in a referrer if you design the exit badly. The How Search works FAQ is saying the exit is designed not to do that.

It is not the same essay as “no sale of account or search data is the deal.” That deal is the company line repeated on About, Privacy, and the guides: Oernoe does not sell account or search data, and Search does not use search history to build advertising profiles. Click-through referrer behavior is a technical detail inside Search’s privacy-during-search story. The commercial deal and the referrer design support each other; they are not interchangeable slogans.

It is not the same essay as “saved preferences are not an ad profile.” Saved preferences are explicit settings under an account—language, region, collections, filters you chose. Referrer stripping applies whether you are logged in or not when you click a result. Preferences change what you asked Search to remember for you. They do not change the FAQ’s answer about what the destination sees in the referrer.

It is not the same essay as “view-source is how you check ads.” View-source checks are about whether Google AdSense client code appears on a given www page. Referrer stripping is about Search result clicks leaving for third-party URLs. Mixing ads disclosure on the publisher hostname with click privacy on Search is how people write confused posts that sound protective and verify nothing.

## What destinations can still know

Honesty requires the overclaim stop. A destination site can still log its own request metadata: your IP address as it arrives, user-agent strings, cookies it already set, fingerprinting scripts it runs, forms you fill, and any identifiers you choose to send. Oernoe cannot prevent a newspaper, a shop, or a forum from operating ordinary server logs after you arrive. The FAQ does not pretend otherwise. It says the query is not revealed by the referrer Oernoe provides. That is the boundary.

People also confuse “generic referrer” with “invisible arrival.” Generic means the referrer does not carry the search string. It does not mean the destination has no idea traffic exists. Websites still receive HTTP requests. They still decide what to store. If a site asks you to log in, the privacy conversation moves to that site’s account system. If a site loads third-party analytics, that site’s partners may process data under their policies. None of that reopens the query inside Oernoe’s stripped referrer.

There is a related confusion with dwell and click signals inside Search. How Oernoe Search works states that Oernoe Search does not use click or dwell signals to build an advertising profile of you. That is about Oernoe’s own ranking and advertising posture. It is adjacent to, but not identical with, referrer stripping. One sentence is about what Oernoe does with clicks for profiling. The other is about what leaves in the referrer header toward someone else’s host. This essay keeps the second sentence in focus.

## Why the FAQ matters for trust

Search privacy marketing often collapses into fog: private, anonymous, untrackable, zero data. Oernoe’s published guides try to stay narrower. Encryption in transit is named. No advertising profile from search history is named. Referrer stripping on click-through is named. Ads on selected publisher pages are named separately, with Google measuring under its own policies. The pattern is to say what happens on a specific step, then stop before inventing a total shield.

That pattern helps readers who arrive skeptical. If the only claim is “we protect you when you click,” a careful reader asks how. The FAQ answers with a mechanism: generic referrer, query not revealed, stripping. A skeptical reader can still ask what else destinations log. The honest reply is: plenty, on their side; just not the query from this referrer design. Trust grows from that precision more than from a louder adjective.

The same guide also separates Search from this publisher site. Selected pages on www may show Google ads. That advertising system is not Search selling queries. Click-through privacy on Search does not mean the journal or a guide is free of ad scripts. It means the results click does not hand the query to the destination via referrer. Keeping Search’s exit behavior and the publisher’s ad disclosure in separate mental boxes is part of reading Oernoe without getting sold a cartoon.

## Practical reading of the stack

Read the privacy-during-search block as a sequence. First you type. HTTPS covers the trip to Oernoe. Then ranking runs without attaching a personal advertising profile from history, location, device, age, or interests as a personal dossier—that is the ranking essay’s territory. Then you click. Referrer stripping covers the query on the way out. Then you are on someone else’s page. Their rules apply. If you later return to www to read a guide, you are on the publisher site again, with whatever disclosures that page carries.

Account holders can save preferences, but those preferences are explicit and deletable through account settings according to the guide. They do not undo referrer stripping. They also do not turn Search into a behavioral ad graph. The click FAQ remains true for ordinary queries without an account and for logged-in sessions alike: the destination does not receive the query through Oernoe’s referrer.

Technical and security logs on Oernoe’s side may still exist for running Search, as Privacy describes. Those logs are framed as operational, not as a license to sell query history to advertisers. Again: operational logging at Oernoe is not the same fact as a destination reconstructing your query from a referrer. Different actors, different headers, different policies.

## Editorial line for this Privacy shelf

The line we will keep repeating is short enough to stay true. Click-through from Oernoe results does not hand over your query in the referrer. HTTPS encrypts the path to Search. Destination sites can still log what they collect after arrival. Oernoe does not sell account or search data, and that commercial fact is adjacent support, not a substitute for the referrer claim. Ads on selected www pages are a publisher disclosure, not proof that Search leaks queries on exit.

If a future product change alters referrer behavior, the guide and this journal shelf have to change the same day. Until then, the published FAQ is the grounding text. Readers who want a larger promise should notice that Oernoe did not write one. Readers who want a smaller, checkable statement have it: generic referrer, query not revealed, stripping named in the open.

That is enough for a Privacy essay without turning into a browser settings tutorial or a control-by-control tour. The mechanism lives in Search’s exit design. The encryption claim lives in transit. The overclaim lives in the temptation to say destinations learn nothing. We refuse the overclaim, keep the FAQ, and leave the rest of the web to speak for itself under its own policies.