MetricsDataPing: Difference between revisions

m
Line 58: Line 58:
* policy changes on the Mozilla side.
* policy changes on the Mozilla side.


The user has no way to verify whether any of that is happening or not, and that already is a privacy violation. So, it's irrelevant what the intended usage was, only what is theoretically possible.
The user has no way to verify whether any of the above is happening or not, and that already is a privacy violation. So, it's irrelevant what the intended usage was, only what is theoretically possible. The above must be impossible - not just "We won't do it, we promise!", but impossible.


Having a UUID would allow, for example, to track all my dynamic IP addresses over time, and allow to build a profile, when combined with access logs. If I have a notebook or mobile browser, it would even allow to track the places where I go based on IP geolocation / whois data.
Having a UUID would allow, for example, to track all my dynamic IP addresses over time, and allow to build a profile, when combined with access logs. If I have a notebook or mobile browser, it would even allow to track the places where I go based on IP geolocation / whois data.
This must be impossible. Not just "We won't do it, we promise!", but impossible.


=== Google Chrome ===
=== Google Chrome ===
Confirmed users
591

edits