Privacy ·9 min read

No-Log VPN Claims: How to Verify a VPN's Privacy Promise

Every VPN advertises "strict no-logs policy" on their homepage. But there is no regulator enforcing that promise. Some VPNs have been caught logging despite their claims. Here is how to separate genuine privacy from marketing.

The 4 Types of Logs VPNs Might Keep

When a VPN claims "no logs," the first question you must ask is: no logs of what? Not all logging is equal. A VPN that records connection timestamps but not browsing history might technically claim "no logs of your activity" while retaining data that could identify you. Here are the four categories:

Log Type What It Records Privacy Risk Acceptable?
Traffic LogsBrowsing history, DNS queries, downloaded files, messages, email contentExtreme — exposes your entire online activityNever
Connection LogsConnection timestamps, IP addresses assigned, duration of sessions, bandwidth usedHigh — can correlate activity to specific users and timesNo
DNS LogsEvery domain name queried through the VPN's DNS serversHigh — reveals which sites you visit, even the content is encryptedNo
Metadata LogsDevice type, OS version, app version, aggregate bandwidth (no timestamps or IPs)Low — cannot identify individual users or activitySometimes

What "No-Log" Actually Means (and What It Doesn't)

There is no legal or industry-standard definition of "no-log." Each VPN defines it differently in their privacy policy. Some VPNs collect connection timestamps but delete them after 24 hours. Others keep bandwidth totals for capacity planning but strip all identifying information. A few keep nothing at all — no traffic logs, no connection logs, no DNS logs, no metadata beyond what is necessary for the app to function.

The safest definition to insist on: the VPN must retain zero information that could be used to tie any online activity to any specific user. If a VPN's privacy policy contains language like "we may collect aggregate data for service improvement," look for specifics. Aggregate data with no timestamps, no IPs, and no user identifiers is acceptable. Anything tied to a session or user ID is not.

Pay attention to the VPN's jurisdiction. Companies incorporated in Five Eyes, Nine Eyes, or Fourteen Eyes countries (US, UK, Canada, Australia, New Zealand, and their intelligence-sharing partners) can be compelled by law to begin logging. VPNs based in privacy-friendly jurisdictions like Panama, Switzerland, or the British Virgin Islands face fewer mandatory data retention laws. However, jurisdiction alone is not sufficient — a VPN in Panama that logs everything is worse than a VPN in Germany that logs nothing and can prove it.

5 Ways to Verify No-Log Claims

1. Independent Security Audits

The gold standard of verification. A reputable third-party cybersecurity firm — such as Cure53, VerSprite, or a Big Four accounting firm (PwC, Deloitte, EY, KPMG) — is given full access to the VPN's server infrastructure and codebase. They verify that no logging code exists, that server configurations are ephemeral (RAM-only, no hard drives), and that no data is written to disk.

Look for audits that are: (a) published in full, not summarized; (b) repeated annually, not one-time marketing stunts; (c) conducted by named, reputable firms. A VPN that says "independently audited" but won't tell you by whom is hiding something. Read the actual audit reports — they are typically published as PDFs on the VPN's website.

2. Warrant Canaries

A warrant canary is a public statement that the VPN has not received a secret government subpoena, national security letter, or gag order. The concept: if the government orders the VPN to hand over data and compels silence, the VPN takes down the canary. If the canary disappears, users know something changed without the VPN violating the gag order.

Warrant canaries typically include: the date of the last update, a statement on the number of national security letters received (usually zero), and a separate line for each type of secret demand. Check that the canary is updated regularly (monthly or quarterly). A canary last updated two years ago is meaningless.

3. Transparency Reports

Transparency reports disclose how many legal requests the VPN received from governments and law enforcement, and critically, what data the VPN was able to provide. A genuine no-log VPN should report: "Received 47 data requests. Provided zero user data because no logs exist." If the report says "complied with 15 requests," the VPN is logging.

Look for reports that break down requests by country and specify the type of data requested vs. provided. The most credible transparency reports include canary statements and are cryptographically signed.

4. Real-World Court Case Evidence

The ultimate test of a no-log policy is what happens when law enforcement comes with a warrant. Several VPN providers have been tested in this way:

  • Perfect Privacy had servers seized by Dutch police in 2016. After forensic examination, authorities found no user data because the servers ran entirely in RAM.
  • ExpressVPN had a server seized in Turkey in 2017 during the investigation of the Russian ambassador's assassination. Turkish authorities found nothing because the server was RAM-only with no logs.
  • Conversely, a VPN provider called PureVPN provided logs to the FBI in 2017 that helped convict a cyberstalker — despite advertising a "no-log policy." Their privacy policy had carved out exceptions for law enforcement requests.

These real-world tests are worth far more than any marketing claim. Search for "[VPN name] court case logs" before subscribing. The results will tell you whether their no-log policy holds up under legal pressure.

5. Open-Source Apps and Infrastructure

A VPN that open-sources its client applications allows independent researchers to verify that no logging code exists in the software. Server-side open source (the VPN server software itself) is even better — it lets anyone audit the infrastructure that handles user traffic. Check GitHub for the VPN's repositories. Look for active maintenance, clear build instructions, and reproducible builds that generate the same binary as the one published on app stores.

Shield VPN builds on open-source WireGuard and publishes its client code for public audit. Open-source infrastructure allows anyone to verify that our no-log architecture is real — not just a promise in a privacy policy. For more on VPN protocols, see our encryption guide covering WireGuard and AES-256.

Red Flags: Signs a VPN Is Lying About Logs

  • The privacy policy is vague — Phrases like "we don't sell your data" instead of "we do not record any data." The second statement is absolute; the first leaves room for collection and internal use.
  • Free VPNs with no visible business model — As we covered in our free VPN safety guide, if you are not paying for the product, your data is the product. Free VPNs have repeatedly been caught selling user browsing data to advertisers.
  • No published audit, or an audit from an unknown firm — A credible audit names the firm, publishes the full report, and repeats the process. A one-time audit from five years ago by an unnamed "independent security firm" is worthless.
  • Jurisdiction in a Five Eyes country, combined with no transparency reports — Being based in the US or UK is not disqualifying by itself, but it demands a much higher standard of proof: regular audits, detailed transparency reports, and ideally, RAM-only server infrastructure that physically cannot retain data.
  • Collecting more data than needed for signup — A VPN should require an email address (for account recovery) and payment information. If they ask for your name, phone number, physical address, or social media accounts, they are collecting data beyond operational necessity.

How Shield VPN's No-Log Policy Is Verified

Shield VPN runs on a simple principle: if we do not collect it, we cannot hand it over — to anyone, under any circumstances, in any jurisdiction. Our VPN servers operate entirely in RAM with no persistent storage. Every server reboot wipes all state. No traffic logs, no connection logs, no DNS logs, no metadata that can be tied to any user.

Our infrastructure uses private DNS on every server node, eliminating the possibility of DNS log leakage. The WireGuard protocol we use is open-source and auditable. Our client applications are designed to minimize data collection: we require an email for account recovery and nothing else. No name, no phone number, no device fingerprinting. For a detailed look at how our infrastructure protects against leaks, read our DNS leak detection and prevention guide.

A VPN that proves it keeps no logs

Shield VPN: RAM-only servers, open-source WireGuard, no traffic logs. Verified infrastructure, not just promises.

Download on Google Play