Privacy & security
Joining their Wi-Fi is a logged event.
It feels harmless — just hop on the guest network to get your slides up. But connecting to any managed network creates records, and on a sensitive engagement those records are exactly what you didn't mean to leave.
6 min read
Apr 2026
Every claim sourced · 3 references
You're pitching to a new client. The polite offer comes: "here's the Wi-Fi password." You connect, present, leave — and never think about it again. Their network did think about it, though. It kept notes.
✕ The myth
"I just borrowed their Wi-Fi for ten minutes — no trace."
I only loaded my slides; nothing to see.
✓ The reality
Connecting is a recorded transaction.
A managed network typically logs your device name and MAC address, a DHCP lease, and your DNS queries — the domains you looked up — retained per their policy.
None of this is exotic; it's routine network hygiene, and logging is a recommended security practice.1 But "routine" cuts both ways: your presence, your device identity, and metadata about where you connected are now on someone else's books. Under data-protection principles, the safest data is the data that was never collected in the first place2 — and that logic applies to you as much as to them.
What they can — and can't — see
To be fair about it: on modern HTTPS sites they generally can't read the contents of your traffic, and most IT teams have zero interest in your lunch-break browsing. What they can see is the shape of it — which devices connected, when, and which domains were resolved — plus whatever their captive portal made you agree to. On an ordinary visit that's a non-issue. On a competitive pitch, a due-diligence meeting, or anything you'd rather not have timestamped on the counterparty's infrastructure, it's the opposite of ideal.
MAC + DHCP
Your device's hardware identity and the address it was leased — a fingerprint of your visit.
1
DNS
Every domain your device resolved while connected — the map of where you went.
1
Minimise
Data-protection's first instinct: don't create the record you don't need.
2
⚖ The honest bit — this is normal, not a conspiracy
Logging isn't spying, and HTTPS protects a lot.
Let's not be dramatic: network logs exist for security and troubleshooting, not to snoop on visiting presenters, and encryption hides your actual content. If you're doing routine internal work, borrowing the Wi-Fi is completely fine. The point is narrower — when discretion matters, the cleanest position is simply not to be in the logs at all. And note the flip side: not joining their network means you also lose the convenience of it (printing, internal resources). Choose per the sensitivity of the room.
Where SyncBy!App fits
Because SyncBy connects your phone to the screen directly — and can run entirely over your own mobile data — you can present without ever joining the client's network. No lease, no MAC in their logs, no DNS trail from your device on their infrastructure. When the meeting is sensitive, "I didn't need your Wi-Fi, thanks" is a quietly strong position.
TL;DR
- Joining a managed network logs your device name, MAC, DHCP lease and DNS queries.1
- It's routine and HTTPS hides content — but your presence and metadata are on their books.
- Data-protection's first rule: don't generate the record you don't need.2
- For sensitive meetings, present over your own data and skip their network entirely.