Tag Inspector — Privacy Policy

Last updated: 26 May 2026

The short version Tag Inspector runs entirely in your browser. It looks at the page you're on to detect tracking tags. It does not collect, store, or send any data to us or anyone else. No accounts, no telemetry, no remote servers.

What Tag Inspector does

Tag Inspector is a Chrome extension built for developers and marketers. It detects tracking tags and cookie-consent platforms on any webpage you visit, and shows what it finds in a popup and side panel.

It currently identifies 12 tracking platforms — Meta Pixel, LinkedIn Insight Tag, GA4, Google Tag Manager, TikTok Pixel, Google Ads, Twitter/X, Pinterest, Snapchat, Bing UET, HubSpot, and Hotjar — along with cookie-consent platforms more broadly.

Data we collect

None. Specifically:

What the extension looks at locally

To detect tracking tags, Tag Inspector inspects the active webpage. Everything happens inside your browser and stays on your device.

Local storage

The extension uses chrome.storage.session to keep detection results for the current browser session, so the popup and side panel can show them as you move between pages. Session storage clears automatically when you close the browser. The extension does not use chrome.storage.local, chrome.storage.sync, IndexedDB, cookies, or any other persistence layer.

Permissions and why each is needed

Third-party services

Tag Inspector uses no third-party services, APIs, SDKs, analytics, or remote configuration.

The extension does detect tags belonging to third parties (Meta, Google, LinkedIn, and so on) on the pages you visit. Those tags are placed by the website owner, not by Tag Inspector. The extension does not communicate with any third party; it only notes that their tags are present.

Children's privacy

We do not knowingly collect data from anyone, including children under 13.

Changes to this policy

If we update this policy, we'll post the changes here with a new date.

Contact

If you have questions about this privacy policy, please open an issue on our GitHub repository or write to nuvix.studio.