Privacy policy
Pixel Data Layers Inspector. Effective date: 2026-10-12.
Published by Ceyhun Aksan (DNOMIA). The extension's single purpose is to help you inspect tracking data layers, event queues and configured object snapshots in the permitted frames of a tab you choose to record.
Summary
- No captured data is sent to the publisher or a server. No analytics, advertising or remote code.
- Sites are granted individually; recording requires an explicit Start in each tab.
- Masking is on by default. Raw values require a separate opt-in for each recording.
- Logs are local session data. Export creates a file under your control.
Data the extension handles
On a permitted site in a recording tab, it reads window.dataLayer and the global queues or objects you select in Settings. It handles event names, parameters, consent commands, configuration, container IDs, pixel display names and change snapshots. It also uses document and frame identifiers, load times and page paths to place records in the correct context.
These payloads may contain website content, browsing information, identifiers, purchase details and personal data such as names, email addresses, phone numbers or postal addresses. Depending on the site's payload, they may also contain financial, payment, authentication, health or other sensitive information. The extension does not separately read cookies, browser history, network request bodies, form fields or browser storage. Those values can still be present if the site puts them in a watched layer.
Pixel display names are obtained only from a matching parent's initialize message. The pixel-name feature does not read customer initialization data, cookies or pixel API settings.
Purpose and use
Data is used only to show you the tracking payloads, their source and changes, and to provide search, filters, grouping, Copy and Export. The extension has no user account, backend, telemetry or monetization of captured data. The publisher has no access to your local log.
Masking and consent
Before Start, the panel presents the data disclosure and requests site access. The accepted disclosure version is stored locally. Masking starts on for each recording. Known personal keys, user_data and address subtrees, and email patterns are masked in the collector and checked again by the service worker before storage. URL query strings and fragments are removed from labels; common checkout and order tokens in paths are masked.
Masking is best effort and is not anonymization. Unknown fields, identifiers or unusual personal values may remain. Raw mode is an explicit opt-in for this recording only. Turning it off masks new entries but does not rewrite earlier raw entries. Copies and exports can include those earlier values. Do not share a file without reviewing its contents.
Storage, retention and deletion
- Logs and recording state are kept in chrome.storage.session, which Chrome holds in browser memory. Tab closure triggers log deletion; browser closure ends the session. If the worker stopped during tab closure, startup removes orphaned logs before accepting collection. Extension reloads or updates may also clear session data.
- There are bounded entry and storage budgets. The extension trims old records and reports dropped counts; a frame's Container Loaded summary may outlive trimmed entries.
- Settings, chosen layer names and the accepted disclosure version are kept in chrome.storage.local until changed or the extension is removed. Chrome stores site grants separately.
- Stop ends collection and keeps the log. Removing a site grant immediately rejects new lines and clears matching visible history, including older pages in other tabs. Matching stored pages and frames are deleted on the write queue. If storage cleanup fails, the panel warns and retries; startup also removes revoked-origin data. This is not a secure-erasure guarantee for operating-system memory.
- Export saves a JSON file only on your click. Copy places chosen data on your clipboard. Downloaded files and clipboard contents are outside the extension's retention control; delete them using your operating system.
Session memory and export files are not encrypted by this extension. Unexpected termination can lose records that have not finished writing.
Sharing and external pages
The extension does not transfer, sell or share captured data, use it for advertising, profiling, credit decisions or lending, or let the publisher read it. If you voluntarily email support with a file, the publisher will receive what you send; sanitize it first. No uninstall feedback page is opened.
The guide, privacy policy and optional support link open ordinary web pages only when selected. Visiting this site sends normal web-request information to its host, Cloudflare, independently of the extension log. The authored product pages contain no publisher analytics, embedded forms or remote fonts. Cloudflare may add email-decoding and browser-security scripts to the delivered pages and process browser signals or set security cookies for bot detection. This hosting activity is separate from the extension and receives no captured extension payload. External coffee and contact links are governed by their providers' policies. No captured payload is appended to their URLs.
Permissions
| Permission | Purpose |
|---|---|
| sidePanel | Display the inspector next to the recorded tab. |
| storage | Keep local settings and bounded session logs. |
| activeTab | Read the clicked tab's current site so the grant request is scoped to it. |
| scripting | Register locally packaged reader scripts on explicitly granted sites. |
| https://*/*, optional | Allow a site-specific HTTPS grant when Start is clicked. No blanket host grant is requested at installation. |
Limited Use
The extension's use of information adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only for the disclosed inspection features and is not transferred for unrelated purposes or advertising. The publisher does not obtain or read captured data.
Changes and contact
If handling changes, this page and its effective date will be updated before publishing the new version. Questions or a deletion request for information you voluntarily sent to support: [email protected].