The Firefox Browser Privacy Notice has an incorrect link to the "Firefox Desktop Attribution" SUMO article

VERIFIED FIXED

Status

www.mozilla.org
Pages & Content
VERIFIED FIXED
4 months ago
4 months ago

People

(Reporter: Alice Wyman, Unassigned)

Tracking

Production

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

4 months ago
+++ This bug was initially created as a clone of Bug #1338601 +++

The Firefox Browser Privacy Notice at https://www.mozilla.org/en-US/privacy/firefox/ includes the following paragraph, under the Referral and Campaign Tracking section:
(quote) "On desktop, Firefox records and sends Referral Data to Mozilla as part of Firefox Health Report. Learn more here, including how to opt-out or disable this reporting."
.... with the 'here' link going to https://support.mozilla.org/kb/desktop-attribution-privacy (a page not found).  The SUMO "Firefox Desktop Attribution" article is currently here: https://support.mozilla.org/kb/desktop-privacy
I opened an issue for this on the legal docs repo: https://github.com/mozilla/legal-docs/issues/871
Hey Alex, we actually wanted to change the location of that article to the url in the live version of the notice. I am trying to work with Patrick and see if we can get it changed.
We are waiting until Joni on the SUMO team returns from PTO to see if we can get the article moved to the URL in the live version of the policy. I am going to check with Elvin on options for the meantime. I'll keep you posted.
(Reporter)

Comment 4

4 months ago
I edited the article description to change the stub from desktop-privacy to desktop-attribution-privacy. 
https://support.mozilla.org/kb/desktop-attribution-privacy is now the article url so this bug can be resolved.
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → FIXED
(Reporter)

Comment 5

4 months ago
(from comment #4)
> I edited the article description to change the stub 
I meant slug.
In any case, the link to https://support.mozilla.org/kb/desktop-attribution-privacy is now working.
Thanks all!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.