This article explains what "no traffic logs" means, what the Transparency Dashboard shows, how the Logs tab differs from browsing history, and what diagnostic information may be used for support.

KlarVPN does not keep traffic logs that reveal what you do online. Traffic logs are records that could show browsing behavior, websites visited, destination servers, or the content passing through the VPN tunnel.

KlarVPN does not store:

The onboarding describes this as "No Traffic Logs. Period." The goal is that your online activity is not saved as an account record that can be reviewed later.

No Traffic Logs screen in the app.

When KlarVPN is connected, your device sends internet traffic through your encrypted KlarVPN tunnel. Websites and apps see the VPN exit connection instead of your normal network connection.

KlarVPN still needs to operate the tunnel in real time. Like any VPN service, traffic must pass through the VPN infrastructure while the connection is active. The privacy difference is that KlarVPN does not keep traffic records after forwarding that traffic.

In practical terms, KlarVPN should not have a saved list of:

This is why the app separates traffic logs from session or diagnostic information. A session count or tunnel status does not tell anyone what you browsed.

KlarVPN creates a private tunnel for the user instead of placing everyone into one shared identity. During setup, the app explains that your device key stays on your device.

This matters because your device key helps identify and secure the tunnel configuration on that device. Support should never ask for your password, private key, payment details, or one-time login codes.

If you contact support, share the issue, time of failure, selected location, device type, and screenshots of safe status pages. Do not share secrets.

The Transparency Dashboard gives users a direct view of what KlarVPN has at the account/session level. It is meant to show the difference between basic session records and traffic logs.

The dashboard may show items such as:

The dashboard should not show websites visited, search activity, DNS requests, destination IPs, packet content, messages, or browsing history.

Transparency Dashboard showing 0 traffic logs kept.

The Transparency Dashboard is not a browsing history page. It is a privacy check page.

A user can open it to confirm that KlarVPN is not keeping activity records for their sessions. The dashboard may show recent session entries so the user can understand app usage, but it does not expose what happened inside those sessions.

For example, a recent session row can show that a tunnel session happened. It should not show what websites were opened, what DNS queries were made, or what packets were sent.

KlarVPN does not keep saved records of the websites you visit while connected.

Traffic does pass through the VPN exit while the tunnel is active. The important point is what happens after forwarding: KlarVPN is built to discard activity information instead of storing it as logs.

That means there should be no retained browsing history, DNS request list, destination list, or packet content available later from the user account.

Help article explaining that KlarVPN does not log DNS queries, destination IPs, or traffic volume.

The Logs tab shows technical tunnel messages. These logs can help support understand whether the VPN tunnel started correctly, whether a configuration loaded, or whether a connection process failed.

Technical logs may include items such as:

The Logs tab should not contain browsing history, website URLs, DNS request history, messages, files, or page content. It is a troubleshooting tool, not an activity record.

Logs tab showing technical tunnel messages, not browsing history.

Only share technical logs when support asks for them. Logs can help support diagnose connection failures, tunnel setup problems, or server-side issues.

Before sending logs or screenshots, check that they do not include anything you do not want to share publicly. Do not send:

If support needs context, include the time of the issue, device model, version, selected VPN location, and a short description of what happened.

Diagnostic information helps KlarVPN identify app or tunnel problems without storing browsing activity. The app help page explains that KlarVPN may use limited technical information such as app version, operating system, current tunnel status, and the tunnel configuration identifier assigned to the user.

This information helps answer questions like:

Diagnostic information is not the same as traffic logging. It should not describe which websites the user visited or what content they accessed.

Diagnostic information page explaining what KlarVPN collects and what it never collects as activity data.

A DNS leak happens when a device sends DNS requests outside the VPN tunnel. This can reveal website lookups to the normal network or ISP. A WebRTC leak can happen when a browser exposes the real IP address through peer-to-peer browser features.

KlarVPN routes DNS through the VPN tunnel and uses KlarVPN resolvers so the normal ISP should not see DNS lookups while the VPN is connected. The tunnel configuration is also designed to prevent IPv6 and split-tunnel leaks by default.

To test this, connect KlarVPN and open the DNS and WebRTC leak test from the Help area or visit the leak-test page in the browser. The visible IP and DNS servers should belong to KlarVPN infrastructure, not the normal ISP connection.

DNS & WebRTC leak test help page.

No. KlarVPN does not store browsing history, DNS queries, destination IPs, or packet content as traffic logs.

Session information helps the app show basic account and connection status. It is not the same as activity logging. It does not show what was visited inside the VPN tunnel.

No. Technical logs are troubleshooting messages about the tunnel and app behavior. Traffic logs would describe browsing activity. KlarVPN is designed not to keep traffic logs.

No. Support should never ask for your password, private key, reset link, or one-time code.

Send the issue description, device model, app version if available, selected VPN location, time of the issue, and relevant screenshots such as the Transparency Dashboard or DNS leak test. Do not send passwords or payment details.