Correction of a field is not deletion

People write to privacy@oernoe.com as if one sentence can do every privacy job at once. It cannot. The privacy-requests guide on www.oernoe.com is blunt for a reason: you have to say which job you want. The jobs are a copy of the account data we hold, a correction of a specific field, a deletion of the account, or a restriction while we look at a complaint. If you want more than one, list them. That list is not bureaucratic theater. It is how a small team avoids guessing the wrong remedy and then having to undo it.

Correction and deletion sit next to each other on that list, which is exactly why they get mashed together. Both sound like “fix what is wrong with my account.” Both can be urgent. Both can arrive in the same week after someone notices a typo, a stale display name, or a service they no longer want. The process still treats them as different work. A correction changes a field we already store. A deletion removes the account and the content attached to it. One is a precise edit. The other is irreversible after confirmation. Confusing them is how people ask us to “wipe everything” when they only meant to fix a phone number, or ask for a “small fix” when they meant to close the account forever.

Write from the email address on the Oernoe account. That is how we tell it is you without asking for a passport scan. If you no longer have that inbox, say so and describe another account fact we 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. None of those prove ownership in a way we can safely handle, and all of them create new risk. The guide is process, not a paraphrase of a statute. The legal basis and the timings sit in the Privacy Policy. The guide exists so you know what to send and what happens after it arrives.

Name the hostnames 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. A correction request that says “fix my profile” without naming which product left the wrong field is still a correction request, but it forces us to rummage. A deletion request that says “close everything” without naming which services hold content still triggers the deletion path, but it also triggers a confirmation step because people write us in a hurry and then want a Drive folder back. Specificity is kindness to your own timeline.

A correction of a specific field means we change something that is wrong or out of date in the account record we hold so we can run the product. Identity fields are the common case: an email that changed, a display name that was mistyped, a preference that no longer matches what you set. It can also mean a content object you control inside a product, when the product itself allows that edit and the privacy inbox is the right place to escalate because the UI cannot finish the job. What it does not mean is a wholesale rewrite of other people’s data that happens to sit near yours. What it does not mean is a silent rewrite of a public web page someone else published. What it does not mean is an export padded with categories we cannot produce.

The export path is related and still distinct. An export is the account record we hold: identity fields, the services attached to the account, and the content you stored in those services where we can retrieve it. It is not a dump of every request log we ever saw. It is not other people’s data. Search queries are not an advertising profile. We still see ordinary request data needed to return a page and fight abuse. If a query log is retained for security, that is described in Privacy. Do not expect an export to read like a complete diary of every search you typed. If we cannot produce a category, we will say so rather than pad the file with a guess. Padding with a guess is a different kind of error from deleting the wrong row, but it comes from the same impatience: treating the privacy inbox as a place that must always produce something impressive.

Deletion removes the account and the content attached to it. It cannot be undone. We confirm once before we act. After confirmation, the login stops working and the stored objects go with it. That sentence is the whole reason this essay exists. A correction does not require that irreversible step. A correction does not shut the login. A correction does not empty Drive. If you asked for a field fix and we deleted the account, we would have failed the job you named. If you asked for deletion and we only fixed a spelling error, we would have failed the job you named. The confirmation step exists because deletion is not a soft synonym for tidy.

Deletion also 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 to support@oernoe.com or privacy@oernoe.com. Copyright claims have their own packet on the DMCA page. We cannot waive those requirements because a message is angry. A privacy request about your account is not a takedown of a third-party article that mentions your name. If you submitted a listing about yourself and want it down, say that. That is a product object we control. If someone else submitted a listing about you, include enough detail to find it. Approval is slow on purpose. Removal of a listing you did not create still needs a check so we do not delete the wrong row.

Some records stay after deletion 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. We will not pretend a deletion is a memory wipe of the entire internet. That honesty matters when someone thinks correcting one billing field and deleting the account are the same request. Billing records can outlive a closed login for reasons the policy already states. Correcting a field inside a live account is still the ordinary path when the account is still yours and the only problem is an inaccurate value.

Restriction is the fourth job on the list, and it is not a soft deletion either. Restriction while we look at a complaint means we limit processing in a defined way while a dispute is open. It is temporary by design. It is not a promise that every field will be frozen forever. It is not a substitute for naming deletion when deletion is what you want. People sometimes ask for “restriction or deletion, whatever is stronger,” which forces a question back. Stronger is not a legal category we can execute without knowing which irreversible step you are asking for.

Incomplete messages get a question back, not a refusal. That is the guide’s line, and it is the editorial line too. Vague text that only says a statute name slows the reply because we still have to guess the job. Messages that are a legal threat should go to legal@oernoe.com. Messages that are a copyright notice should follow the DMCA page. Mixing those jobs in one paragraph is how replies get slower. Oernoe is operated by Anoepal. The privacy 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. We aim to acknowledge a complete request in a few working days. There is no overnight desk. A request that needs a product change before we can answer it 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.

From the editor’s side, the same distinction shows up in how we write about privacy on this publisher site. Selected finished pages on www.oernoe.com may show Google ads. That is disclosed in Privacy and Cookies. 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. Correcting a wrong sentence on a guide is also not deletion of the page. Public pages stay after you leave an account. The publisher site is not your private Drive folder. Fixing a field in an account and removing a finished article from the web are different verbs for a reason.

When you write, prefer concrete nouns. “Please correct the display name on my account to …” is a correction. “Please send a copy of the account data you hold for …” is an export. “Please delete my account and the content attached to it after you confirm” is a deletion. “Please restrict processing on this account while you review this complaint” is a restriction. If you want two of those, put them on two lines. If you are unsure which one you need, say what outcome you want in ordinary language and we will map it. Do not pad the request with threats that belong in another inbox. Do not attach secrets we told you not to send. Do not assume that fixing one field will quietly erase logs we are required to keep, or that deleting an account will erase an ad request Google already processed on a publisher page.

Correction of a field is not deletion because the confirmation step, the irreversible loss of stored objects, and the shutdown of login belong only to deletion. Correction leaves the account standing. It changes what is wrong. It does not pretend the internet forgot you. It does not pretend Search unindexed a third-party page. It does not pretend Ads Settings live inside our database. It is a named job on a short list, and naming it correctly is how the reply stays useful instead of dramatic.

That is the editorial standard we will keep repeating until the mash-up stops arriving: list the jobs if you want more than one; treat deletion as irreversible after confirmation; treat a field fix as a field fix; refuse to pad exports with guesses; send privacy work to privacy@oernoe.com with enough detail to verify you. The process we actually run is already written. This essay exists so the difference between correcting a field and deleting an account is harder to miss than a buried sentence in a guide.