Show HN: I built a cross-browser extension that controls fingerprinting surfaces
Posted by tomaszjanusz 1 day ago
Hello Hacker News! I’m Tomasz, creator of Privacy Thing, a browser extension for Firefox and Chromium-based browsers. I’ve just released its Preview version.
Privacy Thing aims to reduce browser fingerprinting—the tracking of users without cookies.
It began as an internal project: a simple location simulator. Over time, I expanded it to cover more fingerprinting surfaces. It now has 13 protection categories affecting 50+ browser APIs and methods: Geolocation, time and locale settings, Canvas, WebGL, Audio, Navigator, Screen, Client Hints, Battery, WebRTC, Dedicated Workers, Service Workers, and Shared Workers. The list is still growing.
The extension is fully configurable. Users can create regional profiles and assign them to domain rules, with separate protection settings for each domain. Or they can skip domain rules and rely on the global configuration—I’m not here to decide what works best for them :-)
Privacy Thing uses Manifest V3, with all its pros and cons. Chrome and Firefox appear to offer similar extension APIs, but differ fundamentally at the level where Privacy Thing operates. This matters because its scripts must load as early as possible to be effective.
Its X-Ray module communicates with scripts running in the page context to show which APIs a site uses and how often it queries them. An aggregate count appears on the extension’s toolbar badge by default.
Each release includes processed, compact datasets covering Chrome build numbers, supported language codes, language-to-country mappings, popular screen resolutions, and hardware configurations. This keeps the extension independent of external services and there is no good reason to build extra infrastructure for it.
There are two exceptions. The regional preset wizard uses OpenStreetMap’s Nominatim geocoding service, but only after the user consents to sending the query. Maps are displayed using OpenFreeMap.
Presets can also be created manually. Users who know the coordinates can enter them directly without contacting any 3rd-party service.
The extension does not transmit telemetry or usage data. This makes development harder, but it is fundamental to its identity: user data belongs to the user. Privacy Thing configuration can be exported, edited and imported.
The Preview is currently distributed under a proprietary license. This is not ideal; I ultimately intend to release the source under an open-source license, most likely the AGPL.
More about the development process: https://tomaszjanusz.dev/en/projects/privacy-thing/
Download:
- Mozilla Addons: https://addons.mozilla.org/en-US/firefox/addon/privacy-thing...
- Chrome Web Store: https://chromewebstore.google.com/detail/privacy-thing-previ...
The extension is STILL under review in the Microsoft Edge Add-ons store -_-
Thank you for your suggestions and feedback. Please remember that this is still a preview: some things may not work, may be slower, or may not behave as intended. I sincerely hope such issues will be few and far between.
P.S. Yes, Privacy Thing fully supports Firefox Containers. I like the concept and believe extensions should support containers whenever possible. Privacy Thing will support them elsewhere too, including Brave, if Brave Software makes its container API public.
Comments
Comment by gruez 1 day ago
Comment by tomaszjanusz 1 day ago
Your opinion is completely correct if we assume that most users will use Tor Browser. However, it is 2026, and it does not seem that Firefox will regain its position on the market. The idea behind this extension is to provide very basic (relative to what the browser manufacturer could do - and often does not do) protection for users of mainstream browsers. I use Helium and Zen myself, depending on the context of the work I do, but I am aware that most people will reach for a browser whose manufacturer sunsetted Privacy Sandbox a year ago.
Comment by gruez 1 day ago
This seems contradicted by the screenshots, which lists options for "time", "canvas", and "screen". Firefox's RFP has protections for all of those. Not to mention it has "protections" for APIs that don't even exist on firefox.
https://developer.mozilla.org/en-US/docs/Web/API/Battery_Sta...
Comment by tomaszjanusz 1 day ago
As I wrote - the extension does not patch something that does not exist. I didn't mention it in the main post because the 4,000 character limit was simply too limiting for me. The text entry in AMO does not tell the user this either. Thanks for capturing one screenshot, as I simply had to mix up the collection of screenshots when I updated the extension's page - in fact, under Firefox, the configuration window does not present options related to Client Hints (also unavailable on the Mozilla platform) as well as the Battery Status API.
In the extension interface, you will find two places presenting protection details for those APIs with a "Not applicable" status. Configuration options for these items in the settings panel are not visible.
Thanks for pointing out this screenshot, as that wasn't my intention. If you look at the screenshot of the container options, you will see the actual feature set for Firefox. I've already deleted the screenshot, sorry for the confusion.
Comment by mtweak 1 day ago
Like another person said: passive fingerprint protection will be limited.
Comment by xnx 1 day ago
Comment by clonedhuman 1 day ago
Comment by tomaszjanusz 1 day ago
Comment by m00dy 1 day ago
Comment by tomaszjanusz 1 day ago
Comment by levi840714 1 day ago