https://translate.google.com/translate?sl=auto&tl=en&js=y&pr...
Every data send by an extension should be user viewable.
Here's the json file (or maybe something better) that we are posting, press Agree to send it
They'd then claim it was for your security/privacy/protection. You know, like how Microsoft encrypts your Windows 10 usage data it sends them.
At least you could use the presence of such obfuscation as a sign there's probably something bad afoot. Presuming only a tiny number of extensions try to encode the data they send.
So, that "if you have nothing to hide..." argument, basically?
But you can bet GooBookSoft will lobby against that like their lives depended on abusing customer data. And they do depend on it.
With much regret, MiFaceGoo is rarely appropriate in the professional world.
> Every data send by an extension should be user viewable.
You can start Wireshark and get that data. But it would be too complicated for an average Joe.
Their privacy statement [2] includes a section that describes "Browsing usage, including visited web pages, clickstream data or web address accessed;" as one of the categories of "non-personal information" that they may disclose or share with 3rd parties.
I'd imagine most users installing an extension to make their browsing safer would not be happy to know they were also making their entire browsing history available to 3rd party data brokers at the same time.
Unscrupulous business practices are definitely made easier when no one actually reads Privacy Policies...
[1] https://www.mywot.com/
[2] https://www.mywot.com/en/privacy/privacy_policy