The privacy-request inbox is not support

Contact on www.oernoe.com lists support@oernoe.com for bugs, account access, and service problems, and privacy@oernoe.com for privacy requests and security reports. Privacy Policy section 8 and section 10 point rights requests at privacy@, and general support at support@. Those are not two labels for one queue. A password-reset failure is support work. An export or deletion of the account Oernoe holds is privacy work. This essay is privacy writing about that cut, grounded in Contact and Privacy, without cloning the full How a privacy request is handled process guide and without restating the Search-removal versus www-contact hinge already covered elsewhere.

## What Contact publishes for each desk

Support is operational. The Contact card asks for browser, device, and steps when you can give them. The address is support@oernoe.com. Forgotten-password cases are steered first to Forgot Password on the login page; if reset mail does not arrive, then write support@. That is triage for access and breakage.

Privacy is rights and security process. Contact’s privacy block says write to privacy@oernoe.com from the email on the account. Say whether you want an export, a deletion, or both. Deletion removes the account and cannot be undone; the team confirms once. Search listings and third-party web pages are a different job. The full process is pointed at How a privacy request is handled. Legal notices are explicitly not privacy@: they go to legal@oernoe.com.

Contact also states what sits in front of neither desk. There is no contact form behind an account. There is no chatbot. There is no overnight desk. A complete message with a URL, a hostname, and a browser beats a vague complaint. Reply timing is usually one to three working days. If a message needs a product change before it can be answered properly, the team will say so rather than send a holding reply that exists only to close a metric. That honesty applies to both inboxes. It does not merge them.

## What Privacy Policy actually routes

Privacy Policy section 1 sets scope: how Oernoe and Anoepal handle information when you visit www.oernoe.com, contact the company, create an account, or use a service that links to the policy. Product-specific policies may add detail. Advertising disclosures in the policy apply to selected publisher pages on www. They do not mean advertising is enabled on Chat, Drive, Docs, Health, Tracker, Account, login screens, or other application surfaces.

Section 3 states use limits that matter for rights language. The company uses information to provide requested services, secure accounts, respond to support requests, maintain reliability, comply with law, enforce policies, and improve the site and services. It does not sell account information or search history. It does not use search history to create advertising profiles. It does not provide account or search data to advertisers for their own direct marketing.

Section 8 is the rights hinge. Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to certain processing. You may also withdraw consent where consent is the legal basis. Contact privacy@oernoe.com with enough information for the company to verify and respond. Cookie and advertising choices are separate controls: browser cookie settings, Google Ads Settings, Network Advertising Initiative opt-out, Digital Advertising Alliance opt-out. Dismissing the cookie notice is not a consent choice. Rejecting optional advertising cookies does not prevent essential site functions.

Section 10 repeats the three process addresses without collapsing them: privacy questions or rights requests to privacy@oernoe.com; legal questions to legal@oernoe.com; general support requests to support@oernoe.com. No postal or street address is published. Contact is by email. Contact’s closing lines and Privacy’s closing lines agree on that channel map.

## Why support cannot quietly absorb rights mail

Support is staffed to reproduce bugs. It expects hostnames, browsers, and steps. It can help when Forgot Password mail never arrives, when a login wall misbehaves on account.oernoe.com, or when a product shell fails to load. Those messages need operational context. They do not need a statutory rights framing to be actionable.

A rights request needs a different verification posture. Contact and the privacy-requests guide both say to write from the email on the account so the company can tell it is you without asking for identity documents. The request should say whether the job is export, deletion, or both — or, in the guide’s fuller list, a copy, a correction of a specific field, a deletion, or a restriction. Vague mail that only names a statute still forces the desk to guess the job. That guessing is slower when the message landed in support@ between two password tickets.

Deletion is irreversible after confirmation. Contact says the team confirms once. Support’s ordinary “try these steps” reply pattern is the wrong shape for that irreversible act. Putting deletion into the support pile is how a rights request waits behind session debugging, or how an agent accustomed to reversible fixes treats a deletion like a settings toggle. The company publishes privacy@ so that irreversible account work has a labeled door.

Security reports also ride privacy@ on Contact’s card. That is not because every security note is a GDPR packet. It is because security reports and rights requests both need careful handling of account identity and sensitive detail. Support still handles many account-access failures. The published split keeps credential-adjacent reports and statutory rights out of the general bug queue when the sender knows the category.

