Writing in Cafés and Libraries: A Public Wi-Fi Privacy Routine That Takes Two Minutes
Writing in cafés, libraries or co-working spaces? A two-minute public Wi-Fi privacy routine that protects your drafts, accounts and research notes.
Plenty of writers do their best work away from home. A café corner, a library desk, a co-working space with decent coffee. The change of scene helps. The shared Wi-Fi, not so much.
On a public network, you're sharing the connection with strangers and trusting whoever runs the router. For casual browsing that's usually fine. But writers are often logged into email, cloud drives and writing apps full of unpublished work, research notes and sometimes sources who've asked not to be named.
Here's a short routine to run each time you sit down.
Key points:
1. Log in to the Wi-Fi first, then turn on your VPN. Doing it the other way round is why the login page never shows up.
2. Check your IP address and run a leak test once the VPN is on. It takes under a minute.
3. Keep sensitive notes inside your writing app, not in chat messages or emails to yourself.
Why Public Wi-Fi Is Riskier Than It Feels
The risks aren't dramatic, but they're real. WhatsMyIP.now's guide to how public Wi-Fi affects your privacy lists the main ones:
- Rogue hotspots: a fake network with a believable name, like "LibraryFreeWiFi"
- Packet sniffing: someone on the network recording unencrypted traffic
- DNS hijacking: the network quietly sending your lookups to a server it controls
- Session hijacking: stolen login cookies used to act as you
HTTPS protects the content of most pages you visit, but it doesn't solve every risk on that list. That's why a VPN still makes sense for anyone doing real work on a shared connection. If you're fuzzy on the difference, the explainer on HTTP vs HTTPS clears it up in a few minutes.
Step 1: Join the Right Network
Ask staff for the exact network name. Rogue hotspots count on you guessing. If two networks have nearly the same name, don't pick one at random.
Step 2: Log In to the Wi-Fi Before Starting Your VPN
This is the step that trips people up. You connect, your VPN starts automatically, and the café's login page never appears. Nothing loads.
That's your VPN doing its job. It wraps your traffic in an encrypted tunnel before it reaches the local router, so the router can't show you its login page. The WhatsMyIP.now guide on why your VPN blocks the coffee shop login screen explains it in detail. The fix is simple:
- Pause or disconnect the VPN.
- Join the Wi-Fi and finish the login page.
- Turn the VPN back on.
That login page has a name, by the way: a captive portal. It's the "accept the terms to continue" screen most public networks use.
Step 3: Check Your IP and Run a Leak Test
With the VPN back on, check which public IP address you're showing. It should belong to your VPN provider, not the café's internet provider. The same page also tells you whether a VPN or proxy is detected on your connection.
Then run the VPN leak test. It checks three things at once: your visible IP address, which DNS server answers your lookups, and whether your browser leaks your real address through WebRTC. If any of those point back to the local network, your VPN isn't covering everything, and it's worth fixing before you log in to anything important.
The whole step takes less than a minute. Do it once for each new location.
Step 4: Be Careful Where Your Work Lives
Here's something that doesn't get talked about much. Writers on the move tend to scatter their work. A quote goes into a chat message to yourself. An interview note goes into an email draft. A paragraph ends up in a phone memo because the laptop was closed.
Every one of those is another account to protect, and another place a sensitive note can leak from. It's also a mess to pull together when you finally sit down to write.
A better habit is to capture everything in one place that's built for drafts. That's why we built the rough notes panel into every Strut project: notes save as you type, sit one click from the manuscript they belong to, and you can record a voice note straight into the project instead of leaving it in a phone app. Whatever tool you use, fewer places means fewer things to secure.
Step 5: Check Your Main Email for Breaches
If you use the same email address everywhere, check now and then whether it's shown up in a known data breach. The email breach check looks your address up against publicly known breaches (a free account is required). If it finds something, change that password everywhere you've reused it and turn on two-factor authentication.
Step 6: Make the Session Count
Security is only half of it. Public places are full of distractions, and the Wi-Fi itself is one of them. Some writers get more done by switching Wi-Fi off entirely for the first hour.
If you work in short, planned bursts, a simple plan helps. Strut's free focus sprint planner runs in your browser and sends nothing anywhere. It gives you one finish line, one protected block of work and a five-minute close, which is handy when you only have until the lunch crowd arrives.
A Two-Minute Checklist
| When | What to do |
|---|---|
| Sitting down | Confirm the network name with staff |
| Connecting | Log in to the Wi-Fi first, then start the VPN |
| Before logging in anywhere | Check your IP and run the leak test |
| While working | Keep notes in one app, not in chats or emails |
| Once a month | Run a breach check on your main email |
| Leaving | Log out of any shared computer and forget the network if you won't be back |
The Short Version
Log in to the Wi-Fi, then start your VPN. Check your IP and run a leak test. Keep your notes in one place instead of scattering them across chats and emails. It's two minutes of setup for a session where you can focus on the writing instead of wondering who else is on the network.
Write your next long piece in Strut
Keep rough notes, sources and drafts in one project, with AI that works on the passage you select rather than replacing your voice.