What "no advertising business" actually means

Plenty of products say they respect your privacy. The claim worth examining is quieter and more structural: what is the business underneath, and what does it need from you to work?

Follow the incentive, not the settings page

An ad-funded product can have excellent privacy settings and still be, at bottom, a system for learning about you. Not because anyone involved is dishonest, but because the revenue arrives in proportion to what the product knows: better profiles, better targeting, better rates. Every design meeting happens inside that gravity. Data that could be collected eventually is; retention that could be longer eventually gets longer; a new feature that would learn more about you has a business case attached, and one that would learn less does not.

Settings pages sit on top of that structure. The structure wins over time, because the structure is what pays the salaries.

The alternative isn't virtue — it's a different structure. When software is paid for directly, the customer and the revenue source are the same person. The product gets better by being more useful, not by being better informed about you. Nobody is against collecting less data, because nobody's revenue depends on collecting more.

What it means concretely

"No advertising business" cashes out into specific, checkable properties:

• No third-party analytics or tracking pixels in the pages. Not "anonymized" trackers, not a tag manager quietly loading a dozen scripts. You can verify this one yourself: open your browser's developer tools and watch what a page loads.
• No behavioral profiles. Usage can be counted in aggregate — how many people used a feature — without keeping a per-person history of who did what when. The first answers product questions; the second is a dossier.
• No selling or sharing data with data brokers. There's nothing to sell when the model doesn't require assembling anything worth buying.
• Data collected for a feature is used for that feature. A financial app needs your transactions to show you your finances — not to score you, market to you, or enrich someone's model of you.
• A privacy policy that reads like an inventory, not a permission slip. It should say what is stored, which service providers touch it, and what happens when you leave — in language written to inform rather than to authorize.

The honest limits

A subscription model doesn't make data handling perfect by itself. Software still has service providers — hosting, payments, sign-in — and each one is a real decision about who touches what. Security still has to be practiced, not just claimed. And "we don't monetize your data" is only meaningful when the policy is specific enough to be falsifiable.

So the test to apply — to us or to anyone: find the business model, then read the privacy policy asking one question. Does this document describe a company that would still make money if it knew nothing about me beyond what the features require? If yes, the incentives are on your side, and everything else is engineering.