Instructions: Data Stewards will review a request for data collection and endorse responses to each question. If the request does not provide answers to questions, reviewers give an r- and point to the questions that can’t be answered.
- Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
Yes: Schema is available here (link to be updated after PR is merged): mozilla-services/mozilla-pipeline-schemas#381
- Is there a control mechanism that allows the user to turn the data collection on and off? For the initial internal alpha, there will not be a mechanism for turning off data collection. We will ensure that we are transparent with what data is being collected for consent purposes for our internal alpha testers BEFORE they download/install our add-on.
A data collection control will be added in Settings before we release publically.
-
If the request is for permanent data collection, is there someone who will monitor the data over time? Ian Bicking and @harraton will be monitoring the data.
-
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 3.
-
Is the data collection request for default-on or default-off? For the internal alpha, the request is for default-on.
-
Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)? No new identifiers are being created.
-
Is the data collection covered by the existing Firefox privacy notice?
-
Does there need to be a check-in in the future to determine whether to renew the data? (Yes/No) (If yes, set a todo reminder or file a bug if appropriate)**
Yes, in 6 months.
- Does the data collection use a third-party collection tool? No