Best VPNs for Privacy: How to Verify No-Logs Claims and Share Less Personal Information

A practical guide for privacy-conscious users: how to verify no-logs claims, minimize the information shared for signup and payment, and check settings for public Wi-Fi.

How to Choose a VPN for Privacy

Looking for a privacy-focused VPN? First, check whether its no-logs claims can be verified. Then see whether you can share less personal information at signup, and test on your own devices what happens to traffic if the connection drops. Fewer signup fields don’t mean fewer connection logs, and a client showing “connected” doesn’t mean every app is using the tunnel. Check each separately.

A VPN routes traffic between your device and a VPN server through an encrypted tunnel. Your local network can usually still see that you’re communicating with a VPN endpoint, as well as the timing and volume of that traffic. The VPN provider sits on the new network path and may be able to see information such as your source address and destination addresses. HTTPS still protects the content exchanged between your browser and websites. Websites can also identify you through your login session or cookies. Choosing a service changes who can see which information; it doesn’t make all that information disappear.

Bottom line: Choose a service that explains what data it collects, why it collects it, and how long it keeps it—and lets you verify settings on the devices you use. Mark anything you can’t confirm as “unverified”; a policy’s silence about a data type isn’t proof that it isn’t collected.

How to Verify No-Logs Claims

Start with the current privacy policy and confirm it applies to the product you plan to use. Note its version or effective date. Don’t search only for “logs”; also look for terms like “diagnostics,” “analytics,” “retention,” and “third parties.” A service might not store browsing history but could temporarily retain connection times for troubleshooting or keep account usage data for billing. The key questions are whether the data can be linked to you, how long it’s kept, and who can access it.

Data categoryWhat to checkCommonly misunderstood claim
Browsing and DNSDoes the service store destination addresses or DNS queries? Who handles DNS resolution?“We don’t log browsing activity” doesn’t necessarily mean destination addresses aren’t logged.
Connection metadataAre source IP addresses, connection times, or exit routes retained? Can they be linked to an account?“No activity logs” may not cover connection metadata.
Usage and billingIs only the account’s total usage retained, or is each session recorded? What order details must be kept after a refund?“Delete account” doesn’t necessarily mean transaction records are deleted too.
Client diagnosticsAre crash reports uploaded by default? Do they include device identifiers? Can uploads be turned off?Server-side promises may not cover telemetry from the client app.

If a service cites a third-party audit, check the report date, scope, methodology, and exceptions before looking at its conclusions. Reviewing client code and checking log settings on production servers are different exercises. A report on a test environment or spot checks of selected routes don’t automatically cover every production route. If you see only a badge on a marketing page, ask what the report covers and whether a summary is public. Even an audit with a relevant scope supports conclusions only for the period it examined.

If the policy is vague, ask support a specific question, such as: “After a connection ends, do you retain source IP addresses and connection times? If so, for how long, and can they be traced back to an account?” If the only answer is “We take privacy seriously,” the point is still unverified. Keep the response and the policy version so you can compare them with future changes.

How to Minimize Signup and Payment Information

Consider signup, payment, and support separately. At signup, provide only required information with a clear purpose. Don’t include unrelated details such as your real name or employer in a username or note. If the service lets you proceed without an email address, first check how you can recover access if you forget your credentials; sharing less recovery information can also make account recovery harder. If an email address is required, consider using a separate address you can keep long-term for billing and recovery messages, and set a unique password for the account.

Before paying, check what the checkout page and payment provider each require. The merchant may receive only an order number and transaction status, while the payment provider handles billing details under its own rules. Check how refunds are processed and what proof is required before choosing a payment method. Fewer fields at checkout don’t mean the merchant or payment provider keeps no transaction records. Provide accurate billing details when required.

When contacting support, start with the error message, client version, and steps to reproduce the issue. Before sharing a screenshot, crop out account identifiers, order details, and unrelated windows. If the client imports a configuration through a subscription link, treat the full link like a credential: it may contain a token that grants access to the configuration. If it’s posted publicly, revoke or replace the link using the options the service actually provides; deleting the screenshot alone isn’t enough.

  • ✅ Store account credentials and essential recovery information in a password manager.
  • ✅ Before paying, check required information, proof requirements, and the refund process.
  • ❌ Don’t post screenshots or diagnostic bundles containing a full subscription link in public forums.

Public Wi-Fi Connection and Disconnect Checks

  1. Check the network name first. Confirm the hotspot name with the venue, and turn off automatic joining and local sharing if you don’t need them. If the network requires portal authentication, do only what’s needed to get online; don’t enter VPN or other website credentials on the portal page.
  2. Check what’s protected. On a device you use regularly, check whether the client or operating system has a kill switch—a feature that blocks unprotected traffic if the tunnel drops. Review split-tunneling exceptions. A proxy provided by a browser extension usually covers only that browser; it doesn’t tell you whether email or sync apps also use the tunnel.
  3. Test switching networks and reconnecting. Close sensitive apps, such as banking apps and work documents, before testing with a page that contains no sensitive information. During a network change or wake from sleep, check whether the page can send new requests before the tunnel is restored. A cached page loading doesn’t prove you’re still online. And manually disconnecting isn’t a reliable test of what happens during an unexpected drop.
  4. Compare IP and DNS results. On the same device, browser, and network, compare your public IP address and the DNS resolvers shown by a test before and after connecting. If you expect all traffic to use the VPN but still see your network’s original resolver, check split tunneling, system DNS, and your browser’s encrypted DNS settings. Also check whether IPv6 follows the expected route.

Seeing a DNS resolver name that differs from the VPN brand isn’t enough to conclude there’s a leak: the service may use a public resolver, and your browser may have its own encrypted DNS settings. A test reflects only the route used by the app running it at that moment. It can’t confirm what every app does, and it can’t verify whether the service keeps logs.

Keep an eye out for HTTPS certificate warnings even after connecting. If a hotspot asks you to install an unfamiliar certificate or configuration, stop and switch to a trusted network. For tasks where privacy matters, if you can’t confirm that the kill switch works and how your apps route traffic, wait until you’re back on a trusted network rather than relying on the connection icon in the client.

Start Free