Closed Bug 1854659 Opened 2 years ago Closed 2 years ago

Glean debug ping viewer: Handle users' privacy aspects

Categories

(Data Platform and Tools Graveyard :: Glean Platform, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aaggarwal, Assigned: aaggarwal)

References

Details

Attachments

(1 file)

Providing transparency to the app users on:

  1. What privacy policy does the app operate under (thanks to :chutten for reminding us about this) and
  2. How to disable data collection

Find out what needs to be done for Glean Debug Ping Viewer since it is accessible only to Mozilla employees (Mozilla LDAP since it's behind SSO)

Helpful Links:

  1. Mozilla's privacy policy
  2. Mozilla Web Properties Tracking Policy (although it is from 2017, if there is more up-to-date guidance then we should follow that)

Another question that we need to find answer for is: Do we have to be explicit to users about how to disable telemetry collection (by e.g. having a page in the app mentioning it or having it somewhere in the confluence page associated with Glean Debug Ping Viewer) or merely linking Mozilla's privacy policy is enough?

Summary: Figure out what needs to be documented in the context of privacy policy → Figure out what needs to be done in the context of privacy policy notice

(In reply to Abhishek from comment #1)

Another question that we need to find answer for is: Do we have to be explicit to users about how to disable telemetry collection (by e.g. having a page in the app mentioning it or having it somewhere in the confluence page associated with Glean Debug Ping Viewer) or merely linking Mozilla's privacy policy is enough?

This is the recommendation we got from Nneka Soyinka (nsoyinka@mozilla.com) in Legal team:

My recommendation then would be to include a link to the privacy notice, but be more transparent in other areas. Alternatives to adding another page in the app could be including it as part of the sign up experience (if there's a specific email that users will receive to get started) or if there is an accompanying Confluence page having a section there. I'm trying to strike a balance between what our employees might want and what we do (or don't do) externally with Firefox users. Since we don't have a separate page per se in the external context, I don't think you necessarily have to do that in this case - especially if the other options provided are a little easier.

Since we don't have a dedicated Confluence page for glean debug ping viewer and there is no dedicated signup experience linked to this application, I am proposing following to achieve strike a balance between what our employees might want and what we do (or don't do) externally with Firefox users:

  1. Adding a footer to the app and add a link to Mozilla's privacy policy (taking inspiration from https://telemetry.mozilla.org/ which is a public website),
  2. In the same footer, add one more line explaining how to disable data collection
  3. Updating project's Github documentation to explain how to disable data collection
Summary: Figure out what needs to be done in the context of privacy policy notice → Glean debug ping viewer: Handle users' privacy aspects
Assignee: nobody → aaggarwal
Status: NEW → ASSIGNED
Blocks: 1851458
No longer blocks: 1851458
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: