If Tor browser sends additional data over the net, it does so via the Tor network, so you are at no more risk than any other explicit requests you make via Tor

If Tor browser sends additional data over the net, it does so via the Tor network, so you are at no more risk than any other explicit requests you make via Tor browser. Unless you're using uMatrix in advanced mode with extra strict content settings enabled, Tor browser won't keep your session completely private. It isn't designed to do so. It's designed to keep a single session isolated and - if you're careful - anonymous within itself, but any activity within that session can still be easily associated with other activity within that session, unless you're selectively blocking 3rd parties. NoScript (bundled with TorBrowser) does this partially but not fully. Beyond the above (that TorBrowser isn't designed to protect from what we're discussing here, and as such their vetting won't be overly concerned with it), there's also the fact that they track ESR which is likely to have less of these issues since they'll usually be fixed before feature releases are backported. Edit: In case you're still of the view these bugs are "imagined", here's two small (related) examples: [0], [1] though not the only ones. The "lack of consideration" I referred to in my above post that imo causes these bugs is the language seen in the second one of those bugs: > It's not tracking but I'd imagine users who were uncomfortable submitting usage data from the app to GA also don't want to log their errors in Sentry This is a Mozilla developer who seems to fundamentally disagree with (I'd guess most) users on what tracking means. [0] https://bugzilla.mozilla.org/show_bug.cgi?id=1380754 https://bugzilla.mozilla.org/show_bug.cgi?id=1380754 [1] https://github.com/mozilla/addons-frontend/issues/2802 https://github.com/mozilla/addons-frontend/issues/2802