Data-sharing controls you can actually use

Privacy writing loves the word “control.” Product surfaces either ship a switch or they do not. This essay sticks to controls a person can find and use on Oernoe today: account security, document and file sharing permissions, Chat retention choices, Health exports, privacy requests, advertising choices on www, and the honest limits of each. If a brochure sentence promises complete control and the screen does not show a control, the brochure is wrong.

You do not need an account to read www.oernoe.com. You need one to use the products. Creation is free. There is no credit card on the signup form. Basic access does not wait on a paywall. You must be at least 13. If you are under 18, use the services with a parent or guardian. Terms and Privacy say that because ordinary law and AdSense both care.

## Account and session controls

The unified account at account.oernoe.com is the SSO broker across live product hosts: Search, Chat, AI, Docs, Drive, Health, and Tracker. Sign in once; session tokens are scoped with Secure, HttpOnly, and SameSite attributes described in the cloud security guide. Open Account Settings and treat security as a checklist, not a mood.

Enable TOTP two-factor authentication with a standard authenticator app when the setting is there. Store the emergency backup recovery codes in a vault you actually control. Inspect active sessions and sign out anything you do not recognize. Change the password first if you think someone else has it, then write support@oernoe.com with the time and the hostname — never with the password.

Forgot Password lives on the login screen. Check spam. If mail never arrives, write support from the same address if you still can. We will not reset an account because a stranger asked in a chat window. Login, registration, password recovery, and security screens do not load advertising scripts. That is a control you feel by absence: auth is not a magazine.

## Sharing controls in Docs and Drive

Oernoe Docs is a collaborative workspace whose dashboard offers three labeled creation cards: Document (rich text, formatting, autosave), Spreadsheet (cells, rows, live saves), and Presentation (slides, notes, presentation flow). Work saves to Oernoe Drive. Those are Oernoe labels inside Docs — not separate Google Sheets or Google Slides products, and not standalone office hosts. Docs still supports rich text, Markdown, math, and multi-format export. Share by email or with read-only or edit links. Set password requirements or expiry dates on shared links when the product offers those fields. Roles matter: read-only, comment-only, or editor should prevent accidental modification by external viewers.

Oernoe Drive is encrypted cloud storage for documents, photos, and files. Filters visibly include Folders, Documents, Spreadsheets, Presentations, and Uploaded files. Quotas around 2 GB appear in empty-state UI. Upload files or folders. Create expiring download links with optional passphrase protection and other limits the product exposes. Inspect storage usage and purge trash when you mean to delete. Cloud security copy describes TLS 1.3 in transit and AES-256-GCM at rest. Those are infrastructure controls. The sharing UI is the human control: who gets a link, for how long, with which role.

If you cannot find a permission you expect, that is a product bug or a missing feature — not a reason to invent a brochure sentence about complete control. Write support@oernoe.com with the hostname and what you tried.

## Chat and AI boundaries you can set

Oernoe Chat provides direct messaging and team rooms. Start a conversation with a username or email. Attachments have size limits; EXIF metadata such as GPS can be scrubbed on upload. Configure per-room auto-expiration when the product offers retention controls so conversations do not persist indefinitely by accident. Message payloads are not monitored for targeted marketing. That is a policy control enforced by product design, not a toggle labeled “sell my chat.”

Oernoe AI is a conversational assistant with a zero model re-training guarantee described in the AI privacy guide: prompts and completions are not used to train foundational models, and AI surfaces do not load advertising scripts. Your practical controls are still human: do not paste production secrets, private keys, or raw regulated medical records; verify code and citations before you trust them; review AI Terms and Safety. Ephemeral inference is not a license to be careless with secrets.

## Health notes and export

Oernoe Health is a private wellness workspace for personal notes and metrics. It is not a medical device and does not replace licensed clinicians. Log what you choose. Export records when the product offers JSON or CSV export for personal archiving. Treat exports as sensitive. Health content is not Search listings and not ad inventory.

## Privacy requests as a hard control

When in-product buttons are not enough, email privacy@oernoe.com from the account address. Ask for export, correction, deletion, or restriction. Deletion cannot be undone; we confirm once. Name hostnames when you can. Do not send passwords. How a privacy request is handled is the operational guide. Privacy Policy carries legal framing. An export is account-held data we can retrieve, not other people’s data and not a complete diary of every search log line.

Deletion does not unwind third-party web pages in Search results or Google’s copy of an ad request from a www article you opened. For ads choices, use Google Ads Settings. For Search results that are not your account, send the exact URL. Those are different controls for different systems.

## Advertising choices on www are real, and limited

Selected finished pages on www may load Google AdSense. Ads stay off Home, About, Team, Contact, legal, indexes, auth, and product hosts. The cookie bar is a notice, not consent. Dismissing it hides the bar. Non-personalized ads are requested by default; Google may still process page context and technical fields listed in Privacy and Cookies. Your outside controls are browser cookie settings, Ads Settings, NAI, and DAA opt-outs. Search queries are not an input to those units.

If you hate ads, use the apps and excluded company pages. If an excluded page shows an ad, that is a bug — report the URL. If an eligible guide shows an ad, that is expected under current policy.

## What “data sharing” does not mean here

It does not mean we sell account or search data to advertisers for their own marketing. Privacy Policy says we do not. It does not mean every subprocessors’ independent website is under your Oernoe toggle. Providers that host infrastructure, process payments, or prevent abuse have their own policies. We require them to handle information for the agreed service purpose. Their independent services remain theirs.

