CertMon
PRIVACY
Zero telemetry. No accounts.
Your code is your business.
CertMon is built for developers who care about security and privacy. We do not collect analytics, we do not log your traffic, and we do not track how you use the app.
The only network requests CertMon makes
- License activation and validation: When you purchase and activate a license key, CertMon communicates directly with our payment processor, Polar (
api.polar.sh), to verify that the key is valid and track activations against your 3-Mac limit. No site names, project paths, or code metadata are sent. - Purchases: Polar is the merchant of record; we see your email and license key, never card details. After you buy, Polar shows you a discount code for our other apps. We send no other email.
- Software update checks: CertMon uses the industry-standard Sparkle framework to check for updates by fetching our appcast file from GitHub (
github.com/suresk/certmon). Sparkle sends standard macOS system version headers and your current app version.
What stays 100% on your machine
- Certificates & Private Keys: Your Root CA private key is generated locally and stored exclusively in your macOS Login Keychain. CertMon never exports or transmits private keys.
- HTTP Traffic & Request Logs: CertMon’s reverse proxy terminates TLS and routes bytes between your browser and local ports entirely in memory on
127.0.0.1. No request bodies, headers, cookies, or URLs are sent over the network. - Project Discovery: Process paths, Git repository names, and listening ports are inspected using macOS kernel APIs (
libproc) and never leave your Mac.
Website analytics
This static website does not use tracking cookies or advertising pixels. Server logs generated by Cloudflare are retained for standard operational diagnostics and DDoS mitigation in accordance with Cloudflare’s privacy policy.
Questions?
If you have any questions about this privacy policy, email [email protected].