What a No-Log VPN Policy Should Say in Plain English
Every VPN says some version of the same thing: we protect your privacy. A lot of them also say "no logs." That sounds simple, but it is one of those phrases that gets less clear the closer you look at it.
A no-log VPN policy should mean the company is not saving records that connect you to what you did online. Not your browsing history. Not the sites your apps contacted. Not DNS requests. Not a neat little timeline that says your home IP connected to a VPN server at 8:03, visited a certain domain, then disconnected at 8:41.
The tricky part is that VPNs still need some data to run. They need to know that your account exists. They may need payment records. They may measure server load so they know when a location is full. That is not automatically bad. The question is whether any of that data can be tied back to your actual activity.
Activity logs are the big red flag
Activity logs are the obvious stuff: websites visited, DNS queries, files downloaded, app traffic, or anything that describes what you did through the VPN. A privacy-focused VPN should not keep this. If the policy says it does, or dances around it with vague words like "usage information," slow down.
Connection logs are the sneakier category. These can include your real IP address, the VPN IP you used, timestamps, session length, or bandwidth used. Some connection data is harmless when it is aggregated. For example, "this server is busy" is not about you. But "this user connected from this home IP at this exact time" can identify you later if it is retained.
No logs does not mean no account data
This is where people get tripped up. A VPN can avoid activity logs and still keep normal account data. Email address, billing status, support tickets, and fraud prevention records may exist. If you pay by card, the payment processor will also have a record.
That does not mean the VPN is secretly logging your browsing. It means "no logs" is not the same as "no data anywhere." A good policy separates those buckets clearly: what is needed to run the account, what is collected in aggregate, and what is never stored.
Independent audits and transparency reports can help, but they are not magic either. An audit is useful when it looks at real server configuration and operating procedures, not just a nicely written policy page. A transparency report is useful when it explains what happens when legal requests arrive, especially if the provider has no activity data to hand over.
What you actually want to see
A good no-log VPN policy is boring and specific. It should say plainly that the provider does not store browsing history, DNS queries, source IP addresses tied to sessions, assigned VPN IP addresses tied to users, or connection timestamps that can identify a person.
It should also say what it does keep. If the answer is account email, payment status, support messages, and anonymous server health stats, fine. If the answer is hidden behind legal fog, that is the part to question.
This matters because a VPN changes who you trust. Without a VPN, your ISP sees a lot of your connection metadata. With a VPN, the VPN provider becomes the first hop instead. That provider should not be building a better file on you than the ISP would have.
At 99¢ VPN, the goal is intentionally plain: a simple WireGuard VPN that keeps the product small and the promise understandable. If you want a cheap VPN without a giant bundle attached, you can get 99¢ VPN for $11.88/year here.
The bottom line: do not buy the phrase "no logs" by itself. Read the nouns around it. Activity logs, DNS logs, IP addresses, timestamps, retention, sharing. Those words tell you whether the promise means anything.
Written by the person who runs 99¢ VPN. Not legal advice. Just the plain-English checklist I wish every VPN homepage used.