Corrections we have already made closes with a verification rule that is easy to skim past. Product claims are checked against the live hostnames on the homepage. Policy claims are checked against Privacy, Cookies, and Terms. If those sources disagree, the article loses until it is updated. This essay is corrections writing about that pre-check. It is not a remake of the hello intake-format essay about URL plus wrong sentence, and it is not a remake of the no-separate-newsroom essay about who owns the fix. Those pages already exist. The hinge here is what you should open before you send: the live homepage directory and the live legal set, so the complaint is measured against the sources Corrections already said win.
## What Corrections publishes as the check
The Corrections guide, updated 26 August 2026, is the public list of publisher copy the company is willing to put in front of a reader, including a reviewer from the Google publisher network. A correction there means the old wording is no longer the page, or the URL is noindexed, or both. The company does not quietly swap a sentence and pretend the first version never shipped. If you catch something that is not on the list, write hello@oernoe.com with the URL.
The closing section does more than ask for an address and a sentence. It tells you how the desk will judge the claim. Factual errors in articles and guides are corrected with a note rather than edited in silence. Product claims are checked against the live hostnames on the homepage. Policy claims are checked against Privacy, Cookies, and Terms. If those sources disagree, the article loses. The company does not pay for corrections, does not run a public comments thread, and does not promise a same-day rewrite on every mail. It does promise that a specific, checkable complaint is more useful than a topic, and that the list will get longer when the company is wrong rather than shorter when it is embarrassed.
That check is not a courtesy. It is the same rule Editorial Standards and What we publish use before publish. Product copy is checked against the live hostnames on the homepage. Policy copy is checked against Privacy, Cookies, and Terms. About repeats the homepage-wins line in plain language: if a page here disagrees with the homepage directory, the homepage is the one to trust until the page is fixed. Filing without opening those sources asks the desk to do your comparison for you. Sometimes it will. The published standard is still that the live sources win.
## What the live homepage actually is
www.oernoe.com is the public publisher: journal, guides, How-To, and company pages. Search, Chat, and the other products live on their own hostnames. The homepage Services directory currently sends people to search.oernoe.com, health.oernoe.com, chat.oernoe.com, ai.oernoe.com, docs.oernoe.com, drive.oernoe.com, and tracker.oernoe.com. Login is account.oernoe.com. Those apps do not load ads. The homepage also states that the company does not sell account or search data, that Oernoe Search does not use queries to build advertising profiles, and that Google ads appear only on selected publisher pages.
About matches that directory and makes the disagreement rule explicit. From this site the company currently sends people to Search, Health, Chat, AI, Docs, Drive, and Tracker. Those are the hostnames on the homepage. Health is a private workspace for notes you choose to keep. It is not a doctor and it does not replace one. Names that are not listed as live homepage products are not to be written as if a stranger can use them today. Older journal URLs may still talk as if they are. Those URLs are being kept for old links and taken out of the public index. If a page disagrees with the homepage directory, the homepage wins until the page is fixed.
That is why the pre-check starts with the homepage rather than with memory. Memory is how zero-tracking network promises survived past the AdSense application. Memory is how an unreleased product page collected addresses for software that did not exist. Memory is how How-To pointed people at the wrong signup host. The live homepage is a short, public directory. Opening it takes less time than drafting a vague complaint. If your product claim already matches the directory, you may not have a Corrections case. If it contradicts the directory, you have a checkable sentence.
## What Privacy, Cookies, and Terms do in the check
Policy claims need the legal set, not the Services menu. Privacy Policy section 3 says Oernoe does not sell account information or search history, does not use search history to create advertising profiles, and does not provide account or search data to advertisers for their own direct marketing. Section 4 discloses Google AdSense on selected substantial www pages and lists the surfaces where AdSense is not loaded, including the homepage, About, login and signup, legal pages, error pages, indexes, short or promotional posts, editorial standards, and service subdomains. Ads are requested as non-personalized by default. The cookie bar is a notice, not consent. Rights requests go to privacy@oernoe.com. Legal questions go to legal@oernoe.com. Support goes to support@oernoe.com. No postal address is published.
Cookie Policy section 2 keeps account cookies on account and product hosts, not in an advertising file. Section 3 and 3a repeat the excluded and eligible classes. Search queries typed at search.oernoe.com are not an input to publisher units. ads.txt names pub-9477175344230263. A google-adsense-account meta tag may appear even when a URL has no unit. Terms sit beside those pages as the rules for using Oernoe. Corrections’ policy check means a journal line about tracking, ads, sale of data, or consent has to lose when Privacy, Cookies, or Terms say otherwise.
The pre-check matters because many “privacy is wrong” mails are actually disagreements between an old slogan and the current legal set. Corrections already listed “zero tracking” as a site-wide promise that became false once the publisher applied for AdSense. Search still does not use queries as an advertising file. Selected finished pages on www may show Google ads, and Google may process page context, cookies, IP address, and device data on those pages. Both sentences have to be true at once. Opening Privacy and Cookies before you file turns a mood into a comparison. Opening neither turns the desk into a research assistant.
## Why filing first wastes the packet
The hello intake essay already taught that a useful packet needs a URL and the wrong sentence. This essay assumes you can form that packet and asks whether you checked it against the winning sources first. A URL plus a sentence that already matches the homepage is not a product correction. It may be a misunderstanding of Search coverage, a Status question, or a request for a feature the directory does not claim. A URL plus a sentence that already matches Privacy section 4 is not proof that Home should carry ads. It may be a request to change policy, which is a different job from catching a page that lost to policy.
Checking first also protects the Corrections list from noise. The list is supposed to grow when the company is wrong. Growth that is mostly “please re-explain the homepage” dilutes the public record. The named failures already on the list earned their place because live sources contradicted shipped copy: network-wide zero-tracking language versus AdSense disclosures; an unreleased product capture page versus no live product; generic SEO journals versus originality rules; robots.txt shape versus live routes; thin company pages versus publisher quality; How-To signup versus account.oernoe.com; overlapping privacy essays versus one-job-per-URL. Each of those is a homepage or legal comparison you can still perform today.
About’s accountability line does not replace the check. Journal and guides ship as Oernoe Editorial Team unless a byline says otherwise. There is no separate newsroom. If a page on www is wrong, the correction is still owned, and editorial mail goes to hello@oernoe.com. Ownership answers who fixes a real disagreement. It does not invent a disagreement when the live sources already agree with the page you dislike.
## Distinct from intake-format and ownership essays
Hello needs a URL and the wrong sentence already taught packet shape. That hinge was address plus claim. This essay is about the comparison texts Corrections named for judging the claim. You can send a perfect packet that quotes a sentence the homepage already supports. The desk will still measure it against the homepage and close the loop without a Corrections line. The pre-check is how you avoid that loop.
No separate newsroom means Angel owns the fix already taught ownership without a shadow newsroom. Support tickets are not editorial corrections already taught desk choice. Privacy request inbox is not support already taught privacy@ versus support@. This page does not re-map inboxes. When the job is editorial correction, open the homepage for product truth and Privacy, Cookies, and Terms for policy truth before you hit send.
## How to run the pre-check in practice
Open the page you think is wrong. Copy the URL. Quote the sentence. Then open https://www.oernoe.com/ and read the Services directory and the funding sentences in the hero and FAQ. If your claim is about which products are live, which hosts carry ads, whether account or search data are sold, or whether Search builds advertising profiles from queries, the homepage already answers. If the page contradicts the homepage, you have a product-claim case. If it matches, stop and ask whether you actually want a policy change, a Search coverage explanation, or a support ticket.
Next open Privacy and Cookies. If your claim is about AdSense surfaces, non-personalized defaults, cookie notice versus consent, sale of data, search-history profiles, or rights contacts, the legal set already answers. If the page contradicts those policies, you have a policy-claim case. If it matches, the page is not wrong for disagreeing with an older slogan you remember.
Only then send hello@oernoe.com. Include the URL, the sentence, and the live source that wins: homepage directory for products, Privacy or Cookies or Terms for policy. Expect a correction note, a rewrite, a noindex decision, a list update, or a reasoned no when the sources do not actually disagree. Do not expect payment. Do not expect a public argument thread. Do not expect every mail to rewrite the site before the next business morning.
## What this essay refuses
It will not invent a same-day SLA, a bounty, or a comments thread. It will not invent user counts or fake volume of corrections. It will not walk inbox chrome. It will not claim unreleased names are live homepage products. It will not turn every Search emptiness report into a Corrections entry. Search’s tip footer already says not every page on the web is indexed. That limit can falsify a publisher overclaim. It cannot, by itself, become a Corrections line unless a www document said the opposite. It will not pretend silent edits are acceptable when Corrections requires notes for factual errors in articles and guides. It will not clone the intake-format essay or the ownership essay under a new title.
Check the live homepage before you file because Corrections already said the homepage wins on product claims and Privacy, Cookies, and Terms win on policy claims. The pre-check is how a reader turns a worry into a disagreement the desk can verify. Without it, even a careful URL and sentence can waste a cycle proving the live sources already agree. With it, hello@ receives work shaped like the public standard the company published.
## What Corrections publishes as the check
The Corrections guide, updated 26 August 2026, is the public list of publisher copy the company is willing to put in front of a reader, including a reviewer from the Google publisher network. A correction there means the old wording is no longer the page, or the URL is noindexed, or both. The company does not quietly swap a sentence and pretend the first version never shipped. If you catch something that is not on the list, write hello@oernoe.com with the URL.
The closing section does more than ask for an address and a sentence. It tells you how the desk will judge the claim. Factual errors in articles and guides are corrected with a note rather than edited in silence. Product claims are checked against the live hostnames on the homepage. Policy claims are checked against Privacy, Cookies, and Terms. If those sources disagree, the article loses. The company does not pay for corrections, does not run a public comments thread, and does not promise a same-day rewrite on every mail. It does promise that a specific, checkable complaint is more useful than a topic, and that the list will get longer when the company is wrong rather than shorter when it is embarrassed.
That check is not a courtesy. It is the same rule Editorial Standards and What we publish use before publish. Product copy is checked against the live hostnames on the homepage. Policy copy is checked against Privacy, Cookies, and Terms. About repeats the homepage-wins line in plain language: if a page here disagrees with the homepage directory, the homepage is the one to trust until the page is fixed. Filing without opening those sources asks the desk to do your comparison for you. Sometimes it will. The published standard is still that the live sources win.
## What the live homepage actually is
www.oernoe.com is the public publisher: journal, guides, How-To, and company pages. Search, Chat, and the other products live on their own hostnames. The homepage Services directory currently sends people to search.oernoe.com, health.oernoe.com, chat.oernoe.com, ai.oernoe.com, docs.oernoe.com, drive.oernoe.com, and tracker.oernoe.com. Login is account.oernoe.com. Those apps do not load ads. The homepage also states that the company does not sell account or search data, that Oernoe Search does not use queries to build advertising profiles, and that Google ads appear only on selected publisher pages.
About matches that directory and makes the disagreement rule explicit. From this site the company currently sends people to Search, Health, Chat, AI, Docs, Drive, and Tracker. Those are the hostnames on the homepage. Health is a private workspace for notes you choose to keep. It is not a doctor and it does not replace one. Names that are not listed as live homepage products are not to be written as if a stranger can use them today. Older journal URLs may still talk as if they are. Those URLs are being kept for old links and taken out of the public index. If a page disagrees with the homepage directory, the homepage wins until the page is fixed.
That is why the pre-check starts with the homepage rather than with memory. Memory is how zero-tracking network promises survived past the AdSense application. Memory is how an unreleased product page collected addresses for software that did not exist. Memory is how How-To pointed people at the wrong signup host. The live homepage is a short, public directory. Opening it takes less time than drafting a vague complaint. If your product claim already matches the directory, you may not have a Corrections case. If it contradicts the directory, you have a checkable sentence.
## What Privacy, Cookies, and Terms do in the check
Policy claims need the legal set, not the Services menu. Privacy Policy section 3 says Oernoe does not sell account information or search history, does not use search history to create advertising profiles, and does not provide account or search data to advertisers for their own direct marketing. Section 4 discloses Google AdSense on selected substantial www pages and lists the surfaces where AdSense is not loaded, including the homepage, About, login and signup, legal pages, error pages, indexes, short or promotional posts, editorial standards, and service subdomains. Ads are requested as non-personalized by default. The cookie bar is a notice, not consent. Rights requests go to privacy@oernoe.com. Legal questions go to legal@oernoe.com. Support goes to support@oernoe.com. No postal address is published.
Cookie Policy section 2 keeps account cookies on account and product hosts, not in an advertising file. Section 3 and 3a repeat the excluded and eligible classes. Search queries typed at search.oernoe.com are not an input to publisher units. ads.txt names pub-9477175344230263. A google-adsense-account meta tag may appear even when a URL has no unit. Terms sit beside those pages as the rules for using Oernoe. Corrections’ policy check means a journal line about tracking, ads, sale of data, or consent has to lose when Privacy, Cookies, or Terms say otherwise.
The pre-check matters because many “privacy is wrong” mails are actually disagreements between an old slogan and the current legal set. Corrections already listed “zero tracking” as a site-wide promise that became false once the publisher applied for AdSense. Search still does not use queries as an advertising file. Selected finished pages on www may show Google ads, and Google may process page context, cookies, IP address, and device data on those pages. Both sentences have to be true at once. Opening Privacy and Cookies before you file turns a mood into a comparison. Opening neither turns the desk into a research assistant.
## Why filing first wastes the packet
The hello intake essay already taught that a useful packet needs a URL and the wrong sentence. This essay assumes you can form that packet and asks whether you checked it against the winning sources first. A URL plus a sentence that already matches the homepage is not a product correction. It may be a misunderstanding of Search coverage, a Status question, or a request for a feature the directory does not claim. A URL plus a sentence that already matches Privacy section 4 is not proof that Home should carry ads. It may be a request to change policy, which is a different job from catching a page that lost to policy.
Checking first also protects the Corrections list from noise. The list is supposed to grow when the company is wrong. Growth that is mostly “please re-explain the homepage” dilutes the public record. The named failures already on the list earned their place because live sources contradicted shipped copy: network-wide zero-tracking language versus AdSense disclosures; an unreleased product capture page versus no live product; generic SEO journals versus originality rules; robots.txt shape versus live routes; thin company pages versus publisher quality; How-To signup versus account.oernoe.com; overlapping privacy essays versus one-job-per-URL. Each of those is a homepage or legal comparison you can still perform today.
About’s accountability line does not replace the check. Journal and guides ship as Oernoe Editorial Team unless a byline says otherwise. There is no separate newsroom. If a page on www is wrong, the correction is still owned, and editorial mail goes to hello@oernoe.com. Ownership answers who fixes a real disagreement. It does not invent a disagreement when the live sources already agree with the page you dislike.
## Distinct from intake-format and ownership essays
Hello needs a URL and the wrong sentence already taught packet shape. That hinge was address plus claim. This essay is about the comparison texts Corrections named for judging the claim. You can send a perfect packet that quotes a sentence the homepage already supports. The desk will still measure it against the homepage and close the loop without a Corrections line. The pre-check is how you avoid that loop.
No separate newsroom means Angel owns the fix already taught ownership without a shadow newsroom. Support tickets are not editorial corrections already taught desk choice. Privacy request inbox is not support already taught privacy@ versus support@. This page does not re-map inboxes. When the job is editorial correction, open the homepage for product truth and Privacy, Cookies, and Terms for policy truth before you hit send.
## How to run the pre-check in practice
Open the page you think is wrong. Copy the URL. Quote the sentence. Then open https://www.oernoe.com/ and read the Services directory and the funding sentences in the hero and FAQ. If your claim is about which products are live, which hosts carry ads, whether account or search data are sold, or whether Search builds advertising profiles from queries, the homepage already answers. If the page contradicts the homepage, you have a product-claim case. If it matches, stop and ask whether you actually want a policy change, a Search coverage explanation, or a support ticket.
Next open Privacy and Cookies. If your claim is about AdSense surfaces, non-personalized defaults, cookie notice versus consent, sale of data, search-history profiles, or rights contacts, the legal set already answers. If the page contradicts those policies, you have a policy-claim case. If it matches, the page is not wrong for disagreeing with an older slogan you remember.
Only then send hello@oernoe.com. Include the URL, the sentence, and the live source that wins: homepage directory for products, Privacy or Cookies or Terms for policy. Expect a correction note, a rewrite, a noindex decision, a list update, or a reasoned no when the sources do not actually disagree. Do not expect payment. Do not expect a public argument thread. Do not expect every mail to rewrite the site before the next business morning.
## What this essay refuses
It will not invent a same-day SLA, a bounty, or a comments thread. It will not invent user counts or fake volume of corrections. It will not walk inbox chrome. It will not claim unreleased names are live homepage products. It will not turn every Search emptiness report into a Corrections entry. Search’s tip footer already says not every page on the web is indexed. That limit can falsify a publisher overclaim. It cannot, by itself, become a Corrections line unless a www document said the opposite. It will not pretend silent edits are acceptable when Corrections requires notes for factual errors in articles and guides. It will not clone the intake-format essay or the ownership essay under a new title.
Check the live homepage before you file because Corrections already said the homepage wins on product claims and Privacy, Cookies, and Terms win on policy claims. The pre-check is how a reader turns a worry into a disagreement the desk can verify. Without it, even a careful URL and sentence can waste a cycle proving the live sources already agree. With it, hello@ receives work shaped like the public standard the company published.
O
Oernoe Editorial Team
Writes for the Oernoe Journal. Questions about this article can go to the contact page.
Get in touchRelated Articles
Want to Learn More?
Explore our complete guides and knowledge base for more insights on privacy, technology, and best practices.
Browse Our Guides