WebRTC leak protection for Chrome privacy.

Understand the scope of the WebRTC control

WebRTC is used for browser communication features such as calls and peer connections. Shieldly's optional control is intended to reduce local IP exposure through supported browser privacy settings. This is narrower than concealing all network information. It does not replace your public IP address, route traffic through a VPN or promise anonymity. A privacy indicator should be interpreted in the context of the specific browser setting it represents.

Check who controls the browser setting

A browser privacy setting may be managed by policy or another extension. If enabling WebRTC protection does not produce the expected state, inspect Diagnostics for the policy value and control status. Repeatedly toggling the switch cannot override a browser restriction. Record the browser version and the reported state when asking for help so the issue can be distinguished from a page-level filtering problem.

Test the communication features you use

After changing a WebRTC setting, check a representative call or conferencing service. If a connection fails, compare the same action with the setting restored and keep other configuration unchanged. Microphone and camera permission prompts are separate controls, so a denied device permission should not automatically be blamed on WebRTC privacy behavior. Restore the setting you intend to use after testing and note any service-specific limitation.

Frequently asked questions