Privacy policy: Pixel Radar

Last updated: 4 September 2026

In short

Pixel Radar does not collect, transmit or sell any data. It has no server, requires no registration, uses no cookies and contains no analytics or telemetry. Everything it processes stays in your browser.

What it processes, and where that stays

To do its job the extension processes the following locally:

• the domain name of the active tab, shown at the top of the popup;
• the request URLs sent to a closed list of 38 tracking-platform domains, and their parameters;
• the presence in the page of the tags' global variables (fbq, ttq and so on) and of the account IDs they expose;
• the state of the consent management platform, where one is present.

This data is held in chrome.storage.session, a temporary area of browser memory, separately for each tab. It is deleted automatically when the tab changes domain, when the tab is closed, and when you close the browser. No copy exists anywhere else.

What it does not do

• It does not send data to external servers, neither to us nor to third parties.
• It does not track your browsing or build profiles.
• It does not read page content, the forms you fill in, your passwords or your cookies.
• It contains no remote code: everything that runs is included in the package and reviewed by the Chrome Web Store.
• It contains no advertising.

Exports

The JSON and CSV buttons generate a file on your own device, and only when you ask for one. The file contains the data shown in the popup. Nothing is sent over the network.

Why each permission is needed

Access to data on all websites (<all_urls>)

This is the permission that looks most invasive, and the one that deserves the longest explanation. Since Chrome 72, the API that observes network requests only reports a request to an extension if that extension has permission for both the domain being contacted and the page that originated the request. Since any page at all can contact a pixel, the permission has to cover any page. The code, however, only observes a closed list of 38 domains belonging to tracking platforms: requests to any other domain are never examined, and no page content is ever read.

Request observation (webRequest)

Read-only. The extension never blocks, modifies or redirects any request.

Storage (storage)

Session memory, used to hold detections while the tab is open.

Tabs (tabs)

To read the tab's domain and to clear the data when it changes.

Scripting on the active tab (scripting, activeTab)

To inspect the page for tags, only on the active tab and only at the moment you open the popup. No script is permanently injected into pages.

Children

The extension is not intended for children under 13 and does not knowingly collect data relating to them. Then again, it does not collect data at all.

Changes

Any updates to this policy will be published on this page, with the update date revised. Substantive changes will also be noted in the extension's release notes.

Controller and contact