Closed Bug 641537 Opened 11 years ago Closed 11 years ago

Update privacy policy to match changes from bug 635115

Categories

(www.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mossop, Assigned: afowler)

References

()

Details

After a recent review of the add-on update settings and the privacy policy we spotted that there was some incorrect information in the policy. Specifically for the Get Add-ons section we say:

"Firefox sends certain information to Mozilla, including the list of add-ons you have installed, Firefox version information, and your IP address. This communication only happens when the Get Add-ons area is open and can be turned off at any time by opting out of Automatic Updates from the Add-ons Manager"

The setting reference here does not turn this off however. We determined that we didn't want to provide any UI for turning this off either however users can turn off sending the list of installed add-ons using an about:config pref if they really wish, extensions.getAddons.cache.enabled, but the rest of the data is still sent to Get Add-ons in this case.

For "Add-on Information and Searches" we say:

"This communication includes the list of add-ons you have installed, Firefox version information, how long it took Firefox to start up, and your IP address. You can turn off this functionality at any time by opting out of Automatic Updates from the Add-ons Manager."

We felt that it was inconsistent to use the update setting to control this and so this too is now only controllable by the about:config pref extensions.getAddons.cache.enabled.

We should update the privacy policy for this.
I suggest we replace both occurrences of "opting out of Automatic Updates from the Add-ons Manager" with "following <a href="http://blog.mozilla.com/addons/how-to-opt-out-of-add-on-metadata-updates/">these instructions</a>"
Adding Alex from legal so he can address the privacy policy changes needed, if any.
Assignee: nobody → afowler
So we will not have an updated privacy policy online for the todays Fx4 launch?
Alex, what's the urgency level on this?
I think we should update the policy as soon as is feasibly possible. I like the idea of including a link to the blog post on how people can turn it off, using Justin's suggested text above.

In terms of process, in addition to posting the new, updated policy, we need to keep the current one as a "prior version." What I'm not sure of is how material this change is, such that we need to post the change to our newsgroup and mailing list. 

Can you guys advise me on how significant this change is?
We've been announcing the opt out information on the Add-ons Blog, first here:
http://blog.mozilla.com/addons/2011/02/10/add-on-metadata-start-up-time/

then here: http://blog.mozilla.com/addons/2011/02/23/correction-regarding-opting-out-of-add-on-metadata-pings/

I was planning to make the third post of the change once the policy had been updated. I don't think additional posts are necessary but that's up to you.
Firefox 5 is about to be released and this still hasn't been updated. Can we please update the privacy policy?
(In reply to comment #7)
> Firefox 5 is about to be released and this still hasn't been updated. Can we
> please update the privacy policy?

ccing rik so he can get this done today
I submitted a bug (Bug 664845) for a couple of other updates to the privacy policy. Can we coordinate these changes and get all three made at the same time?
Target Milestone: --- → 2.9
I'm currently at the webdev offsite so I can't really take this. A summary of the changes required would be nice.

I'll let James take care of this one.
Perhaps we should close this bug since I added this change to bug 664845. Any objections?
Target Milestone: 2.9 → 2.10
Sounds good.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Firefox policy looks good. Marking as verified fixed.
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.