Privacy Policy

The browser checks read values exposed to JavaScript, including the user agent, languages, timezone, screen characteristics, cookie support, privacy request signals, logical processor count, device memory when available, and selected graphics information.

Canvas, WebGL, offline-audio, font-sample and client-rectangle hashes are computed in your browser for display. BrowserCheck does not include those raw hashes in analytics events and does not send them to the network-metadata endpoint.

Like any website, BrowserCheck's hosting provider receives the IP address needed to deliver the page. The /api/network endpoint returns the IP and available approximate Cloudflare request metadata—such as country, city, region, timezone, network organization and coordinates—back to the same browser. Its response is marked no-store.

The browser no longer calls third-party IP lookup services for this result. Cloudflare may process standard request and diagnostic metadata under its service configuration and policies. BrowserCheck does not deliberately write fingerprint hashes or a custom IP history to server-side application storage. An optional baseline can be saved locally as described below.

The WebRTC comparison creates a data-only peer connection and contacts Google's public STUN service. A STUN request can reveal network addresses to that provider. No camera or microphone permission is requested.

The approximate map is provided by OpenStreetMap. It loads only after you select “Load third-party map”. Before that, the map component makes no request to OpenStreetMap. Your browser sends a normal request to OpenStreetMap containing the requested coordinates and standard network metadata such as your IP address. The iframe uses a no-referrer policy.

Google Analytics loads only after you select Allow analytics in the optional analytics panel. If you select Decline—or if your browser exposes Global Privacy Control before a choice is stored—the analytics script is not loaded. You can reopen Analytics settings from the page and change the choice.

Analytics events are limited to product interactions such as a detection completing, a report opening or an AI-control checklist being used. BrowserCheck does not add raw IP addresses, Canvas hashes, WebGL hashes, audio hashes or full user-agent strings to those events. Google and Cloudflare still process standard connection data when their services are contacted.

The site does not load advertising scripts or ad units.

Your theme preference and analytics choice (browsercheck:analytics-consent:v1) are stored locally. AI Controls checklist progress and its update time are also stored locally so the checklist can resume. These values remain in your browser until you reset the feature, clear site data or remove them with browser developer tools.

On the WebRTC leak test page, choosing Save this result as baseline stores one local record for before/after comparison. It contains observed public request and server-reflexive IP addresses, candidate transport, browser family and version, operating-system family, test states, times and method versions. It excludes private host addresses, full User Agent, fingerprint hashes and precise location. The baseline is not uploaded. It expires after 7 days and is removed when the comparison page next checks storage; data can remain on disk while the site is closed. Use Delete local baseline or clear site data to remove it sooner. A fresh check does not overwrite the baseline.

In BrowserCheck Lab and product self-tests, Save baseline stores the selected product/version, observation time and the displayed browser, language, timezone, screen, graphics and storage values locally. Saving or creating an isolation test writes random test markers in a first-party Cookie, localStorage and IndexedDB. The cookie expires after 30 days; local records remain until explicitly deleted or site data is cleared. Storage comparisons accept codes for 30 days. Test results are not uploaded; the random cookie is sent with normal requests to this origin. Exported JSON remains wherever you save it. Cleanup removes only the selected test's markers in the current profile; separate profiles must each be cleaned.

The installable app caches its icons and offline fallback pages on your device. Its service worker does not cache IP responses, fingerprint values, detection reports or third-party requests. Clear site data in your browser to remove these offline files.

Live browser results exist in page memory and disappear when the page is closed or reloaded unless you explicitly save the local baseline described above. Copied and printed WebRTC comparison summaries omit raw IP addresses and exact browser versions. BrowserCheck does not sell personal data. Service providers receive data only when necessary to host the site, perform the explicitly described WebRTC or map request, or provide analytics after consent.

You can decline analytics, block third-party map requests, block WebRTC through browser or network controls, clear local site data, and use browser privacy protections. Some choices can make a test unavailable; unavailable results are not treated as successful checks.

Questions about this policy can be sent to feedback@browsercheck.net. If the site's processing changes materially, this page and its effective date will be updated before the description is relied upon for the new behavior.