Privacy Policy
DeadPixel's privacy policy — the test runs entirely on your device; what little data the site touches and how to reach us.
Last updated: October 2026.
DeadPixel is designed so that the interesting part — your screen — never talks to us. The test, the exerciser and every guide run entirely inside your browser.
Data we do not collect
- Nothing about your screen or your tests. Color choices, exerciser sessions, defect positions — none of it leaves your device. There is no upload endpoint to send it to.
- No account, no identity. No sign-up, no email capture, no profiles. The tool doesn’t even write to localStorage — closing the tab wipes the session.
- No fingerprinting or session replay. Analytics is limited to the GA4 integration described below, and pixel-test results are excluded.
Data that exists because the web exists
- Server logs. The site is served by Cloudflare, which processes standard request metadata — IP address, user agent, timestamp — to deliver pages and resist abuse. That’s the entirety of server-side processing.
- Advertising cookies. Where ads appear (Google AdSense), the ad network may use cookies to serve and measure ads. You can disable personalized ads in your Google ad settings. The tester itself neither needs nor reads any of this.
Retention and sharing
There is no database of test results, user records or test history. Cloudflare and Google retain request data under their own policies. We do not sell test inputs or results. If you email us, the message lives in our mailbox until the conversation is done; it is never added to a mailing list or used for marketing.
Your choices
- Cookies: your browser can block or clear ad cookies at any time; the test works identically without them.
- Requests: because we hold no accounts or stored test data, deletion requests usually concern email in our inbox; write to us and we will remove it.
Google Analytics 4
We use Google Analytics 4 (GA4) to understand traffic, feature use and site performance. Google processes this information for us and may process it outside your country. See Google’s Privacy Policy.
This root uses its own GA4 Measurement ID. Before GA is configured, Google Consent Mode sets analytics_storage, ad_storage, ad_user_data and ad_personalization to denied. We set ads_data_redaction to true, url_passthrough to false, and both allow_google_signals and allow_ad_personalization_signals to false. GA4 therefore sends cookieless measurement requests and may not read or write analytics or advertising cookies. Google receives each measurement request, including the IP address in transit, and may derive a coarse location. It also receives browser, device, language and network metadata.
Enhanced Measurement is currently enabled, so GA4 may also automatically measure page views, scrolls, outbound-link clicks, site searches, video interactions, file downloads and form interactions, together with relevant link, file or form metadata. Our integration does not send form values.
Our adapter supplies the page location as the origin and path only—never the query string or fragment—and reduces the referrer to its origin. Tool use is sent as a tool_action event with a normalized action_name. Our custom adapter never sends tool inputs or content, uploads or photos, form values, a user ID, or values from local storage.
You can block Google Analytics requests in your browser or a content blocker; the core tools continue to work.
Questions
Privacy questions, corrections or requests: hello@tolerence.net, or the contact page.