Global Privacy Control (GPC) Inspector

This GPC Chrome Extension enables the Global Privacy Control opt-out signal and evaluates how websites respond to the setting

Total ratings

4.43 (Rating count: 7)
See reviews for Global Privacy Control (GPC) Inspector on Chrome Web Store

User reviews

Recent rating average: 4.00
All time rating average: 4.43

Rating filters

5 star
30% (3)
4 star
40% (4)
3 star
30% (3)
2 star
0%
1 star
0%
Date Author Rating Lang Comment
2024-01-19
Ryan Guthrie
en Previously knocked a few stars off because of a small but important bug with the signal. *However*, the devs not only fixed it almost immediately, they also tracked me down on another account because my email was deactivated, to let me know. Honestly shocking how responsive they are. Most of my paid products don't have that level of service. So 5 stars for the extension, and would recommend their business as well if anyone needs it.
2024-01-18
Jonathan Shaw
en The extension works as described! The developer worked with me to fix an issue where the list of scripts did not appear. Now I can copy the list to share in reports. Thank you!
2024-01-11
A Google user
en As a developer I feel like this is missing a lot of features. I want the extension enabled, but be able to turn the signal off/on by default, or set site specific rules. The screenshots with all the details and debug info does not seem to work. Even on your own page to test the signal, it just says "Webpage details not available". For a regular user.. it does send the signal so I guess that's enough.
2023-09-18
Mary kolan
How can I get and extension to prevent my zoosk profile from getting band
2023-09-18
Mary kolan
en 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-08-07
Rutuj Runwal
en 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-05-09
Vict Vict
en 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
2023-05-11
Ward Chan
en 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