Privacy export is not a search diary

A privacy export is one of the jobs the privacy-requests guide names in the first paragraph: write from the email on the account, say whether you want an export, a deletion, or both. People treat that export like a complete diary of every Search query they ever typed. It is not. The guide is blunt about what the file holds and what it refuses to invent. This essay stays on that cut — export contents, query limits, deletion honesty, ads scope on the publisher, and timing for a small team — without restating the inbox-versus-support split, the no-sale deal essay, or the Search-queries-are-not-sold hinge already published elsewhere.

## What to send so the export can start

The process page updated 26 August 2026 says to write from the email address on the Oernoe account. That is how the desk tells it is you without asking for a passport scan. If you no longer have that inbox, say so and describe another account fact the team can check, such as a recent login time or a hostname you used. Do not send a password, a one-time code, or a screenshot of a session cookie. Those details do not help verification; they create a new security mess in the same thread that is supposed to produce a copy of what Oernoe already holds.

Say which job you want. The guide lists a copy of the account data, a correction of a specific field, a deletion of the account, or a restriction while a complaint is reviewed. If you want more than one, list them. Vague messages that only names a statute slows the reply because the desk still has to guess the job. Name the hostnames you used if you can: Search, Health, Chat, AI, Docs, Drive, Tracker, or this publisher site. Health notes and Chat threads are not the same pile as a Search listing you submitted. Specificity is not bureaucracy. It is how a small team avoids rummaging through the wrong store.

The inbox is privacy@oernoe.com. There is no form behind a login wall and no chatbot that closes the ticket to keep a metric down. That sentence is process design, not a slogan. The legal basis and the timings still sit in the Privacy Policy. This guide is the operational sequence: what to send, what arrives, what deletion cannot undo.

## What an export actually contains

An export is the account record Oernoe holds so it can run the product: identity fields, the services attached to the account, and the content you stored in those services where the company can retrieve it. That is the full promise. It is not a dump of every request log the systems ever saw. It is not other people’s data that happens to sit next to yours in a database row. If a category cannot be produced, the guide says the team will say so rather than pad the file with a guess.

That last line matters more than it sounds. Padding an export with invented completeness is how a rights reply becomes a second problem. An incomplete honest file is usable. A padded file that looks complete and is wrong is worse than silence. The desk is supposed to refuse the diary fantasy rather than satisfy it with filler.

Search queries are not an advertising profile. The privacy-requests guide states that in those words. Oernoe still sees ordinary request data needed to return a page and fight abuse. If a query log is retained for security, that retention is described in Privacy. Do not expect an export to read like a complete diary of every search you typed. The same split appears on the Search-and-ads guide and on How Search works: Search may keep technical and security logs needed to run the product; those logs are not a license to sell query history to advertisers or to treat the export as an advertising graph of your interests.

The difference is practical. You can ask for the account record and the stored objects you put into Drive, Docs, Chat, Health, or AI. You cannot treat privacy@ as a court reporter for every keystroke that hit search.oernoe.com. If your mental model of “my data” is every HTTP line that ever touched an Oernoe host, the export will disappoint you on purpose. The disappointment is the policy working.

## What deletion confirms, and what it cannot unwind

Deletion removes the account and the content attached to it. It cannot be undone. The guide says the team confirms once before acting, because people write in a hurry and then want the Drive folder back. After confirmation, the login stops working and the stored objects go with it. That is the irreversible half of the privacy job. It is also where people confuse account closure with erasing the public web.

Deletion does not unwind a public web page that someone else published and that Oernoe Search happened to index. It does not erase Google’s copy of an ad request from a www.oernoe.com article you once opened. Those are different systems. For ads choices, use Google Ads Settings. For a page in Search results that is not your account, send the exact result URL and the reason; that is a removal or listing job, not an export diary. Copyright claims have their own packet on the DMCA page. The company will not waive those requirements because a message is angry.

Some records stay because the law or security requires it: a truncated log that a deletion happened, a billing record if you paid for a labeled premium feature, a fraud note. Privacy says when that applies. The guide refuses to pretend a deletion is a memory wipe of the entire internet. That refusal is the same honesty as refusing to pad an export. Both sentences protect the reader from a fake completeness claim.

## Ads on selected publisher pages are not the export file

