🔒 iBrowe WebRTC IP Handling Policy

iBrowe offers advanced security features, including fine-grained control over how WebRTC handles your device’s IP addresses. This helps prevent privacy leaks that can occur via WebRTC even when using VPNs or proxies.

You can configure this option by visiting:


ibrowe://settings/privacy

⚠️ Most users will never need to change this. The defaults are already privacy-focused.

📋 Available WebRTC Policies in iBrowe

Policy Description
Default WebRTC can enumerate all network interfaces and bind to them to discover public IPs. Used when Fingerprinting Protection is disabled (except in private/Tor tabs).
Default Public and Private Interfaces WebRTC uses only the default route chosen by the OS for HTTP. It exposes both public and associated private IP addresses.
Default Public Interface Only WebRTC uses the default HTTP route but does not expose any private/local IPs.
Disable Non-Proxied UDP (Recommended) WebRTC uses only TCP unless the proxy supports UDP. This setting prevents any IP exposure and is enabled by default if Fingerprinting Protection is on or in Tor tabs.

🔍 Learn More

For a technical deep-dive into how these settings are implemented, see:


[https://cs.chromium.org/chromium/src/content/public/common/webrtc/_ip/_handling/_policy.h](https://cs.chromium.org/chromium/src/content/public/common/webrtc_ip_handling_policy.h)

This documentation is adapted from Brave Browser’s original guidance:
https://github.com/brave/brave-browser/wiki
iBrowe applies the same Chromium policies but with enhanced privacy defaults.