CRX id
niiahgnkkalkindhghjcaojcpbkhfbbp
niiahgnkkalkindhghjcaojcpbkhfbbp
Description from extension meta
This GPC Chrome Extension enables the Global Privacy Control opt-out signal and evaluates how websites respond to the setting
Image from store
Description from store
This Global Privacy Control Chrome Extension enables the GPC setting and evaluates whether whether websites honor the opt-out setting by providing transparency into the personal data shared with third parties.
The right for website visitors to opt-out of the sale of personal information is a hallmark of data privacy laws such as the California Consumer Privacy Act (CCPA). Regulators are accelerating enforcement against companies that do not honor the Global Privacy Control (GPC) signal as a valid opt-out. "Under law, [GPC] must be honored by covered businesses as a valid consumer request to stop the sale of personal information." https://oag.ca.gov/privacy/ccpa";
For developers and IT teams, this extension helps understand and debug how webpages respond to the GPC signal. Diagnostic capabilities include:
- Validate the GPC signal was set and the website response is consistent with the GPC specification
- Diagnose website behavior including whether the GPC signal was read by the page
- Debug whether personal data is shared by examining information provided to third parties using beacons and cookies.
Questions? Feedback? We'd love to hear from you at [email protected]
Latest reviews
- (2023-09-18) Mary kolan: How can I get and extension to prevent my zoosk profile from getting band
- (2023-08-07) Rutuj Runwal: Hi Delson, The extension is really good and works fine There is a minor issue though, whenever the enable GPC option is checked and unchecked, the details are not visible right away even if the page is reloaded. The extension needs to be reopened again for the details to show and it seems to be checking GPC compliance on chrome:// or file:// type urls where it is supposed to do nothing. Also I am confused with the way the headers are set when you are using declarativeNetRequest to set the GPC header, the extension is applying it to all resource types like images,fonts,stylesheets as well is that intended and really necessary? Thanks. Rutuj Runwal, Creator - RR Adblocker
- (2023-06-21) Vict Vict: It is quite good but it does not actually add Sec-Gpc header to requests! So it wont work on websited that use backend to detect GPC. Please fix it. UPD: seems to be fixed now! The devs are great!
- (2023-05-11) Ward Chan: hi Delson, I saw your reply. But it's still like what Vict said, `Sec-Gpc` is indeed not set in the header. My device is a Mac with version 13.3.1 and Chrome with version 112. I can reproduce the same problem on another Windows device, and another colleague of mine has also reported the same issue. Maybe you should verify this issue on a clean machine? https://imgur.com/a/eccVDl7