## What belongs in support even when the subject line says privacy

People sometimes label ordinary breakage as a privacy emergency. An ad appearing inside Search, Health, Chat, AI, Docs, Drive, Tracker, or Account is a bug, not a privacy setting, and the privacy-requests guide sends that class to support@. Login and signup pages are not supposed to load AdSense; Privacy section 4 excludes them. If the script appears there, support needs the URL and the browser, not a deletion request for an account that is otherwise fine.

Forgotten password, locked session, and “I cannot open Drive” are support even if the sender is worried about data. The worry is real. The first job is still restoring or diagnosing access with reproduction detail. Once access works, a separate privacy@ mail can request export or deletion from the account email. Mixing both jobs into one support paragraph is how the irreversible half waits while the reversible half is solved — or how the reversible half never gets steps because the mail read like a legal notice.

Hostname confusion also belongs in support when the product failed. Contact’s FAQ says articles and company pages are on www.oernoe.com, Search is search.oernoe.com, login is account.oernoe.com, and other live products have their own hosts. If you landed on leftover /login or /mail on www, those are leftover routes and are not the index. Writing support@ without the hostname you were on forces the desk to guess which service failed. That guess is support work. It is still not a rights export.

## What privacy@ is not asked to pretend

Privacy@ is not a Search erase key for third-party pages. Contact already separates Search removal from website contact: removal needs the exact result URL and the reason; copyright claims go through DMCA. Account deletion does not unwind a public web page someone else published that Search happened to index. A longer journal essay covers that Search-limits cut. This essay only needs the inbox implication: do not treat privacy@ as silent support for every unhappy Search result.

Privacy@ is not editorial corrections. Something wrong on a www article or guide goes to hello@oernoe.com with the page address, per Contact and About. Factual errors are corrected with a note on the page rather than edited quietly. That is publisher accountability. It is not section 8 access, export, or deletion of account data.

Privacy@ is not partnerships, feedback, or sponsored-content intake. Contact declines selling articles, links, or reviews. Selected long-form pages carry Google AdSense through an ad network with no contact with editorial work. Rights requests do not become a back door into the journal by arriving with a pitch attached.

Privacy@ is also not a guarantee of overnight statutory theater. Contact and Privacy both describe a small team and ordinary working-day replies. Statutory deadlines, where they apply, live in Privacy. Inventing a faster public number to sound helpful is the kind of copy the company has already had to correct in other domains. The honest promise is a labeled inbox, verification from the account email, and a clear statement of whether the ask is export, deletion, or both.

Guides index copy points the same way without turning this essay into the process guide. Start with How a privacy request is handled if you want an export or a deletion. That sentence is navigation. The legal basis and timings still sit in Privacy. Support remains the desk for reproduction detail when the product fails. The index does not merge those doors into one mailto.

## Company facts that keep the cut stable

Homepage and About repeat the basic deal: free accounts, labeled paid features, no sale of account or search data. Oernoe Search does not use queries to build advertising profiles. Selected finished pages on www may show Google ads; Google may process page, device, cookie, and IP information to serve and measure those ads. Those sentences are why rights language and support language must stay distinct. Ads disclosures and account rights are Privacy work. A broken ad unit on an excluded host is support work. Selling account or search data would be a company failure of the deal About states; it is not something support can “reset” like a session.

Anoepal operates Oernoe. Angel Mejia Rodriguez founded the platform and remains the named publisher person for wrong pages on www. Operator clarity does not collapse inboxes. Info@ and hello@ absorb general and editorial mail. Support@ and privacy@ remain the process pair Privacy names at the bottom of the policy. Contact publishes the wider desk map so strangers do not have to invent a master helpdesk that does not exist.

## The usable cut

Use support@oernoe.com when something breaks, when access fails, when reset mail never arrives, or when an ad unit appears on a host that should not load ads. Include hostname, browser, and steps. Use privacy@oernoe.com from the account email when you want an export, a deletion, a correction of a specific field, a restriction, or a security report that needs the rights desk. Say which job you want. Use legal@ for legal notices. Use hello@ when a www page is factually wrong. Read Contact for the desk map and Privacy sections 8 and 10 for the rights routing. Leave the full step sequence and export contents to How a privacy request is handled. Leave Search-removal limits to that separate FAQ and guide. The privacy-request inbox is not support. Keeping the labels honest is how a small operator answers irreversible account work without losing it inside the bug pile.