Approval is slow on purpose for listings

People and company listings in Oernoe Search go through an approval step you can see in the product. About says Search still lets people add people and companies with that process. Search queries and Google ads repeats the same fact: listings are submitted, approved, and treated as part of an index of the public web and of listings people chose to submit. How a privacy request is handled adds the operational edge: approval is slow on purpose, and removal of a listing you did not create still needs a check so we do not delete the wrong row.

This essay is about that slowness. It is not a complaint queue. It is the reason the delay exists, what it protects, and what it is not. It is especially not a back door into Health, Chat, or Drive.

## Two objects that share a word and nothing else

A Search listing about a person or a company is a product object inside Search. Someone submitted fields. An approval step decides whether that object may appear. A privacy request about an Oernoe account is a different object: identity fields, services attached to the account, and content stored in those services where we can retrieve it.

The privacy-requests guide is explicit that Health notes and Chat threads are not the same pile as a Search listing you submitted. Naming the hostname helps because Search, Health, Chat, AI, Docs, Drive, Tracker, and the publisher site are separate jobs. Vague messages that only cite a statute name force us to guess which pile you mean. Guessing is how the wrong row gets touched.

When you want a listing down, say whether you submitted it or someone else did. That fork changes the work. Your own listing is a product object we control once we verify the account relationship. Someone else’s listing about you still needs enough detail to find the row and a check before removal. The check is the slow part. The slow part is intentional.

## Why “fast” would be the bug

Speed feels like good service until you watch what fast removal does in an index that accepts public submissions. A fast delete with weak verification is a vandal’s tool. Anyone angry at a correct listing could send a short demand and erase someone else’s work. Anyone who mistypes an identifier could remove a neighboring row. Anyone who forwards a partial screenshot could trigger a change on the wrong company name.

Slow approval on the way in has the same logic in reverse. A listing that appears instantly without review becomes a spam surface and a harassment surface. We would rather frustrate a legitimate submitter for a stretch than publish garbage that looks official. That trade is a product choice. It is written in public guides so nobody has to reverse-engineer it from silence.

Oernoe is a small team. The privacy guide says we aim to acknowledge a complete request in a few working days, and that there is no overnight desk. Listing approval is not a separate fantasy of instant white-glove service. It sits in the same reality: people read queues, compare rows, and refuse to rubber-stamp. A slower correct decision beats a faster incorrect one when the object is a public row with someone else’s name on it.

The approval step is visible in the product on purpose. Hidden moderation teaches people to assume magic or neglect. We keep the visible wait rather than fake a progress bar that resolves without review.

## Own listing versus someone else’s

If you submitted a listing about yourself and want it down, say that. The guide treats that as a product object we control. We still verify that the request comes from the right place. Write from the email address on the account when you can. Do not send a password, a one-time code, or a session cookie screenshot. Those are the wrong proofs.

If someone else submitted a listing about you, include enough detail to find it. A bare name is often not enough. A result URL, a company legal name, a city, or other stable fields help. Approval is slow on purpose on the way in; removal still needs a check on the way out. We will not pretend that “I dislike this row” is the same workflow as “this row is my submission.”

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 also not a takedown of a third-party article that merely mentions your name. For those, send the exact result URL and the reason to support@oernoe.com or privacy@oernoe.com. Different systems, different packets.

The own-versus-other fork also protects submitters who did everything right. If we removed rows on the strength of an unverified complaint, honest listings would become fragile. The check is not hostility toward the person asking for removal. It is due process for a public object that may have been created by someone else under rules we published.

## What deletion of an account does not do

Account deletion removes the account and the content attached to it after confirmation. It cannot be undone. It 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. For ads choices, use Google Ads Settings. For a page in Search results that is not your account object, use the listing and URL process above.

Some records stay because law or security requires it: a truncated deletion log, a billing record for a labeled premium feature, a fraud note. Those residues are not an advertising profile of Search queries. They are also not a secret way to keep your listing alive after you asked for a proper listing removal. If the listing is the issue, name the listing. If the account is the issue, name the account. Mixing them in one paragraph slows the reply.

