This Privacy Policy explains how WebRTCTest handles information when you browse the site or run a diagnostic. The guiding principle is data minimization: tests should use only the browser capabilities and network requests needed to produce the result you requested.
Camera, microphone and screen data
Camera, microphone and screen-share tests require an explicit browser permission or source-selection action. The resulting media is used for the local preview or measurement in your browser. WebRTCTest does not intentionally upload, record or store the audio, video or shared-screen stream. Stop controls release active tracks, and closing or reloading the page ends the browser session.
Your browser and operating system control permission prompts. You can deny a request, stop sharing, revoke a saved permission or close the page. Some diagnostic details, such as a device label, resolution, frame rate, sample rate or enabled audio processing, may be displayed locally so you can interpret the result.
WebRTC, STUN and TURN network data
WebRTC connectivity tests necessarily communicate with a STUN or TURN endpoint. The main readiness and leak checks use a public Google STUN endpoint by default. A STUN server can receive network information needed to return a server-reflexive candidate, including your public-facing IP address. If you enter a custom STUN or TURN endpoint, your browser contacts that endpoint directly under its operator's policies.
TURN usernames and credentials are used by the browser for the requested live allocation test. WebRTCTest does not intentionally persist them in local storage, URLs or analytics. ICE addresses and raw candidate details are displayed for diagnosis and should be treated as sensitive before copying or sharing.
Parser and local loopback data
SDP and ICE candidate parser input is processed in the browser and is not intentionally sent to a WebRTCTest parsing service. Data Channel and WebRTC statistics tests create local browser peer connections. Their displayed messages, metrics and raw statistics are intended to remain in the current browser session.
Google Analytics 4 disclosure
Current status: WebRTCTest includes a Google Analytics 4 measurement tag on public pages. It is used for standard page-view and site-usage measurement; the site does not intentionally send diagnostic values as custom analytics data.
GA4 may process information such as visited pages, approximate location derived from IP address, browser and device characteristics, referral information and standard interaction or timing data. WebRTCTest will not intentionally send camera or microphone media, SDP, ICE addresses, TURN credentials or device labels as analytics events or parameters. If applicable law requires prior consent for analytics collection, the site configuration must be updated to honor that requirement before analytics is enabled for the affected visitors.
Depending on configuration, consent choices and applicable law, Google Analytics may use cookies or similar identifiers. Users will be able to refuse non-essential analytics where consent is required, use browser controls, or use Google's opt-out tools. Google explains how it handles information from sites using its services in How Google uses information from sites or apps that use our services.
Hosting, security and retention
The hosting or content-delivery provider may process routine request information such as IP address, user agent, requested URL, timestamp and security signals to deliver the site, prevent abuse and maintain reliability. Retention for infrastructure logs depends on the active hosting configuration and provider. WebRTCTest does not use this policy to claim ownership of information independently collected by a custom STUN, TURN, browser-extension or third-party service.
Your choices and policy changes
You may use informational pages without granting media permission. You may deny or revoke device access and avoid connectivity tests if you do not want to contact their configured network endpoints. Material changes to this policy will update the date above and may also be noted in the Changelog.
For questions or privacy requests, follow the privacy-safe instructions on the Contact page. Do not publish personal information, credentials or raw diagnostic data in a public support request.