A No-Log VPN Policy Is Only as Good as the Details
"No logs" sounds simple. A VPN says it does not keep records of what you do online. You feel safer. Done.
The catch is that the phrase is doing a lot of work. Some VPNs use it to mean they do not save your browsing history. Others mean they do not save DNS requests. Others still keep connection records, device IDs, bandwidth totals, or timestamps and call that normal service data.
That is why a no-log VPN policy matters, but the exact wording matters more. The privacy promise is only useful if you know what is not being stored.
Activity logs vs connection logs
Start with the split most people miss.
Activity logs are the scary stuff: websites visited, apps used, DNS queries, searches, and traffic contents. A privacy-focused VPN should not keep those. If a VPN is recording your browsing history, it is not doing the main job people expect from a VPN.
Connection logs are quieter, but still important. These can include your real IP address, the VPN server you connected to, the time you connected, the time you disconnected, and how much data moved through the session.
One connection record might look harmless. But pair a real IP address with a timestamp and a VPN exit IP, and you have a trail. That is why privacy people care so much about whether timestamps and IP addresses are stored together.
Some data still has to exist
A no-log policy does not mean the company knows nothing about you. If you pay for a VPN, the provider may still have an email address, payment status, support messages, abuse-prevention records, and basic account settings.
That is not automatically bad. A VPN needs some operational data to run the service. The honest question is whether that data can be tied back to what you did online.
A plain-English policy should say what is collected, why it is collected, how long it is kept, and whether it can identify a specific browsing session. If it only says "we value your privacy" and moves on, that is not a policy. That is wallpaper.
How to tell if the promise is real
You cannot personally inspect a VPN company's servers. So you are looking for signs that the claim has been tested.
- Specific language. The policy should clearly say it does not store browsing activity, DNS requests, source IP addresses, or identifying connection timestamps.
- Short retention. If operational records exist, the policy should explain how long they are kept and why.
- Independent audits. A third-party audit is not magic, but it is better than a slogan. It means someone outside the company reviewed the claim.
- Simple business model. If the product is free, ad-funded, or owned by a data-heavy company, read more carefully.
The best no-log VPN policy is boring. It does not need dramatic privacy language. It just tells you, in plain English, what the service does not save.
That is also the rule we try to follow at 99¢ VPN. Keep the product simple. Keep the data footprint small. Do not turn a basic privacy tool into a giant account system.
If you want a simple WireGuard VPN without the usual pricing circus, you can start here: 99¢ VPN basic plan. One device, one low yearly price, no bundle maze.
Written by the person who runs 99¢ VPN. Not legal advice. Just the plain-English version of what to look for before trusting a VPN privacy claim.