VPN logging explained
“No logs” is meaningless until you know which events are stored, aggregated, or never written.
Categories of data
- Account & billing — almost every paid VPN keeps some
- Operational metrics — bandwidth totals, error counts, server health
- Connection metadata — timestamps, VPN IPs, device counts
- Destination history — domains, IPs, URLs you visited (the sensitive stuff)
Privacy-respecting designs avoid destination history and minimize connection metadata.
DNS is a logging surface
Even without “browsing history” tables, resolver logs can reconstruct a hostname timeline. Ask whether DNS is logged and who operates upstream resolvers.
Memory vs disk
Some providers process packets without writing destinations to durable storage. That is better—but still requires you to trust their code and operators. Memory can be forensically interesting after compromise; policies are not magic.
VeritasVPN stance
We aim for operational counts without query names in Prometheus, tunnel-IP keyed UI counters that clear with peers, and clear privacy policy language. Upstream DoH resolvers still see forwarded hostnames for non-blocked lookups. Read the privacy policy rather than a slogan.