Is NAI Global Privacy Control Signal safe?

Clean risk

NAI Global Privacy Control Signal adds the Sec-GPC: 1 header and exposes GPC to pages after you enable it.

When enabled, the extension stores the setting, reloads the active tab, and adds Sec-GPC: 1 to browser requests. It also injects a page script that makes navigator.globalPrivacyControl return true so websites can detect the preference.

NAI Global Privacy Control Signalv1.0Chrome Web Store
1Risk
Who publishes it

NAI Global Privacy Control Signal - no other listings under this identity, 1 shared hostname

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
NAI Global Privacy Control Signal

Shared hosts - 1 hostname

Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.

privacycg.github.io
Also called by 6 other listings

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

What it can do

Permissions this extension asks for, as declared in version 1.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on every site you visit

    *://*/*

  • Act on the current tab, but only after you click the extension

    activeTab

  • Store data in your browser

    storage

  • Block and redirect the requests your browser makes

    declarativeNetRequest

  • See which of your requests its blocking rules matched

    declarativeNetRequestFeedback

declarativeNetRequestWithHostAccess
Updated 30 September 2026ecmgoeapljejplncpocmgnpdemidoffo