Direct answer

Setup and decisions in hotels and airports follow the same privacy logic: identify the network you’re using, choose protections that match your device and threat model, then verify that your expected protection is actually working before you rely on it.

In practice, you’ll make a few consistent choices: whether to use a trusted encrypted connection, how to limit passive tracking from your browser and apps, and what fallback to use if the network is restrictive or unreliable.

How it works

First, treat the Wi‑Fi or airport network as an unknown environment. Public networks commonly involve extra intermediaries (captive portals, shared infrastructure, and more observers on-path than you’d see on private home networks). That means your setup should emphasize encryption in transit and reduced local tracking.

Second, align your device with the goal. For many digital nomads, the biggest privacy gains come from controlling what your apps and browser reveal (for example, permissions, background sync, and persistent identifiers). An encrypted tunnel alone doesn’t prevent all tracking; it mainly changes how network observers can interpret traffic.

Third, decide your “resilient access” plan. In transit locations, connectivity can fluctuate. Build decisions around being able to switch networks (hotel Wi‑Fi, mobile data, or another available option) without assuming one path will always work.

Practical context for hotels and airports

In hotels, the network is still shared, but the setup environment is often stable: you can usually test, confirm, and then settle into a workflow. In airports, networks can be more constrained and session-based, which can make reconnection and verification more important.

A practical approach is to:

  • Start with a quick test after connecting (confirm you’re actually using the intended encrypted path).
  • Keep sessions minimal at first (avoid logging into high-value accounts until you’ve verified basics).
  • Use app-level privacy hygiene where possible (disable unnecessary location/background permissions for the duration of the session).

If you’re using an encrypted connection, remember that performance and availability can vary widely by network, device, location, and time. Treat reliability as something you validate, not something you assume.