DataLayer Inspector - Privacy Policy

Summary

DataLayer Inspector is designed with privacy as a priority. The extension processes all data completely locally on your device. No data is transmitted to external servers.

Purpose of the Extension

DataLayer Inspector serves a single, clearly defined purpose: to help digital marketers and developers monitor and debug dataLayer events within Chrome DevTools. The extension exclusively focuses on providing visibility into the dataLayer object used by tag management systems like Google Tag Manager, allowing users to inspect, filter, and analyze these events in real-time as they browse websites.

This functionality is essential for debugging tracking implementations, validating marketing tags, and ensuring data collection accuracy. All features within the extension—including URL filtering, event name filtering, and history tracking—directly support this core purpose of dataLayer monitoring without introducing additional unrelated functionality.

Data Collection and Usage

• DataLayer Inspector does not collect or store any personal data.
• All analyzed dataLayer events are processed exclusively locally in your browser.
• Your browsing session data is temporarily stored in memory and is deleted when you close your browser window or DevTools panels.
• No telemetry or analytics data is sent to the developer or third parties.

Required Permissions and Why We Need Them

DataLayer Inspector requires specific browser permissions to function correctly:

Storage Permission

We need the storage permission because DataLayer Inspector saves your filter preferences and settings between sessions. This allows the extension to remember which URLs you've selected to filter, your event filtering preferences, and your blacklist settings. Without this permission, your configuration would reset every time you close and reopen DevTools, creating a frustrating user experience when debugging across multiple sessions.

Scripting Permission

The scripting permission is essential for DataLayer Inspector to inject the necessary code that monitors the dataLayer object on web pages. This enables the extension to detect when new events are pushed to the dataLayer and capture their content in real-time. Without scripting permission, the extension would have no way to access or monitor the dataLayer events as they occur on websites.

Tabs Permission

The tabs permission allows DataLayer Inspector to track which tab is currently being inspected and maintain the correct association between dataLayer events and browser tabs. This ensures that when you have multiple tabs open with DevTools, the extension shows the appropriate dataLayer events for the specific tab you're debugging, preventing cross-contamination of event data between different websites you're working on.

DevTools Permission

This permission is required to create and display a panel within Chrome DevTools where you can view and interact with the dataLayer events.

Host Permissions

Host permissions (<all_urls>) are required because DataLayer Inspector needs to access and monitor the dataLayer across any website you visit. Since the extension is designed to help marketers and developers debug tracking implementations on various domains, it needs permission to read page content on any site where you might want to inspect the dataLayer. All processing happens locally in your browser - no data is sent elsewhere.

Transparency

DataLayer Inspector is built with transparency in mind. While it's not open source, it's designed to be completely focused on local data processing with no external connections.

Cookies and Local Storage

DataLayer Inspector only uses local storage to save your filter preferences. No cookies are set, and no information is stored on external servers.

Changes to This Privacy Policy

Any changes to this privacy policy will be posted on this page. The policy is effective as of January 1, 2025.

Contact

If you have any questions about this privacy policy, please contact me at [email protected].