Direct answer
Setup and decisions for account and identity privacy work like a chain: you first decide what you’re trying to protect against, then configure services and accounts accordingly, and finally verify that the behavior matches your expectations. For a privacy-conscious digital nomad, this typically means making choices that reduce unnecessary linkability (between your identity and your browsing) and limiting avoidable metadata exposure, while understanding that no single step guarantees anonymity, safety, or reliable access.
How it works in practice
Start with operating conditions: you’ll be using different networks (cafés, hotels, mobile hotspots), multiple devices, and recurring account logins while traveling. Your setup decisions should be consistent and account for how traffic and account sessions are handled.
A common approach is to combine: (1) account-hardening choices such as strong unique passwords and multi-factor authentication, (2) browser and device settings that limit tracking surface you control, and (3) a network-layer privacy tool that changes how your traffic is observed on local networks. The key decision is not “best privacy,” but “best match to your threat model,” such as reducing local eavesdropping risks versus lowering online tracking linkability.
Practical context for digital nomads
Digital nomads often care about two different linkages: identity-to-account linkage (how services connect you over time) and activity-to-location linkage (how observed traffic correlates with where you are). Your setup should address both.
For example, if you frequently log into the same accounts from different countries, identity services may still correlate sessions through normal authentication signals and device/browser characteristics you can’t fully control. Meanwhile, network-layer protection can help with what a local observer can see, but it won’t stop the service provider you log into from seeing that you are using their account.
Limitations to plan around
A VPN (or similar tool) does not guarantee anonymity, safety, or access. Performance and availability vary by network, device, location, provider, and time, so your “setup decision” must include a fallback plan. Also, current product, legal, and empirical claims about specific services should be treated as requiring authoritative verification.