Privacy Policy
Last updated: February 2026
Summary
Hushbug collects no user data. No analytics. No telemetry. No phone-home after license validation.
Every detection, suppression pattern, baseline snapshot, and setting lives in
chrome.storage.local
on your machine and nowhere else.
Data storage
All data generated by Hushbug is stored locally in your browser using the Chrome storage API. This includes detected issues, suppression rules, baseline snapshots, user settings, and license keys. No data is transmitted to any external server during normal operation.
Network requests
Hushbug makes exactly one network request: validating your license key with Stripe when you activate a Pro subscription. This request sends only the license key. No browsing data, no detection results, no personal information. After validation, the extension makes no further network requests.
Permissions
- storage -- Stores detected issues, settings, suppression rules, and baselines locally.
- sidePanel -- Opens the issue review panel when you click the extension icon.
- activeTab -- Reads the current page URL and sets the per-tab badge count.
- alarms -- Runs periodic cleanup to evict old issues (every 30 minutes).
No host permissions. No remote code execution. No debugger permission.
Third parties
Hushbug does not share data with any third parties. The only third-party service involved is Stripe, which processes Pro subscription payments. Stripe's handling of payment data is governed by Stripe's privacy policy.
Content script behavior
Hushbug injects a content script into pages you visit to detect issues. The script patches browser APIs (console.error, fetch, XMLHttpRequest) and uses PerformanceObserver and MutationObserver to detect problems. All detection data stays within your browser. The content script does not read, collect, or transmit page content, form data, passwords, or personal information.
Contact
For questions about this privacy policy, contact us at privacy@hushbug.dev.