Update Firefox Privacy Policy

RESOLVED FIXED

Status

www.mozilla.org
General
RESOLVED FIXED
9 years ago
6 years ago

People

(Reporter: Catherine C. Brady, Assigned: Julie Martin)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

9 years ago
Created attachment 355946 [details]
Updated Firefox Privacy Policy

Attached is the updated Firefox Privacy Policy to be posted to the website.
(Reporter)

Comment 1

9 years ago
Created attachment 356011 [details]
Updated Firefox Privacy Policy - (Jan 8)

Revised to incorporate feedback from this morning.
Attachment #355946 - Attachment is obsolete: true
Is there a reason why this bug is confidential?
(Reporter)

Comment 3

9 years ago
Habit on my part.  Please change.
Group: mozilla-corporation-confidential
(Reporter)

Comment 4

9 years ago
Checking on where we are in getting this policy posted.  ETA?

Comment 5

9 years ago
Hi Steven. We need to update mozilla.com with a new corporate privacy policy. Can you help get this text (from comment #1) up on the site?

We'd like to have it up sometime this week if at all possible. If you have any questions about the content, format, etc Catherine Brady can help you.

Thanks much!
John
Assignee: nobody → steven
Done in trunk in r21770 and sync to stage:

en-US/legal/privacy/firefox-en.html
en-US/legal/privacy/firefox-en.txt

These should be carefully proofed before being pushed to production. I did do a careful line-by-line comparison, but I would still like to have a second set of eyes on it.

It appears the text version had been a bit sloppy in the previous version - it container lines like "insert link here". This has also been cleaned up.

For the longer term, it seems like there should be a better way to track changes in a document like this that lives in a Word document, but is exported to the web in HTML and plain-text formats. It's a laborous (and possibly error-prone) process to turn the .doc file into HTML/text versions.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(Reporter)

Comment 7

9 years ago
Steve,

Thank you for your work on this.  I'll talk with John about the best way for me to submit the changes to these documents.

I'll also proof the text and give you any changes I may have.
(Reporter)

Comment 8

9 years ago
I've proofed both the txt and the html versions posted in trunk in r21770.

txt version:

1. Under "Interactive Product Features" "Firefox 3.0 to present - 7th line down: "3.05" should be changed to "3.0.5". 

2. Under "Security Features" "Firefox 2.0 to 2.x  - 5th paragraph ("Each time Firefox checks . . ."), 10th line: delete the extra space between "Firefox" and "for purpose"

3. Under "Security Features" "Firefox 3.0 to 3.x  - 4th paragraph ("Each time Firefox checks . . ."), 10th line: delete the extra space between "Firefox" and "for purpose"

4. Under "Security Features" "Firefox 3.0 to 3.x  - 5h paragraph ("Please not that we're not yelling . . .") - change "not" to "note".  It should now read: "Please note that we're not yelling . . ."

For the html version: 

1. Under "Interactive Product Features" delete the introductory sentence right before "Crash Reporting". The sentence reads: "Mozilla has additional interactive product features, some of which are provided by third party service providers, which additional interactive features are available depends on the version of Firefox you are using."

2.  Under "Interactive Product Features" "Firefox 3.0 to present - 7th line down: "3.05" should be changed to "3.0.5". 

3. Under "Security Features" an additional clause was added at the end of the introductory sentence that needs to be deleted.  It is: "which security features are available depends on the version of Firefox you are using."

4. Under "Security Features" "Secure Website Certification Verification" Two (2) paragraphs are missing after the first paragraph.  Insert the following:
"Protection Against Suspected Forgery and Attack Sites Features.  The Firefox forgery and attack protection feature displays a warning if the website you are visiting is suspected of impersonating a legitimate website (commonly referred to as a phishing or forgery website) or a site that infiltrates or damages a computer system without your informed consent, including, without limitation, any computer viruses, worms, trojan horses, spyware, computer contaminant and/or other malicious and unwanted software (commonly called an attack site or malware).  By default, Firefox checks the web pages that you visit against a blacklist that is downloaded to your hard drive at regularly scheduled intervals (e.g., approximately twice per hour), the rate of frequency may change from time to time.  The blacklist does not include the full URL of each suspicious site. Instead, each URL is hashed (obscured so it can't be read) and then broken into portions. Only a portion of each hashed URL is included on the blacklist on your hard drive. If there is a match, Firefox will check with its third party provider to ensure that the website is still on the blacklist.  The information sent between Firefox and its third party provider(s) are hashed URLs.  In fact, multiple hashed URLs are sent with the real hash so that the third party provider(s) will not know what site you are visiting.  If there is a match, Firefox displays either a “Reported Web Forgery” or “Reported Attack Site” alert, as applicable. 
 
You may completely turn off the forgery and/or attack site protection features in Firefox’s preferences.  If you do this, none of the information discussed here will be downloaded to your hard drive or sent to any third party service provider.  An article in our Firefox Knowledge Base gives you information about changing your preferences. "

5. Under "Security Features" last paragraph ("Please note that we're not yelling"), change "Mozilla Firefox End User License Software Agreement" to Mozilla Web Site Services Terms".

Thank you.
(Reporter)

Comment 9

9 years ago
Just following up on the changes submitted last week (Comment #8).  When do you expect them to be done?  We would like to have the revised policy posted the week (early).

Thanks, Steve.
(In reply to comment #9)
> Just following up on the changes submitted last week (Comment #8).  When do you
> expect them to be done?  We would like to have the revised policy posted the
> week (early).

Sorry for the delay. I'll have these changes done today.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 11

9 years ago
Thanks, Steve.
The changes from comment #8 are done in trunk in r21894.

(In reply to comment #8)
> 5. Under "Security Features" last paragraph ("Please note that we're not
> yelling"), change "Mozilla Firefox End User License Software Agreement" to
> Mozilla Web Site Services Terms".

I wondered if the link here should change too? Right now, it's pointing to http://www.mozilla.com/en-US/legal/eula/
(Reporter)

Comment 13

9 years ago
Good point Steven. I think the link should still go to this page, as there are versions of Firefox out there subject to a EULA.  We should actually update that page (http://www.mozilla.com/en-US/legal/eula/) to include the new About Rights and Web Site Services Terms.
(In reply to comment #13)
> Good point Steven. I think the link should still go to this page, as there are
> versions of Firefox out there subject to a EULA.  We should actually update
> that page (http://www.mozilla.com/en-US/legal/eula/) to include the new About
> Rights and Web Site Services Terms.

Catherine, can you file a separate bug for that? Thanks.
(Reporter)

Comment 15

9 years ago
John & Steven - I filed a new bug for updating the EULA page. Bug 476494.  I was unable to assign it.  Can one of you work on it?

Catherine

Comment 16

9 years ago
Just assigned it to Steven...
Is this still needed?  I think we've updated the policy page (in different bugs) once or twice since the last comment in this bug.

Cbrady is gone, CC'ing Jmartin

Comment 18

8 years ago
The page does not adapt to various browser window sizes and monitor resolutions.  With SeaMonkey's window at a maximum, I still get a horizontal scroll bar.  

Note that a maximized window on my PC is less that the full width of my monitor screen because I have a Windows toolbar on the right side.  Even if I remove that toolbar, however, I still get a horizontal scroll bar.  

Furthermore, my resolution is set to 800x600 because my eyes are getting old.  Yes, there are several ways to increase the sizes of fonts, both in Windows and in some Mozilla products.  However, those methods do not work with ALL applications, especially with applications that are developed by neither Microsoft nor Mozilla.  

Per Gervase Markham: 
"This seems to be a general problem with the mozilla.com website, not
just this page."  

Although the content is substantially the same, the privacy page at <http://www.mozilla.org/about/policies/privacy-policy.html> does not exhibit this problem.  Thus, if Markham is correct, this is localized as a mozilla.com problem and does not seem to affect mozilla.org.

Comment 19

8 years ago
Oops!  I forgot to give the URI of the problem page.  It's <http://www.mozilla.com/en-US/privacy-policy.html>
Julie, this can be closed right?  

Normally I'd just close it, but since it touches legal stuff, I figured I should make sure first.
Assignee: steven → jmartin
(Assignee)

Comment 21

8 years ago
Yes, please do close.  But thank you for asking.
Status: REOPENED → RESOLVED
Last Resolved: 9 years ago8 years ago
Resolution: --- → FIXED

Comment 22

8 years ago
Given that the problem I cited in comment #18 still exists, why was this bug report closed?
(In reply to comment #22)
> Given that the problem I cited in comment #18 still exists, why was this bug
> report closed?

Because it's separate from updating the privacy policy itself (one bug per issue).  Please file a new bug on Mozilla.com, and we'll take a look at it.  A screenshot/screenshot would help, too.  Thanks!
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.