It does not mean Mail is a live sharing surface. Mail is upcoming. Maps, Music, Studio, News, and OerAlerts are not live How-To products. Do not look for sharing controls on software that is not released. Status notices exist so we stop collecting personal data for vapor features.

## Controls that are not switches

Some protections are architectural: hostname isolation, TLS, encryption at rest, no AdSense on product hosts, referrer stripping on Search result clicks, EXIF scrubbing on Chat uploads, edge filtering on AI prompts. You do not flip those one by one. You benefit from them by using the product as designed. The journal’s job is to name them without turning them into unverifiable magic.

tracker.oernoe.com, in the live UI, is a personal life tracker — Today, Habits, Homework, School, Relationships, Check-ins, Focus, Insights, and Reminders — not an operations status page. Prefer that live UI over older marketing blurbs that called Tracker telemetry. Treat habits and check-ins as personal notes in a privacy request. They are not public journal content and not ad inventory. Empty Tracker states are ordinary.

## A practical weekly hygiene list

1. Skim active sessions on the account host.
2. Confirm 2FA is on and backup codes still exist.
3. Review Docs and Drive shares you no longer need; expire links.
4. Check Chat rooms for retention settings you meant to set.
5. Export Health or Drive data if you want a personal archive.
6. On www, remember the cookie bar is a notice; use Ads Settings for Google choices.
7. If you want deletion, write privacy@ once, clearly, and confirm when asked.

## What this essay refuses

It refuses “complete control” slogans without screens. It refuses network-wide ad-free claims. It refuses fake user counts. It refuses treating upcoming services as live controls. It refuses collapsing Account cookies and advertising cookies into one file. It refuses promising that a privacy request can erase the public web or Google’s ad systems.

Controls you can actually use are boring when they work. Boring is the goal. If a control is missing, say so and file a bug. If a control exists, use it before you write a manifesto. Sovereignty over personal data starts with the switches and inboxes that ship — and with the honesty to admit which promises still need engineering.

## Search preferences are not a hidden dossier

Search can be used without an account for ordinary queries. An account is what lets you save preferences you chose — bookmarks or language settings when the product exposes them — not a hidden profile we infer from every click. If a saved preference exists, you should be able to delete it from account settings. If you cannot find the control, that is a product bug, not a reason to invent a brochure sentence about complete control. Site and quote operators, entity submissions, and verified sources workflows described in How-To are user-directed actions. Submissions undergo review to prevent search poisoning. That review is editorial quality control, not an advertising pipeline.

Referrer stripping on outbound clicks is another control you do not toggle daily but should know exists: destination sites should not automatically inherit your query string from our results page. Combined with the “no query advertising file” rule, that is how Search stays a lookup tool instead of a profiling pump.

## Docs collaboration without turning shares into marketing

Visible permissions are only useful if people look at them. Before you hand an edit link to a contractor, ask whether read-only would do. Before you paste a link into a public forum, ask whether the document contains anything that should stay in Drive with a passphrase. Expiring links exist because “forever open” is how accidental leaks age into incidents. Exporting to PDF or Markdown is a control against lock-in: you can leave with your words.

Team files in Drive and shared Docs are still your responsibility to scope. Oernoe provides the locks. You choose the keys. Infrastructure encryption does not decide whether your roommate should have editor access.

## What support can and cannot change

support@oernoe.com can help with broken auth, missing password mail, and product bugs. It cannot invent a GDPR export format we do not produce. It cannot silently delete someone else’s account because you forwarded a screenshot. It cannot disable Google Ads Settings on Google’s side. When you write support, include browser, approximate time, and hostname. Leave passwords out. When you write privacy@, include the job type and hostnames. Leave passwords out there too. Parallel inboxes exist so the right human sees the right queue.

hello@oernoe.com handles editorial corrections and company mail that is not a rights request. legal@oernoe.com handles legal process. partnerships@ and info@ handle commercial and corporate questions. Misrouting a deletion into partnerships is how requests go stale.

## Children, age gates, and why they appear in a controls essay

The services are not directed at children under 13. Age rules appear in Terms and Privacy because ordinary law and publisher advertising programs both care. A control you “use” here is simply not creating accounts for children who should not have them, and supervising teens when required. That is not a toggle in settings. It is a responsibility at signup.

## Premium labels as a consumer control

If advanced tools, expanded storage, or power features carry a price, the price has to be labeled. A labeled premium feature is a control in the consumer sense: you can see the cost before you pay. Hidden subscriptions behind privacy slogans are a refusal. Payment providers may process card details when a paid feature is offered. That processing is commerce under the provider’s policy, not a side door into Search history.

## Putting the controls in a story

Imagine you join, enable 2FA, write a spec in Docs, share a read-only link that expires in seven days, store a zip in Drive, leave a wellness note in Health, ask AI a research question without pasting secrets, and later decide to leave. Your path out is export plus deletion through account settings or privacy@. Your path for ads annoyance on a long guide is Ads Settings or reading excluded pages instead. Your path for a weird login is session revoke plus support. None of those steps require believing a network-wide slogan. All of them require the screens and inboxes to keep working as described.

If a step diverges from live UI, the UI wins until we correct the docs — and then Corrections should say so when we were publicly wrong. Controls you can actually use are the ones that survive contact with the product.