For travel: - Travel with wiped devices with a cloud backup. - Restore from backup when you reach your destination. - You could be compelled to give up your

For travel: - Travel with wiped devices with a cloud backup. - Restore from backup when you reach your destination. - You could be compelled to give up your cloud login, (since you'll have to know the password in your head) so have a fake one available for plausible deniability. - Your (real) backup needs: browser, password safe, system patches, system hardening. Anything else should likely be delegated to installing from a script, Ansible, etc, after the fact. This helps minimize history and other private information you could carry around (just in case they DO get your real login). - Not sure if necessary, as I haven't heard stories by border agents to give up email passwords, but an extra email address for plausible deniability can't hurt. - All (other) passwords should be stored in a password safe, so you can't be compelled to give them those passwords, since you have no idea what they are anyway. - Passwords should always be generated and be as long as possible for a particular service. - Usernames should always be generated and unique. - Don't use services that restrict password lengths to 20 or less characters. - Don't use services with a known history of hacks or leaks (i'm looking at you Yahoo/Target). All that said, it's pretty terrible that joe user will need to know this information just to travel. I doubt many are technically capable of executing on the above strategies. Even software engineers are unlikely to have such due diligence.