Privacy Policy

1. What Pixel Lint Observes

Pixel Lint is an inspector for Meta Pixel tracking. On the pages you visit, it observes:

• Calls the page makes to its own pixel function (fbq)
• Requests the page sends to Meta's collection endpoint, including the parameters attached to them
• Which pixel IDs are present, which frame each event came from, and how each event was sent
• The address and title of the tab being inspected, so recordings are grouped by page and reports are labelled

It observes requests to Meta's endpoint only. Traffic to any other destination passes through untouched and is neither read nor recorded. It does not read page text, form fields, images, cookies, local storage or the DOM beyond the pixel's own calls.

2. Personal Data and Masking

One class of problem this tool exists to catch is a website sending personal data — an email address, a phone number, a name — to Meta without hashing it first. To make that safe to inspect, values that look personal are masked the moment they are read: an email address becomes j***@e***.com, a phone number becomes +4*******58.

The original text is never written to storage and never shown in the panel, so a screenshot or screen recording of a debugging session is not itself a data breach. Exports contain the masked values, because no unmasked copy exists anywhere.

3. Where the Data Lives

All recorded data is stored in your browser, on your device:

• Event recordings:the browser's session storage, keyed by tab. Cleared automatically by the retention window, and discarded the moment the tab closes.
• Your settings:the browser's local storage. Kept until you change them or uninstall.

There is no account, no sign-in, and no copy of your recordings anywhere outside this browser.

4. Retention and Deletion

• Recordings are kept for the retention window you choose — 15, 30 or 60 minutes (30 by default) — and then deleted automatically
• Closing a tab erases that tab's recording immediately
• Clearing the recording from the panel erases everything recorded in it
• Uninstalling the extension removes all stored data with it

5. Network Activity

Your recorded event data never leaves your browser. The network traffic you see while using Pixel Lint is the traffic the pages you visit already produce on their own — the extension watches it happen; it does not generate, forward or modify it. Every wrapped call is delegated to the original with the original arguments.

There are no accounts, no analytics, no telemetry, no crash reporting and no advertising. The extension does not sell or share data with anyone.

6. Sharing

We do not sell, rent or trade your data. Data recorded by the extension is never shared with third parties, including:

• Meta / Facebook
• Advertising networks
• Analytics providers
• Data brokers or any other party

7. Exports

When you export a recording as JSON, CSV or curl commands, the file is written by the panel from its own data, on your device. It contains masked values only. Treat an export as you would any file containing debugging data.

8. Permissions and Why They Are Needed

The extension requests only what its features require:

• storage

  Recorded events are held in the browser's session storage, and your settings (language, theme, retention window, recording on or off) in its local storage. Both live on your device only. Session storage is what lets a recording survive the browser reclaiming the extension's background worker, which happens after a few seconds of inactivity. Nothing recorded is ever written to a server.

• alarms

  Once a minute, an alarm wakes the extension to enforce your chosen retention window: it deletes recorded events that are older than the limit and discards recordings belonging to tabs you have closed. This is the only way a promised time limit can be kept even on a tab that stops producing events.

• sidePanel

  The whole interface is a side panel, so the event stream stays visible while you interact with the page you are testing — something a popup, which closes the moment focus moves away, cannot do. This permission declares where the interface is drawn and grants no access to any data.

• host access (all sites)

  A Meta Pixel can be installed on any website, and a developer implementing one works across staging domains, client storefronts and third-party sites — none of which can be listed in advance. Access is used only to run two small observing scripts on the pages you visit and to read the address and title of the tab being inspected, so recordings can be grouped and labelled. Page content is not read.

• content scripts (all frames)

  One script runs in the page's own context to watch the pixel's fbq function and its network calls; the other relays what it saw to the side panel. They also run inside embedded frames — including frames with no URL of their own — because checkout, booking and donation widgets frequently carry their own pixel, and missing them is exactly the kind of mistake the tool exists to find. Every wrapped call is passed through to the original untouched: the page's tracking behaves exactly as it would without the extension.

9. Children

Pixel Lint is a developer tool and is not directed at children. It collects no personal information from anyone.

10. 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.

11. Contact

Questions about privacy or requests about data can be sent through the Chrome Web Store listing page for Pixel Lint — Meta Pixel Event Inspector.