Privacy Policy

1. Data Collection

The Extension collects and processes the following data locally on your device only:

User-provided data:

• Extension settings and preferences (filter preferences, auto-clear interval, display options)

Automatically collected data (for debugging purposes only):

• Meta Pixel event names observed on pages you visit (e.g., PageView, Purchase, AddToCart)
• Event parameters included in those pixel fires (e.g., value, currency, content_ids)
• Pixel IDs present on the page
• Page URL and timestamp at the time of each pixel event
• Domain statistics (which domains have pixels detected)

Data NOT collected — ever:

• No personal identification information (name, email, address)
• No payment or financial data
• No browsing history, cookie values, or cached content
• No device identifiers
• No usage analytics or crash reports

2. Data Handling

All debugging data handling occurs locally on your device:

• Pixel events are captured on-page by a lightweight detector script that watches the Meta Pixel activity the page itself produces — the standard technique used by pixel debugging tools
• Captured event data is held in memory and displayed in the Extension side panel for your review
• Event logs are stored locally per your configured retention setting
• Event exports (JSON/CSV) are generated locally and saved to your device when you click Export
• Your pixel event data is never sent to us, to Meta/Facebook, or to any third party
• The Extension observes pixel events — it does not modify, block, or interfere with them

3. Data Storage

All debugging data is stored exclusively on your local device:

• Storage mechanism: chrome.storage.local — browser-native, sandboxed per extension
• Location: your local browser profile on your device
• Event logs: stored temporarily; auto-cleared based on your settings or on manual clear
• Settings: persist until you reset them or uninstall the Extension
• No cloud storage and no server-side storage of your pixel or browsing data of any kind

You can delete all stored data at any time by:

• Clicking "Clear" in the Extension panel to clear all event logs
• Uninstalling the Extension — this automatically removes all locally stored data

4. No Network Requests

The Extension operates entirely offline. It makes no outbound network requests of its own — no data is transmitted to us, to Meta/Facebook, or to any third party at any time.

• No install, update, or uninstall pings are sent
• No anonymous identifiers or version signals are transmitted
• No analytics, telemetry, or crash-reporting requests are made
• The only network traffic your browser sees is the Meta Pixel requests that the pages you visit send on their own — the Extension merely observes these; it does not generate or forward them

5. Data Sharing

We do not sell, rent, or trade your data with any third parties. Your pixel event data and browsing activity stay on your device.

We do NOT share data with:

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

6. Permissions and Why They Are Needed

The Extension requests only the permissions required for core functionality:

• storage

  Save your settings and temporary event logs locally on your device using chrome.storage.local.

• activeTab

  Read the active tab's context when you open the panel, so events are shown for the page you are currently viewing.

• scripting

  Inject the pixel detector script into pages so Meta Pixels can be found and monitored on the page.

• sidePanel

  Display the extension as a browser side panel instead of a small popup.

• alarms

  Schedule automatic event log cleanup and lightweight background housekeeping tasks.

• host access (all sites)

  A Meta Pixel can appear on any domain, so the detector must be able to run on any page you choose to inspect. Access is used only to detect and read pixel activity on the page in front of you.

• content scripts (all frames)

  Two small scripts run on the pages you visit — one in the page context to detect pixel activity and one in an isolated context to relay it to the panel. They run in subframes too, so pixels inside iframes are not missed. The scripts only observe pixel activity — they do not read or transmit your page content.

7. No Tracking or Analytics

Zero usage analytics, zero crash reporting, zero telemetry. We do not track how you use the Extension, which websites you visit, or how many events you inspect. None of your data is collected, transmitted, stored on our servers, or shared with anyone.

8. Changes to This Policy

We may update this Privacy Policy from time to time. Significant changes will be communicated via the Extension's Chrome Web Store listing and by updating the "Last updated" date on this page. Continued use after changes constitutes acceptance of the updated policy.

9. Contact

For privacy questions or data-related requests, contact us through the Chrome Web Store listing page for Pixel Tap — Meta Pixel Inspector.