user.js: [user.js suggestion] Do Not Track and Global Privacy Control signals [redundant with dFPI]

Wouldn’t it be good to enable them by default, or aren’t they enabled because of fingerprinting?

<spoiler>
privacy.globalprivacycontrol.enabled
privacy.globalprivacycontrol.functionality.enabled
privacy.globalprivacycontrol.was_ever_enabled
privacy.donottrackheader.enabled

</spoiler>

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 17 (9 by maintainers)

Most upvoted comments

I am hoping to convince you to reopen Issue #1542. The GPC concept has made a lot of progress and it I think it is worth re-evaluating. Consider the following:

  1. The GPC header is honored by a lot of highly ranked sites. These include news orgs like the NYTimes, Washington Post and the Financial Times. Top visited sites like People Magazine which has 4.1 billion weekly media impressions, Entertainment Weekly, Better Homes & Gardens (59 million monthly page views), Martha Stewart (13 million monthly page views) Travel + Leisure (33 million monthly page views) Health and Medical sites that consistently rank on the 1st page of search engines like Health, VeryWell and Parents as well as major lifestyle outlets like InStyle, Brides and Shape.
  2. In California, The GPC signal will be intended to communicate a Do Not Sell request from a global privacy control, as per CCPA-REGULATIONS §999.315 for that browser, or, if known, the consumer.
  3. Under the GDPR, the intent of the GPC signal is to convey a general request that data controllers limit the sale or sharing of the user’s personal data to other data controllers GDPR Articles 7 & 21.

And some counter examples to @Thorin-Oakenpants earlier points from this comment,

in reality, No. One. Cares.

The California DOJ cares and the GPC header under the CCPA is being enforced. From the August 24, 2022 CA AG’s Press Release:

Today’s settlement is part of ongoing efforts by the Attorney General to enforce California’s comprehensive consumer privacy law that allows consumers to tell businesses to stop selling their personal information to third parties, including those signaled by the Global Privacy Control (GPC).

“Technologies like the Global Privacy Control are a game changer for consumers looking to exercise their data privacy rights. But these rights are meaningless if businesses hide how they are using their customer’s data and ignore requests to opt-out of its sale,” said Attorney General Bonta.

I don’t know off-hand if there are any GDPR enforcement actions, but I am sure the EU wouldn’t hesitate to enforce if they felt it was appropriate.

Currently, GPC isn’t included in your user.js I believe it would require the addition of two additional prefs:

user_pref("privacy.globalprivacycontrol.functionality.enabled", true);
user_pref("privacy.globalprivacycontrol.enabled", true);

But you would know about this bit better than than I.

Anyway, I’ll get off my soapbox. Here’s hoping you reconsider!

I didn’t mean that literally no one cares. Obviously some do re enforcement and usage. But in terms of effectiveness it is statistically moot, and it is practically obsolete with dFPI + sanitizing - hence NO ONE CARES.

It will change when Mozilla changes it. Go ask them to do it, it’s all set up.

@Thorin-Oakenpants It has been a couple years since this was last discussed, I’m here to pester you about this once more. (sorry…)

More US states have enacted privacy laws mandating the GPC signal be respected, and setting up a framework for penalties or lawsuits if it is not respected.

Additionally Firefox has now enabled by default in Private Browsing mode (as of version 120) and Brave has enabled it by default for all users.

In my eyes, there is no cost to enabling this by default

  1. It communicates a privacy preference that is legally binding and enforceable in jurisdictions like California, Colorado, and Connecticut. (and more coming in '24 and '25.
  2. It communicates a general pro-privacy, anti-tracking stance, that may or may not matter, but certainly doesn’t hurt.
  3. It can minimize or eliminate cookie pop-up notifications, and handles this automatically. So its also a QOL thing, not just Privacy.
  4. I see technical solutions like dFPI and legal solutions like privacy legislation as the GPC as complementary. One doesn’t preclude the usefulness of the other. At best it is an improvement to privacy, at worst it doesn’t hurt to enable it, and users like me stop pestering you 😃
  5. As @debsidian pointed out it may be legally binding the EU as well, and while @fxbrit points out it won’t necessarily impact the rest of the world, what we’ve seen with a lot of these privacy regulations is they have ripple effects that benefit people even in jurisdictions where the regulation isn’t enforceable because corporations can’t always be bothered to differentiate based on legal jurisdiction.
  6. dFPI only offers protection against cross site tracking right? GPC may be able to do more in the case of 1st party tracking, and abuse of user data.

But my strongest argument is simply why not? If the only argument against it is “nobody cares” and it becomes clear that many people do actually care, and enabling it wouldn’t harm anything, then why not enable it, if it improves things for ~50 million potential users, and doesn’t negatively impact the rest?

It will change when Mozilla changes it. Go ask them to do it, it’s all set up.

It’s okay. I’ll just add it to my user-overrides.js and call it a day. Thanks for your time.

FYI: unlike DNT, the Global Privacy Control is legally binding, but from my understanding that applies exclusively to California and Colorado. GPC wouldn’t mean anything for the rest of the world, at least not now. also see -> https://bugzilla.mozilla.org/show_bug.cgi?id=1670058#c1

even if statistically it went up, it doesn’t really DO anything for us because dFPI

I still feel like you may not be appreciating the different focuses of dFPI and GPC, as I understand it dFPI does one thing, GPC another.

(edit: to be more explicit, dFPI seems only useful in the context of preventing tracking specifically cross site tracking. Whereas GPC, is a signal not to share or sell personal data, and applies not just to cross site/3rd party trackers, but first parties as well, this is something dFPI cannot address, so no, I do not agree that GPC and dFPI are redundant, I see them as complementary layers with some overlap but considerable differences).

My understanding is dFPI is an effective tool at preventing cross site tracking, through state partitioning (correct?). I accept that that is a better solution for 3rd party trackers and tracking cookies and the like. But I don’t believe dFPI has any impact on first party abuse of your personal information.

If you live in the EU, you enjoy stronger privacy rights than most. I believe GDPR mandates no business can sell or share your personal info without your consent. Most of the rest of the world does not have that right. In the states, we must manually opt-out, and even then, that opt-out is only legally required in a number of states. GPC is the most efficient method to perform that opt-out From 1st parties (as well as 3rd parties) selling or sharing your personal information please correct me if I am wrong and dFPI can do something in that context?

once again

in terms of effectiveness it is statistically moot, and it is practically obsolete with dFPI + sanitizing

even if statistically it went up, it doesn’t really DO anything for us because dFPI. Tor Browser doesn’t care and neither should we. Tor Browser doesn’t even care about blocking trackers, because FPI. Capsice?

changing it is just another pref to add, another thing to read in the user.js, another thing to be asked about … the answer is no - AND it will be an outlier in fingerprints INCLUDING headers (passive fingerprinting … so no, just … NO

The signal is only sent to the trackers that the ETP module blocks, not all websites.

How is it send if they are blocked. 🤔