PrivacyTestLab is built around transparency, minimal data collection, and browser privacy awareness. This Privacy Policy explains how our tools work, what technical information may be processed during testing, and how we protect user privacy across the platform.
PrivacyTestLab provides browser-based privacy and security testing tools designed to help users understand IP exposure, browser fingerprinting, DNS leaks, WebRTC behavior, and related privacy risks.
Most tools operate directly inside the user's browser without requiring account creation, downloads, or permanent storage of personal data.
PrivacyTestLab does not require user accounts or personal profiles to browse the site, read articles, or use any of its diagnostic tools — every leak test, lookup, and scanner is fully usable without signing in. The one exception is the optional developer API, which requires a free account only if you choose to query our tools programmatically. See API Accounts below for what that involves.
To generate accurate privacy diagnostics, certain technical information may be processed temporarily during testing. Depending on the tool being used, this may include IP address details, browser user-agent information, DNS resolver data, WebRTC network details, screen resolution, device capabilities, or approximate geolocation derived from IP connectivity.
This information is used solely to display privacy-related test results and explain potential browser or network privacy exposure.
Many PrivacyTestLab tools run directly in the browser using JavaScript and browser networking APIs. These tools are designed to analyze privacy exposure without requiring software installation or user registration.
Available tools may include IP leak testing, DNS leak detection, WebRTC analysis, browser fingerprinting analysis, and related privacy diagnostics.
Some tests temporarily access browser-provided network information in order to display diagnostic results. In many cases, processing occurs locally inside the browser session.
PrivacyTestLab offers an optional developer API that lets you query our tools programmatically. Using the API is the only part of this site that requires an account — browsing, articles, and every browser-based tool remain fully usable without one.
If you create an account with an email and password, we store your email address and a one-way cryptographic hash of your password — never the password itself. If you sign in with Google or GitHub instead, we only receive and store your email address and the account ID that provider assigns you; we never see or store your Google or GitHub password.
To block automated password-guessing, failed sign-in attempts are logged with the originating IP address and timestamp. These entries are temporary and are automatically deleted after 24 hours.
An API key itself is stored only as a one-way hash. The full key is shown to you once, at the moment you generate it, and cannot be retrieved by us afterward — only revoked. We keep a daily count of how many requests each key has made, to enforce the rate limit; we do not log the content or parameters of individual API requests.
PrivacyTestLab does not currently use invasive tracking systems or custom behavioral profiling technology for identifying users across the web.
However, third-party advertising providers, embedded content, or analytics services may use cookies, local storage, or similar technologies to deliver advertisements, improve services, measure engagement, or prevent abuse.
Users can choose which optional cookies run at any time via the Cookie Settings link in the site footer, or disable cookies entirely through browser settings — although some website functionality or advertisements may not operate correctly afterward. See our Cookie Policy for the full breakdown of cookie categories.
PrivacyTestLab relies on selected third-party providers for hosting infrastructure, domain management, email delivery, DNS services, and website security operations.
These providers may process limited technical information as part of normal infrastructure and operational functionality.
PrivacyTestLab does not directly control how external service providers manage their own internal systems, security practices, or data retention policies.
PrivacyTestLab uses reasonable technical and administrative safeguards designed to reduce unauthorized access, abuse, misuse, or service disruption.
Security protections may include HTTPS encryption, firewall systems, server monitoring, spam prevention systems, and restricted file handling procedures.
Although reasonable efforts are taken to improve platform security, no online system can guarantee complete protection against every security threat or cyber attack.
Depending on your country or region, applicable privacy laws may provide rights related to personal information and data processing.
These rights may include requesting access to submitted information, requesting deletion of certain data, correcting inaccurate information, or managing browser cookie preferences.
Because PrivacyTestLab generally avoids account systems and large-scale personal data storage, many requests may already be inherently limited by platform design.
PrivacyTestLab may periodically update this Privacy Policy to reflect operational changes, new features, legal requirements, advertising updates, or security improvements.
Updated versions will be published on this page along with a revised “Last Updated” date.
Tool releases and research notes, sent when there's something worth reading. Nothing else.
