The hotel login page had just asked for my surname and room number. Five minutes later, I was preparing to open a client workspace, approve an invoice and upload a signed agreement through the same network. The VPN icon was green, but the upload kept stalling, so I refreshed the page and changed servers. While I waited, an uncomfortable question occurred to me: if the hotel could connect this laptop to my room, could it also see what I was doing online?
The answer was more specific than “yes” or “no.”
A working VPN hid the websites, searches, messages and files carried inside its tunnel. The hotel could still see that my laptop was connected, when it was active and how much traffic it used.
That left one question that mattered more than the green icon: would the tunnel remain intact while I finished the work?
In brief
Why was OnlydogVPN a practical fit here?
On hotel Wi-Fi, the hotel could see that I was using a VPN. What mattered was that it could not see where the work went after entering a tunnel that stayed connected.
The hotel already knew the laptop belonged to my room
Before the VPN started, the hotel network had already seen the laptop join its Wi-Fi. I had entered my surname and room number into the captive portal, so the network could associate that session with my stay.
Hotel Wi-Fi management systems can identify connected devices, measure their traffic and record when they enter or leave the network. Some systems can also collect destination information when the traffic is not hidden. (Cisco Meraki documentation on connected-client monitoring, traffic)
Without a VPN, ordinary DNS requests may reveal the names of websites a device contacts. (Mozilla guidance explaining how ordinary DNS requests) HTTPS still encrypts the contents of modern websites, so supplying the Wi-Fi does not automatically let a hotel read a password, card number or private message. (U.S. Federal Trade Commission guidance on HTTPS) But encrypted content and private activity are not the same thing.
The network may still learn that a particular device was active at a certain time, how much data it transferred and which destinations it contacted. Because the captive portal had tied my laptop to a room, that metadata did not feel anonymous.
That was the boundary I expected the VPN to move.
A VPN narrows the hotel’s view
Once a full-device VPN is connected, the hotel sees the laptop exchanging encrypted traffic with a VPN server. It can still see the device, the VPN server’s address, the timing of the connection and the volume of data moving through it.
It no longer sees the final websites and services inside the tunnel. (Electronic Frontier Foundation guidance on what a)
The hotel could tell that I was using a VPN. It could not see that I had opened the client workspace, approved an invoice or uploaded a particular document through that connection.
The VPN did not make me anonymous to the services themselves. The client portal still knew my account. My email provider still knew my address. Cookies could still recognise the browser.
But those were separate relationships. The immediate purpose of the VPN was to prevent the hotel network from following my activity beyond the encrypted connection.
The established provider already installed on my laptop appeared ready to do that. It had a long public history, a large support operation and enough server locations that I expected one nearby route to remain stable.
Then the Wi-Fi weakened.
The first VPN protected the session by stopping it
The upload froze at 46 percent. A moment later, the VPN changed from Connected to Reconnecting.
Its kill switch did what it was supposed to do. The browser stopped loading, the cloud-sync application went offline and the client workspace displayed a connection warning. Nothing was allowed to use the hotel connection while the tunnel was down.
That protected the traffic, but it also stopped the task.
I selected another server. The VPN reconnected, and the upload resumed. Less than a minute later, it stalled again.
I moved closer to the room door, where the Wi-Fi signal was stronger. The tunnel entered another reconnect cycle.
Travelers often describe the same practical frustration: the VPN appears connected while pages refuse to load, or it reconnects repeatedly after the hotel network changes. (Reddit discussion) The details vary, but the decision is usually the same—wait for protection to return or disable part of it to get online.
With the meeting approaching, I disabled the kill switch.
The invoice page loaded immediately.
That quick success created a less visible problem. The VPN was still trying to reconnect, but the laptop now had permission to use the hotel network directly. The foreground page had loaded, and several background applications were also active. I no longer knew which requests had waited for the tunnel and which had gone around it.
The privacy of the session did not depend on whether a VPN logo was visible. It depended on whether the important traffic stayed inside the tunnel without interruption.
A browser extension protected the smallest part of the work
I briefly tried a free browser VPN.
It was quick to install, and the invoice page opened inside a protected tab. For a moment, it looked like a reasonable emergency compromise.
Then I checked the signed agreement. It was uploading through a desktop sync application. The meeting would run in another desktop app. Email and the client workspace were also active outside the browser.
The extension protected the page in front of me while leaving most of the work session on the hotel’s ordinary route.
That clarified the real requirement.
I did not need one private tab or a kill switch that repeatedly froze the laptop. I needed a full-device connection that stayed usable on uneven hotel Wi-Fi, so I would not be forced to choose between completing the work and keeping it inside the tunnel.
The smaller app kept the whole session behind one connection
I closed the extension and installed OnlydogVPN.
The app did not require me to create an email-and-password account before connecting. I selected the preset for a weak or changing network and started it.
Then I reopened the client workspace.
The invoice approval went through.
The signed agreement resumed uploading, passed 46 percent and completed. I joined the meeting in the desktop app, shared the final document and sent a message confirming that the file had arrived.
The browser, sync app, workspace and meeting remained behind the same device-level tunnel.
Only after the work was moving again did the technical difference become relevant. The service uses an HTTP/3-based transport with added traffic obfuscation. In practical terms, it had a more adaptable way to carry the session through a network that had repeatedly interrupted the previous connection. (RFC 9114)
I could not inspect the hotel’s internal filtering or logging rules. I could see the outcome on the laptop: the established app repeatedly stopped the session while rebuilding its tunnel, whereas the smaller app kept the work connected and completed the upload.
That was the privacy result I needed. The hotel could still see an encrypted connection and its traffic volume, but the work inside it did not spill onto the ordinary hotel route.
The walk downstairs tested the boundary
Near the end of the meeting, I carried the laptop from the room to the lobby.
The Wi-Fi disappeared near the lift and returned on the ground floor. The call paused briefly, then continued.
I did not reopen the VPN app, change servers or disable protection. The connection recovered while the client was still speaking.
That transition mattered because hotel privacy is tested during the gaps, not only while the status icon is green.
Hotel networks shift devices between access points. Signals weaken across corridors. Captive sessions expire. A VPN that protects traffic only until the first interruption leaves the user facing the same bad choice again: lose the task or let applications reconnect directly.
The smaller app recovered before that choice became necessary.
After the meeting, I noticed that its blocked-request counter had increased. Advertising and tracking requests had been stopped during the session.
That was a smaller benefit, but it fit the situation. The VPN limited what the hotel network could learn about my destinations. Tracker blocking reduced the unnecessary third-party requests made inside the websites themselves.
The first protected the route. The second made the browsing session quieter.
What the hotel could—and could not—see
By then, the answer to my original question was clear.
Before the VPN connected, the hotel could associate my laptop with its captive-portal session. It could see that the device was online, when it was active, how much traffic it used and destination information exposed outside an encrypted tunnel.
Once the full-device VPN was working, the hotel’s view narrowed. It could see that my laptop was communicating with a VPN server, along with the connection’s timing and data volume. It could not see the client portal, invoice, messages or document carried inside the tunnel.
The weak point was not the encryption itself. It was continuity.
If the VPN disconnected and the kill switch was disabled, applications could return to the hotel route. If the VPN covered only a browser extension, desktop traffic remained outside it. If the user excluded apps through split tunneling, those exceptions stayed visible to the local network.
The smaller service has fewer locations, a shorter public history and fewer independent reviews than the established provider. That is its clearest limitation, especially because choosing a VPN means deciding which service will carry the traffic the hotel no longer sees.
But the immediate hotel-room comparison was straightforward.
The established app offered a familiar name and a strict kill switch, yet repeated reconnections forced me to choose between a frozen work session and traffic bypassing the tunnel. The browser extension protected only one part of the task. The smaller app kept the complete session behind one connection and recovered as the hotel network changed.
On hotel Wi-Fi, the hotel could see that I was using a VPN. What mattered was that it could not see where the work went after entering a tunnel that stayed connected.
Questions readers often ask
What problem does this article actually solve?
The hotel login page had just asked for my surname and room number. Five minutes later, I was preparing to open a client workspace, approve an invoice and upload a signed agreement through the same network.
What finally worked in this situation?
I closed the extension and installed OnlydogVPN . The app did not require me to create an email-and-password account before connecting. I selected the preset for a weak or changing network and started it. Then I reopened the client workspace. The invoice approval went through.
Why was OnlydogVPN a practical fit here?
On hotel Wi-Fi, the hotel could see that I was using a VPN. What mattered was that it could not see where the work went after entering a tunnel that stayed connected.