Privacy Policy
GPC & Opt-Out Checker sends the Global Privacy Control (GPC) signal to websites and shows you which known advertising vendors a site contacts with GPC on and off. It is built so your browsing stays on your device. This policy explains exactly what the extension does with information.
The short version
The extension does not collect, upload, sell, or share your browsing data, and has no analytics of its own. DigiBiz360 receives information from it only if you click "Get a paid audit" (or the audit link), which opens our website and shares the tested site's domain name, the test result, and the names of ad vendors involved.
What the extension does on your device
- Sends GPC. While "Send GPC signal" is on, the extension adds the
Sec-GPC: 1header to your browser's web requests and tells web pages thatnavigator.globalPrivacyControlis true. - Observes vendor requests. To detect trackers, it compares the addresses of network requests made by the tab you are viewing against a built-in list of known advertising and analytics services. This happens entirely in your browser.
- Notes ad cookie names. While GPC is on, the extension notes the names of known advertising cookies a page writes after the signal is sent (for example
_fbp), so it can report them. Cookie values are never read or stored, and the names stay on your device. - Tests extra pages only when you ask. If you choose "Also test 2 more pages on this site," the extension opens up to two pages from the same site in your tab during the test, then returns you to the page you started on.
- Keeps results briefly. Results for open tabs are kept in the browser's session storage, which Chrome clears when you close the browser.
- Remembers a few settings. Your GPC on/off setting, the date and version of the Terms of Use you agreed to on first run, whether to test extra pages, and a count of completed tests (used only to show a one-time request for a store review) are kept in the extension's local storage on your device. None of this is sent anywhere.
- Checks the site's GPC declaration. When you open the popup, it requests
/.well-known/gpc.jsonfrom the website you are viewing, without cookies. - Says no to cookie pop-ups for you (optional). While "Say no to cookie pop-ups for me" is on, the extension looks for consent pop-ups from known consent tools on the pages you visit and clicks the most private choice (for example "Reject all"). It uses DuckDuckGo's open-source Autoconsent rules, which are bundled inside the extension. Pop-ups it does not recognize are left alone. It can run a small number of fixed checks that come with those rules inside the page to confirm your choice was saved; it never runs code from outside the extension. You can pause it on any site or turn it off. It is on by default for new installs, and people updating from an earlier version are asked first.
- Keeps a weekly summary (optional). While "Keep a weekly summary on this device" is on, the extension keeps daily counts for up to 35 days: how many sites received your GPC signal, how many cookie pop-ups it answered for you, which consent tools those were, and how many sites contacted each advertising company on its list after GPC was sent. Past days hold numbers only. To avoid counting a site twice, the names of sites you visited today are kept until the day ends and are then deleted. You can clear the summary at any time, and turning the setting off deletes it.
- Makes share images only when you ask. "Make my Privacy Receipt" and "Share my week" draw a picture on your device from the results already shown in the panel. Nothing is uploaded. You decide whether to copy, save, or post it. The picture includes the site name and the vendor names shown; check it before you share. It also includes a QR code that points to the extension's Chrome Web Store page.
- Reads a privacy policy only when you ask. "Read this site's privacy policy for me" looks for a privacy policy link on the page you are viewing, then requests that policy page from the website (as a normal page visit would, but without cookies). The extension checks the text for a few keywords on your device. If your computer supports Chrome's built-in on-device AI (the Summarizer), the extension also asks it to write a short summary; this runs on your device and the policy text is not sent to DigiBiz360. If Chrome needs to download its on-device AI model first, Chrome does that itself, and only after you click.
- Copies results only when you ask. "Copy test results" places a text summary on your clipboard. Nothing is uploaded.
When information leaves your device
Only when you click "Get a paid audit" (or the audit link) in the popup. That opens digibiz360.com/gpc-audit/ and passes the tested site's domain name, the test result, the names of ad vendors observed, and the extension version. This information is placed in the part of the link after the # (the fragment), which browsers do not send to web servers, so it is not recorded in our server logs. The page reads it only to prefill your request. Campaign tags identifying the extension as the source are sent in the normal way. Full request addresses are never included, because they can contain identifiers about you. If you then submit the request form, the details you enter, together with the prefilled information, are used only to respond to your request.
What the extension never does
- It does not send your browsing history, page contents, or request data to DigiBiz360 or anyone else.
- It does not use analytics, advertising, or tracking of its own.
- It does not sell or transfer user data to third parties, use it for purposes unrelated to the extension's single purpose, or use it to determine creditworthiness or for lending.
- It does not load or run code from outside the extension package.
The use of information received by this extension will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Our own pages and GPC
The DigiBiz360 pages the extension links to (the audit request page, this policy, the Terms of Use, and the methodology page) do not load advertising or analytics trackers.
Permissions and why they are needed
| Permission | Why |
|---|---|
| Access to all websites | To send the GPC signal to every site and detect vendor requests on whichever site you are viewing. |
| webRequest | To see which known vendor addresses a page contacts. Requests are only observed, never changed or blocked. |
| declarativeNetRequest | To add the Sec-GPC: 1 header to requests. To block requests to web addresses on the extension's built-in known-bad list (addresses that published security research has tied to attacks); this is on by default and you can turn it off in Settings. If you turn on "Back up my opt-out", also to block requests to the advertising companies on our list. All blocking happens inside your browser. |
| scripting | To run the "Say no to cookie pop-ups for me" rules on pages while that setting is on, to find a privacy policy link when you ask, to tell pages that GPC is on, to note the names of known ad cookies a page writes while GPC is on, to scroll the page and find same-site pages during a test, and to read the site's consent settings and any opt-out status message for the popup. |
| sidePanel | To show results in Chrome's side panel, next to the page you're viewing. |
| favicon | To show vendor icons from Chrome's own local icon cache. No request is sent to any vendor or to DigiBiz360 to display them. |
| storage | To remember your settings and Terms acknowledgment, keep results for open tabs, and keep the optional weekly summary counts. |
| Access to all websites (also) | To answer known cookie pop-ups on the sites you visit while "Say no to cookie pop-ups for me" is on, and to request a site's privacy policy page when you ask. |
Outside code checks. The extension notes which outside companies' code a page loads (host names only), whether the page has password or card fields (counted by type; what you type is never read), and whether the page contacts an address on the known-bad list that ships with the extension. These checks run on your device and nothing is sent anywhere. The known-bad list is part of the extension and is updated only through new versions; the extension does not download it.
Optional look-back. If you turn on "Keep a private 30-day look-back" (off by default), the extension stores, on your device only, which outside host names each site contacted on each day for 30 days, so it can warn you if one of them is later added to the known-bad list. You can clear it at any time, and turning the setting off deletes it. It is never sent to DigiBiz360 or anyone else.
Floating button. The extension can show small buttons at the edge of web pages that open the panel. The buttons do not read the page or send anything; you can hide them on one site or turn them off.
Settings kept on your device. Your choices are saved in your browser only: the GPC switch, the optional blocking switch, the list of sites where you paused blocking, whether known-bad blocking and look-back are on, whether "Say no to cookie pop-ups for me" and its on-page note are on, the list of sites where you paused it, how many pop-ups it has answered in total, light or dark mode, whether the floating button is shown and where you placed it, which view you last used, and which checklist steps you ticked. None of this is sent to DigiBiz360 or anyone else.
Open-source components. The cookie pop-up rules come from DuckDuckGo Autoconsent, licensed under the Mozilla Public License 2.0. DuckDuckGo is not affiliated with DigiBiz360 and does not receive any information from this extension.
Limits of the results
The extension reports what your browser can observe. Data a website shares from its own servers is not visible to it. Results are technical observations, not legal conclusions or advice. See the methodology.
Changes and contact
If this policy changes, the effective date above will change with it. Questions: sales@digibiz360.com.