7
edits
Data Collection: Difference between revisions
Jump to navigation
Jump to search
Updated Data Steward names and added additional clarification to Data Steward's role with sensitive review process.
m (→Create documentation and request review: name typo) |
(Updated Data Steward names and added additional clarification to Data Steward's role with sensitive review process.) |
||
| Line 12: | Line 12: | ||
Data Stewards: | Data Stewards: | ||
* [https://people.mozilla.org/p/jhirsch Jared Hirsch] | * [https://people.mozilla.org/p/jhirsch Jared Hirsch] | ||
* [https://people.mozilla.org/p/TheOne Andreas Wagner] | * [https://people.mozilla.org/p/TheOne Andreas Wagner] | ||
| Line 27: | Line 26: | ||
* [https://people.mozilla.org/p/groovecoder Luke Crouch] | * [https://people.mozilla.org/p/groovecoder Luke Crouch] | ||
Data stewards come from a variety of teams within Mozilla, including data science, Firefox engineering, mobile products, Pocket | Data stewards come from a variety of teams within Mozilla, including data science, Firefox engineering, mobile products, Pocket, AMO, and Thunderbird. You are welcome to tag any steward for any collection request, without respect to the nature of your collection. | ||
Contact Us on Matrix https://chat.mozilla.org/#/room/#data-stewards:mozilla.org | Contact Us on Matrix https://chat.mozilla.org/#/room/#data-stewards:mozilla.org | ||
| Line 46: | Line 45: | ||
* Data steward - the person who ensures the data collection process is followed and that requested data complies with Mozilla policies | * Data steward - the person who ensures the data collection process is followed and that requested data complies with Mozilla policies | ||
In some cases a data steward may escalate concerns to the Trust and Legal teams. They are the teams responsible for defining | In some cases a data steward may escalate concerns to the Trust and Legal teams. They are the teams responsible for defining data collection policies and can field questions about internal policy and laws governing user privacy. | ||
Mozilla always strives to make data reviews public. However, there are sometimes limited sets of circumstances when we may conduct our reviews in a private bug; for example, a service is part of an agreement where the partnership is not yet public. These reviews will be made public once the actual data collection begins. | Mozilla always strives to make data reviews public. However, there are sometimes limited sets of circumstances when we may conduct our reviews in a private bug; for example, a service is part of an agreement where the partnership is not yet public. These reviews will be made public once the actual data collection begins. | ||
| Line 110: | Line 109: | ||
=== Determine if you need to follow this process === | === Determine if you need to follow this process === | ||
For any data collection that is classified as category 3 or 4 (described below) – including in pre-release channels and experiments – we require additional review to be performed and an announcement to a mailing list. The reason for this is that while our privacy policies describe what we can do without additional user notice, this is an upper bound; even for collection which fits within the policy, we need to determine whether that collection is appropriate and conforms to our overall commitment to privacy and minimization. | For any data collection that is classified as category 3 or 4 (described below) – including in pre-release channels and experiments – we require additional review to be performed and an announcement to a mailing list. The reason for this is that while our privacy policies describe what we can do without additional user notice, this is an upper bound; even for collection which fits within the policy, we need to determine whether that collection is appropriate and conforms to our overall commitment to privacy and minimization. While a Data Steward may provide assistance with escalating a request or submitting it through the sensitive data review process, they are not part of the actual review of escalations. That is handled by a separate cross-functional team. | ||
=== Create documentation and request review=== | === Create documentation and request review=== | ||