Most people try to "do privacy" by flipping toggles: disable a permission here, download an app there, maybe add a VPN and call it done.
That approach fails for the same reason crash diets fail: it's not a system.
Privacy is what happens when you intentionally design:
- what you share
- where it lives
- how easily it can be correlated
- how quickly it can be used against you
Here's the mental model I use because it actually holds up in real life: inputs, outputs, and choke points.
Inputs: what you intentionally hand out
Inputs are the identifiers you give away on purpose:
- the email you use for signups
- the phone number you enter "just in case"
- the address you put on a form
- the profile photo you reuse everywhere
- the accounts you link together
Inputs aren't just "data." They're handles other systems can grab.
Ask yourself:
- Which identifiers do I give out by default?
- Which ones are permanent (hard to change) vs. disposable?
- Where am I reusing the same input across unrelated contexts?
You don't need to stop sharing. You need to stop reusing.
Outputs: what gets revealed about you
Outputs are the side effects you didn't publish, but the ecosystem publishes for you:
- people-search pages
- marketing profiles
- "suggested contacts"
- identity graphs that connect family members, old addresses, and phone numbers
- search results that make you one-click legible
Outputs happen because inputs get copied, aggregated, and matched.
If you hand every vendor the same phone number, that number becomes a universal join key.
If you use the same email everywhere, your accounts become stitchable.
Outputs are the math of your inputs.
Choke points: where a small change removes lots of exposure
A privacy system becomes manageable when you focus on the few places that shape everything downstream:
- Primary email + phone used for signups
- Public-facing address used in business records and registrations
- Core accounts (Apple/Google, password manager, banking)
- Public profiles that define how people find and verify you
Fixing a choke point is high leverage: one change prevents dozens of future messes.
A baseline system you can actually run
If you want privacy that survives busy weeks, start here:
-
One public identity, one private identity.
Public = credibility. Private = life. They shouldn't overlap. -
Use "real" inputs only where you must.
If a site doesn't need your real phone number, don't give it one. -
Default to less.
Optional field? Skip it. Public profile? Prune it. -
Quarterly cleanup (30 minutes).
Review your top five exposures: search results, broker listings, social profiles, business filings, and old accounts.
Privacy isn't a heroic act. It's a small system you maintain.
Stop hunting toggles. Start designing your system.
Educational only; not legal advice.