1653098 - User Reads Pioneer Consent before clicking Join

Status: RESOLVED FIXED

(Firefox :: General, task, P1)

Description

[MarniePW [:marnie]]

Wireframes, page 3
Screen ID: 1
Annotation ID: A1a

As a user, I want to read the Pioneer Consent notice before I join, so that I understand what it entails.

A/C
User clicks the privacy notice link, we pop open the Pioneer Privacy Consent modal [S2]

• User sees the Accept (A2) and Cancel (A3/A3a) buttons
• If user cancels (A3/A3a) the modal closes
• If User accepts the policy, we mark them as Consented. We send the telemetry ping for their acceptance
  • This user has accepted the consent so if they click "Join/Enroll" they do not see the modal again

Comment 1

[Robert Helmer [:rhelmer]]

Attachment: Bug 1653098 - pre-enrollment consent dialog for Pioneer v2 r?mstriemer

Comment 2

[Robert Helmer [:rhelmer]]

(In reply to Marnie Pasciuto-Wood [:marnie] from comment #0)

Wireframes, page 3
Screen ID: 1
Annotation ID: A1a

As a user, I want to read the Pioneer Consent notice before I join, so that I understand what it entails.

A/C
User clicks the privacy notice link, we pop open the Pioneer Privacy Consent modal [S2]

• User sees the Accept (A2) and Cancel (A3/A3a) buttons
• If user cancels (A3/A3a) the modal closes
• If User accepts the policy, we mark them as Consented. We send the telemetry ping for their acceptance

I think we should defer all the Telemetry-related work to bug 1653145, that way we can batch it up and ask for data/privacy review in one patch.

• This user has accepted the consent so if they click "Join/Enroll" they do not see the modal again

Marnie, how important is this bit? Do we expect users to re-enroll like this? It's simpler to not have to store the state and just show the dialog every time.

Comment 3

[MarniePW [:marnie]]

Got it on the telemetry, that makes sense.

Good question re: the modal. I'll defer to @javaun, since I believe this was his story and I don't want to misspeak.

Comment 4

[Javaun Moradi [:javaun]]

Rob I think I can simplify this one for you. The original idea here is that both the core Pioneer add-on and the study add-ons are all just add-ons that collect data. Before we send code down to the user's machine (the add-on) or collect data they will have to accept a consent policy, and both situations should work the same way not just for technical simplicity, but also so the user has a consistent expectation.

The thinking on this one is that on each study (or the core panel) there is a full privacy policy the user must accept for joining.

• There would be a link to it because the user might want (or expect) to read it before they join. (they don't know we're going to give them a modal until they've done this a few times.)
• They also might want to go back and re-read after joining: "what did I sign up for again?"

The easiest thing here might be simply that anytime they click on the link, hide the "accept" button so they can't accept it here. They can read-only. And regardless of whether they've already seen the policy prior, we always show them a modal after clicking Join. They always must "accept" that modal right then.

Does this make it easier for you? I actually think it's better for users bc it requires consent right at the time of intent to join

Comment 6

[MarniePW [:marnie]]

[Tracking Requested - why for this release]:

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/39eaccc7889d
pre-enrollment consent dialog for Pioneer v2 r=mstriemer

Comment 8

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/39eaccc7889d