Fraud notes are not a secret profile

Account deletion is a real action with a sharp edge. After confirmation, the login stops working and the stored objects go with it. People still ask whether that means every trace vanishes as if the account never existed. The privacy-requests guide answers without theater: 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. We will not pretend a deletion is a memory wipe of the entire internet. This essay is about those residues, especially fraud notes, and why they are not a secret advertising profile of Search queries.

## What deletion actually does

The process page is explicit about the job. Deletion removes the account and the content attached to it. It cannot be undone. Oernoe confirms once before acting, because people write in a hurry and then want a Drive folder back. After confirmation, the account gate closes and the objects tied to that account leave with it.

Deletion does not unwind a public web page someone else published that 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, Google Ads Settings and the industry opt-outs linked from Cookies are the tools that reach Google’s side. For a third-party page in Search results, a privacy request about your account is not a takedown; you send the exact result URL and the reason to support or privacy, and copyright has its own DMCA path.

That split matters before we talk about residues. Residues are not “we kept your Chat history anyway.” Residues are the narrow set of records the guide names as staying when law or security requires it. Confusing residues with a full diary of product content is how people leave a deletion request expecting a memory wipe and feeling lied to when a billing row still exists.

## The three residues the guide names

First, a truncated log that a deletion happened. That is an audit fact: something was deleted, at a time, under a process. Truncation matters. The point is not to preserve the deleted content. The point is to retain evidence that the deletion request was processed, which protects both the person who asked and the operator that has to show it acted.

Second, a billing record if you paid for a labeled premium feature. Optional premium is labeled in the product. Payment details may be handled by a payment provider when a paid feature is offered. Accounting and dispute rules often outlive the login. The journal already has room for the idea that billing can outlive a deleted account; this essay’s focus is narrower: a billing residue is not a Search interest graph, and it is not a reason to keep Health notes after deletion promised their removal.

Third, a fraud note. Fraud notes exist so the operator can recognize patterns of abuse, chargebacks that need investigation, credential stuffing, spam signup rings, or other attacks that target free accounts and paid features alike. A fraud note is a security artifact. It is not a taste profile. It is not a list of queries you typed into Search. It is not a substitute for an advertising file.

Privacy’s retention section says Oernoe keeps 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 the legal home for residues. The process guide is the operational home: it tells you what to expect when you ask for deletion, without inventing a faster number or a cleaner fairy tale.

## Why “fraud note” sounds scarier than it is

In ordinary speech, “note on your file” sounds like a secret score. In security work, a fraud note is closer to an incident breadcrumb: that this account or payment instrument was involved in an event that needed review. The purpose is prevention and investigation, not marketing. If a fraud note ever became a way to keep Search queries, Chat text, or Health content after deletion, it would have left its lane and should be treated as a bug and a policy failure.

The privacy-requests page also says Search queries are not an advertising profile. Ordinary request data still exists to return a page and fight abuse. If a query log is retained for security, Privacy describes that. An export is not a complete diary of every search you typed. Do not expect the export file to read like a private journal of every phrase. Do not expect a fraud note to be that diary either.

## What an export is for, and what it is not

An export is the account record held to run the product: identity fields, services attached to the account, and content stored in those services where it can be retrieved. It is not a dump of every request log ever seen. It is not other people’s data that happens to sit nearby. If a category cannot be produced, the guide says we will say so rather than pad the file with a guess.

That honesty helps deletion conversations. People sometimes ask for export and deletion in one letter. Listing both is fine. Expecting export to contain every transient security log, and then expecting deletion to erase every security residue named in Privacy, is how expectations break. Correction of a specific field is also a different job from deletion. If you only need a field fixed, say that. Vague messages that only name a statute slow the reply because the team still has to guess the job.

## How to ask without making it harder

Write from the email address on the Oernoe account. That is how identity is checked without a passport scan. If that inbox is gone, say so and describe another account fact that can be checked, 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. Say whether you want a copy of account data, a correction of a specific field, a deletion, or a restriction while a complaint is reviewed. Name hostnames when you can: Search, Health, Chat, AI, Docs, Drive, Tracker, or the publisher site. Health notes and Chat threads are not the same pile as a Search listing you submitted.

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 protect a metric. The team aims to acknowledge a complete request in a few working days. There is no overnight desk. Statutory deadlines, where they apply, sit in Privacy. Incomplete messages get a question back, not a refusal. Legal threats belong at legal@oernoe.com. Copyright notices follow the DMCA page. Mixing those jobs in one paragraph slows every reply.

## Residues versus publisher ads versus Search

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. 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 for support, not a privacy toggle.

Fraud notes and billing residues live on the account and security side. Publisher ads live on eligible www documents. Search ranking and query handling live on search.oernoe.com with a promise not to build an advertising profile from query history. Keeping those three stories separate is the same discipline as refusing to mash Search and publisher privacy into one “zero tracking” sentence. Residues do not license an ad graph. Ads on www do not license keeping deleted Chat. Search logs for abuse do not become a secret profile just because a fraud note also exists for a different reason.

## What we will not pretend

We will not pretend deletion is a memory wipe of the entire internet. We will not pretend a truncated deletion log is the same as retaining your documents. We will not pretend a billing row for a labeled premium payment is an interest profile. We will not pretend a fraud note is a Search diary. We will not pretend Oernoe can delete Google’s prior ad request records. We will not pretend a privacy request about your account removes a third-party article from the index without a separate, specific process.

Public pages can stay after you leave because they were never only your account objects. Listings you submitted about yourself are product objects Oernoe controls and can address when you say so. Listings someone else submitted still need a check so the wrong row is not removed. Approval is slow on purpose. None of that turns a fraud note into advertising infrastructure.

## Security information is not an interest map

Privacy says systems may receive technical and security information such as IP address, browser and device type, request time, requested page, referring page, and diagnostic events, used to deliver pages, protect accounts, prevent abuse, investigate failures, and maintain reliability. A fraud note sits in that family. It is a labeled security memory, not a marketing segment. When retention drifts into “keep everything useful for later ads,” it has left the Privacy section that authorizes it. Search request data kept for abuse follows the same refusal: useful for security review, not licensed as an advertising file, and not padded into an export that pretends to be a complete search diary.

## Residues after you leave the products

Health, Chat, Docs, and Drive hold objects you stored under account controls. Deletion that removes the account is supposed to take those attached objects with it. Residues named in the guide are not a back door to keep them. A truncated deletion log records that deletion happened. A billing record for labeled premium records payment facts accounting may require. A fraud note records a security event. None of those should silently restore a Drive folder or a Chat thread after confirmation. Opening a publisher article that loaded AdSense does not make that article your account content, and deleting the account does not unpublish someone else’s page.

## Small-team timing without false speed

Oernoe is a small team. Acknowledgement aims for a few working days on a complete request. Statutory deadlines remain in Privacy. Inventing a faster public number to sound helpful is the kind of soft claim the guides refuse. Incomplete messages get clarifying questions. Fraud-note and billing checks often need care against payment providers or security logs; rushing them is how you over-delete required evidence or under-delete content you promised to remove.

## The sentence worth keeping

Some records stay because law or security requires them. Privacy says when. Fraud notes are in that bucket. They are not a secret profile of what you searched. Deletion remains real for the account and its attached content. The residue list is narrow on purpose. If the live privacy-requests page and Privacy ever disagree about what stays, the pages should be corrected until they match. Until then, the honest reading is the one on the process guide: deletion is not theater, residues are not a wipe denial dressed as marketing, and a fraud note is a security record — not an advertising file of your queries.