Direct answer
For a privacy-conscious digital nomad, “setup and decisions” means choosing and configuring the browser (and any add-ons) plus deciding how your traffic is routed (e.g., through your operating system, browser, and network). These choices determine what identifiers are reduced, what data is blocked, and what can still leak. The key is to layer controls, then verify what actually happens on real sites from each location.
How it works
Start with operating conditions: which browser you use, whether it is kept up to date, which profiles you use (separate identities when needed), and which privacy-relevant features are enabled (cookie handling, third-party tracking prevention, and permission controls for location/camera/mic). Next, decide on add-ons and their scope: privacy extensions can change what scripts and trackers load, but they also introduce configuration decisions and potential breakage.
Then make a network routing decision at the start of a session. Browser privacy is affected by where DNS requests go, whether your traffic route changes by network, and whether your device applies proxy/VPN-like settings system-wide or only in one application. For nomads, these “routing” decisions matter because airports, hotels, and local networks differ, and your behavior may change when you switch Wi‑Fi, use mobile data, or travel across countries.
Practical context for digital nomads
Use a consistent baseline per travel day: one browser profile for sensitive activities, explicit cookie/permission policies, and a predictable set of extensions. When you switch networks, re-check your baseline rather than assuming it carries over. Also consider that many websites use multiple tracking pathways—cookies, local storage, device fingerprints, and account signals—so a single setting rarely covers everything.
Limitations to keep in mind
A privacy setup does not guarantee anonymity, safety, or reliable access. Performance and behavior can vary by device, browser version, network, location, and time. Additionally, some protections can create trade-offs: blocking trackers may reduce analytics-based functionality, and stricter browser controls can cause login/session issues.
Verification steps you can do
- Check browser privacy settings and extension permissions after each major change (browser update, new add-on, new profile).