canmove, Confirmed users
1,537
edits
Privacy/Reviews/Telemetry/Encountered Plugin Types: Difference between revisions
Jump to navigation
Jump to search
Privacy/Reviews/Telemetry/Encountered Plugin Types (view source)
Revision as of 22:57, 18 August 2011
, 18 August 2011→Privacy Considerations
| Line 40: | Line 40: | ||
= Privacy Considerations = | = Privacy Considerations = | ||
''This section will contain potential privacy risks and measures taken to minimize them.'' | ''This section will contain potential privacy risks and measures taken to minimize them.'' | ||
=== Affiliation Disclosure === | |||
Some plug-ins are not very common (used for corporate internal site or for uncommon public sites). Learning that such an uncommon plug-in is instantiated could leak information about the users' relationships with these uncommon and potentially very specific sites. | |||
''Requirement'': We should avoid collection of information on the long tail of uncommon/infrequently used plug-ins. To do this, we should pre-define the set of plug-ins whose histogram data we want to collect. The top ten ''(?)'' should be chosen in advance, and only information about those plug-ins should be collected. | |||
''Recommendation'': If we cannot pre-define a set of plug-ins to investigate as required above, we should limit the data collected to the top four most commonly invoked plug-ins on each instance of Firefox. For example, if Bob's Firefox has ten plug-ins installed and six of them are invoked as he browses the web, telemetry should only report information about the four encountered most commonly by his install of Firefox. | |||
{{ResolutionBox|{{new|not yet considered}} }} | |||
== Consent and Privacy Policy Considerations == | == Consent and Privacy Policy Considerations == | ||
''This section contains notation of any changes to privacy policies or user opt-in/opt-out consent UX that is updated to include this measurement.'' | ''This section contains notation of any changes to privacy policies or user opt-in/opt-out consent UX that is updated to include this measurement.'' | ||
The privacy policy covering Telemetry already mentions usage statistics, covering this data type. The opt-in alludes to usage measurements, but doesn't call it out: | |||
Would you like to help improve %1$S by automatically reporting memory usage, | |||
performance, and responsiveness to %2$S? | |||
[http://mxr.mozilla.org/mozilla-central/source/browser/locales/en-US/chrome/browser/browser.properties#332 see browser.properties] | |||
''Requirement'': make it clear in the opt-in that we're collecting usage stats, not just memory usage stats. | |||
{{ResolutionBox|{{new|not yet considered}} }} | |||
=== Alignment with Operating Principles === | === Alignment with Operating Principles === | ||
''This section briefly describes how the measurement and technique lines up with our operating principles''' | ''This section briefly describes how the measurement and technique lines up with our operating principles''' | ||
; Transparency / No Surprises : - | ; Transparency / No Surprises : The opt-in dialog presented to users needs to obviously cover "usage" (see above) | ||
; Real Choice : - | ; Real Choice : This is collected by telemetry opt-in only. | ||
; Sensible Defaults : - | ; Sensible Defaults : Telemetry is opt-in. | ||
; Limited Data : | ; Limited Data : We should only collect version numbers that are relevant. | ||
''Recommendation'': Trim version strings to reduce version data to only what is absolutely necessary. | |||
{{ResolutionBox|{{new|not yet considered}} }} | |||