Privacy policy
What stays on your machine, what leaves it, and to whom.
Kongtrol is a free, open-source tool made by one person (there is no company behind it) that runs on your machine. The author receives and processes none of your data: each user controls their own. There are no accounts, no servers of its own, no telemetry and no analytics. Your configuration and passwords stay on your machine. The only connections it makes on its own are checking that your VPN server answers before connecting and resolving the domains in your rules. Looking up your public IP is optional and off by default. This website uses no cookies and no analytics.
Version 1.2.0 ·
What stays on your machine
Kongtrol keeps everything locally, in your user folder. None of it is sent to anyone:
~/.kongtrol/kongtrol.yaml: your VPN profiles, groups, rules and settings. It never contains passwords.~/.kongtrol/preferences.json: this machine's preferences (language, favorites, dashboard port).~/.kongtrol/audit.log: event log (connections, security changes), HMAC-signed.- Metrics history, background-service logs and the local dashboard token (
~/.kongtrol/api-token). - Passwords and the log signing key: in the operating system's credential store (Windows Credential Manager, macOS Keychain, Secret Service/GNOME Keyring on Linux).
To erase everything: delete the ~/.kongtrol folder and Kongtrol's entries in the credential store.
Connections Kongtrol makes on its own
Besides the traffic of your own VPNs, Kongtrol makes these connections:
- Public IP check (optional, off by default) — only if you turn it on, an HTTPS request to
api.ipify.org(a third-party service) or another service you choose, to show your public IP and detect leaks. When you enable it, your IP is visible to that service, like any site you visit. It runs only when a tunnel connects or disconnects (at most once every 30 seconds) and when you ask (kongtrol check, "Check" in the dashboard or the tray); never periodically. The kill switch and DNS guard do not need it. The request leaves through the active route (your VPN, if there is one). - Pre-connect check — a short TCP connection to your VPN profile's server and port, to warn you if it doesn't answer. It only goes to the server you configured.
- DNS resolution for your rules — Kongtrol resolves your policy domains with the system's or the tunnel's DNS, to know which tunnel to send them through.
Kongtrol does not send telemetry, analytics, crash reports or update checks (checked in the source code on 2026-11-17). Your VPN clients (NordVPN, FortiClient, etc.) may make their own connections; that depends on each provider and its policy.
Local web dashboard
The dashboard runs on your machine (127.0.0.1) and requires a local token on every request. That token travels in a single local cookie (kongtrol_control, HttpOnly) that never leaves your machine. It keeps only your language, theme and sidebar state in the browser's local storage.
The dashboard serves its fonts and logos from the binary itself: opening it makes no request to Google or any other third party.
This website (kongtrol.app)
This site uses no cookies, analytics or tracking pixels, and serves its own fonts (nothing is loaded from Google). It only stores in your browser the language or theme you explicitly pick (kglang, kgtheme).
The site is hosted on Cloudflare (Workers): Cloudflare processes the technical data of each visit (such as IP address and browser) to serve and protect the site, under its privacy policy.
Downloads and source code live on GitHub; using them is covered by the GitHub General Privacy Statement.
How to control it
What you can adjust:
- The public IP check is off by default. Turn it on or off in the dashboard (Security), in the setup wizard or with
kongtrol config public-ip on|off(security.public_ip_check.enabled). Pick another service withsecurity.public_ip_check.endpoints(https only). - The pre-connect check only runs for profiles that have a host set.
Changes to this policy
This policy changes when what the code does changes. Each version carries its number and date at the top, and its history stays in the GitHub repository.