Direct answer

Setup and decisions are useful for data minimisation when they reduce what your device, apps, and websites can observe or store about you—especially before sensitive actions like logging in, uploading files, or visiting high-tracking pages. Their usefulness is limited because many forms of tracking still rely on data you voluntarily provide (accounts, identifiers, cookies), on information gathered on the destination side, or on network conditions that change over time.

What “setup” and “decisions” mean for data minimisation

For a privacy-conscious digital nomad, setup decisions usually include browser/app settings, device privacy controls, and choices that affect how traffic is routed. The key idea is to minimise new data exposure during activities likely to trigger tracking: authentication, profile creation, payment flows, and repeated visits.

A simple way to think about it: data minimisation works best when you (1) limit data you send, and (2) limit data others can infer. It tends to be less effective when tracking is driven by identifiers you already have (account logins, long-lived cookies, device fingerprints) or when the service you visit collects rich behavioural data.

How it works in practice

Start with the basics that shape what gets emitted or persisted:

  • Use privacy-focused settings that reduce persistent identifiers where possible (for example, restricting third-party storage and limiting cross-site tracking).
  • Decide how and where you authenticate; sign in only when necessary, and avoid mixing separate identities across contexts.
  • Treat network changes (new country, new Wi‑Fi, roaming) as a chance for different logging, captive portals, or app behaviours.

If you use a VPN, the contribution is typically about reducing direct visibility of your IP to destinations, not about making you “invisible.” Outcomes vary with provider, device, and destination behaviour.

Limitations you should assume

  • A VPN does not guarantee anonymity, safety, or access.
  • Performance and availability vary by network, device, location, provider, and time.
  • Some tracking happens regardless of routing (account-based tracking, first-party cookies, analytics, and device-level signals).

Because of this, data minimisation should be approached as risk reduction, not elimination.