Data retention is not a sell license

How Oernoe Search works puts Data Retention under Your Privacy During Search in three sentences that are easy to compress into one wrong idea. 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. The third sentence is the editorial hinge. Retention for operations is not a commercial permission slip.

This essay stays on that hinge. It is not a rewrite of the piece that says technical logs are not an ad graph. It is not the essay that says no sale of account or search data is the deal. It is not the claim that fraud notes are not a secret profile. It is not the piece about billing records that can outlive a deleted account. It is not the essay that says search queries are not sold as a file. Those URLs already exist. The camera here stays on retention language as something readers often mishear as permission to sell, and on the guide’s explicit refusal of that mishearing.

## What the Data Retention bullet is allowed to mean

The bullet answers a predictable objection. If Search may keep technical and security logs, does that mean the company can later sell the query stream? How Search works says no. Retention of operational logs is described, pointed at the Privacy Policy, and then fenced: not a license to sell query history to advertisers. The fence matters because retention periods and commercial use are different decisions. Keeping a log long enough to investigate abuse does not authorize packaging that log as an advertising product.

The Privacy Policy states the commercial refusals in legal voice. Oernoe does not sell account information or search history. Oernoe does not use search history to create advertising profiles. Oernoe does not provide account or search data to advertisers for their own direct marketing. Retention and Security, later in the same policy, says information is kept 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. None of that paragraph quietly converts into a sell license. The Data Retention bullet in How Search works is the ranking guide’s plain-language version of the same wall.

Search-and-ads repeats the wall for people who arrive from ads questions. Search does not use query history to build an advertising profile and does not sell account or search data to advertisers for their own marketing. Ordinary request data needed to return a page—the query, the fact that a browser asked, technical logs for abuse and uptime—is not an ad graph. If the company cannot keep those apart in code, it should not keep the sentence on the site. Journal writing exists to keep the retention-versus-sale distinction readable without pretending logs do not exist.

## Retention is operational; sale is commercial

People flatten “we keep some logs” into “they monetize everything they keep.” That flatten is useful to critics and useless to operators. Operational retention has concrete jobs named in the Privacy Policy: deliver pages, protect accounts, prevent abuse, investigate failures, maintain reliability, comply with law, enforce policies. Those jobs can require keeping request metadata for a time. They do not require, and the published policies do not allow, selling query history to advertisers.

How Search works also places No Profiling and No Behavioral Tracking in the same section. Search does not create a profile of your interests based on your searches. Each search is processed independently without connection to previous searches as an interest profile. Search does not use click or dwell signals to build an advertising profile of you. Retention language that ignored those bullets would be dishonest. Retention language that sits beside them is the honest narrow claim: some technical and security logs may exist; they are not an advertising-profile factory and not a sell license.

About states the company-level deal that the retention bullet supports. Anoepal exists so Oernoe can keep running without changing the basic deal: free accounts, labeled paid features, and no sale of account or search data. Selected finished pages on the publisher may show Google ads. That publisher advertising is a different system with its own disclosures. It is not Search converting retained query logs into an advertiser product.

The homepage states the same deal in shorter public language. www.oernoe.com is the publisher. Search lives on its own hostname. Oernoe does not sell account or search data. Search does not use queries to build advertising profiles. Google ads appear only on selected publisher pages. Retention of technical logs needed to run Search has to fit inside that public deal, not punch a hole through it. If retention ever became the quiet path to selling query history, the Data Retention bullet would be false even if the no-sale slogan remained on the homepage.

## What retention does not claim

It does not claim that logs never exist. Denying request data entirely would be a fairy tale about how online services run. Search-and-ads refuses that fairy tale on purpose. The honest story is ordinary request data plus a commercial fence. The Data Retention bullet is that fence in the ranking guide.

It does not claim that every retained record vanishes the moment a session ends. The Privacy Policy says retention periods vary. Some security and legal needs outlast a single visit. Nearby journal work already covers fraud notes and billing records that can outlive a deleted account. Those are not secret advertising profiles, and they are not this essay’s focus. The focus is the license question: keeping something for operations is not permission to sell query history.

It does not claim that the publisher hostname has no advertising systems. Selected finished pages on www.oernoe.com may load Google ads. Ads are requested as non-personalized by default. Google processes advertising data under its own policies. The Privacy Policy and Cookie Policy disclose that. Search queries typed at search.oernoe.com are not an input to those units, in the Cookie Policy’s wording. Retained Search logs are still not a sell license, and publisher ads are still not proof that Search sold query history.

