Privacy and data transmission — updated 2026-10-15
Applies to WireGuard for Firefox extension 0.2.1 and Firefox WireGuard macOS companion 0.2.1.

When you choose Connect, Firefox sends covered browsing traffic through the local companion and your chosen WireGuard server. This includes destination domains and IP addresses and the requests and responses needed to load websites. WireGuard encrypts traffic between your Mac and that server. HTTPS remains encrypted between Firefox and the destination website. The server operator can observe connection metadata and traffic not separately protected by HTTPS. Choose a server you trust. This project does not operate a VPN service.

The extension sends connection commands, a random local client identifier, and the selected profile identifier to the companion through native messaging. The companion returns profile names and identifiers, connection state, and displayed connection details. Website contents are not sent in these control messages. Keys and complete configurations never reach the extension; the companion uses them to establish the WireGuard connection.

Public IP and country lookup
After a healthy handshake and approximately every five minutes while connected, the companion makes an HTTPS request through the tunnel to https://ipwho.is/?fields=success,ip,country_code. The service receives the exit IP and ordinary request metadata, such as timing and the HTTP user-agent. It does not receive WireGuard keys, profile names, configured client/DNS addresses, or browsing history from this lookup. There is no direct-network fallback; failure displays Unavailable. Country describes the exit IP, not GPS or your physical location.
The provider has its own privacy policy (https://ipwhois.io/privacy) and terms (https://ipwhois.io/terms), including possible request logging. The project does not control its retention or availability.

Local storage
Complete tunnel configurations are stored in macOS Keychain. Profile names and identifiers are stored in the companion's per-user application folder. Firefox local extension storage retains a random client identifier, selected profile identifier, desired connection state, and kill-switch choice. Public IP, country, tunnel DNS/client addresses, and connection byte counters stay in memory; the product does not save them as history.
The product does not record browsing history, website content, or private browsing activity. It has no analytics, advertising, or remote error reporting. Project maintainers receive no automatic reports. Your chosen server, DNS provider, websites, and the IP lookup provider process requests under their own policies. Endpoint resolution and encrypted WireGuard transport use the Mac's ordinary network.

Controls and limits
Firefox's installation prompt declares browsing activity, website content, and location information because traffic is forwarded and the exit IP is geolocated. This describes transmission for connection features, not analytics or storage by the project. Firefox 140 or later is required for built-in consent.
Disconnect stops tunnelling and returns to ordinary browsing. The kill switch blocks covered requests during detected failures when on; switching it off permits ordinary browsing during an outage. Localhost bypasses the tunnel. Disabling or removing the extension ends enforcement. This is a browser proxy control, not an operating-system firewall.
Delete profiles in the companion to remove their Keychain entries. Uninstalling the extension removes its local extension storage. Deleting the companion alone does not delete saved Keychain entries.

Full policy and removal instructions: https://github.com/kristof-dragon/firefox-wireguard/blob/main/docs/privacy.md
Questions: https://github.com/kristof-dragon/firefox-wireguard/issues
Do not post keys, real configurations, private endpoints, or unredacted screenshots.