43
So... seems like Firefox has its own trackers too?
(thelemmy.club)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Feb 2026
43 points (82.1% liked)
privacy
8485 readers
27 users here now
Big tech and governments are monitoring and recording your eating activities. c/Privacy provides tips and tricks to protect your privacy against global surveillance.
Partners:
- community.nicfab.it/c/privacy
founded 3 years ago
MODERATORS
No it's false, TorBrowsers, Librewolf and IronFox doesn't contains telemetry.
Just because some browsers are forks doesn't mean they contain telemetry.
The code is open-source, so anyone can see it by taking a look.
The screenshot in the post is from IronFox.
That doesn't mean it's true, you have access to the source code and you can see it's false.
https://gitlab.com/ironfox-oss/IronFox
It's not, though? Let me guess, it's from some tool or page doing static analysis on the APK and reporting results? Please include a link or reference to actual source when reporting in the future.
So, Firefox contains a library that can be used for reporting telemetry to Mozilla. When you download Firefox from Mozilla, this is enabled and pointing to Mozilla servers. After reading Privacy Notice shouldn't be a surprise.
When you install one of the fork that disables telemetry (IronFox, LibreWolf, Konform Browser at least do it this way), they will configure the build such that the endpoints are never called. Mozilla are actually reasonable enough that this is supported, documented, and reasonably straightforward for those bothering to build FF from source.
So yes, when you download IronFox it contains a library that could be used for Mozilla Telemetry. It's just that it's never used to do so (assuming no bugs).
Why not rip it out completely? Because completely ripping it out is more work, has its own risk of introducing bugs, and could introduce more work for maintainer with patching ~whenever they pull updates from Mozilla - increasing the time users have to wait for getting the monthly security fixes for their fork.