Why tracking still matters (and what to expect)

Online tracking is rarely a single mechanism. Sites, ad networks, analytics, and device features can collect information through cookies, scripts, browser fingerprints, and account-based identifiers. Even when you reduce one signal (for example, your IP address), other signals may remain, and new tracking methods can appear.

A privacy-conscious digital nomad should also expect that “what happens” depends on operating conditions: the device you use, your browser settings, whether you’re logged in, the network type (home Wi‑Fi, mobile data, public Wi‑Fi), the country/region, and even time-based changes such as policies and routing.

How it works in practice

In day-to-day browsing, tracking often happens when a page loads resources and scripts that can read or store data in your browser. That data can then be reused across sessions or shared with third parties. Some trackers rely on:

  • Identifiers you keep: accounts, saved logins, and long-lived cookies.
  • Identifiers you expose: IP address and network metadata.
  • Signals that can vary subtly: browser configuration, fonts, device characteristics, and behavior patterns.

If you use a privacy tool like a VPN, it may change some network-level signals, but it cannot automatically remove every other identifier, script, or data collection path.

Limitations to keep in mind

Common limitations include:

  1. No guarantee of privacy or safety: reducing tracking from one channel does not eliminate tracking from others.
  2. Inconsistent results: performance and effectiveness can vary with your device, browser, location, and network conditions.
  3. Changing behavior over time: websites update scripts and detection logic, so the same setup may not work the same way later.

Because of this, it’s better to treat online privacy as a continuous risk-management process rather than a one-time switch.

Practical verification steps

To check whether your current setup meaningfully reduces tracking or improves resilience, use verification instead of assumptions:

  • Test with a clean session: use a private/incognito window and sign out where possible to see what still loads and stores. - Observe stored data: after browsing, review cookies and site data for domains you didn’t expect.