Remote Work Guide

How to Use a VPN for Remote Work in Hotels and Coworking Spaces

Working from a hotel lobby or a shared desk in Singapore brings different risks than your home office. This guide helps you tell apart employer-mandated security from your own privacy choices, set up sensible routing rules, and know exactly when to escalate a VPN problem rather than try to fix it yourself.

Why Hotel and Coworking Wi-Fi Needs Separate Attention

Public Wi-Fi in hotels and coworking spaces is shared by many devices. While HTTPS already encrypts your communication with most websites-protecting passwords and bank details from casual snooping-the network itself can still reveal which domains you visit and how much data you transfer. For remote work, that metadata might include the name of your company’s cloud portal or the timing of your file uploads.

A VPN adds a layer of encryption between your device and the VPN server. This prevents anyone on the same Wi‑Fi from seeing the content or destination of your tunneled traffic. However, the VPN operator could see the IP address of the sites you access through the tunnel, depending on their configuration. A no-logs policy does not remove this technical visibility; it only states that the operator promises not to record that data.

Separate your needs: employer‑mandated access usually goes through a corporate VPN that may log or inspect traffic. Your personal privacy setup is a different tool. Never route personal banking through a work VPN, as the employer may have visibility. Use a separate VPN account for non‑work browsing in shared spaces.

Split Tunnelling: Route Only What Matters Through the VPN

Split tunnelling lets you send some traffic through the VPN tunnel while other traffic goes directly to the internet. For example, your company’s internal server and collaboration tool use the tunnel, while your Spotify streaming or local news website uses your regular connection. This reduces bandwidth demand and can improve speed for the applications that need it most.

Many corporate VPN clients offer split tunnelling as an option. If your employer requires an “always‑on” configuration, you may not be able to enable it yourself-changing that setting could violate policy. In that case, ask IT whether a rule‑based split is possible.

For your own VPN, you can typically configure split tunnelling in the app or operating system. Decide which apps or domains need protection: work email, file storage, internal portals. Leave everything else direct. This setup is especially useful in coworking spaces where a single video call could otherwise saturate the VPN tunnel.

Be aware that split tunnelling can sometimes leak traffic. If your VPN app or device OS has a kill switch, enable it so that when the tunnel drops, all internet access stops until the VPN reconnects. Test this before you rely on it for a deadline.

Always-On VPN: When to Set It and Forget It

An always‑on VPN ensures every bit of traffic from your device goes through the tunnel, with no exceptions. This is common in corporate setups where IT policy demands that all data leaving the device is encrypted to the company’s server. If your employer mandates this, do not disable it, even if it slows down a streaming site. The policy exists to protect company data, not your personal comfort.

For your own remote work setup, always‑on mode is useful when you cannot trust any network-airport lounges, hotel lobbies, conference halls. You set the VPN to start on boot and reconnect automatically. This removes the mental load of remembering to turn it on each time you switch Wi‑Fi.

Two practical considerations: battery life and app compatibility. Always‑on tunnelling consumes more power than a standard connection. If you work from a coworking desk all day, plug in. Some apps, especially certain banking or travel‑booking portals, may block traffic that appears to come from a foreign IP. In that case, you may need to exempt that app from the tunnel or use a server in the same country as the service.

If an always‑on VPN causes a work app to fail, do not disable the VPN yourself. Escalate to your IT team so they can update the rules or add an exception.

Build Your Remote Work Setup: Practical Steps

Start by listing the applications you use for work: email, file sharing, internal chat, project management, video conferencing. Mark each one as mandatory for the tunnel or acceptable on a direct connection. Check your employer’s acceptable use policy-some companies prohibit split tunnelling or require that all traffic goes through their VPN.

Choose a VPN provider that offers a kill switch and supports your operating system. Install the app and configure it for the networks you expect to use: open Wi‑Fi triggers always‑on mode; your home network can use split tunnelling. Test each scenario before you travel.

Keep escalation rules clear. If the VPN breaks an app, try restarting the app first. If that fails, reconnect to a different VPN server. If the issue persists, contact your IT support-do not adjust security settings on your own. For personal VPN problems, check the provider’s status page before contacting their support.

Finally, review your setup every quarter. Networks change, employer policies update, and VPN providers modify their features. What works today in a Singapore coworking space may need adjustment next month in a Bangkok hotel. Stay informed, but avoid changing settings on a live work call.

Build the connection before the trip

Set up mobile data and your VPN while you still have a trusted connection. That leaves time to test both layers and save the instructions you may need after arrival.

Continue at the TPG Mobile VPN travel desk