The Tagfire Live Tag Debugger extension never sends the data it observes to our servers, third parties, or anywhere else. Here is exactly what it does and does not do.
Last updated: June 8, 2026
No telemetry
The extension does not phone home. There is no analytics or error reporting baked in.
No remote servers
Captured analytics traffic is relayed only inside your browser via window.postMessage.
No accounts
Using the extension does not require a Tagfire account or any sign-in.
The Tagfire Live Tag Debugger is a companion browser extension for the Tagfire Live Tag Debugger tool. While you have the tool open, you can attach the extension to a browser tab — either from the extension popup (“Capture this tab”) or from the Tagfire panel in your browser's DevTools, which attaches to the tab DevTools is inspecting. The extension then observes that tab's analytics activity and streams it into the debugger UI so you can inspect each hit in real time.
It observes two kinds of activity from the attached tab:
dataLayer and gtag pushes — the events your site itself sends into the Google Tag Manager queue.Capture is scoped to the tab(s) you explicitly attach — the one attached from the popup, plus any tab a Tagfire DevTools panel is open on. Every other tab is ignored.
The debugger can record a flow on the attached tab so you can replay it later and check which tags fire. While a recording is active, the extension captures the interactions you perform on that tab — clicks, form-field edits, dropdown and checkbox changes, form submissions, Enter keypresses, and page navigations — along with a CSS selector for the element and, where relevant, the value you entered. These steps stream into the debugger UI, the same way captured hits do.
Passwords are never recorded. The recorder ignores <input type="password"> fields entirely — it captures neither the value nor a value step for them. Recording only happens while you have explicitly turned it on for the attached tab; nothing is recorded otherwise.
Replay drives a saved recording by opening its start URL in a fresh tab and re-performing the recorded steps with synthetic events, so the resulting tags fire and can be inspected. The extension only opens http / https URLs for this.
Nowhere outside your browser. The observed hits are relayed from the extension's background worker to the Tagfire debugger tab through the browser's own messaging APIs and window.postMessage. Tagfire's servers never receive any of this data. The extension makes no outbound network requests of its own.
The debugger UI keeps the most recent captured hits in memory only. Closing or reloading the debugger tab discards them. Nothing is written to disk by the extension except the tab-id of the tab you are currently attached to (see “Storage” below).
Recorded steps are relayed the same way — in-browser, into the debugger tab. If you then choose to save a recording, the Tagfire web app stores it to your account so you can replay it later; that persistence is performed by the web service and is covered by our main privacy policy, not by the extension. The extension itself never persists or transmits recordings on its own.
webRequest — needed to observe outbound analytics beacons fired by the attached tab. The extension only reads request URLs and bodies; it never blocks, cancels, or modifies a request.tabs — lets the extension read the attached tab's URL and title (so the popup and debugger can show what is attached and label each hit with the page it fired on), and open, navigate, or close the replay tab during a replay run. It is not used to read the contents of any tab.<all_urls> — analytics can fire from any site, so the observer has to be able to watch from any site. The extension processes hits only from the tab(s) you explicitly attached, and it never reads page content outside of what the page itself pushed into dataLayer / gtag (plus the interactions you perform while a recording is active — see above).storage — remembers the id of the tab you are currently attached to so capture survives the extension worker going idle. Stored in chrome.storage.session, cleared when the browser closes or when you detach.The extension does not:
dataLayer / gtag pushes and the interactions you perform while recording,The only thing the extension writes is the tab-id of the tab you have currently attached, stored in chrome.storage.session. Session storage is cleared automatically when the browser closes, and the extension also clears the entry the moment you detach or when the attached tab closes.
Captured hits themselves are never persisted. They live in the debugger tab's memory and disappear on reload.
Tagfire's use of information received from browser extension APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not transfer user data to third parties except as necessary to provide or improve the extension, comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to users. We do not use user data for advertising, including personalised, retargeted, or interest-based advertising. We do not allow humans to read user data unless we have your affirmative consent for specific instances, it is necessary for security purposes such as investigating abuse, to comply with applicable law, or the data is aggregated and used for internal operations.
The extension is not directed at children under 13, and we do not knowingly collect data from children.
If we update this policy we will change the “Last updated” date at the top and, for material changes, mention it in the extension release notes on the Chrome Web Store.
Questions or concerns about extension privacy? Email hello@tagfire.app. For the broader Tagfire web service, see our main privacy policy.