Closed Bug 974032 Opened 11 years ago Closed 11 years ago

Privacy-Policy Review: Firefox Telemetry Experiments (rev 1)

Categories

(Privacy Graveyard :: Product Review, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: benjamin, Assigned: ahua)

References

Details

Initial Questions: Project/Feature Name: Firefox Telemetry Experiments (rev 1) Tracking ID:973990 Description: This is the first form of variation testing that we're going to deploy to our Firefox audience by default that doesn't require explicit opt-in. Additional Information: PRD: https://docs.google.com/document/d/1GPpkIcWFNkZmXONjqBCc05U3uocOD-1jpZHdAsR0v1k/edit?usp=sharing Key Initiative: Firefox Desktop Release Date: 2014-03-17 Project Status: development Mozilla Data: Yes Mozilla Related: Firefox desktop, Firefox Health Report, Telemetry Separate Party: No Is there a privacy policy for this new feature/product?: This should be covered by the Telemetry privacy policy What assistance do you need from the privacy team (if any)?: As already discussed, proper sampling requires the beta user population and so we want to enable Telemetry by default for the beta audience and also include telemetry data in the FHR data format.
Group: mozilla-corporation-confidential
Assignee: smartin → ahua
Hi Ben - I've assigned to Alina and copied the members of the Privacy Council. This would be a good one for the Privacy Council (formerly Privacy Friends) to review.
This project is moving fast, setting it to P1
Priority: -- → P1
@bsmedberg mentioned in irc that proposals on this topic are happening in the dev-privacy email list and the conversation has been occurring already with afowler, ahua, jmenon
Hi Ben - Can you provide an update on the status of this?
Flags: needinfo?(benjamin)
Comment 3 has it right: the proposals were sent to mozilla.dev.privacy (and cc'ed to a bunch of other lists) over the past week and jishnu/gpiper are doing legal review to see exactly what changes are necessary in the Firefox privacy policy.
Flags: needinfo?(benjamin)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.