What data is collected
The extension does not collect, transmit, or sell any personal data. All processing happens locally on your device.
When you visit a webpage, the extension analyzes its source code to detect marketing tools and tracking pixels. The following information is stored locally:
- URLs of pages you have opened while the extension is active
- List of detected trackers, pixels, CMS platforms, and payment systems found on each page
- Public tracker IDs extracted from page code (e.g. Google Analytics measurement ID, Yandex Metrica counter ID)
- Names and types of intercepted analytics events (e.g. "Purchase", "Lead", "PageView")
The extension does not collect:
- Personal information (names, emails, passwords, payment data)
- Contents of forms or user inputs on visited pages
- Cookies or authentication tokens
- Browsing history beyond the extension's own scan log (max 50 entries)
How data is stored
All data collected by the extension is stored exclusively using chrome.storage.local — a browser-managed storage that resides entirely on your device.
- Data is never uploaded to any remote server
- Data is never shared with the developer or any third party
- Per-tab scan results are automatically removed when you close that tab
- The scan history is limited to 50 entries and can be cleared manually at any time
Network requests
The extension makes exactly one type of outgoing network request, and only under a specific condition: when you open the extension popup on an HTTPS page, it sends a HEAD request to that page's origin in order to verify the validity of its TLS/SSL certificate.
- The request targets only the origin of the page currently open in your browser tab
- No user data, cookies, or identifiers are included (
credentials: 'omit') - The response body is not read — only the success or failure of the connection is used
- The extension never contacts any server belonging to the developer
The extension also intercepts outgoing network requests made by the page itself to known tracker domains (e.g. Google Analytics, Facebook Pixel). This interception is read-only: the URL is inspected to confirm a tracker fired, but the request is not modified, blocked, or logged beyond noting the tracker name and event type.
Permissions explained
The extension requests the following browser permissions:
| Permission | Why it is needed |
|---|---|
| storage | Stores scan history (max 50 entries) and per-tab results locally on your device using chrome.storage.local |
| tabs | Required to update the extension icon badge with the count of detected trackers and to communicate with content scripts running in the active tab |
host_permissions<all_urls> | The extension must be able to analyze any webpage you visit on demand. Without access to all URLs, it could not detect trackers on arbitrary sites |
| web_accessible_ resources | The file injected.js is injected into page context to intercept tracker JavaScript API calls (e.g. fbq(), ym(), gtag()). This is the only way to detect whether a tracker has actually fired at runtime |
Third-party services
The extension does not integrate with, report to, or depend on any third-party analytics, advertising, or data broker services.
The extension detects the presence of third-party tools on websites you visit — but this detection is entirely passive and local. The extension does not interact with those tools' servers on your behalf.
Data deletion
You can delete all locally stored data at any time:
- Open the extension popup
- Navigate to the "История" (History) tab
- Click the "Очистить" (Clear) button
Uninstalling the extension from Chrome will automatically remove all data stored by the extension via chrome.storage.local.
Contact
If you have questions about this privacy policy or the data practices of this extension, please contact the developer through the Chrome Web Store support page for this extension, or visit barakaev.ru.