The Ultimate Online Privacy Guide for 2026

Data brokers and breach-aggregation sites build profiles by joining records on shared identifiers. Email address is the strongest join key most people have, followed by phone number.

Compartmentalisation means deliberately using different identifiers for different categories of account, so a leak from a retailer can't be joined to your bank, your employer, or your health records.

The critical tier — banking, tax, healthcare, government, your primary identity provider — should be an address you never publish, never use for marketing signups, and never post publicly. It exists to receive recovery mail and nothing else.

The alias tier covers everything you plan to keep using: each service gets its own forwarding address that you can disable individually. When one starts leaking, you know exactly who leaked it, and you can shut it off without changing anything else.

The disposable tier covers gated downloads, one-off quotes, forum registrations, and trials you don't expect to renew. These addresses expire on their own, which is the point.

Credential stuffing — replaying leaked passwords across other sites — remains the most common way ordinary accounts are taken over, and unique passwords make it structurally impossible.

For second factors, passkeys and hardware keys resist phishing because the credential is bound to the site's origin. SMS codes are better than nothing but can be intercepted through SIM swaps; app-based codes sit in between.

• Unique, generated passwords in a manager — the manager is the point, not the memorisation.
• Passkeys or a hardware key on email, banking, and your identity provider.
• Review and remove stale account sessions and connected third-party apps yearly.
• Lock down account recovery: recovery email and phone are the real front door.

Fingerprinting identifies you from the combination of your fonts, screen metrics, extensions, and settings. Blending in with a large population of default configurations beats a bespoke setup that only a handful of people share.

Enable HTTPS-only mode, block third-party cookies, and clear site data on close for the profile you use for casual browsing. Keep a separate profile for accounts you stay signed into — that separation is the browser-level version of compartmentalisation.

Use a VPN for a specific reason: untrusted public networks, hiding traffic from an ISP that monetises it, or accessing your own resources. Running one permanently in the belief that it prevents tracking is misplaced — you're still signed into the same accounts.

Encrypted DNS (DNS over HTTPS or TLS) is a cheap, always-on improvement with no meaningful downside, and a filtering resolver can also block known tracker and malware domains network-wide.

Optional form fields are optional. Date of birth, physical address, and phone number are frequently requested and rarely necessary for the service being delivered, and each one strengthens a broker's ability to join records.

Social sign-in is convenient and quietly expensive: it hands one company a live map of every service you use and makes those accounts dependent on that relationship continuing.

• Leave optional fields empty; supply the minimum a service genuinely needs.
• Prefer email-and-password over social sign-in for services you want to keep separate.
• Turn off ad personalisation in the accounts that offer it — it's a real reduction in profiling inputs.

Start by identifying which of your addresses appear in known breaches, then change those passwords and any account sharing them. This is the highest-value cleanup step because it closes credential-stuffing exposure.

Broker opt-outs are slower. Each broker has its own process, and the same data flows back in from upstream sources, so treat it as maintenance on a schedule rather than a one-time project.

These rights are the difference between hiding from a data holder and making them delete the data. A disposable inbox stops future mail; an erasure request removes the record.

Requests are usually free and time-bound — commonly one month under GDPR, extendable in limited circumstances. Keep them short and specific: identify yourself, state the right you are exercising, and name the data.

The common thread is that these measures feel protective while leaving the actual linkage — shared email addresses, reused passwords, signed-in sessions — untouched.

If a product can't explain which specific linkage it breaks, it probably doesn't break one.

Sequence matters because each step reduces the work in the next one. Fixing credentials first means the breach cleanup later only has to rotate what is still reused, and building the email tiers before the cleanup means new signups stop adding to the pile while you work through the old ones.

• Week 1 — password manager, unique passwords on email and finance, passkeys where available.
• Week 2 — create the private/alias/disposable tiers and migrate critical accounts to the private address.
• Week 3 — browser profiles, content blocker, encrypted DNS.
• Week 4 — breach check, credential rotation, first broker opt-out sweep.
• Ongoing — quarterly session review and a repeat opt-out sweep twice a year.