Privacy & Network
Configure WebRTC, geolocation, and DNS settings for a browser profile
Last updated
Was this helpful?
Configure WebRTC, geolocation, and DNS settings for a browser profile
These settings control how your profile handles network and location data. Sites use these to detect inconsistencies with your proxy.
WebRTC is a browser feature some sites use for video calls and also probe for IP detection. This setting controls whether your profile leaks your real IP through it.
Altered
Reports a fake public and local IP while keeping WebRTC functional.
Real
Reports your actual IP.
Disabled
Turns WebRTC off entirely, which can be detected by sites.
Only proxy
Routes WebRTC through the proxy, depending on proxy support.
Keep this set to Altered. It keeps WebRTC working for sites that require it while hiding your real IP, which is the point of running a proxy in the first place. Switch to Disabled only if a target site flags WebRTC-altered profiles specifically.
Turn on Fill WebRTC public IP based on the IP to populate the public IP automatically from your profile's connection. Leave this on unless you need to set a specific IP value manually.
This setting controls how your profile responds when a site requests its location.
Prompt
Asks each time, like a normal browser.
Allow
Always grants the request automatically.
Block
Always denies.
Set this to Allow and turn on Fill location based on IP. This keeps your reported location consistent with your proxy's region, which sites commonly cross-check against IP location. Prompt adds friction with no benefit, since you already control how the profile behaves. Use Block only if your workflow never needs location and you'd rather avoid the request entirely.
Turn on Enable custom DNS to route your profile's DNS lookups through a custom server instead of the system default. Most profiles don't need this. Enable it only if you're troubleshooting DNS-based detection or have a specific server you need to route through.
Last updated
Was this helpful?
Was this helpful?