One Oernoe account across live apps

One Oernoe account is supposed to open the live product hosts without turning every subdomain into a separate password circus. That is the point of account.oernoe.com as a unified identity broker. This essay explains what “one account” actually means today, which hosts it covers, how sessions move across apps, and what the account deliberately does not invent.

You do not need an account to read www.oernoe.com. You need one to use the products. Search can still answer ordinary queries without a login. Creation is free. There is no credit card on the signup form. If a paid feature exists later, it has to be labeled as paid. That is the deal Anoepal is supposed to keep, and it is the deal the Oernoe Editorial Team will keep repeating until the signup form itself contradicts it.

## The live hosts the account is for

The homepage markets seven live services: Search, Chat, AI, Docs, Drive, Health, and Tracker, with Account as the SSO door. In hostname terms that is search.oernoe.com, chat.oernoe.com, ai.oernoe.com, docs.oernoe.com, drive.oernoe.com, health.oernoe.com, and tracker.oernoe.com, plus account.oernoe.com for credentials, profile, security, export, and deletion paths.

SSO means single sign-on credentials across those seven live product hostnames. Sign in at account.oernoe.com/auth/login. The live login screen shows Continue with Google, an email path, Email and Password fields, Forgot password, Show password, Sign in, and Create an account. Signup at account.oernoe.com/auth/sign-up shows Continue with Google or create with email, plus Email, Username, Full Name, Password, Confirm Password, optional Bio and Profile Picture, username guidance of three to thirty characters using letters, numbers, dots, and dashes, and a reCAPTCHA “I’m not a robot” control.

Session tokens are described in How-To as scoped securely via HTTP-only, SameSite cookies. When you visit Chat or Drive later, the authentication broker validates the active session so you are not retyping the password for every tab. That is convenience with a security boundary, not a license to collapse all data into one advertising profile.

www remains the publisher and documentation hub. It is not a tenth file locker. Reading guides and journal essays does not require the same session the Drive folder uses. Selected finished www pages may show Google AdSense while Account and the apps stay in the published ads exclusion set. Login, signup, and password recovery screens are part of that exclusion story. Do not mash “publisher ads exist” into “Account shows ads.”

## What the account holds

The account is a login, a profile you choose to fill, security settings, and the data you put into a service: files in Drive; Document, Spreadsheet, or Presentation work in Docs; messages in Chat; notes and metrics in Health; prompts in the Noevik AI assistant; and personal habits, homework items, check-ins, and focus sessions in Tracker. Those stores belong to the product you used. They are not a public journal article. They are not a source of advertising profiles for Search.

We may keep technical logs to run the service: sign-in events, IP address, device type, errors. That is described in the Privacy Policy. It is not a license to sell the contents of Health, Chat, or Tracker. Search queries are not an advertising file. Ordinary request handling still exists to return pages and fight abuse. Keep those sentences separate even when one cookie family sits under the oernoe.com domain tree.

Preferences you choose to save should be deletable from account settings when the product offers them. If you cannot find a control the guide promises, that is a product bug for support@oernoe.com, not a brochure opportunity to claim complete control in the abstract.

## What the account is not

It is not Mail as a live homepage product. Mail is active research and development and has not shipped yet. Older copy that treated an unreleased mailbox like a joinable product was wrong, and Corrections already said so. The account does not invent a mailbox because a stranger wants one, and journal essays should not teach Mail as How-To.

It is not Maps, Music, Studio, News, or OerAlerts as live public products. Those names still haunt some old URLs. Those URLs are noindexed and are not How-To. If the homepage does not list a service as live, do not assume the account unlocks it.

Use a password manager. Twelve characters with mixed case and numbers is the floor How-To tells people; longer is better, with symbols included in the How-To floor. Minimum age is thirteen. Under eighteen needs a parent or guardian. The site is not directed at children under thirteen.

## Sessions, switching, and everyday use

A practical day with one account looks like this: create or sign in on Account; search on Search; keep a file in Drive; draft a Document, Spreadsheet, or Presentation in Docs; message in Chat; ask Noevik for a draft you will edit; log a wellness note or metric in Health; use Tracker for a habit, homework item, daily check-in, or focus block. You should not need seven passwords for that path. You should still treat each hostname as its own data boundary.

Sign out when you leave a shared computer. Inspect active sessions periodically and terminate stale browser sessions. Enable TOTP two-factor authentication from Account Settings → Security when you are ready, using a standard authenticator app. Store emergency backup recovery codes in an encrypted vault.

Forgot password lives on the login page. Check spam. If reset mail never arrives, write support@oernoe.com from the address you still control, or explain which address the account used. Do not send the password, a one-time code, or a screenshot of a session cookie to any inbox.

## Security without slogans

