Telemetry dashboard tracking and privacy 2012-06-11

Attendance: Lawrence Mandel, Taras Glek, David Asher, Alina Hua

• Small set won't be statistically meaningful
• Need to considering privacy implications, legal, etc.
  • Keep focus on user's best interest
• Can we solve this in another way?
  • We need tracking technology to tell how people actually use Telemetry
  • Would like to have features to make smarter decisions about displaying probes
  • Would like to know how other browser vendors use this information
    • Thought that this may be considered fair exchange for value
• Per user tracking would require opt-in tracking - ask for user consent
• Also requires a clear explanation about what data will be collected and what will be done with the data

• Summary 3 options:
  • Aggregate
    • Covered by existing privacy policy
    • Go ahead today with no roadblocks
  • Opt-in per user tracking
    • Requires community discussion
    • Need to draft opt-in statement
    • Requires privacy policy changes
  • Opt-in by default
    • Requires community discussion
    • Requires privacy policy changes

• Next steps
  • Speak to Jishnu and Stacy to explain
    • Privacy policy needs (different than policy for existing sites)
    • Opt-in for individualized tracking of X (be specific)
    • What are constraints that these analytics need to operate under (how implemented)?
    • Who gets access to the data - aggregate or individualized

[action] lmandel to follow up with e-mail