Most VPNs promise no logs. We make logging actively difficult at the server layer, so there is nothing to leak, audit, or be compelled to hand over.
Two ways to "have a no-log policy":
Logging is on by default at the OS / server level. The VPN operator manually filters or deletes logs. If anything goes wrong — config drift, dev oversight, court order — the data is there.
Most "no log" VPNs.
Logging is disabled at the WireGuard config level. Servers run on RAM-disk so nothing persists. DNS goes to a public resolver, never our infrastructure. The data is never written to begin with.
ClownVPN.
If a court compels us to hand over user logs, we hand over an empty file. Not by refusing — by genuinely not having the data.
If a server is compromised, attackers find no historical traffic data. The RAM wipes on reboot. Worst case = forward-only.
"No logs" is the most overclaimed term in VPN marketing. We've made it verifiable, not just claimable.
Short list. The /no-logs/ audit page has the full granular version with retention windows and what we'd hand over if subpoenaed.
| Data type | Status |
|---|---|
| Your originating IP address | Never collected |
| The VPN IP we assigned you | Never collected |
| The websites or services you visit | Never collected |
| Your DNS queries | Never collected |
| Bandwidth used per session | Never collected |
| Session start / end timestamps | Never collected |
| Account info (email, name, payment) | No accounts exist |
Things we do have (anonymous crash reports, aggregate load stats, ad SDK identifiers) are documented in Privacy Policy sections 3 and 4.