What PixelPeek records
On the pages you inspect, PixelPeek records: the names of Meta Pixel events the page sends, the parameters attached to them, which Pixel IDs are present, which frame each event came from, and the address of the page being inspected so detections can be grouped by site. It observes requests to Meta's collection endpoint only — traffic to any other destination passes through untouched.
Personal data and masking
Pixel events can include hashed user-data fields (such as em, ph, fn, ln). PixelPeek flags when these are present so you can verify your own hashing is working. Parameters are shown as the page sends them — the extension adds nothing and changes nothing.
Where the data lives
Detections for the tab you are inspecting are held in the extension memory while the tab is open. Your recent-detections history (page host, Pixel ID, event name, time) and your settings are held in the browser's local storage. There is no account, no sign-in, and no copy of your data outside this browser.
Retention and deletion
The history keeps your most recent detections — 25, 50 or 100, as you choose (50 by default) — and you can clear it at any time from Settings. Navigating a tab starts a fresh view for that tab. Uninstalling the extension removes all stored data with it.
Network activity
Your recorded event data never leaves your browser. The network traffic you see while using PixelPeek is the traffic the pages you visit already produce on their own — the extension watches it happen and does not generate, forward or modify it. The extension contacts exactly one website of its own: the PixelPeek product site, which hosts the release notes it opens after updates. That site keeps a record of the installed version so the notes match what you are running, and nothing else.
Sharing
Data recorded by the extension is never sold, rented or traded, and never shared with third parties — including Meta / Facebook, advertising networks, analytics providers and data brokers.
Exports
Exports (JSON, CSV or HTML report) are written from your local data on your device.
Permissions and why they are needed
storage — holds your detection history and settings on your device; nothing recorded is ever written to a server.
alarms — schedules the history housekeeping and checks the product site for release notes.
webRequest — observes requests to Meta's pixel collection endpoints so events can be listed. It is read-only: the extension never modifies, blocks or generates network traffic. A Meta Pixel can be installed on any website, and a developer testing one works across staging domains, client storefronts and third-party sites that cannot be listed in advance — which is why access is not limited to specific sites.
sidePanel — the inspector window opens as a Chrome side panel next to the page you are inspecting.
Access to the PixelPeek site — the extension's own product website only, which serves its release notes.
Children
PixelPeek is a developer tool and is not directed at children. It collects no personal information from anyone.
Changes to this policy
If this policy changes, the updated version is published on this page with a new date at the top. Continuing to use the extension after a change means you accept the revised policy.