Hacker News Reader

    The "Get Add-ons" view in Firefox is an iframe

Please don't hide behind technical details. If click something in the browser and it causes Google to be notified, then you have send data about me to Google. Without my consent.

    privacy policy is linked from the Get Add-ons view

Nobody reads those and you know it. The reason people use Firefox is to not get tracked by Google.

Honestly, you hugely fucked up with this one. You lost a massive amount of trust with me that took years to grow.

> Nobody reads those and you know it. The reason people use Firefox is to not get tracked by Google.

If you care about privacy, blind trust is never something you should have.

This has all the trappings of a mistake to me. A group of developers responsible for developing one area (the add-ons page), was not considering the impact it might have on another (the browser developers). Perhaps they should find a different solution, but it rings hollow to argue that a privacy conscious user shouldn't be expected to have read the privacy policy.

Someone submitted a PR to Mozilla to fix this, and the Mozilla devs closed it, arguing that Google Analytics does not count as tracking. See: https://github.com/mozilla/addons-frontend/pull/2787#issueco...

The TOR devs are fixing this part in their browser, and their comment was:

> Disallow `about:addons` unless the extensions directory is volatile, because regardless of what Mozilla PR says about respecting privacy, loading Google Analytics in a page that gets loaded as an IFRAME as part of an `about:` internal page, is anything but.

Check that issue again. Before you posted this they agreed and pushed the issue to the add-ons team. Do not track should turn off Analytics.

But that's not my point. As I said, they could well be wrong, but it's over the top to argue that it's Mozilla's fault for disclosing this in the privacy policy (which apparently no one reads). If you are so privacy conscious that this bothers you that much, the privacy policy should be required reading.

> If you are so privacy conscious that this bothers you that much, the privacy policy should be required reading.

No, this is something that by law I have to be informed about. And Mozilla has a reputation of working for their users, so I actually trusted them.

I do agree with you after this, the trust was misplaced, Mozilla is not any better than Google, NSA, MfS/Stasi or GeStaPo, just not giving a single fuck about privacy, but I did trust them before this, and so did many others.

In fact, people only used Mozilla products because of this trust.

There goes yet another example of Goodwin's law in action, but I'm not so glad for the arguably rash, overly emotional, and definitely not balanced analogy.

May I suggest that Mozilla stops walking a "very thin line" between telemetry and user privacy and instead walks beside a very thick line, on the side of user privacy. This incident has proven how easy it is to step off a very thin line into territory that your users are disgusted by.

Choose to walk the thick line and even if you stumble, you will not fall.

That’s all fine and nice, but how did Mozilla Legal approve this in the first place?

It’s obvious this violates both the so-called "Cookie Law" and the Google Analytics ToS, as both require any page with tracking to specifically tell the user that they will track the user. And the so-called "Cookie Law" goes even further, and requires it to be directly done in a modal.

How did Mozilla, a company saying they fight for privacy, approve something that does not even meet the absolute minimum bar for privacy, the actual privacy laws?

It's not "obvious" that it violates either of those.

The general consensus is that normal GA tracking alone does not meet the standards to trigger either the EU or the stricter Dutch cookie notification requirements since they are using first-party cookies not tied to PII and don't follow you across sites. And that's assuming a standard GA snippet, not the smaller subset of data Mozilla is collecting here.

And the GA ToS require you to have a privacy policy and to make users aware of it. It doesn't require a link on every page. You already agreed to the Mozilla privacy policy as part of the Firefox install process, right?

The general consensus is that normal GA tracking alone does not meet the standards to trigger either the EU or the stricter Dutch cookie notification requirements since they are using first-party cookies not tied to PII and don't follow you across sites

Do you have a good reference for this? Especially the "don't follow you across sites" seems weird as Google will end up collecting hits from the same IP/browser/etc combo across sites, which trivially allows following.

Found a source for this opinion. Here [1] are instructions from the Dutch Government's "Personal Data Authority" on setting up GA in compliance with their laws in a way that does (did?) not require an explicit notice. See [2] for an explanation in english

[1] https://autoriteitpersoonsgegevens.nl/sites/default/files/at... [2] https://www.iabeurope.eu/eucookielaws/nl/

TLDR: If you use the following code. You are fine to use GA without a notice under Dutch law.

ga('set', 'forceSSL', true); ga('set', 'anonymizeIp', true);

Thank you! This is really useful.

Be aware, this changes in 316 days, when the EU GDPR comes into force, and makes even for those cases opt-in required.

Opt-in via published policy or some silly explicit checkbox?

Opt-in via an explicit dialog, and, most importantly, you have to give the user the ability to select "no" and still use your website (in which case you aren’t allowed to do any tracking).

I don't know what firefox addon pages does (and i see they have a special arrangement) and am not taking sides but for IP at least there is an option partially scrub it before it gets to disk at Google.

https://support.google.com/analytics/answer/2763052?hl=en

Edit: what do we think?

> The general consensus is that normal GA tracking alone does not meet the standards to trigger either the EU or the stricter Dutch cookie notification requirements since they are using first-party cookies not tied to PII and don't follow you across sites

I don't know about following you across sites, but "PII" is a US legal term, so I highly doubt it's a determiner in applying EU law. GA may not collect PII under US law, but it does fall into EU data protection compliance.

The problem in the EU is the system of enforcement. EU directives require member states to legislate individually, and to enforce their own legislation individually. If that enforcement is deficient, the case can be taken to the ECJ on an individual basis (at possibly significant cost). This doesn't work. Which has motivated the creation of GDPR[0], but unfortunately this doesn't come into play until 2018

[0] https://en.wikipedia.org/wiki/GDPR

I'm not sure what the "Mozilla Legal" process is, but this thread[0] from 2012 seems to be a recurring source of authority on decision-making around this, from my reading of Bugzilla.

This is what tofumatt was referring to when closing this Github thread.

[0] https://groups.google.com/forum/#!msg/mozilla.governance/9IQ...