It does not claim that encryption in transit answers the retention question. HTTPS protects data on the wire. Retention concerns what happens after a request arrives. How Search works separates those topics into different bullets for a reason. A securely delivered query can still be misused later if retention becomes a sell license. The guide refuses that later misuse in the Data Retention paragraph itself.

It does not claim that Search matches every other engine’s index size. How Search works already refuses that comparison. The difference the company will stand behind is narrower: no personal advertising profiles for ranking, disclosed publisher ads when they appear, and no sale of account or search data. Retention for technical and security needs has to live inside that narrower difference, not outside it as a quiet exception.

It does not claim that saved preferences are retained advertising profiles. How Search works allows explicit personalization under your control: saved searches, bookmark sources, language and region options, and filters. You can delete them through account settings. Preferences you authored and can remove are not query-history sales. They are chosen state. The Data Retention bullet is about technical and security logs and the refusal to treat those logs as a sell license, not about rewriting personalization as covert advertising.

It does not claim that rights requests are unnecessary because retention is harmless. The Privacy Policy lists choices and rights that may include access, correction, deletion, export, restriction, or objection depending on where you live. Contact the privacy inbox with enough information to verify and respond. Retention limits and rights tools are complementary. Neither one is a sell license.

## Why the “license” metaphor matters in journal copy

Editors sometimes write as if policy silence were permission. If a page says logs may be kept and does not restate the no-sale line in the same paragraph, a careless rewrite can imply that retained query history is inventory. How Search works refuses to leave that implication hanging. It uses the word license on purpose. A license is permission. Retention is not permission to sell. Journal essays should keep that metaphor sharp because readers already know companies that kept data “for security” and later used it for advertising. Oernoe’s published sentence is written against that pattern.

The metaphor also helps when talking to ads reviewers without turning the journal into a review request. Search-and-ads already says the page is a map of two systems, not a pitch to click an ad. The retention hinge belongs on that map. Reviewers who only see “we keep logs” need the third sentence. Readers who only see “we never sell” need the admission that technical and security logs may still exist. Honest privacy writing holds both.

## How this stays distinct from nearby essays

Technical-logs-are-not-an-ad-graph is about the ontology of logs versus advertising graphs. No-sale-of-account-or-search-data-is-the-deal is about the company promise as a deal structure. Fraud-notes-are-not-a-secret-profile is about abuse records. Billing-records-can-outlive-a-deleted-account is about payment residue after deletion. Search-queries-are-not-sold-as-a-file is about the no-sale promise as a file metaphor. Save-searches, delete-prefs, same-algorithm, encryption-in-transit, and funding-split essays already occupy other corners. This essay keeps the focus on the Data Retention hinge: keeping technical and security logs needed to run Search is not a license to sell query history to advertisers.

## Practical reading for a careful user

Read the Data Retention paragraph in How Search works as three linked claims, not as one vague comfort sentence. Queries are not used to build an advertising profile. Technical and security logs may be kept as the Privacy Policy describes. Those logs are not a sell license. If a product behavior keeps the first two and drops the third, the guide is broken. If a product behavior pretends no logs exist, the guide is also broken, because Search-and-ads already admitted ordinary request data.

Read the Privacy Policy’s “How Oernoe Uses Information” and “Retention and Security” sections together. Use and retention are related, but neither section authorizes selling search history. Read Search-and-ads when you need the short commercial map. Read About when you need the operator, Anoepal, the founder credit for Angel Mejia Rodriguez, and the standing test that a feature should give more control over data or less. Read the homepage when you need the live lineup and the plain statement that Search does not use queries to build advertising profiles while selected publisher pages may show Google ads.

If you are comparing engines, do not grade Oernoe on whether retention exists. Retention exists in every serious service that fights abuse and keeps systems up. Grade it on whether retention is treated as a sell license. How Search works refuses that treatment in public. This journal essay exists to keep the refusal attached to the exact bullet where readers usually hear the wrong permission.

Data retention is an operations decision. A sell license is a commercial decision. Keep them apart in language and in code. Drop the distinction and every log starts sounding like inventory for advertisers. Oernoe’s guide and Privacy Policy refuse that inventory story. The Data Retention bullet is where the refusal has to remain checkable.