What a no-logs claim covers
When choosing a privacy-focused VPN, look for a service that clearly explains its no-logs policy: what data it does and doesn’t store, for how long, and whether any of it can be tied to your account. Saying it doesn’t record browsing content isn’t enough. If it keeps your source IP, connection times, and exit IP, other records could still be used to link a connection to you—even without browsing history.
First, distinguish what a service can see while you’re connected from what it can retrieve later. An access server needs to know where a connection comes from to send data back; that doesn’t mean the provider writes your source IP to a log. When reading a policy, separate “not collected,” “not retained,” and “retained in aggregate.” If it mentions only “anonymous analytics,” check whether each device gets a persistent identifier and whether the data can be combined with account details.
| Data category | Fields to check | Questions to ask |
|---|---|---|
| Browsing activity | Destinations visited, DNS queries, traffic content | Does the policy rule out only content logging, or does it explicitly exclude destination and DNS query records too? |
| Connection records | Source IP, connection start and end times, exit IP | Are these fields written to disk? If retained, can they be retrieved by account or session? |
| Client diagnostics | Crash reports, device identifiers, connection failure details | What gets sent by default, and can you turn it off? How long are diagnostics you submit kept? |
| Account and billing | Account identifiers, order numbers, payment status | Who stores this data? Can an order be linked to connection records or support tickets? |
Don’t treat usage counters as browsing history. Total data use tracked by account may be needed to enforce a plan limit. What matters is whether those counters also include destinations, precise timestamps, or individual connection details. Likewise, a sound no-logs policy doesn’t make billing records or support tickets disappear. Check separately what each type of data is used for and when it’s deleted.
How to review a privacy policy and audit report
- Start with the official policy. Note its effective date and which products it covers. Use the page search to look for “connection,” “diagnostics,” “retention,” “third parties,” and “deletion.” Pay close attention to exceptions such as “logged only for troubleshooting”: who can enable logging, is it off by default, and when is the data deleted?
- Check what the report covers and when. Identify the auditor, the audit date or period, the systems reviewed, and the actual findings. A client vulnerability review can’t tell you whether servers retain connection logs. And an audit of the access service alone doesn’t establish that related data isn’t kept by DNS resolvers, monitoring platforms, or support systems.
- Match the findings to the current setup. Check whether the report describes its sample, findings, and remediation. If the operator, client, or access architecture has changed since the audit, ask which parts of the findings still apply. If all you can find is a badge or press release, mark anything you can’t verify as “unverified.”
- Ask specific questions about important gaps. For example: “Do the access layer, monitoring dashboard, or troubleshooting tools store source IPs and connection times? Can those fields be linked to an account using a session identifier? If retained, when are they deleted?” Compare the answers with the policy; don’t let a one-line support assurance override exceptions in the written terms.
You can also check who operates the service and how it responds to lawful data requests. Jurisdiction and transparency reports offer useful context, but they don’t replace a retention policy. What a provider can hand over depends first on what it actually stores and which systems can combine the records.
Minimize the information you share when signing up and paying
Before signing up, separate required details from optional ones and anything requested during payment. VPNLabel lets you create an account without an email address. When comparing other services, check whether they require an email you use regularly and what recovery options are available if you lose your credentials. If recovery depends on credentials stored on your device, keep them in a trusted password manager—not on a shared device or in chat history.
Before paying, consider what the provider and payment processor can each see. Even if you enter payment details on the processor’s page, the provider usually still needs an order reference and payment status to activate service or handle a refund. Keep receipts if you need them for reimbursement or refunds. When contacting support, share only the order details needed to resolve the issue—not a full billing statement or your account credentials.
Checking your connection on public Wi-Fi
Choose a network whose name you can verify with venue staff, and turn off automatic connections to unfamiliar hotspots. If the hotspot requires a sign-in page, complete the necessary access steps before enabling the VPN. If you see a certificate warning, stop; don’t ignore it or install a certificate from an unknown source just to get online. A VPN protects traffic routed through its tunnel, but it can’t tell a fake sign-in page from a real one.
- ✅ Use the same browser to check your public IP before and after connecting; you can use IP lookup. A changed IP only shows that this web request took a different route. It doesn’t prove that other apps use the same route.
- ✅ Check which resolver actually handles your DNS queries, then compare it with the client settings. Your browser’s Secure DNS may use a separate resolver; seeing a third-party name doesn’t by itself mean your queries bypassed the tunnel. To check for a leak, confirm whether queries took a network path you didn’t expect.
- ✅ Check split tunneling and what happens when the connection drops. If you route traffic by app, test the browser and each app you plan to use; don’t assume the rules cover every process. If the client has a kill switch, enable it and use a page with no sensitive information to check whether internet access resumes directly during a network transition.
- ❌ Don’t treat an IP check as proof of a no-logs policy. A website can tell you which IP it sees, but it can’t inspect the provider’s storage systems. Likewise, an audit report can’t replace checking split tunneling and disconnection behavior on your current device.
Websites you’re signed in to can still identify you through your account, cookies, and other signals, and the site can still keep its own activity records. On public networks, keep HTTPS enabled and pay attention to domain names and sign-in prompts; checking the tunnel is only part of the picture. If you need to handle sensitive tasks and can’t verify the network or device, switch to a trusted network first.