Selected finished pages on www.oernoe.com may load Google AdSense. That is not Search selling queries. Google may process cookies, IP address, device data, and page context on those pages. Oernoe can delete the account it holds. Oernoe cannot reach into Google’s ad systems and erase a prior ad request. Use Ads Settings and the industry opt-outs linked from the Cookie Policy. Login, signup, Account, Search, Health, Chat, AI, Docs, Drive, and Tracker do not load that ads script. If you saw an ad unit inside those products, that is a bug, not a privacy setting, and it should go to support@oernoe.com.

The export and the ads system sit on opposite sides of that split. An export is Oernoe’s copy of what it holds to run your account. An AdSense request on a long How-To or a finished journal piece is Google processing advertising data under Google’s own policies. Closing the account does not rewrite Google’s prior measurement. Asking privacy@ for “every ad impression I ever generated on www” is asking for a file Oernoe does not hold as a complete diary. The Privacy Policy is explicit that Oernoe does not receive a copy of a visitor’s complete browsing history from Google.

Homepage and About keep the funding sentence short: account creation is free; optional paid tiers are labeled; selected finished pages on this hostname may show Google ads; the company does not sell account or search data. The privacy-requests guide’s ads paragraph is the rights-facing version of that split. Export the account. Use Ads Settings for the ad side. Do not mash them into one file request.

## Timing honesty for a small team

The team aims to acknowledge a complete request in a few working days. Oernoe is a small team. There is no overnight desk. A request that needs a product change before it can be answered will get that said in plain language, not a holding paragraph. Statutory deadlines, where they apply, are in Privacy. The guide will not invent a faster number to sound helpful. Incomplete messages get a question back, not a refusal. A message that is a legal threat should go to legal@oernoe.com. A message that is a copyright notice should follow the DMCA page. Mixing those jobs in one paragraph is how replies get slower.

That timing paragraph is part of what an export is not. An export is not a same-day theatrical dump produced to impress a reviewer. It is a verified copy of the account record and retrievable content, produced by people who also ship Search and keep the publisher honest. The same small-team honesty shows up on Contact and on Corrections: checkable complaints beat vague topics; holding replies that exist only to close a metric are refused.

## Why “every request log” would be the wrong completeness

People who ask for every request log are usually chasing a feeling that something invisible was kept. The privacy-requests guide answers that feeling with a boundary, not with theater. Ordinary request data needed to return a page and fight abuse is not the same object as an advertising profile, and it is not promised as a portable diary. Security retention, when it exists, is described in Privacy. Asking the export to flatten every temporary security line into a human-readable story is how a rights reply turns into a second security review of logs that were never meant to be a personal archive.

The same boundary protects other people. An export that included neighboring account rows, shared Chat participants’ full histories, or Drive collaborators’ files would violate the sentence that says the file is not other people’s data that happens to sit next to yours. Completeness that steals a neighbor’s privacy is not completeness. It is a breach dressed as helpfulness. The desk is supposed to refuse that shape even when the sender phrases the ask as “everything you have on me,” because “everything adjacent” is not “on me.”

Hostname naming in the request is the practical tool here. Health notes are not Search listings. Chat threads are not Docs drafts. A vague statute citation forces the team to open the wrong store first. A named hostname and a named job — copy, correction, deletion, or restriction — lets a small operator pull the right pile once. That is why the guide treats specificity as speed, not as a hurdle.

## How this sits next to related privacy writing

Other journal pieces already cover the labeled inbox versus support, the no-sale deal on account and search data, the handling sequence in fuller operational detail, and the refusal to sell Search queries as a file. This essay’s job is narrower. It is about the fantasy that a privacy export is a search diary. The fantasy fails in three places the live guide already names: the export is account record plus retrievable content, not every request log and not other people’s data; Search queries are not an advertising profile and the export will not read like a complete typed diary; deletion and ads limits mean Oernoe cannot unwind third-party indexed pages or erase Google’s prior ad request from a www article.

If you want the operational checklist, read How a privacy request is handled. If you want the legal basis, read Privacy. If you want where ads sit on the publisher versus what Search is allowed to mean, read Search queries and Google ads. Use privacy@ from the account email, name the job, and expect a file that matches what Oernoe can retrieve — not a reconstructed history of every query that ever crossed the wire.