Why a VPN here?
Three vectors specific to cafes/coworkings: (1) passive sniffing - a malicious freelancer 5 m from you can capture metadata from your Slack, GitHub, Figma sessions (who talks to whom, active projects, transfer sizes); (2) active MITM - on open WeWork/Spaces Wi-Fi, an attacker can intercept your Notion or Slack cookie and access your workspace for 24-72h; (3) Evil Twin - a fake "WeWork-Guest-Free" SSID captures new members' credentials. A VPN encrypts the entire network layer and neutralizes all three vectors.
Full procedure
- 1
Connect + optional captive portal
Connect to the official space Wi-Fi. Accept the captive portal if present. Verify the auth page is in valid HTTPS (green padlock) - otherwise it's an Evil Twin.
- 2
Enable the VPN immediately
Before opening Slack, GitHub, Figma, Notion, Linear or any work tool. Kill switch mandatory - a VPN drop exposes your credentials to other cafe clients.
- 3
Disable file sharing
On macOS: System Preferences → Sharing → uncheck all. On Windows: mark the Wi-Fi network as "Public". Prevents your MacBook from appearing in Bonjour discovery to other clients.
- 4
Check DNS leak during the session
Open our DNS leak test tool - confirm your DNS is no longer the cafe's. Re-test after 1h, some coworkings force DNS re-routing hourly.
WeWork and Spaces have offered since 2024 a paid "Private Office" Wi-Fi (+€15/month) creating an isolated VLAN for your session - each member isolated from others. Neutralizes internal sniffing. For freelancers with sensitive data (health, finance, legal), this option pays off vs leak risk.
Try NordVPN for this scenario
No marketing fluff.
Frequently asked questions
Is cafe Wi-Fi really dangerous?
Yes, statistically. A 2024 Kaspersky study showed 28% of European cafe public Wi-Fi were vulnerable to passive sniffing, and 7% to active MITM. Numbers are worse on chains (Starbucks, Costa) where Wi-Fi is shared across thousands of sites with little individual maintenance.
Isn't HTTPS alone enough?
For content (email bodies, data typed in Slack), yes. But metadata leaks: sites visited, session duration, request sizes, frequency. On a cafe with 200 freelancers connected, these metadata build an exploitable profile - typically for social engineering or competitor scouting. A VPN also encrypts the metadata.
Does the VPN slow down collaborative work?
Marginally. On typical cafe Wi-Fi (10-30 Mbps), VPN adds 3-8 ms latency and costs 2-5% throughput. Imperceptible for Slack, GitHub, Figma. For Zoom/Teams video, pick a VPN server geographically close to the service DC (Amsterdam or Frankfurt in Europe).