VPN privacy and security explained
Decide whether you need a VPN. Understand HTTPS, provider trust, browser-only coverage, kill switches, split tunneling and practical checks before choosing a service.
A VPN, or virtual private network, routes selected network traffic through another network using an encrypted connection. A consumer VPN can hide your usual public IP address from the sites reached through it and reduce what the local network can inspect. It also places the VPN operator in a position of trust.
A VPN can be useful for a particular privacy or remote-access need. It does not remove malware, verify an email sender, or make a fraudulent website trustworthy. Begin with the job you need it to do rather than an advertisement saying your computer is unprotected without one.
Decide whether a VPN addresses your concern
| What you want to do | Useful next step | What a VPN does not settle |
|---|---|---|
| Reduce network visibility of traffic you route through a tunnel | Evaluate a provider and its supported device app | Whether that provider’s data handling suits you |
| Use a work network remotely | Follow your organization’s approved access instructions | A consumer subscription does not grant company access |
| Browse on public Wi-Fi | Check the network, HTTPS and device updates; consider a VPN for your privacy needs | The hotspot, website or download can still be deceptive |
| Hide your usual public IP from a website | Confirm that the relevant connection is routed through the VPN | Signing in can still identify you to that website |
| Verify an unexpected email or payment request | Use phishing checks and independent confirmation | A changed IP address cannot authenticate the request |
| Fix pop-ups, redirects or an infected device | Follow the beginner investigation | A tunnel does not remove the cause or repair exposed accounts |
Write a simple requirement before comparing services: “I want my laptop’s relevant connections routed through a provider I have evaluated.” Then check which app, platform and settings meet that requirement. “Make everything safe” is too broad to evaluate.
Understand the tunnel and HTTPS separately
For traffic actually inside the tunnel, the connection from the device to the VPN endpoint is encrypted. The local network or internet provider can still observe a connection to the VPN and information such as its timing and traffic volume. At the other end, the service forwards the traffic toward its destination. That changes the observer; it does not remove every observer.
EFF’s VPN explanation discusses this trust change and warns against promises of complete anonymity. Decide whether reducing the local network’s visibility is useful to you and whether you trust the provider that receives the connection.
HTTPS provides a separate encrypted connection between the browser and the website. Mozilla’s HTTPS-Only guidance explains that protection and the warning when a secure version is unavailable. The VPN operator can handle routing information without thereby reading properly encrypted HTTPS passwords or page content. A VPN does not replace HTTPS for the onward connection from its server to the website. Avoid entering sensitive information over plain HTTP or bypassing a certificate warning to finish a transaction.
Most web browsing already uses HTTPS. Do not assume everyone on a café network can read the passwords you send to correctly authenticated HTTPS sites. Network metadata and other applications’ connections are different questions. Conversely, encryption to a fake sign-in site protects delivery to the wrong recipient; it does not validate that recipient’s request.
On unfamiliar Wi-Fi, confirm the network name through a trusted route and treat the access portal as an unverified request. Do not supply your primary email password, install an unexpected certificate, or disable protection just because a page says access requires it. Prefer another trusted connection if the portal or network makes unreasonable demands.
Check what the app actually covers
| Connection arrangement | Scope to establish | Common misunderstanding |
|---|---|---|
| Device VPN application | Which traffic, DNS requests and exceptions the app routes on your platform | The app being installed is mistaken for an active connection |
| Browser VPN extension | The supported browser, profile and enabled window modes | Other browsers, mail clients and apps are assumed to use it |
| Work VPN | The organization’s destinations, routing and device policy | It is assumed to be a private consumer browsing service |
| Router VPN | Which devices and routes use the configured tunnel | Every device is assumed to be covered without checking |
| Safari Private Relay | Apple’s documented relay scope and account requirements | A Safari privacy feature is assumed to cover every app |
For a concrete example, Proton’s browser-extension guide says its extension covers that browser’s traffic, rather than other applications or browsers. It documents Chrome and Firefox extensions, private-window enablement, and a Firefox DNS configuration caveat. Read those limitations before treating an extension as device-wide protection. Its current guide makes the extension available to free Proton accounts; that does not establish every service feature’s entitlement.
The same guide documents split-tunneling choices that either exclude selected sites or cover only selected sites. These have opposite effects. A green connection indicator does not show that a particular excluded destination uses the tunnel.
Apple’s Private Relay explanation describes an iCloud+ feature for Safari browsing using two relays, with regional availability limits. Use its documented scope rather than assuming a general device VPN. On Windows, Microsoft’s VPN setup guide requires a profile and settings supplied by a service or organization. The built-in connection interface alone does not give you a VPN provider or subscription.
Inspect provider claims before choosing a plan
A privacy policy should answer concrete questions about data and responsibility. Use it alongside public technical documentation, app support and any published assessment. A store listing, familiar logo or “no logs” headline is insufficient evidence on its own.
| Question to ask | Information worth finding | Decision it helps you make |
|---|---|---|
| Who operates the service? | Named operating company, ownership and responsible contacts | Whether you can identify who receives the trust |
| What is collected? | Traffic, connection records, account, payment, telemetry and support data | Whether the actual categories match your privacy need |
| What was assessed? | Public report, date, app or infrastructure scope and findings | Whether an audit addresses the component you will use |
| What works on my device? | Supported OS, app version, connection and blocking limitations | Whether a feature exists in your configuration |
| How is the service funded? | Subscription or free-tier model and stated data practices | Whether the offer’s tradeoffs are understandable |
| What happens after a trial? | Paid entitlement, renewal, cancellation and device allowance | Whether you can keep the intended arrangement |
An assessment is evidence about its stated scope and date. It cannot promise unchanged future behavior. Prefer reading the report over converting an “audited” badge into a universal security rating. Likewise, paid does not automatically mean private, and a free tier is not automatically malicious.
As an example of the distinctions a policy can make, Mullvad’s data policy says it does not log user traffic or DNS requests while separately describing account, payment, support and operational data. That is a provider statement, not something we independently verified. Read the categories and exceptions instead of interpreting “no logs” as “no information is processed.”
Understand blocking and exceptions before enabling them
A kill switch is intended to block traffic when the VPN connection fails. Its triggers and exclusions depend on the app and operating system. It can deliberately leave the computer without internet access while the tunnel is unavailable; that symptom alone is not evidence of malware.
Proton’s kill-switch documentation distinguishes Standard behavior after an accidental drop from stricter Advanced behavior on supported platforms. It also documents platform limitations, including macOS server-switch exposure and some Apple-service DNS requests bypassing the VPN. Check the guidance for your platform before assuming a change of server or network keeps every connection inside the tunnel.
Split tunneling sends selected applications or destinations outside the VPN, or includes only selected traffic, according to the chosen mode. Understand each exception. Excluding a troublesome banking app may make it work while changing the privacy arrangement you intended for that app.
Mullvad’s desktop guide, updated 18 September 2026, distinguishes its built-in connection-failure kill switch from optional Lockdown mode, which also blocks after deliberate disconnect or quit. It notes that excluded applications can still access the internet with split tunneling enabled. Treat stricter blocking as a configuration with consequences, not a required setting for every beginner.
Before making changes, save work and read how to return to the previous arrangement. On a managed device, let IT handle VPN software and routing. Avoid combining several VPN apps or blindly changing DNS, firewall rules and browser proxy settings to make a connection work.
Verify a normal connection without overclaiming the result
Follow the vendor’s current installation and connection instructions for your platform. Use a trusted official download route, complete updates and inspect the app’s connection status. Check whether the intended coverage is a device app or a browser extension before assuming the same result in another program.
If you choose to use a provider’s connection-check page, it sees the connection and public IP used to reach it. That is a disclosure to the check service. Use one you trust, without submitting private messages or files. A reported VPN address shows the route of that request; it cannot prove that every app, DNS query or later reconnection is covered.
Check ordinary behavior after startup, sleep and a network change using the app’s documented status controls. Review exclusions and platform-specific limitations. If deliberate disconnect or failure testing matters to your requirements, use the vendor’s documented procedure in a non-sensitive session. A successful browsing check is not an independent leak audit or malware test.
If a site stops working, record the app state, server choice, time and exact error before changing settings. It could be a blocked VPN address, routing issue or intentional kill-switch block. Avoid disabling antivirus, trusting a new root certificate or creating broad exclusions as an improvised fix.
Keep account and device protection in place
A site you sign into still knows which account is using it. Mozilla’s private-window explanation also distinguishes session cleanup from anonymity: private windows do not hide the IP address by themselves, and signing in identifies you to that site. Private browsing, tracking controls and VPN routing answer different questions.
Use supported updates, appropriate browser warnings, unique passwords and additional sign-in protection alongside any VPN. Our safer-browsing guide and extension guide explain those controls. Optional VPN filtering is an extra documented feature to assess, not evidence that every malicious link or download is blocked.
If credentials were exposed or software ran, follow account recovery and device investigation. Connecting a VPN afterward cannot revoke a stolen session, undo disclosure or clean the device. Proton and Mullvad appear here as examples of readable documentation and differing workflows, not a ranked shortlist. We have not tested their speed, leaks, logging practices or protection effectiveness.
For a service choice, read our 2026 VPN provider comparison. It compares six providers and recommends Proton VPN for everyday needs or Mullvad for minimal account data and straightforward monthly billing, with the reasons and evidence limits explained.
Sources & documentation
Sources checked on 7 Oct 2026. Documentation research does not establish independent testing.
- EFF Surveillance Self-Defense: Choosing a VPN and understanding trust
- Mozilla Support: HTTPS-Only Mode and encrypted website connections
- Mozilla Support: Private-window protections and anonymity limits
- Microsoft Support: VPN profiles and connections in Windows
- Apple Support: iCloud Private Relay and Safari browsing scope
- Proton VPN: Browser-extension scope, window modes and DNS caveats
- Proton VPN: Kill-switch behavior and platform limitations
- Mullvad VPN: Desktop application, kill switch and Lockdown mode
- Mullvad VPN: Stated logging policy and other handled data