Early Access - WireGuard configs - No traffic or DNS query logs stored on VPN servers

No-Log Policy

NoLogVPN No-Log Policy

This page explains the specific meaning of NoLogVPN's no-log claim. The promise applies to VPN usage activity, not to the minimal account, billing, device, and bandwidth-accounting records needed to operate the service.

Effective: 21/08/2026Updated: 21/08/2026Version: 2026-08-21-r6

Short Version

We do not collect, store, or monitor VPN activity logs. This means we do not store browsing history, DNS queries, destination IP addresses, traffic contents, VPN session activity, or records linking a user account to websites or services accessed through the VPN. We may process limited account and billing data, such as email address, subscription status, payment processor reference, support messages, and security events necessary to operate the service. This data is not VPN activity data.

We Do Not Store

• We do not collect, store, or monitor VPN activity logs.

• We do not store browsing history, DNS queries, destination IP addresses, or traffic contents.

• We do not store VPN session activity or records linking a user account to websites or services accessed through the VPN.

• We do not keep a persistent per-user history database of destinations, packets, or activity through the VPN.

• We do not copy WireGuard keys, endpoints, live handshakes, or transfer counters into the account history retained after closure.

We Do Store

• While the account is active: email, password hash, creation time, and status. The password hash is deleted with the account.

• Short-lived password reset token hashes retained only until they are used or expire.

• Subscription status, renewal timing, and payment/provider references.

• For active devices: device name, WireGuard public key, assigned internal VPN IP, and selected protection profile. Revoked-device records and their linked device-scoped events are erased within 7 days.

• For Basic and Pro: minimal current-cycle and current-day bandwidth totals used for fair-use enforcement, network protection, and throttling.

• For Flex, where offered: the aggregate total of received and sent bytes for the invoice cycle, required Stripe references, and reported billing quantities. These billing records are retained for no more than 5 years after the cycle ends, except where a legal obligation, dispute, or applicable Legal Hold requires longer, and contain no destinations, DNS queries, content, protocols, or session history.

• Essential account/billing events for consent, checkout, and major subscription changes. Non-essential operational events are auto-purged after a short retention window.

• Checkout consent record with typed name, timestamp, agreement version, and related billing references.

• After account closure: a minimal account and contract timeline with the normalized email, account reference, checkout signature where supplied, consent, plan, and important account or subscription actions. It contains no VPN activity.

Live Session Enforcement

Simultaneous connection limits are enforced from recent live WireGuard handshake state rather than from a stored long-term activity log. In practice, the service can see live runtime session state needed to keep the VPN working, but that data is not kept as a persistent browsing or DNS history database.

Scope of the Promise

The no-log promise applies to NoLogVPN's own VPN servers and application stack. Third-party services such as Stripe, Cloudflare, the IP lookup provider used by the public status card, and upstream DNS resolvers operate under their own policies and may keep their own records outside NoLogVPN's servers. The public IP lookup does not include browsing history, DNS queries, or traffic contents.

What This Policy Does Not Mean

This policy does not mean that NoLogVPN keeps no records of any kind. It means that NoLogVPN does not keep VPN usage activity logs on its own servers. Minimal operational data is used to supply the service, handle support, enforce fair use, and manage billing, then deleted under the applicable periods. One minimal account and contract timeline may remain after account closure for legal obligations and the defense of claims; it expressly excludes browsing, DNS, destinations, traffic contents, WireGuard keys, endpoints, and handshakes. If a Flex subscription generated usage-based billing, the separate billing ledger may retain only the aggregate quantity described above until its retention period expires.

All Policies SupportSupport us