Closed Bug 1570738 Opened 8 months ago Closed 8 months ago
Prevent usage of eval() in any context in the Parent Process
Status: NEW → ASSIGNED
Priority: -- → P2
Type: defect → task
Comment on attachment 9082418 [details] data-review.txt ( ni?ckerschb to clarify that they're fine with being nominated to permanently monitor this data ) DATA COLLECTION REVIEW RESPONSE: Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate? Yes. This collection is Telemetry so is documented in its definitions file [Events.yaml](https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/telemetry/Events.yaml) and the [Probe Dictionary](https://telemetry.mozilla.org/probe-dictionary/). Is there a control mechanism that allows the user to turn the data collection on and off? Yes. This collection is Telemetry so can be controlled through Firefox's Preferences. If the request is for permanent data collection, is there someone who will monitor the data over time? Yes, ckershub is responsible. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 1, Technical. Is the data collection request for default-on or default-off? Default on for all channels. Does the instrumentation include the addition of any new identifiers? No. Is the data collection covered by the existing Firefox privacy notice? Yes. Does there need to be a check-in in the future to determine whether to renew the data? No. This collection is permanent. --- Result: datareview+
Attachment #9082418 - Flags: data-review?(chutten) → data-review+
You need to log in before you can comment on or make changes to this bug.