Recent searches
Search options
Administered by:
I'm really trying to make sense of the new @mozillaofficial privacy policy.
Here's where I'm getting tripped up:
> Mozilla doesn’t sell data about you (in the way that most people think about ‘selling data’)
OK, sure. But if Moz isn't "selling my data in the way that most people think about selling data" then how *is* Moz selling my data?
@pluralistic @mozillaofficial Apparently it has to do with CCPA’s definition of “selling data” which simply includes data being transferred to any third party for any reason. Because Mozilla uses tools for collecting usage metrics and has some marketing and tracking stuff built in, any third party involved in this would receive this data, and the CCPA considers this “selling data”.
It can apparently be so over-broad that service providers have included this kind of language simply for your data being hosted in their services in a third party provider like Hetzner, AWS, etc.
So it appears to be some potentially over-broad definitions in law.
@bedast @pluralistic @mozillaofficial Why is Mozilla using these third-party providers when there are many, many alternatives that would not require distributing personal information to other organisations?
@wizzwizz4 @pluralistic @mozillaofficial The problem is the moment you use a third party, it has to be disclosed. Firefox has a sync feature. Where are those services hosted? Firefox has Pocket, which has had its own controversies in the past. Where is that hosted?
It’s not always about telemetry. But in the case of Mozilla, it definitely includes telemetry.
@bedast Sync is supposed to be encrypted data that Mozilla can't read, so neither should the server owner be able to, and Pocket is one of the services, but that sentence is not in the part specific to Mozilla services.
@wizzwizz4 @pluralistic @mozillaofficial
@ciourte @bedast @wizzwizz4 @pluralistic @mozillaofficial When in doubt, you could use a project like this; https://www.xbrowsersync.org/
@RandamuMaki Firefox Sync is Open Source as well though, and encrypted client side too. You can run your own server (if you really want to https://github.com/mozilla-services/syncstorage-rs) and change identity.sync.tokenserver.uri in about:config to point to it. The biggest differences are the supported browsers are not the same (Firefox, most of its forks, Epiphany and Gnome Web, but not Google Chrome/Chromium) and the fact that it's built-in so it doesn't need a browser extension.
@bedast @wizzwizz4 @pluralistic @mozillaofficial