Privacy policy
A tool about what websites can see has to be straightforward about itself first. ReadMyBrowserruns no analytics, carries no advertising and loads no third-party script. Browsing it makes two network requests, both to this domain, and a third only if you choose to send us a message. What follows is the whole of it, and every claim in it can be checked in your browser's network panel.
Last updated: 5 August 2026
The short version
Nothing about you is collected, stored, sold or measured. Every value the site shows you is read in your browser and displayed to you, and it is gone when you close the tab. There is no analytics product on this site, no advertising, no tag manager, no session recording, no A/B testing tool, no externally hosted font and no embedded video. Not disabled, not consent-gated: absent.
That includes your fingerprint. The uniqueness test computes a hash in your browser and shows it to you. It is not transmitted, not stored, not written into a URL, and not folded into any kind of event. A site that explains fingerprinting while fingerprinting its readers would be worth nothing, so that line is not a policy preference, it is the product.
What runs in your browser
Every value on the dashboard and property pages (your user agent, screen, timezone, WebGL renderer and so on) is read locally using standard web APIs. Those readings are displayed to you and never transmitted to us. When you close the tab, they are gone.
The external lookups, and why
A few features need a network call. We keep them minimal and name them plainly:
- Public IP lookup. To show your IP address, your browser asks our own endpoint to echo back the address the request came from. This is inherent to checking your IP. We do not log or store it.
- IP location estimate. The IP location page uses the approximate, city-level geolocation our hosting platform (Vercel) derives from your IP and attaches to the request. No precise location is involved, and we do not log or store it.
- Reverse geocoding, only with consent. The zip code, postal code and address pages ask your browser for GPS coordinates, and only after you press the button and accept the browser prompt. To turn coordinates into a zip code or address, those coordinates are relayed through our endpoint (which adds the service identification the provider requires and does not log or store anything) to the public OpenStreetMap Nominatim service. If you do not consent, no coordinates are read and no such request is made.
The one third-party service involved (OpenStreetMap Nominatim, for reverse geocoding) has its own privacy practices. We pass along only the coordinates strictly needed for the lookup you triggered, and only after you consent.
Advertising
There is none, and there is no advertising partner, no ad network account and no ad script on any page. An earlier version of this policy described advertising cookies and a consent banner for visitors in the EEA and UK. That text was inherited from a template and described a site that does not exist. It has been removed, and the removal is listed on the changelog rather than made quietly.
If advertising is ever introduced, this policy changes first, the date above changes with it, and the change appears on the changelog. Until you see that, take the absence at face value.
Cookies and storage
One thing is stored on your device, and it is a preference rather than an identifier: whether you chose light or dark mode, kept in your browser's local storage. It never leaves your device and it identifies nothing.
One cookie is written, briefly, and only on the cookies page: a throwaway value written, read back and deleted again in the same moment, because that is the only honest way to test whether cookies actually work. Asking the browser whether it thinks cookies are enabled gives the wrong answer often enough to be useless.
There is no cookie banner on this site. That is not an oversight. Asking your consent for tracking that does not happen would be theatre, and it would train you to click through a dialogue that means nothing.
Security headers, as verifiable evidence
Claims in a privacy policy are cheap. Response headers are not: your browser enforces them whether we mean them or not, and you can read them yourself in the network panel. This site sends a Content-Security-Policy that permits no third-party script, style, font or frame at all, so any tracker added here by accident, in any future change, would simply fail to load rather than quietly working. It also sends a Permissions-Policy that grants geolocation and denies camera, microphone, payment, USB and the rest, and a strict Referrer-Policy so the pages you visit here are not announced onward.
The contact form
One outbound connection is permitted, and only when you press send on the contact form: the message posts to bindly.nl, a shared endpoint run by FusionStudios, the same studio that maintains this site. It receives the name, email address and message you typed and nothing else. No detected value, no fingerprint and none of the signals on this site go with it.
If you would rather not use the form, do not use it. Nothing on the site requires it, and every explanation here works without ever contacting us.
The embeddable widget
The widgetfollows the same detection rules: it reads values in the visitor's browser and makes only the first-party IP echo lookup. It sets no cookies and reports nothing back to us or to the site hosting it beyond what the visitor's own browser already reveals. It carries no ads and no analytics, which is the point of offering it.
Analytics
There is none. No product, no self-hosted alternative, no pixel, no beacon, not even a cookieless one. The only picture we have of who visits is the aggregate query and impression data Google Search Console reports about its own users, which we can read and you are already counted in whether this site exists or not.
The cost of that choice is real and worth naming: we cannot tell which explanations are working, and we find out about a broken page when somebody writes in. On this particular site that is the right trade, because the alternative is asking you to accept a measurement script on a page that is explaining measurement scripts.
Children
The site is a general-audience reference tool and is not directed at children, and it collects no personal data from anyone.
Changes and contact
If this policy changes, the date above will change with it. Questions are welcome via the contact page.