No browsing activity logs

VPN traffic data we do not intentionally record

The VPN node configuration maintained in this repository does not enable packet capture or destination logging for user traffic. Standard infrastructure and API access logs are separate and may temporarily contain source IP addresses and request metadata for security and operations.

• Browsing history
• Visited URLs or page content
• DNS query names
• Destination IP addresses of VPN traffic

Data processed to operate the service

Providing and securing HarmanVPN requires limited account, device, security, quota, billing, and operational records. These are separate from a history of sites visited through the VPN.

• Account details, password hash, email verification, and acceptance timestamps
• Login/security events, source IP, device details, app version, and last-seen information
• WireGuard public key, assigned tunnel address, selected node, and connection state
• Connection, disconnection, and last-seen timestamps plus per-report, monthly, and lifetime receive/transmit byte totals
• Subscription and billing entitlement status
• FCM registration tokens and delivery status when notifications are enabled
• Advertising consent state and provider diagnostics when Free ads are enabled and consent permits requests

Why the distinction matters

“No browsing activity logs” describes the VPN destinations and browsing data HarmanVPN does not intentionally retain. It is not a claim that the service processes no technical data.

The Privacy Policy describes categories, purposes, providers, retention, account deletion, and legal rights in more detail.