1888925 - Add installation ID Glean event in Firefox Bridge registration idle task

Status: NEW

(Firefox :: Shell Integration, enhancement, P3)

Comment 1

[Nipun Shukla]

Attachment: Bug 1888925 - Added Glean metric for retrieving Firefox Bridge install id r=mhughes,nalexander

Comment 2

[Nipun Shukla]

Attachment: 1888925-data-review.md

Hi, I've attached the data review request. Please let me know if you have any further questions.

Comment 3

[Chris H-C :chutten]

Comment on attachment 9394273 [details]
1888925-data-review.md

New identifiers are cases of special concern for data collection review, so let's take a close look. This id will be sent alongside the Glean client_id so has the same reach characteristics. It also extends the reach of Glean's client_id into the space of these extensions. Presumably these extensions will have their own data collections that will then be reachable, but this is nothing new under the sun. It's the same as adding a component to Firefox and instrumenting it, really.

Except.

Except that this is per-install. That's something new. The client_id-reachable data in every profile that installs this extension will now be reachable from every other one.

Has this undergone discussion or review with Trust or Privacy? I think you're proposing a novel linking across profiles and browsers here. It's probably all fine and dandy, and not dissimilar from other collections that are being designed and proposed, but identifiers are, as I said, cases of special concern.

Comment 4

[Nipun Shukla]

We've had a separate data review with some discussion about other components over here: https://docs.google.com/document/d/1XC5qQnDECjKRpAeEiChuq4OfbPrrSdjOjF2zj2xhvHo/edit. Is this what you were looking for or is there a separate process that I need to go through?

Comment 5

[Chris H-C :chutten]

(In reply to Nipun Shukla from comment #4)

We've had a separate data review with some discussion about other components over here: https://docs.google.com/document/d/1XC5qQnDECjKRpAeEiChuq4OfbPrrSdjOjF2zj2xhvHo/edit. Is this what you were looking for or is there a separate process that I need to go through?

The process for reviewing sensitive data collection is the, descriptively-named, Sensitive Data Collection Review Process. I see Martin Thompson in that doc, and he's on the mailing list for sensitive reviews, so maybe a lot of the necessary conversation has already been had?

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:nshukla, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.

Comment 7

[Nipun Shukla]

Awaiting sensitive data review completion before landing.

Comment 8

[Robin Steuber (she/her) [:bytesized]]

Is this still waiting on the data review?

Comment 9

[Nipun Shukla]

I believe that Product went back to thinking over different ways to collect the data we need. The project has been put on hold for now so it may be some time before this is worked on more.

Comment 10

[Robin Steuber (she/her) [:bytesized]]

Marking this as unassigned since no one seems to be working on it at the moment.