Let me give you more context.
DataUnlocker has a long history and comes from years of hard work, mainly to help developers and product teams deal with missing data. If you’re in tech or marketing, you know how critical accurate metrics are – attribution, conversion rates, traffic volumes. The goal isn't to track individuals – it's to ensure these metrics aren't broken.
I’d ask you to consider this perspective: - People who want to stay anonymous, will stay anonymous. DataUnlocker doesn’t interfere with that at all! - It fixes just the technical accounting of data. Things like location masking, anti-fingerprinting, VPN use, etc., – all still apply and protect your privacy (and moreover I can confirm there's no way around them).
Hence, even on websites which don't respect your privacy (there are not many, to be completely honest) and try to misuse tracking, blocker users would still appear as anonymous, ID-less visitors. That’s by design, here to stay – and I can assure this from my experience.
DataUnlocker just. Fixes. Tech. (think of it like DataUnlocker making web apps behave more like mobile apps — hard to tamper with)
Accurate metrics may be useful, but business got along just fine without all this data for centuries, so to say they are critical is a joke. Targeted advertising might make a lot of money for a very small number of people, but it has been a disaster for society at large.
This tool is designed and proudly intended to allow exactly that. After all, someone taking actions to prevent data collection is unambiguously signalling that they do not consent to being spied on, and this tool intentionally subverts their wishes.
You don't wear a balaclava to walk down the street just to avoid being seen – you still share some minimal data with the world, like your appearance.
Similarly, on the Internet, some minimal metadata is inevitably shared, even if you're privacy-conscious.
So a genuine question is: what do you consider acceptable "minimal data" to share with websites? None?
Jshelter will block that shit https://jshelter.org/
Detects and blocks nonfree and potentially dangerous JavaScript.
I am sure Ublocks gorhill will be on this
Here's the bigger picture, from my point of view:
The web is shifting toward consent-based tracking – and rightly so. Cookie and data collection consents are now standard (and even legally required in the EU). DataUnlocker is fully compatible with this. When implemented on the website, it activates only after user consent – just like any compliant tracking setup. The tech to do that wasn't trivial a few years ago, and it still catches up. https://support.google.com/tagmanager/answer/10718549?hl=en
In fact, if you visit pages with an ad blocker, cookie consent modals will not even appear – meaning no tracking starts at all. That's a win–win: privacy respected, no shady behavior, "no" is the default. Big companies can't afford to violate that.
What DataUnlocker addresses is a different issue:
Let's say a user wants to grant "essential" tracking consent — they've consented — but uses an ad blocker by default. They load the page, bounce in 5 seconds, and are gone. Most won't bother to disable the blocker for 5 seconds – maybe 1–2% will. So how do you solve this from the publisher's perspective?
Even the best tools can be misused (think Google Sheets). But when used responsibly, DataUnlocker simply helps fix a technical blind spot – surely not spy on people who didn't opt in.
nikitaeverywher•4h ago
DataUnlocker 2.0 offers a drop-in solution: a proxy and JavaScript protection layer that shields tracking from blockers. It becomes an integral part of your web application — not only hiding analytics from generic blocking filters, but also making the code essential for the app to function. Blockers simply have no safe way to remove it.
Your feedback is welcome – happy to dive deeper.
azalemeth•4h ago
nikitaeverywher•3h ago
It's a broader topic worth deeper discussion to be honest. I'll be posting more on it soon — including why I believe the internet privacy "movement" should align with this: instead of breaking tools used in web apps (while I agree if you can, you can), the focus should go on pseudo-anonymizing users (web clients) while preserving functionality – parts of it are already implemented (VPNs, one-time sessions, etc). I can honestly see both sides of the debate — it's a long-standing and nuanced topic.
JohnFen•3h ago
nikitaeverywher•1h ago
I'm sure when one uses Tor browser (an example of what I mean under pseudo-anonymizing), they are as safe from tracking as possible. They will get tracking cookies and all that, but from a random location, and all IDs the web app could have created will be destroyed right after closing the browser tab.