[Telemetry] New descriptive/warning text about Telemetry to Aurora and Nightly users

RESOLVED FIXED

Status

RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: gjimenez, Assigned: matej)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
Hi Matej, 

Telemetry will be enabled by default on Nightly and Aurora channels. Due to this, we need to notify nightly and aurora users that telemetry is enabled by default and notify them with what information is being collected and why.

This will be an in-product doorhanger notification on the first launch (user will see after a new installation or after the next update for existing users on these channels)

Since this is appearing in the in-product doorhanger we need to simplify the privacy language/notification (preferably single line or max of two lines). The doorhanger notification will also have two buttons: "OK" and "Learn More". 

The language provided by the privacy team can be found here: bug 701178 (desktop) & bug 702284 (mobile).

We will need a doorhanger copy for desktop and one for mobile. (they might be same copy but slightly shorter for mobile).

Lawrence, can you please provide char. limit for mobile?

I apologize for the urgent request, Would you be able to provide a copy to review by tomorrow? and hopefully we can finalize by Friday?

Thanks!

other related bugs:
bug 701182
bug 702284
bug 701178
bug 699806
(Reporter)

Comment 1

7 years ago
Created attachment 593465 [details]
in-product doorhanger

i cant find the previously telemetry door hanger, but here is another example of a doorhanger for your reference.
(In reply to Grace Jimenez :grace from comment #0)
> Lawrence, can you please provide char. limit for mobile?

I didn't get a strict char limit for mobile. We should work with Madhava to ensure that the experience of the prompt is what we want. In general, we don't have a lot of space to work with on mobile and there is currently no support for links in door hangars. (We'll need to use a button.)
(In reply to Grace Jimenez :grace from comment #1)
> i cant find the previously telemetry door hanger, but here is another
> example of a doorhanger for your reference.

We use the term "notification bar" for these guys, actually. "Door hanger" is the term used for things like the geolocation popup (that you see when visiting http://gavinsharp.com/tmp/geo.html ).

I'm a little confused by this bug - we don't have any plans in bug 699806 to add any extra notifications (doorhanger or otherwise), as far as I know. Bug 701182 added extra text to Firefox's about dialog, bug 702284 is adding extra text to Mobile's about page, and bug 701178 is about adding extra text to the mozilla.org web pages, and my understanding was that those were the extent of the changes we were making for enabling telemetry by default in Nightly/Aurora.
(In reply to Gavin Sharp (use gavin@gavinsharp.com for email) from comment #3)
> (In reply to Grace Jimenez :grace from comment #1)
> > i cant find the previously telemetry door hanger, but here is another
> > example of a doorhanger for your reference.
> 
> We use the term "notification bar" for these guys, actually. "Door hanger"
> is the term used for things like the geolocation popup (that you see when
> visiting http://gavinsharp.com/tmp/geo.html ).
> 
> I'm a little confused by this bug - we don't have any plans in bug 699806 to
> add any extra notifications (doorhanger or otherwise), as far as I know. 

These are changes we discussed last week with Privacy and Engagament in an effort to figure out the best way to move forward with some of the privacy team's concerns around the new opt-out policy of telemetry.  The bugs you referenced wouldn't have that info I don't think, but we're happy to sync with the PM team and the engineers on point for this so we're all on the same page.



Bug
> 701182 added extra text to Firefox's about dialog, bug 702284 is adding
> extra text to Mobile's about page, and bug 701178 is about adding extra text
> to the mozilla.org web pages, and my understanding was that those were the
> extent of the changes we were making for enabling telemetry by default in
> Nightly/Aurora.
(Assignee)

Comment 5

7 years ago
I recommend using the same text from bug 701182 for consistency:

$PRODUCTNAME is experimental and unstable. It automatically sends test information back to Mozilla to help make Firefox better.

Or, if we don't need the first line here:

$PRODUCTNAME automatically sends test information back to Mozilla to help make Firefox better.
This message is specifically about the collection of data. I don't think we need the first line. If we go with the second line the notification will look something like:

$PRODUCTNAME automatically sends test information back to Mozilla to help make Firefox better. OK Learn more

where 'OK' and 'Learn more' are buttons.

Madhava - Do you think this sentence will work on mobile? Do you need to see a mockup? Also, do you have a preference for the order of the buttons? 'OK' 'Learn more', 'Learn more' 'OK'

I was also thinking of using 'Dismiss' or somthing along those lines instead of 'OK' as we're not asking the user to opt-in. However, 'Dismiss' has many more chars than 'OK'.
Sid - Does "$PRODUCTNAME automatically sends test information back to Mozilla to help make Firefox better." work for privacy? Do we have an existing page that you want to link to with "Learn more"? (SUMO article?)
I would like to see information in the prompt that actually explains a little bit about the types of information being sent.  I'm willing to bet that very few people will click the "learn more" link, and that's not enough information for people to understand what kind of information Telemetry collects.

More about my bikeshedding: the problem here is that we don't know (1) if people understand what "test information" means (2) if people better understand any alternative or (3) how many people click "learn more".  Until we do, I'd rather err on the side of having categorical info in the prompt.  See also, bug 685373 and bug 699513.  We need to study user interactions and have some data to guide us about how much people read, understand, and are willing to click.
Rereading all of the referenced bugs in comment 8, bug 685373 settled on the string
 
"Will you help improve %1$S by sending anonymous information about performance, hardware characteristics, feature usage, and browser customizations to %2$S?"

However, there was a lot of discussion after the fact about simplifying the string and calling out the details in the privacy policy. Similarily, bug 699513 settled on the string

"Help improve %3 by sending anonymous usage information to Mozilla?"

Bug 702319 was opened to further work on the string for mobile. The latest proposal is

"Send info to Mozilla so that we can improve %s."

Sid, based on the existing string, it sounds like you're looking for a string like

"$PRODUCTNAME sends anonymous information about performance, hardware characteristics, feature usage, and browser customizations back to Mozilla to help improve Firefox."

This may cover issue (1) on desktop but is way too long for mobile. Issue (2) was planned to be covered by the Learn more link (details are now available via the SUMO article [1]). I was going to say that we could determine (3) by adding a Telemetry probe but that's kind of a chicken and egg problem. 

[1] https://support.mozilla.org/en-US/kb/how-can-i-help-submitting-performance-data
That's a good summary, Lawrence.  Thanks.  

Either way, someone is going to be unhappy with whatever string we use until we know whether people need categorical information in the string or not to make an educated decision or if they're fine with clicking a link.  Until we know this, I'd rather err on the side of more up-front information, but that's apparently not feasible for mobile.

So for now we need to align this new string with the other strings that are currently shipping, and then when we get around to studying the opt-in string effect (or someone finds an equivalent study done somewhere else) we can make a better educated decision about how to surface this to our users.
(In reply to Matej Novak [:matej] from comment #5)
> I recommend using the same text from bug 701182 for consistency:
> 
> $PRODUCTNAME is experimental and unstable. It automatically sends test
> information back to Mozilla to help make Firefox better.
> 
> Or, if we don't need the first line here:
> 
> $PRODUCTNAME automatically sends test information back to Mozilla to help
> make Firefox better.

Sid, for consistency I feel that I need to throw Matej's suggestion above back into the mix. This is the string that Tom worked on including in the about dialog (currently in product) in bug 701182.
I think priority one is that we convey the same message to all users of Telemetry.  This means we should have one consistent string if possible.

Priority two is that the string is informative enough that users can make an *informed* choice about whether or not to participate.

But according to what Tom says in bug 701182 comment 41, "Test information" is the choice of words for telemetry, so for consistency run with that.  I personally don't think it's informative enough, but if I'm the only one who feels this way, go for it.
I agree with what Sid stated in comment 12, that he has a concern that "Test information" is not informative enough. I caught up with Sid and Matej quickly. Here is a modified version of the message that I proposed in comment 9, which is based on the existing Telemetry opt-in message:

"$PRODUCTNAME sends information about performance, hardware, usage and customizations back to Mozilla to help improve Firefox."

I would like to propose that we go with this statement on desktop. The about dialogs should be updated to use the same language as the notification.

We will need to mock this up on mobile and iterate to come up with a message that meets the demands of notifying users about data collection and having a pleasant first run experience.
I am resolving this as fixed. We will go with the message in comment 13. Feel free to reopen if you have a concern.

I have opened bug 728340 to track the message for mobile.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.