Privacy is a posture, not a feature

A lot of software talks about privacy the way a kitchen talks about a lock on the cookie jar. The data is already gathered. The promise is that someone will guard it carefully.

That is privacy as a feature: bolted on after the product already needs your information to run. Settings, policies, and assurances try to make the collection feel safe.

There is another posture. Do not collect it. Design so the useful part of the app can live without a dossier on the person using it. No sync means no server copy. No account means no profile to sell or leak.

"We protect it" is a promise about behaviour. "We don't have it" is a promise about architecture. The second one is harder to ship and easier to trust.

That is why privacy shows up early in how we build, not late as a badge. The principle holds whether the product is money, habits, or something quieter still.