Confirmation before deletion exists because people request destruction in a hurry and then want a Drive folder restored. Listing removal is a different confirmation problem: we must be sure which row is meant. Both are slow for safety. Neither is a promise that the open web forgets every mention of a name.

## Not a back door into Health, Chat, or Drive

Search listings are not a way to open Health notes, Chat threads, Drive files, or account settings. Search queries and Google ads says that in one sentence on purpose. Approval queues for public people and company rows do not grant staff a casual stroll through private workspaces. Private products stay behind their own authentication and their own request paths.

If your privacy request is really about a Health note, say Health. If it is about a Chat thread, say Chat. If it is about a Drive folder you want back after a hasty deletion request, understand that deletion confirms once and then cannot be undone. Listing approval slowness does not create a master key across hostnames. Treating it as a master key is how people send the wrong packet to the wrong inbox.

Login, signup, Account, Search, Health, Chat, AI, Docs, Drive, and Tracker do not load the publisher AdSense script. Ads on selected finished www.oernoe.com pages are a different system. Listing approval has nothing to do with toggling those ads. Do not file a listing complaint as an ads complaint or the reverse.

Listing queues do not authorize browsing private notes. Public submission plus approval is a narrow door into a public index, not a skeleton key for every Oernoe hostname.

## What we will not turn this into

We will not turn listing approval into a press-kit factory. Knowledge panels elsewhere on the web are not our product name, and we are not selling a brochure service under a privacy essay. We will not treat adding people and companies to Search as the same act as publishing a journal article on www.oernoe.com. We will not treat a listing you submit as a Health note. We will not treat a Search removal request as a general contact form for every company question. We will not claim that deleting an account unindexes the entire web.

Those neighboring mistakes have their own essays. This one stays on purposeful slowness for listings: why inbound approval waits, why outbound removal of a row you did not create still checks, and why none of that opens private product stores.

We will not invent vanity metrics about monthly approvals to make the delay look smaller. The guides describe the process; the journal explains the reason.

## How to write a request that moves

Write from the account email address when you can. Say export, correction, deletion, restriction, or listing removal in plain words. Name the hostname. If the object is a listing, say whether you created it. Paste the result URL if you have one. Do not paste secrets. Incomplete messages get a question back, not a theatrical refusal. Legal threats belong at legal@oernoe.com. Copyright notices follow the DMCA page. Privacy questions belong at privacy@oernoe.com.

We will not invent a faster statutory number in this journal than Privacy already states. We will not apologize for a check that prevents deleting the wrong row. Slow on purpose is a safety property. It is also a honesty property: the product you see matches the process we describe.

If you no longer have the account inbox, say so and describe another account fact we can check, such as a recent login time or a hostname you used. That path is slower still, because verification is harder. It is still better than accepting a stranger’s word that a public row should vanish tonight.

## Publisher context without slogans

Anoepal operates Oernoe. www.oernoe.com is the publisher site. Search is at search.oernoe.com. Selected finished publisher pages may show Google ads. We do not sell account or search data, and we do not use search history to build advertising profiles. We will not claim the whole network has no ads, no cookies, and no third parties. Listing policy does not need that false slogan to make sense. It needs a clear queue and a refusal to rush a destructive edit.

What we publish already says the public index should hold original writing about behaviors we run, not promotional stubs. Listing approval is one of those behaviors. Explaining why it is slow is journal work. Pretending it is instant would be marketing work we are done doing.

Angel Mejia Rodriguez founded Oernoe and later Anoepal. About’s standing test is whether a feature gives people more control over their data, or less. A slow, checked listing queue gives more control to someone who might be misrepresented than an instant publish button. That is the trade documented here.

## Closing

Approval is slow on purpose for people and company listings. The delay protects the index from junk on the way in and protects the wrong row on the way out. Your own listing and someone else’s listing about you are different jobs. Account privacy requests, third-party web pages, ads choices, and private product data are different jobs again. None of the listing queue is a back door into Health, Chat, or Drive. If you need a change, name the object and accept the check. Speed without the check would be the defect.