Privacy & Compliance
Transparency is core to HTTP Tracker Plus. We believe you should know exactly how your browser extension works and what data it interacts with.
TL;DR Summary
This is an open-source tool. We capture HTTP traffic for your debugging purposes only. All data stays in your browser. We don't have a server. We don't track you.
Data Collection & Usage
We do not collect, store, share, or transmit any of your personal data.
All data intercepted, analyzed, or modified by HTTP Tracker Plus stays locally on your device. We do not have servers to receive your data, and we do not use any third-party analytics services.
Key Privacy Facts:
- ✅ No Analytics: We do not use Google Analytics, Mixpanel, or any other tracking SDKs. We do not track your usage or clicks.
- ✅ No User Authentication: You do not need to create an account to use this extension. No email or identity verification is required.
- ✅ No Remote Code: All code is bundled within the extension package. We do not execute remote scripts.
- ✅ Local Storage Only: Settings and logs are stored in your browser's local storage (`chrome.storage.local`).
- ✅ No Cookies: This extension does not use cookies for tracking purposes.
- ✅ Zero Data Transmission: No network data is ever uploaded to a remote server or third party.
- ✅ Session Volatility: Captured data is purged when the extension tab is closed or the 'Clear' button is clicked.
Permissions Declaration
HTTP Tracker Plus requires specific permissions to function as a developer tool. We limit these permissions to the absolute minimum required for the core features.
| Permission | Justification |
|---|---|
cookies |
Necessary to display, analyze, and filter request/response cookies for recruitment and debugging. |
debugger |
Used to capture response bodies and detailed network timing data not available via standard APIs. |
declarativeNetRequestdeclarativeNetRequestFeedback |
Enables the user-defined URL blocking feature (simulating ad-blocks or failed endpoints) and provides feedback to the UI when a blocking rule is triggered. |
<all_urls> (Host Permissions) |
Required to monitor traffic on any site the user is debugging (general-purpose debugger). |
storage |
Used to save user preferences, persistent filters, and global exclusion patterns. |
tabs |
Needed to identify which tab a request originated from and provide the "Open Extension" functionality. |
webRequest |
Primary permission used to monitor and log network headers and metadata in real-time. |
webRequestBlocking |
Required for the "Add/Modify Headers" feature before requests are sent. |
Code Transparency & Auditability
Our code is open source and free of obfuscation. You can inspect the source code at any time on our GitHub repository to verify our privacy claims.
We strictly adhere to the Web Store policies against obfuscated code and hidden functionality. Community contributions are reviewed to ensure no privacy-invading code is added.
You can verify the contents of manifest.json and background scripts to confirm no
external API calls exist.
Official Store Compliance
- We comply with the Chrome Web Store User Data Policy ("Limited Use" disclosure).
- Non-Commercialization: We do not sell, trade, or rent user data to third parties.
Single Purpose Description
"HTTP TRACKER PLUS is a centralized network debugging utility designed to monitor, filter, and inspect HTTP requests and responses across all browser tabs in a single unified interface."