Effective date: August 26, 2026 Last updated: September 22, 2026

ClickSnitch (“we”, “our”, or “the Extension”) is a browser privacy inspection tool. We believe in absolute privacy, transparency, and data sovereignty.

1. Core privacy guarantee: 100% local execution

ClickSnitch does not collect, store, transmit, or monetize any of your personal data.

• All network sniffing, DOM event correlation, corporate-parent mapping, and forensic visualizers execute 100% locally inside your browser.
• ClickSnitch maintains zero external servers, zero backend databases, zero telemetry services, and zero analytics trackers.
• Your browsing history, visited URLs, inspected payloads, and cookies never leave your device.

2. Information handled locally on your device

ClickSnitch processes the following data exclusively within your local browser memory:

1. DOM interaction events: captures clicks, form submissions, and scrolls solely to correlate them with outgoing network requests within a short (roughly one-second) attribution window.
2. Network requests: observes HTTP/HTTPS request URLs, methods, headers, bodies, and beacons on the pages you visit — including sub-frames and requests that fire before the in-page script loads — to detect third-party trackers and display security insights.
3. Local preferences: stores your settings (such as light/dark theme, custom blocked domains, and trusted-domain lists) locally on your device via chrome.storage.local.

3. Chrome permissions & why they are used

ClickSnitch only requests permissions strictly necessary for its core functionality:

• declarativeNetRequest / declarativeNetRequestWithHostAccess — used to implement 1-click tracker-domain blocking (“Shield Me”) directly via Chrome’s native network engine.
• webRequest — used in observation mode only (no blocking) so ClickSnitch can see every network request a page makes — including tracking pixels, sub-frame requests, and requests that fire before the in-page script loads — and report the real HTTP status code. Request data is read in memory on your device and never transmitted.
• storage — used to save your settings and blocklists locally on your computer.
• cookies — used by the Cookie Vault to inspect first-party vs. third-party tracking flags (HttpOnly / SameSite / Secure) on the active tab.
• sidePanel — used to render the privacy dashboard alongside your active web page.
• notifications — used to alert you when aggressive third-party trackers or data leaks are detected.