SWG bar permissions, local privacy & TLS probe limits
How SWG bar handles macOS System & Network Filter permissions, local SQLite storage, probe rate limits (12/min, 300/hr, 1000/day), and Manual probes only mode.
SWG bar · Updated
Security-conscious engineers often ask what a menu bar inspection tool actually sees on their Mac, whether it installs a new root certificate, and how many outbound network probes it creates. SWG bar is built to run locally on your Mac with transparent permission and rate boundaries.
Why SWG bar never installs a root CA or reads HTTP bodies
Unlike an intercepting proxy, SWG bar does not install any root CA certificate, does not take control of private keys, and does not decrypt your browsing traffic:
- System extension permission & Network filter permission: Used solely to observe outbound hostname/IP metadata for domain discovery (and, only when you explicitly enable Bypass SWG on a domain, to apply that domain’s bypass rule). Traffic passes immediately without buffering or inspecting HTTP message bodies.
- No central analysis server: All domain records, certificate chains, and trust evaluations are processed and stored locally on your Mac—none of this detection data is uploaded to SWG bar servers.
- Chrome companion data boundary: The optional Chrome extension passes only the active tab’s hostname and port over local Chrome Native Messaging to read existing local results. It does not read webpage contents, URL paths, query strings, or cookies. Review the privacy notice and extension privacy notice.
Built-in probe rate limits and Manual probes only mode
To avoid flooding corporate networks or triggering rate-limit alarms, SWG bar enforces strict caps on automatic background TLS handshakes:
- Automatic probe limits: 12 probes per minute, 300 probes per hour, and 1,000 probes per day.
- Manual probes only: In SWG bar settings or monitoring controls, you can pause automatic discovery or switch to Manual probes only mode, where SWG bar performs TLS handshakes only when you explicitly request one (such as via
swgbar probe <domain>). - Pause/resume via CLI: Terminal users can check or toggle monitoring anytime with
swgbar monitoring status,swgbar monitoring pause, andswgbar monitoring resume(CLI guide).
Where local detection data is stored on macOS
SWG bar stores its local SQLite database and logs inside standard macOS user directories:
~/Library/Application Support/SWGBar/~/Library/Logs/SWGBar/
Selected sensitive stored fields are encrypted with a local key, though logs and some metadata (such as hostnames, IP addresses, and certificate subjects) are not encrypted—review log files before sharing them during troubleshooting. Note that upgrading to a newer version of SWG bar may reset the local database, rules, encryption key, and archived logs, so save any evidence you wish to keep beforehand.
Clear history or reinitialize cleanly
If you switch corporate networks, change VPN environments, or simply want a fresh baseline, click Reinitialize inside SWG bar to clear historical probe records and re-probe active domains from scratch—or review how SWG bar works and how to detect HTTPS & SSL inspection.