
Surviving In A Surveillance State
Privacy protection starts with the information you want to protect and the realistic ways it could be exposed. No VPN, password manager or hardware key makes an account or device immune to compromise. Use several appropriate controls and maintain a recovery plan.

Protect accounts and recovery
Use unique credentials, supported additional sign-in protection and up-to-date recovery details. Review account access and connected applications. A hardware key protects supported authentication workflows; it does not remove every recovery, device or social-engineering risk.
Understand the limits of a VPN
A VPN changes which network path carries your traffic and whom you trust with parts of that traffic. It is not a universal anonymity service and does not remove tracking through signed-in accounts, cookies, malicious software or information you disclose. Check the provider's actual practices rather than a generic no-logs promise.
Reduce unnecessary disclosure
Review app permissions, sharing settings and publicly visible personal information. Use supported privacy options without assuming false identity details are acceptable for every contract or service. Necessary legal or account-verification requirements still need to be met.
Prepare devices for disposal appropriately
Follow current device and storage guidance for secure removal of data. A universal multi-pass overwrite instruction is not suitable for every storage technology. Verify necessary backups and account removal before disposal; use qualified help where sensitive data requires a defined sanitisation process.
Do not confuse tools with assurance
A consumer RF detector cannot certify that a phone is free of malware or that a room contains no recorder. Choose an inspection scope and appropriate expertise. For routine phone protection, see the phone security checklist.
Prefer documented controls and tested recovery over absolute claims about state access, untraceability or impenetrable storage.



