Privacy

What Routekeeper knows and where it doesn’t go

Routekeeper doesn’t collect data about you or your traffic and doesn’t send it anywhere. Everything it knows about your connections stays on your Mac.

In effect from the first public version of Routekeeper. Revised October 5, 2026.

What Routekeeper sees

To decide where a connection goes, the Routekeeper system extension sees, for every outgoing connection:

Routekeeper doesn’t read what’s inside connections. Traffic sent through a proxy is passed on as is, without decrypting it.

Where it’s kept

WhatWhereFor how long
Connection log for the monitorIn the system extension’s memory, the last few thousand entriesUntil the extension restarts. Never written to disk.
Rules, proxy list, settings, proxy passwordsThe system extension’s configuration file, readable only by rootUntil you delete them. Kept when the app is removed, so your rules come back if you reinstall.
Service logsThe macOS system log (unified logging)As long as macOS keeps them, usually a few days.
Service catalogThe app’s folder in ~/Library/Application SupportUntil you delete it. Updated every 6 hours.
License: a name, an email if given, the Mac’s code and the termThe macOS keychain; the time of the last check is in the app’s folder in ~/Library/Application SupportUntil you delete it. Checked on the Mac, with no network requests.
Unpacked country and network database for the traffic map~/Library/Caches, about 55 MBUntil you delete it. If you do, the app unpacks it again.

The Routekeeper window receives settings without proxy passwords.

Service logs contain technical events: startup, errors, decisions about connections. They may include addresses that apps connected to. Logs don’t leave your Mac unless you attach them to a bug report yourself. “Collect diagnostics” in Settings puts an archive on your desktop and sends it nowhere. It contains a summary, the settings without passwords (but with the proxy address and login), the last 500 connections and 30 minutes of logs. How to remove everything that stays behind.

The traffic map looks up countries and networks in a database built into the app (DB-IP Lite), without any requests to the internet.

What Routekeeper connects to on its own

Nothing else. No analytics, telemetry, crash reports or advertising identifiers.

The website

Pages on getroutekeeper.app count visits with Cloudflare Web Analytics: no cookies and no visitor identifiers. The script loads from static.cloudflareinsights.com, so Cloudflare sees your device’s address and the page you opened. The app has no such counter.

Your proxies

Traffic you send through a proxy is visible to whoever runs the proxy server. Routekeeper can’t vouch for it: use proxies you trust.

If you contact us

Bug reports in GitHub Issues are public. Before attaching a log or a diagnostics archive, look through it and remove anything you don’t want to share.

Changes

If this policy changes, the new revision will appear on this page, and the history of changes in the repository history.