Oernoe started with a question that sounds soft until you apply it to a product meeting. What does a technology company owe the people who use it?
The first version of this post said the answer is respect. I'll keep that word. I'll also say what it is not. Respect is not a homepage badge. It is not "no ads, no tracking" said as a spell while the journal loads a script. It is a pile of smaller choices, some of which we still get wrong.
Late August 2026. Founded by Angel Mejia Rodriguez, operated by Anoepal. That ownership is public on purpose. You should know who to be angry at.
## Respect, made boring
People should understand what a service does. They should pick the features they want. They should find a human when a page is wrong.
That is why clear descriptions matter. That is why Support exists. That is why Tracker exists. That is why we keep saying one account, no credit card to join.
It is also why we have to walk back our own tense. We printed months for Mail and for an Android app. The months moved. Leaving the old tense in place is a respect failure. I'm rewriting those posts on the same slugs.
## What we can say without turning it into a myth
We do not sell account or search data.
Search is built so queries aren't used to build an ad profile.
Account creation is free. Some features may later sit behind an optional paid tier. I will not invent a menu of prices.
The publisher pages on www.oernoe.com may show contextual Google ads. Google may process page, device, cookie, and IP information to serve and measure those ads. This journal is part of that publisher surface. If you need the long version, it's https://www.oernoe.com/legal/privacy
Those sentences can live together. The myth version is not a sentence I will put here.
## The live services, as a privacy story
Search: you type, you click, you leave. The respect test is whether we resist the urge to turn that typing into a dossier.
Health: a place for health-shaped notes. The respect test is whether we talk like a clinic (we shouldn't) and whether we tell you a roommate can see an open tab (they can). Not emergency care.
Chat: messages go to people. Those people can screenshot. The respect test is readable controls, not a claim that a conversation is unstealable.
AI: a draft box. The respect test is whether we tell you not to paste secrets, and whether you listen.
Docs and Drive: we store what you asked us to store. Sharing is a user action. The respect test is a share dialog that doesn't trick you, and a delete path that works.
Tracker: operational honesty. The respect test is no decorative green.
## Other names, kept in their place
Music, Mail, Studio, Maps, Alerts, News have shown up in older writing. Some have hosts. Some have waitlists. Some have dates we missed. Privacy as a theme does not make an unshipped inbox real.
Mail's sneak peek talked about not scanning messages for advertising. Fine as a goal. As of this month Mail is not sitting next to Search as a peer you can treat the same way. Goals are not hosts.
## What you still have to do
Unique password. A manager if you can stand one. Recovery mail you still own.
Don't type that password on a page that only looks like us.
Don't dump a third person's life into AI.
Don't share a Drive folder like a hallway flyer.
Read the policy when you're about to put something in Health or Drive that would ruin a week if it leaked.
Export or delete through account settings if you want out. If a control fails, Support. https://support.oernoe.com
We can design for respect and you can still donate the data in a prompt. Shared work. The stub said that. It was the best line in the stub.
## Money, again, because privacy questions always get here
How do we eat if joining is free? Optional paid features, in pieces I will not overstate, and contextual ads on selected publisher pages. Not by selling your account as a row in a broker sheet. If that mix is unacceptable, you should know now.
I will not print a user count to look loved. I will not print a fake quiet year.
## What still needs to improve
The homepage still talks louder than the policy in places. Some cards still sound like the myth version.
Thin journal posts still teach the myth by omission. A 700-character "we care about privacy" page is an ad.
Help text should point at real settings, not at slogans.
When we miss a date, we should say we missed it on the same URL. That's honesty about what exists for you to put data into.
## A practical hour
Read the policy. Open Search and do three queries you already do. Open Tracker so you know the healthy view. If you create an account, do it on a machine you trust. Put one harmless file in Drive before you put the serious one.
If you don't like the ad disclosure on the publisher site, you can still use Search and judge the box. Different hosts. Different jobs.
That's why the company was built around user privacy, said without a parade: we wanted tools that do not require you to be the product in the usual way, and we still have to tell you where that claim stops. The stop is part of the respect.
## What "built around" does not mean
It does not mean we never log a request. Hosts have logs. Security needs them. The policy is allowed to say that.
It does not mean a journalist can never ask us for a comment. It does not mean a court cannot exist.
It does not mean every teammate is a monk. People make mistakes. The respect move is to shrink what a mistake can touch.
It does not mean you should put your only copy of a will in Drive on week one. Start small. See if delete works. See if export works. Then decide.
## A comparison I will allow
Other search companies made a business of knowing you. We are trying to make a business that does not need that dossier. Ads on the publisher site are a narrower thing: a page context, a device, the usual ad machinery Google documents. If that is still too much, I understand. I would rather you walk with the facts than stay with a fairy tale and feel betrayed later.
DuckDuckGo and others already occupy the "less profiling in search" shelf. We are not the first. We don't need to be the first. We need to be accurate about our own shelf.
## Closing the loop with the rest of this rewrite batch
If you came from the thin post, you got a sermon. If you leave with this one, you should have a policy link, a live-service list, a warning about our missed dates, and a job for yourself: passwords, share dialogs, prompts.
That's enough philosophy. The rest is the product, or it isn't.
The first version of this post said the answer is respect. I'll keep that word. I'll also say what it is not. Respect is not a homepage badge. It is not "no ads, no tracking" said as a spell while the journal loads a script. It is a pile of smaller choices, some of which we still get wrong.
Late August 2026. Founded by Angel Mejia Rodriguez, operated by Anoepal. That ownership is public on purpose. You should know who to be angry at.
## Respect, made boring
People should understand what a service does. They should pick the features they want. They should find a human when a page is wrong.
That is why clear descriptions matter. That is why Support exists. That is why Tracker exists. That is why we keep saying one account, no credit card to join.
It is also why we have to walk back our own tense. We printed months for Mail and for an Android app. The months moved. Leaving the old tense in place is a respect failure. I'm rewriting those posts on the same slugs.
## What we can say without turning it into a myth
We do not sell account or search data.
Search is built so queries aren't used to build an ad profile.
Account creation is free. Some features may later sit behind an optional paid tier. I will not invent a menu of prices.
The publisher pages on www.oernoe.com may show contextual Google ads. Google may process page, device, cookie, and IP information to serve and measure those ads. This journal is part of that publisher surface. If you need the long version, it's https://www.oernoe.com/legal/privacy
Those sentences can live together. The myth version is not a sentence I will put here.
## The live services, as a privacy story
Search: you type, you click, you leave. The respect test is whether we resist the urge to turn that typing into a dossier.
Health: a place for health-shaped notes. The respect test is whether we talk like a clinic (we shouldn't) and whether we tell you a roommate can see an open tab (they can). Not emergency care.
Chat: messages go to people. Those people can screenshot. The respect test is readable controls, not a claim that a conversation is unstealable.
AI: a draft box. The respect test is whether we tell you not to paste secrets, and whether you listen.
Docs and Drive: we store what you asked us to store. Sharing is a user action. The respect test is a share dialog that doesn't trick you, and a delete path that works.
Tracker: operational honesty. The respect test is no decorative green.
## Other names, kept in their place
Music, Mail, Studio, Maps, Alerts, News have shown up in older writing. Some have hosts. Some have waitlists. Some have dates we missed. Privacy as a theme does not make an unshipped inbox real.
Mail's sneak peek talked about not scanning messages for advertising. Fine as a goal. As of this month Mail is not sitting next to Search as a peer you can treat the same way. Goals are not hosts.
## What you still have to do
Unique password. A manager if you can stand one. Recovery mail you still own.
Don't type that password on a page that only looks like us.
Don't dump a third person's life into AI.
Don't share a Drive folder like a hallway flyer.
Read the policy when you're about to put something in Health or Drive that would ruin a week if it leaked.
Export or delete through account settings if you want out. If a control fails, Support. https://support.oernoe.com
We can design for respect and you can still donate the data in a prompt. Shared work. The stub said that. It was the best line in the stub.
## Money, again, because privacy questions always get here
How do we eat if joining is free? Optional paid features, in pieces I will not overstate, and contextual ads on selected publisher pages. Not by selling your account as a row in a broker sheet. If that mix is unacceptable, you should know now.
I will not print a user count to look loved. I will not print a fake quiet year.
## What still needs to improve
The homepage still talks louder than the policy in places. Some cards still sound like the myth version.
Thin journal posts still teach the myth by omission. A 700-character "we care about privacy" page is an ad.
Help text should point at real settings, not at slogans.
When we miss a date, we should say we missed it on the same URL. That's honesty about what exists for you to put data into.
## A practical hour
Read the policy. Open Search and do three queries you already do. Open Tracker so you know the healthy view. If you create an account, do it on a machine you trust. Put one harmless file in Drive before you put the serious one.
If you don't like the ad disclosure on the publisher site, you can still use Search and judge the box. Different hosts. Different jobs.
That's why the company was built around user privacy, said without a parade: we wanted tools that do not require you to be the product in the usual way, and we still have to tell you where that claim stops. The stop is part of the respect.
## What "built around" does not mean
It does not mean we never log a request. Hosts have logs. Security needs them. The policy is allowed to say that.
It does not mean a journalist can never ask us for a comment. It does not mean a court cannot exist.
It does not mean every teammate is a monk. People make mistakes. The respect move is to shrink what a mistake can touch.
It does not mean you should put your only copy of a will in Drive on week one. Start small. See if delete works. See if export works. Then decide.
## A comparison I will allow
Other search companies made a business of knowing you. We are trying to make a business that does not need that dossier. Ads on the publisher site are a narrower thing: a page context, a device, the usual ad machinery Google documents. If that is still too much, I understand. I would rather you walk with the facts than stay with a fairy tale and feel betrayed later.
DuckDuckGo and others already occupy the "less profiling in search" shelf. We are not the first. We don't need to be the first. We need to be accurate about our own shelf.
## Closing the loop with the rest of this rewrite batch
If you came from the thin post, you got a sermon. If you leave with this one, you should have a policy link, a live-service list, a warning about our missed dates, and a job for yourself: passwords, share dialogs, prompts.
That's enough philosophy. The rest is the product, or it isn't.
O
Oernoe Editorial Team
Technology experts committed to building privacy-first solutions and helping users understand how digital services work. Passionate about creating transparent, ethical platforms.
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