Auth surfaces are described as free of third-party advertising scripts in the published guides. That is not the same as claiming the entire Oernoe network is ad-free. Selected www educational pages may show Google ads. Product apps and Account should not. Corrections already retired the site-wide zero-tracking promise. One-account writing should inherit that correction.

If you think someone else has the password, change it first, then write support. Include the time you noticed the problem and the hostname where you noticed it. Do not paste recovery codes into chat windows. Do not photograph backup codes and upload them to a shared Drive folder named “secrets.”

## Export, deletion, and control

How-To describes Settings → Data Management → Request Export, and an alternate path of emailing privacy@oernoe.com from the registered address. The privacy-request guide adds the human process: write from the account email, say whether you want export, deletion, correction, or restriction, and name hostnames when you can—including Tracker when your request covers habits or check-ins.

Deletion is irreversible after confirmation. Login stops; stored objects go with the account on the published timeline. How-To states permanent expunging from active production databases within thirty days after confirmation. Deletion does not unwind a third-party web page Search indexed, and it does not erase Google’s copy of an ad request from a www article you once opened. For ads choices, use Google Ads Settings. For account sovereignty, use Account settings and the privacy inbox.

Vague mail that only says GDPR slows the reply because the team still has to guess the job. Health notes and Chat threads are not the same pile as a Search listing you submitted. Specific requests get specific work.

## How SSO should feel day to day

You should be able to move from Docs to Drive without a second password prompt while the session is valid. You should not assume that a publisher page on www automatically mixes ads context with private files. You should not assume Chat can see Health notes or Tracker check-ins because both apps recognize the same login. Recognition of identity is not permission to merge product stores.

If a product asks you to sign in again after you already signed in, note the hostname, browser, and whether you recently cleared cookies. Cleared cookies kill sessions. Private browsing windows do not share the same jar. Essential authentication cookies keep accounts and security working; blocking everything can look like an unexplained logout.

## Why unified identity is a technology essay

Company essays fail when they sell a roadmap as a catalog. One account across live apps is a present architecture: Account issues session cookies for the product family; each product keeps its job. Tracker is a personal life tracker, not an ops status page, even if older blurbs said otherwise. Docs offers Document, Spreadsheet, and Presentation cards without being renamed into Google product names in our wording. AI is branded Noevik inside Oernoe AI. Mail remains unreleased.

Distributed hostnames are also a security story. Isolate auth from publisher ads. Isolate Search from Drive. Isolate Health and Tracker from public index pages. Reviewers who only read a homepage slogan miss that. This essay exists so the SSO story stays concrete: which hosts, which cookie role, which recovery path, which privacy inbox.

If we add a live host later, Home, About, How-To, the hostname guide, and this kind of journal essay have to move together. Until then, one account means the seven live services plus Account—not a fantasy suite of unreleased brands.

Use the account for access and control. Use www for reading. Use Tracker for personal habits and check-ins. Use privacy@oernoe.com when sovereignty over stored data is the actual request. That is the honest shape of one Oernoe account today, written for people who want the map more than the myth.

## Closing note for “One Oernoe account across live apps”

This page’s reader job stays fixed on the title above. Neighboring journal essays cover other hosts and policies. Open the live product beside How-To when you need screens. Prefer the September 17, 2026 service-tour labels when older marketing conflicts. If a live screen and this essay disagree, write hello@oernoe.com with both URLs.

## Publisher and ads boundary worth repeating

www.oernoe.com is the publisher hub for About, Journal, Guides, How-To, Contact, and legal pages. Selected finished Guides, How-To pages, and journal essays may load Google AdSense with non-personalized requests by default. ads.txt at the site root names publisher id pub-9477175344230263. Home, About, Team, Contact, legal pages, the journal listing, the guides index, login, signup, password reset, and the product applications themselves—Search, Chat, AI, Docs, Drive, Health, Tracker, and Account—are in the published exclusion set for that ads script. Search queries typed at search.oernoe.com are not sold, not retained as advertising profiles, and not used as AdSense input. Older site-wide “ad-free” or “zero tracking” promises were false once the publisher used AdSense; Corrections already said so in public. Keep those sentences true at the same time.

## Account security baseline from How-To

How-To’s security module still matters beside every product essay. Use a password manager. Choose at least twelve characters with upper and lower case letters, digits, and symbols. Enable TOTP two-factor authentication from Account Settings → Security with a standard authenticator app. Store emergency backup recovery codes in an encrypted vault offline from the primary password. Inspect active sessions periodically and terminate stale browser sessions. Sign out on shared computers. Forgot password lives on account.oernoe.com/auth/login. Never send passwords, one-time codes, or session cookie screenshots to support@oernoe.com, privacy@oernoe.com, or hello@oernoe.com. You must be at least thirteen; under eighteen needs a parent or guardian.