Closed Bug 637482 Opened 11 years ago Closed 11 years ago

Broken Link to Privacy Policy: 404 Page Not Found


(Firefox for Android Graveyard :: General, defect)

Not set



Firefox 4.0
Tracking Status
fennec 2.0+ ---


(Reporter: afowler, Assigned: mbrubeck)




(Keywords: privacy)


(1 file)

Unfortunately, the link to the privacy policy from within the 4.0b5 version of Firefox Mobile gives me a 404 Page Not Found. 

Here's the path: 
Under Preferences
Click About Firefox
Click Privacy Policy
404: Page Not Found
Does this need to be a confidential bug?
tracking-fennec: --- → ?
OS: Mac OS X → All
Hardware: x86 → All
The current link in Fennec is:

Do we have a separate privacy policy for mobile, or should we just link to the Firefox privacy policy?
Group: mozilla-corporation-confidential
Mike, what do we need to do here?
I don't think we have a separate policy.  If we don't, we should do two things:

1. fix the link in firefox before GA - we don't need extra redirects
2. set up a redirect for (maybe)

If we can fix this in the prefs for fennec that's the main thing.  Setting up a redirect for a 404 in a beta probably isn't necessary but we can do that too.
tracking-fennec: ? → 2.0+
Assignee: nobody → doug.turner
Seems like and also Google Search results point to (see attachment) which now shows a 404. Webdev, can you restore the page?
Assignee: doug.turner → nobody
Component: General → Webdev
Product: Fennec →
QA Contact: general → webdev
Version: Trunk → other
Here's the mobile friendly version of the Firefox privacy policy:

This is the one that we should use.
Component: Webdev → General
Product: → Fennec
QA Contact: webdev → general
Target Milestone: --- → fennec2.0
Version: other → Trunk
Assignee: nobody → mbrubeck
Attached patch patchSplinter Review
Attachment #516921 - Flags: review?(wjohnston)
Attachment #516921 - Flags: review?(wjohnston) → review+
Closed: 11 years ago
Resolution: --- → FIXED
Verified on:
Mozilla/5.0 (Android; Linux armv7l; rv:2.0b13pre) Gecko/20100307
Firefox/4.0b13pre Fennec/4.0b6pre
You need to log in before you can comment on or make changes to this bug.