Privacy Policy
Pixel Log — Meta Pixel Event Logger — Chrome Extension. Last updated: September 5, 2026
Summary
- Pixel event data is processed and kept locally on your device
- The extension only watches pixel events — it never alters or blocks them
- Your personal details, browsing history, and pixel data are never sold or shared
- Nothing is shared with Meta/Facebook, ad networks, analytics services, or data brokers
- No usage tracking, no analytics, no telemetry, and no crash reporting
- The extension sends no outbound network requests of its own — nothing leaves your device because of us
1. Data Collection
Everything the Extension collects and processes stays local to your device:
Data you provide:
- Extension settings (filter choices, auto-clear timing, appearance preferences)
Data picked up automatically (for inspection only):
- Names of Meta Pixel events seen on pages you visit (such as PageView, Purchase, AddToCart)
- Parameters attached to those events (such as value, currency, content_ids)
- Pixel IDs found on the page
- The page URL and timestamp for each recorded event
- Per-domain counts of detected pixels
Data that is never collected:
- No names, emails, addresses, or other identifying details
- No payment or financial information
- No browsing history, cookie contents, or cache
- No device identifiers
- No usage analytics or crash reports
2. Data Handling
All inspection happens locally on your device:
- A small detector script on each page listens for the Meta Pixel activity the page itself generates — the same approach used by standard pixel debugging tools
- Recorded events sit in memory and appear in the side panel for you to review
- Event logs are kept locally according to the retention setting you choose
- Exports (JSON/CSV) are produced on your device when you press Export
- Your pixel event data is never sent to us, to Meta/Facebook, or to anyone else
- The Extension watches pixel events — it does not change, block, or otherwise interfere with them
3. Data Storage
Everything the Extension stores lives on your local device:
- Storage mechanism: chrome.storage.local — built into the browser and sandboxed per extension
- Location: your own browser profile, on your own machine
- Event logs: kept temporarily and cleared based on your settings or manually
- Settings: kept until you reset them or remove the Extension
- No cloud storage and no server-side copy of any pixel or browsing data
To wipe everything at any time:
- Hit "Clear" in the side panel to erase all event logs
- Remove the Extension — all locally stored data goes with it
4. Network Requests
The Extension works fully offline. It does not send data anywhere — not to us, not to Meta/Facebook, not to any third party.
- No install, update, or uninstall pings are sent
- No anonymous identifiers or version signals are transmitted
- No analytics, telemetry, or crash-report calls of any kind
- The only network activity you will notice is the Meta Pixel traffic the pages you visit already produce — the Extension simply watches it; it does not create or forward it
5. Data Sharing
We never sell, rent, or trade your data. Your pixel event data and browsing activity remain on your device.
Your data is never shared with:
- Meta / Facebook
- Advertising networks
- Analytics providers
- Data brokers or anyone else
6. Permissions and Why They Are Needed
The Extension asks only for the permissions its features require:
storageKeep your preferences and short-term event logs on your device using chrome.storage.local.
alarmsRun periodic housekeeping, such as trimming old event log entries, in the background.
sidePanelShow the extension inside a browser side panel rather than a cramped toolbar popup.
host access (all sites)Meta Pixels can live on any domain, so the detector has to be able to run on whatever page you are inspecting. This access is used purely to find and read pixel activity on the page in front of you.
content scripts (all frames)A pair of small scripts runs on the pages you browse — one watches pixel activity from within the page, the other relays what it sees to the side panel in an isolated context. They also run inside iframes so embedded pixels are caught. The scripts only observe pixel traffic — your page content is not read out or transmitted anywhere.
7. No Tracking or Analytics
No usage analytics, no crash reporting, no telemetry of any kind. How you use the Extension, which sites you inspect, and how many events you look at are not tracked. None of your data is gathered, sent, kept on our servers, or given to anyone.
8. Changes to This Policy
This policy may be revised occasionally. Notable updates will be announced on the Extension's Chrome Web Store listing along with a new "Last updated" date here. If you keep using the Extension after a change, you accept the revised policy.
9. Contact
Questions about privacy or data requests? Reach us via the Chrome Web Store listing page for Pixel Log — Meta Pixel Event Logger.