1687039 - Data Review Request for Fission subframe crash reporter

Status: RESOLVED FIXED

(Core :: DOM: Content Processes, task, P2)

Description

[Chris Peterson [:cpeterson]]

Data requester: Chris Peterson <[e-mail]> (Fission EPM)

Comment 1

[Chris Peterson [:cpeterson]]

Attachment: Fission data review request.txt

Requesting data review for Fission's new subframe crash reporter, as per our email conversation waaay back in November 2021 (Subject: "Data Privacy review for unsent crash report notification and Fission subframe crash reporter?").

Comment 2

[Chris H-C :chutten]

Comment on attachment 9197493 [details]
Fission data review request.txt

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. Crash reports are documented throughout Firefox and Mozilla's support sites like https://docs.telemetry.mozilla.org/datasets/other/socorro_crash/reference.html?highlight=socorro#socorro-crash-reports

Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection 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, Nika Layzell 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 4, Highly Sensitive.

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. (Privacy (Emily Litka) confirmed as much in an email thread)

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+, since Privacy (Emily Litka) confirmed that this is acceptable collection.

Comment 3

[Emily Litka]

please confirm that the UI hasn't changed since last discussing (i.e., still opt-in) and that that the relevant documentation is included here (https://firefox-source-docs.mozilla.org/toolkit/crashreporter/crashreporter/index.html). thanks!

Comment 4

[Chris Peterson [:cpeterson]]

(In reply to Emily Litka from comment #3)

please confirm that the UI hasn't changed since last discussing (i.e., still opt-in) and that that the relevant documentation is included here (https://firefox-source-docs.mozilla.org/toolkit/crashreporter/crashreporter/index.html). thanks!

We've made only one change to the UI of the Fission subframe crash reporter since I shared the early UI design with you: we are including a new "Learn more" link to a SUMO KB article about Firefox crashes:

https://support.mozilla.org/kb/firefox-crashes-troubleshoot-prevent-and-get-help

Fission subframe crash reporting is still opt-in by default and (unlike the about:crashcontent reporter UI for tab crashes) does NOT include an "automatically submit reports without asking" checkbox.

Comment 5

[Chris Peterson [:cpeterson]]

Do you need any additional information? Or can we resolve this bug report as "fixed"?

Comment 6

[Emily Litka]

Ok, sounds good to me. Thanks so much! Approved.