963816 - update privacy center

Status: VERIFIED FIXED

(www.mozilla.org :: Pages & Content, defect)

Description

[Jennifer Bertsch [:jbertsch]]

The Legal team has asked us to update the privacy center (http://www.mozilla.org/privacy/) as follows (https://docs.google.com/a/mozilla.com/presentation/d/1l2JRe_X6uTlnsoDzYZatpN_rVHkn6iZyjpPoGzY0Tgk/edit#slide=id.g29b8722ab_050):

1.  On http://www.mozilla.org/privacy/, replace "Our Principles, Your Information, Your Choices and When We Share Your Information" in center content well with new Mozilla Privacy Policy (to be attached)

2.  Make new page for new "Our principles" doc at privacy/principles (to be attached) and link to it from the right hand navigation area above Product Privacy Policies(Notices)

3.  In the right hand navigation:  Update Product Privacy Policies to read Product Privacy Notices and:
a.  migrate Fx desktop policy to bedrock
b.  make all privacy policies on bedrock responsive

4.  Keep Get Involved text as is

5.  Update Contact section to read:
(1) should say “Contact Mozilla” (2) address should be: 2 Harrison St,
San Francisco, CA 94105
-  current email address receives too much spam
- change to new email [e.g. yourprivacyis#1!@mozilla.com] which redirects to legal distro list

6.  Use Fx OS format for Firefox and Mozilla privacy policies, but improve "desktop" formatting to look less mobile

7.  Edit text on Fx OS privacy policy to read:
Mozilla cares about your Privacy.  When Firefox OS sends information to us, our Mozilla Privacy Policy describes how we handle that information.
(see slide 12)

8.  Talk to Steven Garrity about questions on slide 13

Comment 1

[Jennifer Bertsch [:jbertsch]]

Attachment: Mozilla Privacy Policy

Comment 2

[Jennifer Bertsch [:jbertsch]]

Attachment: Our Principles

Comment 3

[Kohei Yoshino [:kohei]]

(In reply to Jennifer Bertsch [:jbertsch] from comment #0)
> 6.  Use Fx OS format for Firefox and Mozilla privacy policies, but improve
> "desktop" formatting to look less mobile

The content based on the new format ("Things you should know") will be provided for the Firefox and Mozilla Privacy Policies?

Comment 4

[Kohei Yoshino [:kohei]]

Attachment: Firefox OS Privacy page mockup

I've made a mockup of the Firefox OS Privacy page to make it looking better on desktop. The graphic is from http://www.mozilla.org/en-US/about/partnerships/

Comment 5

[Kohei Yoshino [:kohei]]

The current Firefox OS Privacy page is
http://www.mozilla.org/en-US/privacy/policies/firefox-os/

Comment 6

[Jennifer Bertsch [:jbertsch]]

(In reply to Kohei Yoshino [:kohei] from comment #3)
> (In reply to Jennifer Bertsch [:jbertsch] from comment #0)
> > 6.  Use Fx OS format for Firefox and Mozilla privacy policies, but improve
> > "desktop" formatting to look less mobile
> 
> The content based on the new format ("Things you should know") will be
> provided for the Firefox and Mozilla Privacy Policies?

Hi Kohei-

Legal will not be providing "Things you should know" text for the Firefox and Mozilla privacy policies.  I think they just like the style of the Fx OS page (http://www.mozilla.org/en-US/privacy/policies/firefox-os/) vs the Mozilla websites (http://www.mozilla.org/en-US/privacy/policies/websites/) page.  So they are asking us to style the Mozilla websites, Mozilla, and Firefox (desktop and Android) privacy policies more like the Fx OS one for mobile and then make them all prettier for desktop (and of course, still responsive).  

Does that make sense?

Thx,
Jen

Thx,
Jen

Comment 7

[Kohei Yoshino [:kohei]]

Okay, so we need a pretty design with the product logo anyway. My attachment 8366048 [details] could be a solution.

I still have a question on the Firefox Privacy Policy.
Looks like there's a new text on Bedrock:
https://github.com/mozilla/bedrock/blob/master/bedrock/privacy/templates/privacy/firefox.html
Will it be replacing the current policy?
http://www.mozilla.org/en-US/legal/privacy/firefox.html

Comment 8

[Jennifer Bertsch [:jbertsch]]

Hi Kohei-

We are probably going more for "clean" than "pretty."

I'll ping Mika here in the bug to clarify which Firefox privacy policy we should use, the one in github:

https://github.com/mozilla/bedrock/blob/master/bedrock/privacy/templates/privacy/firefox.html
or the one on mozilla.org 
http://www.mozilla.org/en-US/legal/privacy/firefox.html

Thanks,
Jen

Comment 9

[Mika]

(In reply to Jennifer Bertsch [:jbertsch] from comment #8)

> I'll ping Mika here in the bug to clarify which Firefox privacy policy we
> should use, the one in github:
> 
> https://github.com/mozilla/bedrock/blob/master/bedrock/privacy/templates/
> privacy/firefox.html
> or the one on mozilla.org 
> http://www.mozilla.org/en-US/legal/privacy/firefox.html


Hi Jen and Kohei,

Good question. The Privacy and Legal teams actually worked together recently to update the Firefox Browser policy and make it shorter.  The updated copy is located at: https://mozilla.box.com/s/39i9331hlexg407c5n0b

This would replace both the Github and the mozilla.org versions.  

Geoff Piper (he's another product attorney in MTV office) worked on this with me and Alina.  Any of us can answer questions, if you have any, on the format and copy of the new updated privacy notice.

Thanks,
Mika

Comment 10

[Jennifer Bertsch [:jbertsch]]

Thanks so much for the quick reply, Mika!

Kohei - I'll download the file from Box and upload it here for you.

Sgarrity -  Please note there's a new Fx browser privacy policy that Kohei will build on Bedrock.  We don't need to migrate http://www.mozilla.com/en-US/legal/privacy/firefox.html as part of 960689

Comment 11

[Jennifer Bertsch [:jbertsch]]

Attachment: Firefox Privacy Notice

Comment 12

[Kohei Yoshino [:kohei]]

jbertsch: Thanks for sharing the doc!

sgarrity: I'm migrating all files under /legal/privacy/

Comment 13

[Mika]

I forgot to mention, if you can put the updated copy that I included above in a gitbug repo, we can make sure to treat that as the "Master" to make future edits to (Geoff and I both have github accounts so we can make the changes directly and submit a pull request).  Also, this can be used as the "Master" from which the localization team can do translations from.  Peiying Mo helped me with the translations for other legal documents.  

Thanks,
Mika

Comment 14

[Kohei Yoshino [:kohei]]

Attachment: screenshot, landing page

Comment 15

[Kohei Yoshino [:kohei]]

Attachment: screnshot, principles page

Comment 16

[Kohei Yoshino [:kohei]]

Attachment: screnshot, Firefox Browser Privacy Notice page

Comment 17

[Kohei Yoshino [:kohei]]

Please take a look at some screenshots I've attached. It's almost done, and it works on mobile too.

Questions: there are two placeholders say "See <add link> to learn more about the usage statistics collected" in the Firefox Notice doc. Is this the URL?
https://support.mozilla.org/en-US/kb/send-performance-data-improve-firefox

There's the Privacy Principles section on the right side of the page, I think a short summary could be added here. Mika, could you write something for this part ("Lorem ipsum dolor sit amet" in the screenshot)?

Comment 18

[Kohei Yoshino [:kohei]]

Attachment: Pull Request on GitHub

Comment 19

[Kohei Yoshino [:kohei]]

On the Firefox OS Privacy page, I have replaced the Mozilla Privacy Policy and Contact content with simple links to the landing page. (The slide 13)

Comment 20

[Kohei Yoshino [:kohei]]

Attachment: screenshot, Firefox OS Privacy page

Comment 21

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #17)
> Please take a look at some screenshots I've attached. It's almost done, and
> it works on mobile too.
> 
> Questions: there are two placeholders say "See <add link> to learn more
> about the usage statistics collected" in the Firefox Notice doc. Is this the
> URL?
> https://support.mozilla.org/en-US/kb/send-performance-data-improve-firefox

Yes, this link is good.

> There's the Privacy Principles section on the right side of the page, I
> think a short summary could be added here. Mika, could you write something
> for this part ("Lorem ipsum dolor sit amet" in the screenshot)?

You can use this: "Mozilla is an open source project with a mission to improve your internet experience.  This is a driving force behind our privacy practices. Read More."

For the blurb underneath the right hand section called "Our Product Privacy Notices" you can change it to say: "We created short and clear Privacy Notices to describe how each of our products and services receives, shares, and uses data and what your choices are.  Learn more:"

Comment 22

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #14)
> Created attachment 8366936 [details]
> screenshot, landing page

This looks great.  Can you delete the word "Product" on the right hand side where it says "Our Product Privacy Notices".  So the final copy will say "Our Privacy Notices"

Comment 23

[Mika]

Hi Kohei, is there a link to a staged server? I have to share with the legal team to get authorization before it's pushed live.  They may have some final edits also.

Thanks very much,
Mika

Comment 24

[Kohei Yoshino [:kohei]]

(In reply to Mika from comment #21)
> > https://support.mozilla.org/en-US/kb/send-performance-data-improve-firefox
> 
> Yes, this link is good.
> 
> > There's the Privacy Principles section on the right side of the page, I
> > think a short summary could be added here. Mika, could you write something
> > for this part ("Lorem ipsum dolor sit amet" in the screenshot)?
> 
> You can use this: "Mozilla is an open source project with a mission to
> improve your internet experience.  This is a driving force behind our
> privacy practices. Read More."
> 
> For the blurb underneath the right hand section called "Our Product Privacy
> Notices" you can change it to say: "We created short and clear Privacy
> Notices to describe how each of our products and services receives, shares,
> and uses data and what your choices are.  Learn more:"

Great. Will use those.

(In reply to Mika from comment #22)
> This looks great.  Can you delete the word "Product" on the right hand side
> where it says "Our Product Privacy Notices".  So the final copy will say
> "Our Privacy Notices"

Got it.

(In reply to Mika from comment #23)
> Hi Kohei, is there a link to a staged server? I have to share with the legal
> team to get authorization before it's pushed live.  They may have some final
> edits also.

Will ask someone to push the new pages to a staged server.

Comment 25

[Kohei Yoshino [:kohei]]

Attachment: screenshot, landing page with updated blurbs

Comment 27

[Kohei Yoshino [:kohei]]

Mika: the original request included a change to the email address to avoid spams. Do you have a new address that can be replaced with?

> -  current email address receives too much spam
> - change to new email [e.g. yourprivacyis#1!@mozilla.com]
> which redirects to legal distro list

Comment 28

[Kohei Yoshino [:kohei]]

(Forgot to check needinfo)

Comment 29

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #27)
> Mika: the original request included a change to the email address to avoid
> spams. Do you have a new address that can be replaced with?
> 
> > -  current email address receives too much spam
> > - change to new email [e.g. yourprivacyis#1!@mozilla.com]
> > which redirects to legal distro list

I don't know much about naming conventions.  How about the one I suggested? yourprivacyis#1!@mozilla.com 
It would be great if the emails went there.  On the backend, a few of us on the legal/privacy teams can take turns checking the account.

Comment 30

[Mika]

Hi Kohei and Jen, 

Question for you.  Before Matt Basta left Mozilla, he worked with me and Peiying to put our Marketplace legal documentation in GitHub so that legal could directly make any changes and submit a pull request (instead of legal filing a bug and attaching word docs for developers to go in and make the changes).  Peiying from localization then worked out a system with a translation vendor so the vendor could go into github and make translations easily (legal translations are done by a vendor, and the community reviews the final work).

Is it possible to create a similar system for the privacy site?  I'm not sure where the source documents are right now.  But it would be cool to create a process that will be efficient for both webdev and localization.  

Let me know.  We can have a quick meeting with Peiying next week since she's been very involved with this.

Thanks!
Mika

Comment 31

[Kohei Yoshino [:kohei]]

(In reply to Mika from comment #29)
> I don't know much about naming conventions.  How about the one I suggested?
> yourprivacyis#1!@mozilla.com 
> It would be great if the emails went there.  On the backend, a few of us on
> the legal/privacy teams can take turns checking the account.

You may need to ask IT about it :)

(In reply to Mika from comment #30)
> Question for you.  Before Matt Basta left Mozilla, he worked with me and
> Peiying to put our Marketplace legal documentation in GitHub so that legal
> could directly make any changes and submit a pull request (instead of legal
> filing a bug and attaching word docs for developers to go in and make the
> changes).  Peiying from localization then worked out a system with a
> translation vendor so the vendor could go into github and make translations
> easily (legal translations are done by a vendor, and the community reviews
> the final work).
> 
> Is it possible to create a similar system for the privacy site?  I'm not
> sure where the source documents are right now.  But it would be cool to
> create a process that will be efficient for both webdev and localization.  

I could find the Marketplace legal doc at
https://github.com/mozilla/zamboni/tree/master/media/docs/dev-agreement

The Mozilla Privacy Policy and Firefox Privacy Notice will go under
https://github.com/mozilla/bedrock/tree/master/bedrock/privacy/templates/privacy

Currently the translations of mozilla.org are *not* on GitHub but on another Subversion repository. But yes, it would be very nice if legal and vendor could maintain docs on GitHub. I'll ask the team if it's possible.

Comment 32

[Kohei Yoshino [:kohei]]

Attachment: screnshot, principles page

Adjusted the layout of the Privacy Principles page.

Comment 33

[Mika]

Can you send me the URL to the staged server? Thanks! I need to share with the team for review :)

Comment 34

[Mika]

Can you add a section called "Cookies and Analytics" on the right hand side, below the "Our Privacy Notices" section and above the "Get Involved" section. 

The blurb is: We use online data tools to improve our products, services, and communications.  To learn about how this works and what your choices are, click here.   

The text is available at this link (let me know if you can't access): https://mozilla.box.com/s/2pkyfs5ka3cwa5mv46k1

Comment 35

[Kohei Yoshino [:kohei]]

(In reply to Mika from comment #34)
> The text is available at this link (let me know if you can't access):
> https://mozilla.box.com/s/2pkyfs5ka3cwa5mv46k1

Got the text. I'll add that section and ask folks to prepare a staging server.

Comment 36

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #35)
> (In reply to Mika from comment #34)
> > The text is available at this link (let me know if you can't access):
> > https://mozilla.box.com/s/2pkyfs5ka3cwa5mv46k1
> 
> Got the text. I'll add that section and ask folks to prepare a staging
> server.

Many thanks!

Comment 37

[Mika]

The text for the updated "Mozilla Websites" Privacy Notice is at this link: https://mozilla.box.com/s/tc2jyb0huylyjz8ismq8

Can you add the github link here so I can make any changes if needed? Thanks so much.

Comment 38

[Mike Alexis [:malexis]]

Updates ready for review:
https://www-demo1.allizom.org/en-US/privacy/

Comment 39

[Jennifer Bertsch [:jbertsch]]

Hi John-

Could you or someone from your team please review from a brand/design point of view?

https://www-demo1.allizom.org/en-US/privacy/

Thx,
Jen

Comment 40

[Kohei Yoshino [:kohei]]

Updated my pull request with the following changes:

* Moved the docs to external files for easier update by legal (Comment 30)
* Added the Cookies & Online Data Tools (Comment 34)
* Updated the Websites Privacy Notice (Comment 37)
* Removed the old Firefox Privacy Policies (Bug 960689)

Asked :jpetto on IRC to update the demo1 server.

Comment 41

[John Slater]

From a design point of view, it looks to be consistent with the Sandstone style, etc so no big worries there. Is there any info you can share about what the goal of making these changes is? What problem are we trying to solve?

And how does this page fit with the more marketing-friendly one we created for privacy day last month? Seems like we should at least be linking to it here.

To sum up, I guess my questions are more about content than design.

Comment 43

[Jennifer Bertsch [:jbertsch]]

Hi John-

The changes were requested by Mika and the Legal team.  Primarily, they wanted the following:
1.  the main Mozilla Privacy policy front and center on this landing page vs privacy principles that were featured there previously (and can still be seen in prod)

2.  some text updates

3.  improved formatting for mobile and desktop viewing

Thx,
Jen

Comment 44

[Jennifer Bertsch [:jbertsch]]

Hi Mika-

What do you think about adding a link to our "Mozilla puts your privacy first" landing page (http://www.mozilla.org/en-US/privacy/you/) from the privacy policy landing page (https://www-demo1.allizom.org/en-US/privacy/)?

Also, what is your timeline for providing final feedback?

Thx,
Jen

Comment 45

[Jennifer Bertsch [:jbertsch]]

Hi Kohei-

Could you please add one additional line of spacing above each sub header within the privacy policy on https://www-demo1.allizom.org/en-US/privacy/?

Thx,
Jen

Comment 46

[Jennifer Bertsch [:jbertsch]]

Also, Kohei, I'm thinking:

1.  All the text should default to be open/expanded for desktop users on this page https://www-demo1.allizom.org/en-US/privacy/firefox/

2.  Same here  https://www-demo1.allizom.org/en-US/privacy/firefox-os/ - text defaults to open/expanded for desktop users

John S:  could you please confirm the logo usage is correct on each of these pages?

Comment 47

[Mika]

I summed up the feedback into this deck: https://docs.google.com/presentation/d/1tHqeS-0C1SNBuq3p4n6llbGP9QEblKVhdB--iqJnmx0/edit?usp=sharing
 (open to anyone with link). 

Everything is okay to start except for the last 3 slides. Jishnu is reviewing the final copy of the privacy policy and privacy notices (which the last 3 slides discuss).  Is it better for Jishnu and I to make the copy changes in github, or for you to do it?  I thought we could make edits to the updated documents at this link, but it seems I have the wrong link?: https://github.com/mozilla/bedrock/tree/master/bedrock/privacy/templates/privacy (are they somewhere else?)

If possible, can you move them to: https://github.com/mozilla/legal-docs so that we can directly update the legal documents? I think this might save time between our teams, but I am open to feedback.

Comment 48

[Mika]

(In reply to Jennifer Bertsch [:jbertsch] from comment #44)
> Hi Mika-
> 
> What do you think about adding a link to our "Mozilla puts your privacy
> first" landing page (http://www.mozilla.org/en-US/privacy/you/) from the
> privacy policy landing page (https://www-demo1.allizom.org/en-US/privacy/)?

Let's save this for v2 of the privacy revamp.  There are product changes that will happen over the next 3 months that will require us to come back to this page to remove & add product notices.  

Jishnu's thought is that we should go live with v1 as soon as possible (that includes the last round of edits I just posted).  The goal of v1 is to get the proper legal documents out to the public, in mobile format, and with the major products in the new format.

We can do v2 in a few months.  The goal of v2 will be to include one line descriptions of the products, ways to engage (that could include link in proper place to the landing page), and a fuller set of updated privacy notices (there are products missing from the list now).  

Does that sound okay?

Comment 49

[Kohei Yoshino [:kohei]]

Okay, I'm working on it.

Comment 50

[Mika]

Feedback from Pete Scanlon is that only the community uses the Dino icon.  Please remove it as the logo associated with the "Mozilla websites" Product Notice.  You can check with John Slater if there is a more appropriate logo, otherwise, it's fine if there is no logo.  Thanks!

Comment 51

[Kohei Yoshino [:kohei]]

Mika: Can I get access to the updated Firefox Privacy Notice on Box?
https://mozilla.box.com/s/r2zj8khsqcqvwkvdiphj

I've got the Mozilla Privacy Policy and Websites Privacy Notice. Thanks!

Comment 52

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #51)
> Mika: Can I get access to the updated Firefox Privacy Notice on Box?
> https://mozilla.box.com/s/r2zj8khsqcqvwkvdiphj
> 
> I've got the Mozilla Privacy Policy and Websites Privacy Notice. Thanks!

I'm waiting for Jishnu and Geoff to update the copy on those notices.  Can you post the github links so they can make any copy changes directly?

Comment 53

[Kohei Yoshino [:kohei]]

Got it. I'll send a pull request to https://github.com/mozilla/legal-docs to add the current version of the privacy notices.

Comment 54

[Jennifer Bertsch [:jbertsch]]

Hi Kohei-

I spoke with John about the dino.  Let's replace it with the Mozilla M - like in the favicon.

Thx,
Jen

Comment 55

[Kohei Yoshino [:kohei]]

Attachment: Pull Request to add the docs to github.com/mozilla/legal-docs

Comment 56

[John Slater]

> Feedback from Pete Scanlon is that only the community uses the Dino icon. 
> Please remove it as the logo associated with the "Mozilla websites" Product
> Notice.  You can check with John Slater if there is a more appropriate logo,
> otherwise, it's fine if there is no logo.  Thanks!

Summing up various recent conversations in the bug, email, etc:
- replace dino with M
- remove Sync, Test Pilot and Thunderbird
- this will require final approval by Pete, but for now would recommend changing Firefox to Firefox Browser and continuing to use the logo as the symbol for both it and Firefox OS.

Comment 57

[Kohei Yoshino [:kohei]]

Attachment: screenshot, landing page

Thanks :jslater, here's a screenshot of the updated landing page. I'll finish the code and revise my pull request tomorrow.

Comment 58

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #55)
> Created attachment 8378816 [details] [review]
> Pull Request to add the docs to github.com/mozilla/legal-docs

Thanks, Kohei. Is the Facebook Privacy Information link connected to something? I'll figure out where it should go on the revamped webpage.

For the third party stuff, that link can be deleted. 

For the historical Firefox Browser policies, is it possible to the title "Outdated Policies" be linked to a new page, and on that page, is where all the links appear?  That will look better and we can put all outdated policies from other products on the same page.

Thanks!
Mika

Comment 59

[Kohei Yoshino [:kohei]]

(In reply to Mika from comment #58)
> Thanks, Kohei. Is the Facebook Privacy Information link connected to
> something? I'll figure out where it should go on the revamped webpage.

The Facebook Privacy Info has been under the /privacy/ directory and it looks like a standalone page which is shown in https://www.facebook.com/Firefox/app_500891979928786

We have to port the current page to the new Bedrock platform anyway.

> For the third party stuff, that link can be deleted. 

This page has also been under /privacy/. Will remove it.

> For the historical Firefox Browser policies, is it possible to the title
> "Outdated Policies" be linked to a new page, and on that page, is where all
> the links appear?  That will look better and we can put all outdated
> policies from other products on the same page.

Got it!

Comment 60

[Kohei Yoshino [:kohei]]

The third party page has been linked from older Firefox privacy policies, so it could also be archived. (or those links will 404 Not Found)

Comment 61

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #60)
> The third party page has been linked from older Firefox privacy policies, so
> it could also be archived. (or those links will 404 Not Found)

Okay, please archive.

Comment 62

[Kohei Yoshino [:kohei]]

(In reply to Kohei Yoshino [:kohei] from comment #55)
> Created attachment 8378816 [details] [review]
> Pull Request to add the docs to github.com/mozilla/legal-docs

This pull request has been merged so the legal team can easily edit the docs on GitHub from now on!

https://github.com/mozilla/legal-docs

Comment 63

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #62)
> (In reply to Kohei Yoshino [:kohei] from comment #55)
> > Created attachment 8378816 [details] [review]
> > Pull Request to add the docs to github.com/mozilla/legal-docs
> 
> This pull request has been merged so the legal team can easily edit the docs
> on GitHub from now on!
> 
> https://github.com/mozilla/legal-docs

Woohooo! This should make it easier for everyone, lawyers, localizers, and webdev team :)

Comment 64

[Mike Alexis [:malexis]]

(In reply to Kohei Yoshino [:kohei] from comment #57)
> Created attachment 8378826 [details]
> screenshot, landing page
> 
> Thanks :jslater, here's a screenshot of the updated landing page. I'll
> finish the code and revise my pull request tomorrow.

Kohei,
The screenshot is still showing Test Pilot, otherwise looks good. I think we can push once these changes are committed and reviewed.

Comment 65

[Kohei Yoshino [:kohei]]

Attachment: screenshot, landing page

Removed Test Pilot. The pull request is ready of review.

Comment 66

[Mika]

Hi Kohei, 

Some final tweaks before pushed live.

(1) we now have the email address: yourprivacyis#[e-mail].  In the "Contact Mozilla" section on the landing page, can you change it so that if someone fills out the web form with a question, it will route to this new email address. 

Also, can we remove the field for "your name"? We don't need a person's name.  

(2) Will the Thunderbird privacy policy be connected to the privacy policy link on the Thunderbird webpages, once the changes are pushed live?  Currently, clicking on the Thunderbird privacy policy link connects to the Mozilla Websites page.

Thanks,
Mika

Comment 67

[Kohei Yoshino [:kohei]]

(In reply to Mika from comment #66)
> (1) we now have the email address: yourprivacyis#[e-mail].  In the
> "Contact Mozilla" section on the landing page, can you change it so that if
> someone fills out the web form with a question, it will route to this new
> email address. 
> 
> Also, can we remove the field for "your name"? We don't need a person's
> name.  

Okay, I'll update my pull request with those changes.

> (2) Will the Thunderbird privacy policy be connected to the privacy policy
> link on the Thunderbird webpages, once the changes are pushed live? 
> Currently, clicking on the Thunderbird privacy policy link connects to the
> Mozilla Websites page.

I'll make a patch for this also.

Comment 68

[Kohei Yoshino [:kohei]]

Attachment: Changes to the Thunderbird site

Maybe :sancus can review and land this patch? I know the Thunderbird site will soon be migrated to Bedrock, but it's a legal request. To prevent the effect to l10n, I've kept the string like this:

> {$l10n->get('Thunderbird')} {$l10n->get('Privacy Policy')}

Comment 69

[Mika]

IT suggested implementing a CAPTCHA into the "contact Mozilla" section to reduce the spam.  Jen, is this something your team can do? 

For timing on when to push this live, we're going to release a blog post this week or next explaining what all the changes are.  We'll give it a week after that, and then push live.  I'll give you the green light.

Thanks!
Mika

Comment 70

[Jennifer Bertsch [:jbertsch]]

+needinfo for jpetto to talk to Kohei about options for limiting spam on the form

Hi Mika-

We are experimenting with a couple of different ways to limit spam from forms.  CAPTCHA is bad for website accessibility.

Do you know how much spam per day/week/month is currently generated by the Contact form at the bottom of /privacy?

Thx,
Jen

Kohei and Jon- let's talk about a solution.

Comment 71

[Jennifer Bertsch [:jbertsch]]

And thanks for the update on timing, Mika!

Comment 72

[Mika]

Attachment: Screenshot of privacy inbox.PNG

Attaching a screenshot of the spam that was in the inbox today.  Multiple languages.

I counted 24 spammy emails on March 2nd.  There are 100+ emails from the month of February, and I think only 1 was a legitimate email.  It's hard to tell.

If it helps, there was a separate bug filed by the privacy team on the spam issued - Bug 959605.  I don't think it was ever resolved.  We have a new email address now, so hopefully we can find a good solution going forward.

Comment 73

[Geoff Piper]

Kohei, would you please put the development website back up (I think it was located at this link but is down right now: https://www-demo1.allizom.org/en-US/privacy/)

I need to work with it over the next couple of days and it will be much easier if I can interact with the site in real time browsing around it as it is in its development today.
~Geoff

Comment 74

[Kohei Yoshino [:kohei]]

Bug 945476 might help reduce spam. We'll fix the Internal Server Error soon.

Comment 75

[Jonathan Petto [:jpetto]]

Yep, as Kohei mentioned, in bug 945476 we're discussing improved spam protection measures. In the mean time, I would suggest adding the honeypot/CSRF protection as we've done for other forms. When we decide on additional protection measures, we'll update all forms on bedrock.

Comment 76

[Kohei Yoshino [:kohei]]

The demo server is back! Check it out: https://www-demo1.allizom.org/en-US/privacy/

Comment 77

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #76)
> The demo server is back! Check it out:
> https://www-demo1.allizom.org/en-US/privacy/

(1) How come the "learn more" links in the privacy notices got disabled? :(

(2) If I make the changes to the marketplace and persona privacy notices in Github, is there a way that I can request theze changes not go live until the mozilla.com/privacy page goes live?

Comment 78

[Kohei Yoshino [:kohei]]

(In reply to Mika from comment #77)
> (1) How come the "learn more" links in the privacy notices got disabled? :(

:jbertsch said "All the text should default to be open/expanded for desktop users on this page" in her Comment 46, so I have just disabled the "learn more" links on desktop. On mobile, those links should appear for convenience on the Firefox and Firefox OS privacy notices.

> (2) If I make the changes to the marketplace and persona privacy notices in
> Github, is there a way that I can request theze changes not go live until
> the mozilla.com/privacy page goes live?

The Marketplace Privacy Policy is on marketplace.firefox.com, so you may have to let the Marketplace team know when to deploy those changes.

And the Persona Privacy Policy is still in https://github.com/kyoshino/bedrock/blob/master/bedrock/persona/templates/persona/privacy-policy.html This can be ported to https://github.com/mozilla/legal-docs (in another bug) but anyway the timing of deployment is controllable on mozilla.org side.

Comment 79

[Kohei Yoshino [:kohei]]

Can we take down the demo server? There are only 3 demo servers so we'd like to use it for another projects.

Comment 80

[Mike Alexis [:malexis]]

(In reply to Kohei Yoshino [:kohei] from comment #79)
> Can we take down the demo server? There are only 3 demo servers so we'd like
> to use it for another projects.

We can take this off as long as we can test the spam protection updates to the /legal/fraud-report/ form with out it being up on the demo server.

Comment 81

[Jishnu Menon :jishnu]

How do we get access to the content if we take down from the demo server? We will be directing community to preview the changes so should spin something up for that. We are targeting next week for the full release.

Comment 82

[Mika]

I'm not clear on the resolution to the spam issue - was something done to fix it? I know Jen B. said CAPTCHA is not desirable and other experiments are being done in comment 70.

Have you switched the email on the form to yourprivacyis#[e-mail]? I'm set up with both that email and the old one, so I can tell you if the spam filter is working.  Just let me know the date range to check if there is a difference.

Comment 83

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #78)
> (In reply to Mika from comment #77)
> > (1) How come the "learn more" links in the privacy notices got disabled? :(
> 
> :jbertsch said "All the text should default to be open/expanded for desktop
> users on this page" in her Comment 46, so I have just disabled the "learn
> more" links on desktop. On mobile, those links should appear for convenience
> on the Firefox and Firefox OS privacy notices.

Hi Kohei & Jen - 
Can you reenable the learn more links? Maybe it was miscommunication on my side. We wanted the links to appear for convenience on all platforms (regardless of desktop or mobile) because one recurring comment we received was there is too much text and users can't navigate quickly to the specific section they care about.  That's why we shortened and used the learn more links.  I confirmed w. Jishnu that this is the plan. Let me know if you have any questions.  Thank you!

Comment 84

[Kohei Yoshino [:kohei]]

Okay, I'll re-add learn more links.

Comment 85

[Kohei Yoshino [:kohei]]

(In reply to Jishnu Menon :jishnu from comment #81)
> How do we get access to the content if we take down from the demo server? We
> will be directing community to preview the changes so should spin something
> up for that. We are targeting next week for the full release.

We'll keep the demo server if needed, though the content is always available at https://github.com/mozilla/legal-docs

Comment 86

[Kohei Yoshino [:kohei]]

(In reply to Mika from comment #82)
> Have you switched the email on the form to yourprivacyis#[e-mail]?

I have update the email address in my pull request but it's not live yet.

Comment 87

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #84)
> Okay, I'll re-add learn more links.

Thanks very much, sorry for the extra work on your end.

Comment 88

[Mika]

Hi Kohei, can you make the changes today to re-add the learn more links? 

The blog post will be published today or tomorrow.  People will be able to view the revamped website on the demo server for one week to provide feedback, and then we'll push it to production after making any needed changes (based on the feedback).

Comment 89

[Mike Alexis [:malexis]]

(In reply to Mika from comment #88)
> Hi Kohei, can you make the changes today to re-add the learn more links? 
> 
> The blog post will be published today or tomorrow.  People will be able to
> view the revamped website on the demo server for one week to provide
> feedback, and then we'll push it to production after making any needed
> changes (based on the feedback).

Hi Mika,
We only have a limited amount of demo servers available and having this up for another week is going to be disruptive to other projects. I know getting community feedback is necessary--if we're only soliciting feedback for text changes (not the features and functionality of the site itself) would it be OK to put that on the wiki instead? Then once approved we can put the site back on demo1 and push live.

Comment 90

[Kohei Yoshino [:kohei]]

Yeah, IIUC, a demo server is only for a temporary preview (among WebDevs and WebQAs) but a link in a blog post could be referred later...

Links to the up-to-date legal-docs repository might be better:
https://github.com/mozilla/legal-docs/blob/master/mozilla_privacy_policy/en-US.md
https://github.com/mozilla/legal-docs/blob/master/websites_privacy_notice/en-US.md
https://github.com/mozilla/legal-docs/blob/master/firefox_privacy_notice/en-US.md

Comment 91

[Mike Alexis [:malexis]]

+1 to pointing to the up-to-date legal docs in the Github repo.

Comment 92

[Jishnu Menon :jishnu]

Hi - 

The github repo is only text - people are going to be interested in presentation. I'm going to talk to CMore about this to figure out the right path - appreciate everyone's patience here.

I only need it up on staging a couple days before the announcement for a couple weeks and can coordinate that when it happens.

Thanks
Jishnu

Comment 93

[Kohei Yoshino [:kohei]]

Updated the demo site: https://www-demo1.allizom.org/en-US/privacy/

Comment 94

[Mika]

Hi Kohei, we received feedback to make the styles consistent across the notices (the use of bullets, headings, and drop downs was different across the Firefox OS, Firefox, and Websites notices).  Firefox OS is the sample we got good reviews on, so we want to follow that.  I created a quick style guide  here (slide 14): https://docs.google.com/presentation/d/1tHqeS-0C1SNBuq3p4n6llbGP9QEblKVhdB--iqJnmx0/edit?usp=sharing

Using the style guide, I made changes to the Firefox & Websites privacy notices:

- Firefox PN changes are here - https://github.com/mozilla/legal-docs/blob/master/firefox_privacy_notice/en-US.md  

- Websites changes are here - https://github.com/mozilla/legal-docs/blob/master/websites_privacy_notice/en-US.md

For the Firefox privacy notice, can you add "Learn More" options after the 2 sentences: "Firefox automatically connects to us and our service providers to provide the features below." and "When you ask it to, Firefox also connects to Mozilla to provide you with features such as Sync, location services, crash reporting, and add-ons."  I wasn't sure how to do that.

Can you also check to make sure the font sizes and typefaces are consistent? Again, not sure how that's done.

When will these changes be reflected on the demo server? I wasn't sure if my changes to the master are enough, or if something else has to happen.  

Thank you,
Mika

Comment 95

[Kohei Yoshino [:kohei]]

I'll check the changes on my local server. The demo server may be updated on Monday.

Comment 96

[Mika]

(In reply to Kohei Yoshino [:kohei] from comment #95)
> I'll check the changes on my local server. The demo server may be updated on
> Monday.

Did you have a chance to check the changes? When will the demo server be updated today? Thanks.

Comment 97

[Kohei Yoshino [:kohei]]

Mika: we've just updated the demo site: https://www-demo1.allizom.org/en-US/privacy/

An expander is not working on the Firefox Browser Privacy Notice page... It should be fixed with the next push: https://github.com/mozilla/legal-docs/pull/27/files

Comment 98

[Mika]

Hi Kohei & Jen - 

Here is the combined feedback for edits.  Please push the privacy website to production as soon as these are taken care of. Let me know if this can be live by tomorrow (and if not, by when).

(1) I made some edits to the copy of the notices below.  Please push these to production.
- Mozilla Privacy Policy (https://github.com/mozilla/legal-docs/blob/privacy-website-update/mozilla_privacy_policy/en-US.md)
- Firefox Notice - https://github.com/mozilla/legal-docs/blob/privacy-website-update/firefox_privacy_notice/en-US.md
- Websites Notice - https://github.com/mozilla/legal-docs/blob/privacy-website-update/websites_privacy_notice/en-US.md

(2) Fix the expander on Firefox Browser Privacy Notice. 
(3) Someone commented that the hashtags are not all functioning. Please fix.
(4) Can you confirm that new email address will be used on the production page, with the improved spam filters.  

Thanks!
Mika

Comment 99

[Mika]

Also, 

- please archive the Firefox policy that is being replaced on the "Outdated Policies" webpage (currently - https://www-demo1.allizom.org/en-US/privacy/archive/)

- please add a section to that page that says "Mozilla Websites" and add the policy that's being replaced there.

Comment 100

[Chris More [:cmore]]

:kohei: let us know you have a PR to address the items in comment 98 and comment 99. Thanks!

Comment 101

[Kohei Yoshino [:kohei]]

I have updated my pull request:

(In reply to Mika from comment #98)
> (1) I made some edits to the copy of the notices below.  Please push these
> to production.

Included in my pull request. Will be pushed tomorrow.

> (2) Fix the expander on Firefox Browser Privacy Notice. 

I have already fixed this.

> (3) Someone commented that the hashtags are not all functioning. Please fix.

Fixed.

> (4) Can you confirm that new email address will be used on the production
> page, with the improved spam filters.  

I'm not sure about the spam filter but the form now uses the new address.

(In reply to Mika from comment #99)
> - please archive the Firefox policy that is being replaced on the "Outdated
> Policies" webpage (currently -
> https://www-demo1.allizom.org/en-US/privacy/archive/)

The current Firefox Privacy Policy is already archived at
https://www-demo1.allizom.org/en-US/privacy/archive/firefox/2013-05/

> - please add a section to that page that says "Mozilla Websites" and add the
> policy that's being replaced there.

Added to my pull request.

Comment 102

[Kohei Yoshino [:kohei]]

In r126388 I have activated the locales that have already localized the Firefox OS Privacy Notice. The content has been moved the legal-docs repo but we still need .lang files on SVN to make l10n available (or those locales will be redirected to en-US). Can someone merge the commit to stage and production?

Comment 103

[Mika]

Merged the branch into master.  Tried to preserve the hashtag changes Kohei made to master in that process, but Kohei, please check to make sure they still work.

Can you let us know approx what time this will go live on www.mozilla.org/privacy? We'll time our blog updates around the push.

Thanks,
Mika

Comment 104

[Pascal Chevrel:pascalc (PTO until April 26)]

(In reply to Kohei Yoshino [:kohei] from comment #102)
> In r126388 I have activated the locales that have already localized the
> Firefox OS Privacy Notice. The content has been moved the legal-docs repo
> but we still need .lang files on SVN to make l10n available (or those
> locales will be redirected to en-US). Can someone merge the commit to stage
> and production?

Pushed to prod in r126406

Comment 105

[Jennifer Bertsch [:jbertsch]]

Hi Mika-

I think we need to wait to tomorrow to do the push, just to make sure that we have crossed all our "T"s and dotted all the "I"s.

With Mike on PTO and me focused on the Australis-related work, I didn't get everything organized early enough in the day to push today.

I'm sorry for the delay.  Is tomorrow OK?

Thx,
Jen

Comment 106

[Kohei Yoshino [:kohei]]

:pmac has just updated the demo server with my latest pull request so you can give your final review on https://www-demo1.allizom.org/en-US/privacy/

Comment 107

[Mika]

Tomorrow is fine - can you just let me know approx what time (noon? afternoon?) so we can coordinate the comms plan.  I'll review the demo now.

Comment 108

[Mika]

Demo looks good, green light to share with the world today.  Jen - let us know approx what time the switch will happen.

Thank you everyone!!!
Mika

Comment 109

[Chris More [:cmore]]

(In reply to Mika from comment #108)
> Demo looks good, green light to share with the world today.  Jen - let us
> know approx what time the switch will happen.
> 
> Thank you everyone!!!
> Mika

woo hoo! I will ping pmac/jgmize about merging demo1 into master and pushing to dev, stage, and then production!

Comment 110

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/6f2cd5ecf9dced5f61055f6f1f35e9c5a0ce7652
Fix Bug 963816 - update privacy center

https://github.com/mozilla/bedrock/commit/c4ccb51dc24cdc154d8856205e87e74ff646eb6a
Merge pull request #1637 from kyoshino/bug-963816-update-privacy-center

Fix Bug 963816 - update privacy center

Comment 111

[Mike Manning]

Would we be able to push to production at around 11:00 am PT today? I'll be standing by to post a notice on the Mozilla Privacy blog once it's live.

Comment 112

[raymond [:retornam] (inactive)]

Kohei on https://www.allizom.org/en-US/privacy/ can you please change the clas for the firefox-os policy to policy-firefox-os  for consistency

Comment 113

[Kohei Yoshino [:kohei]]

Sure thing, I just wanted to use the same icon for the FxOS link.

Comment 114

[Josh Mize [:jgmize]]

(In reply to Mike Manning from comment #111)
> Would we be able to push to production at around 11:00 am PT today? I'll be
> standing by to post a notice on the Mozilla Privacy blog once it's live.

This is now in production: https://www.mozilla.org/en-US/privacy/

Comment 115

[Kohei Yoshino [:kohei]]

I'll update the class name on the link in the next round. We have to add this soon:
https://github.com/mozilla/legal-docs/tree/master/firefox_cloud_services_PrivacyNotice

Comment 116

[Mike Manning]

> This is now in production: https://www.mozilla.org/en-US/privacy/

Thanks, I've updated Denelle's Privacy blog post: https://blog.mozilla.org/privacy/2014/04/08/clearer-mozilla-privacy-website-policies/

Comment 117

[Mike Manning]

Found a typo on the main Privacy page: one of the subheads towards the bottom reads: "What else do we want you know?" Should read "want you *to* know".

www.mozilla.org/privacy

Comment 118

[Chris More [:cmore]]

(In reply to Mike Manning from comment #117)
> Found a typo on the main Privacy page: one of the subheads towards the
> bottom reads: "What else do we want you know?" Should read "want you *to*
> know".
> 
> www.mozilla.org/privacy

That's a type in the legal text stored here:

https://github.com/mozilla/legal-docs/blob/master/mozilla_privacy_policy/en-US.md

The legal team has ownership over that and they can make the change. 

Mika: can your team make this text change in the legal-docs repo?

Comment 119

[Mika]

(In reply to Chris More [:cmore] from comment #118)

> Mika: can your team make this text change in the legal-docs repo?

Done - committed the fix.

Comment 120

[Kohei Yoshino [:kohei]]

Attachment: pull request change the link class name; pick the latest legal-docs change to fix a typo

Comment 121

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/364923aab87947d36d907738e95aebba07021cfa
Bug 963816: Move privacy redirects above main /privacy/ passthrough.

https://github.com/mozilla/bedrock/commit/d755d27cc53b03367bf6424a2ab309b86ac6ea53
Merge pull request #1889 from pmclanahan/fix-privacy-policy-redirect-963816

Bug 963816: Move privacy redirects above main /privacy/ passthrough.

Comment 122

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/aab10d35b172e419dc830ebaf017cdb2c6c00f5a
Bug 963816 followup: change the link class name; pick the latest legal-docs change to fix a typo

https://github.com/mozilla/bedrock/commit/f3569560585f1d8632b7ec56e946e9b1d0eaa388
Merge pull request #1887 from kyoshino/bug-963816-privacy-center-followup

Bug 963816 followup: change the link class name; pick the latest legal-docs change to fix a typo

Comment 123

[Kohei Yoshino [:kohei]]

The typo has been fixed on production http://www.mozilla.org/en-US/privacy/

Comment 124

[Mika]

The new privacy email already has 21 junk messages and the website's only been live for a few hours :(  How can this be fixed? Should I reopen this bug or file a new one?

Comment 125

[Jennifer Bertsch [:jbertsch]]

Hi Mika-

Could you please file a new bug for the junk emails?

I'll ask Mike when he's back next week on progress on spam prevention on mozilla.org

Thx,
Jen

Comment 126

[Kohei Yoshino [:kohei]]

Filed Bug 997415.

Comment 127

[Wayne Mery (:wsmwk)]

Comment on attachment 8382602 [details] [diff] [review]
Changes to the Thunderbird site

Now on bedrock, so presumably we no longer needs this.