Web Sniffer Privacy Policy

Last updated: June 7, 2026

Web Sniffer is a Chrome DevTools extension for monitoring and validating analytics network traffic. This policy describes what data the extension handles and how it is used.

Data stored locally on your device

• Captured network data — Request and response bodies, headers, and extracted analytics events are processed inside Chrome DevTools. They remain on your machine in extension storage and session memory. Web Sniffer does not upload captured network traffic to our servers.
• Saved collections, rules, and filters — Snapshots, header rules, and user preferences are stored in chrome.storage.local on your device only.
• Authentication session — If you sign in, your Firebase auth token and basic profile (email) are cached locally so you stay signed in between DevTools sessions.
• License key — If you activate a Pro license, the key is stored locally for offline validation.

Data sent to third-party services

• Firebase Authentication — When you create an account or sign in, your email address and authentication credentials are sent to Google Firebase to verify your identity. Google sign-in uses Chrome's OAuth flow.
• Firestore (app configuration) — The extension may fetch public app configuration (pricing, promo messages, version) from Firebase Firestore. No captured network data is written to Firestore.
• License validation — When you activate a license key, the key and your user ID are checked against Firestore license documents to confirm Pro access.
• Anonymous usage — When enabled, which DevTools tab you open (Network, Help, etc.) is logged as a one-line event with date and extension version. No captured traffic, no page URLs from the site you inspect.

What we do not do

• We do not sell your personal data.
• We do not transmit captured HAR entries, analytics events, or page content to our servers.
• We do not track your browsing history outside the DevTools-inspected page context.

Permissions

Web Sniffer requests Chrome permissions to capture DevTools network data, run validation scripts in the inspected page, apply header/redirect rules, and manage sign-in. These permissions are used only to provide extension functionality described above.

Contact

Questions about this policy? Contact the developer through the Chrome Web Store listing support channel.