What “online privacy vs tracking” really means

Online privacy and tracking are connected, but they are not the same thing. “Tracking” is the process of collecting signals about your activity or identity—such as which sites you visit, what device you use, and sometimes which accounts you are associated with. “Privacy” is how much of that information is revealed, inferred, stored, or shared.

For a privacy-conscious digital nomad, the practical question is: which observers can still see or infer what you do, even if you change some settings? Common observers include the websites and apps you use, advertising and analytics services, your internet service/provider, and—depending on your setup—networks in the path between you and the service.

A useful framing is: you can reduce exposure (what gets collected and where it goes), but you usually cannot fully control inference (what can be deduced from patterns, device traits, or logged-in accounts).

How tracking works in practice

Tracking typically comes from a combination of identifiers and measurement methods. The exact mix varies by website, app, and technology, but many real-world flows share these patterns:

  • Browser and device signals: browser type, operating system, language/locale, time zone, screen characteristics, and other fingerprints.
  • Cookies and storage: first-party or third-party cookies, local storage, and sometimes persistent identifiers.
  • Network and session behavior: IP address and session patterns can be used to estimate or correlate activity.
  • Account-based linking: when you are logged in, many trackers can associate activity across sessions and devices.
  • Script and tag execution: pages load code from multiple domains (analytics, ads, social widgets), which can observe your visit.

Even when a specific tracker is blocked, the site can still measure outcomes (for example, page load and navigation) using remaining tags. Also, “anonymous” tracking claims are often conditional: results may change if you log in, accept permissions, allow third-party content, or use browser features that reduce separation across contexts.

Which privacy tools help—and what operating conditions matter

Privacy approaches usually fall into layers. None of them removes tracking in every case, but together they can reduce the amount of information that gets exposed.

1) Browser and app controls

These are often the most direct ways to limit tracking because many trackers rely on browser features.

  • Limit or block third-party cookies and cross-site tracking features where available.
  • Review site permissions (location, notifications, camera/microphone) and disable ones you do not need.
  • Use tracking protection or reputable ad/tracker blocking features in the browser.
  • Separate identities: using separate browser profiles for different “roles” (work vs personal) can reduce cross-linking by cookies and local storage.

Operating conditions: behavior differs by browser version, browser privacy settings, and whether a site still functions without certain scripts.

2) Network-level tools

A VPN (virtual private network) changes how your traffic appears to some observers. In broad terms, it can shift what your internet connection sees and can help reduce visibility of your traffic to certain third parties that would otherwise observe your direct network path.

However, for digital nomads, the key limitation is conditionality: VPNs do not automatically prevent tracking performed by websites and apps themselves. If you visit a site while logged in, or if the site runs tracking scripts, those parties can often still observe your activity.

Also, performance and availability are not constant. Performance and connection behavior vary by network, device, location, provider, and time.

3) DNS and security features

Even without claiming specific technical outcomes, it helps to understand that DNS-related decisions can affect which network services resolve names and how quickly or reliably connections establish. Some users combine DNS and browser controls for more consistent behavior.

Operating conditions: captive portals, hotel Wi‑Fi, and network filtering can change how services behave, which can affect both privacy controls and day-to-day access.

Key limitations to keep in mind

Several limitations should guide expectations:

  • A VPN does not guarantee anonymity, safety, or access.
  • Online tracking can still occur via device/browser signals, site scripts, and account login, even if network visibility is reduced.
  • Performance and availability vary by network, device, location, provider and time.
  • Current product, legal, and empirical claims should be treated as needing verification because capabilities and enforcement can change.

For digital nomads, the most common practical failure mode is “it worked yesterday.” Your settings might remain the same, but network paths, browser updates, and website tracking policies change. That’s why verification matters.

Practical verification steps you can do

Instead of trusting marketing statements, verify outcomes using observable signals. Here are practical checks that work across most privacy setups.

1) Confirm which identifier is being used

  • Check your public-facing IP address in a way that reflects your current browsing session.
  • Compare results across networks (mobile data vs Wi‑Fi) to understand how your environment changes what others can see.

If you use a VPN, verify that the active connection is the one you expect for your browsing session, not just for background apps.

2) Measure tracking signals at the browser level

Use your browser’s developer tools to look for network requests from tracking/analytics/ad domains.

  • Before changing settings, note the kinds of requests that appear.
  • After enabling tracking protection or blockers, confirm which requests are reduced or blocked.

3) Check login and cross-site linking risk

  • If you are logged in to major services, assume that tracking can be account-linked.
  • Test in a private/incognito window and compare results to a normal session.

If privacy gains mostly disappear in incognito (or vice versa), that pattern is a useful indicator that account state and stored data are driving the tracking.

4) Watch permissions and persistent storage

  • Review site permissions for location and notifications.
  • Clear site data for specific sites you test, then revisit to see what comes back.

This helps you understand which trackers rely on stored identifiers rather than only on immediate session signals.

5) Validate real-world usability

Anti-tracking changes can break functionality (logins, embedded content, payment flows, or essential scripts).

  • Test your key daily tasks: email access, banking/app sign-in (if relevant), and the websites you rely on.
  • If a site stops working, try narrowing the change: adjust permissions or allowlist only what is required.

What to do next, depending on your situation

If you want to “own” this knowledge area, the best next step is to create a small repeatable routine:

  • Choose one or two browsers/profiles for your main identities.
  • Apply your baseline tracking protections.
  • Verify with observable checks (IP/session behavior and network request reductions).
  • Re-check after updates, travel moves, or when a website behaves differently.

This approach keeps you from chasing uncertain claims and instead anchors your privacy posture in what you can observe—across the environments you actually use.