Privacy/Reviews/Telemetry/SSL Certificates And Errors
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: | David Chan |
Product Contact: | David Chan |
Privacy Contact: | Sid Stamm |
Document State: | [ON TRACK] |
Problem Statement
What problem will this solve?
- Does a significant percentage of our userbase visit sites with weak encryption e.g. < 512bit RSA, < SSLv3, weak ciphers?
- What kind of certificate related errors are our user's encountering?
Measurement to Collect
Describe the data that will be recorded and transmitted to our servers, and how it will be kept (as unique measurement or in aggregate) on our servers. The product or engineering contact should fill this out.
Privacy Considerations
This section will contain potential privacy risks and measures taken to minimize them. The privacy contact will fill this out.
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. The privacy contact will fill this out.
Alignment with Operating Principles
This section briefly describes how the measurement and technique lines up with our operating principles. The privacy contact will fill this out.'
- Transparency / No Surprises
- -
- Real Choice
- -
- Sensible Defaults
- -
- Limited Data
- -