Privacy/Reviews/Telemetry/Default Browser Status: Difference between revisions
| Line 21: | Line 21: | ||
''Briefly state the problem to be solved by collecting this type of data: a question we have and how the answer can make our users' web experience better. The product or engineering contact should fill this out.'' | ''Briefly state the problem to be solved by collecting this type of data: a question we have and how the answer can make our users' web experience better. The product or engineering contact should fill this out.'' | ||
The | The Blocklist Ping (updates to browser including security updates and addon related notices) is sent once a day. | ||
For installations where Firefox is not the default, how often is Firefox used?: how many days will it take till they see security updates? | For installations where Firefox is not the default, how often is Firefox used?: how many days will it take till they see security updates? | ||
Revision as of 16:59, 7 September 2011
This page documents one type of data collected by telemetry: what is collected, the problem we seek to solve by collecting the data, and how we minimize any risks to users' privacy in deploying the measurement.
Status:
| Engineering Contact: | Taras Glek |
| Product Contact: | Chris Blizzard |
| Privacy Contact: | Sid Stamm |
| Document State: | [NEW] documenting |
Problem Statement
Briefly state the problem to be solved by collecting this type of data: a question we have and how the answer can make our users' web experience better. The product or engineering contact should fill this out.
The Blocklist Ping (updates to browser including security updates and addon related notices) is sent once a day. For installations where Firefox is not the default, how often is Firefox used?: how many days will it take till they see security updates?
Is the browser uptime for the 'non default' users long enough for Firefox to send the AMO/BU ping: if isn't the ping wont go through and they wont see the security update.
Is Firefox not the default on 'low hardware' installations e.g. installations with low memory. This might indicate that users with constrained hardware do not choose to use Firefox as their primary browser. Firefox could be improved to work across a variety of hardware profiles.
Measurement to Collect
Describe what type of measurement will be recorded and transmitted to our servers, and how it will be kept (as unique measurement or in aggregate) on our servers.
This measurement is a boolean (yes or no) describing whether or not the running instance of Firefox is the default browser on its host.
See bug 679938
Privacy Considerations
This section will contain potential privacy risks and measures taken to minimize them.
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.
Alignment with Operating Principles
This section briefly describes how the measurement and technique lines up with our operating principles'
- Transparency / No Surprises
- -
- Real Choice
- -
- Sensible Defaults
- -
- Limited Data
- -