Forward defense · After the cleanup

Stop new leaks

Cleanup removes what's already out there. These habits stop new data from leaking after the cleanup. Minimising data beats poisoning it — that is the consensus, and the caveat the original source itself makes.

1. Alias emails for all future signups

Use a different email alias for every new signup. Your real address never enters a new database, so future breaches expose only throwaway aliases.

Rule of thumb: if a service doesn't need your real email, it doesn't get it.

2. Canadian virtual cards instead of Privacy.com

Privacy.com is US-only — US residents only — so skip it. The Canadian equivalents:

One card per merchant limits what any single breach exposes. A merchant that gets breached only ever sees that one card.

3. A no-logs VPN on untrusted Wi-Fi

Useful on hotel and airport Wi-Fi, where the network itself is the risk. Mullvad is the one cited by the source material — no-logs, anonymous accounts, flat pricing. A VPN does not hide you from the sites you log into; it hides your traffic from the network you're on.

4. Fauxx — optional, experimental Experimental

Fauxx is an open-source Android app (AGPL, via F-Droid or GitHub Releases — the Google Play build is discontinued) that generates continuous, plausible off-demographic synthetic activity to bury your real behavioural signal in decoy traffic.

Honest caveats: battery and data impact; effectiveness debated; it is noise on top of minimisation, not a replacement for it. Try it only if you understand what it does and are comfortable with the trade-offs.

What we deliberately skipped

Two tactics from the same source material did not make the cut:

Minimising what you share beats trying to poison the well after the fact.

Source: forward-defense layer from a vetted Instagram reel by @thepeoplescybersecurity (instagram.com/p/DdwwC68FsVR), October 2026, plus the reel's own caveats and comment consensus.