Privacy Policy

Summary

What Data the Extension Observes

To perform its monitoring function, the extension observes the following data on each web page you visit:

• Network request URLs — to identify known analytics, advertising, and session-recording tags by their URL patterns
• Request payloads — URL query parameters and POST body content sent by tag vendor endpoints, used to detect PII keys in the payload
• HTTP response headers — specifically Set-Cookie headers, to record cookie names, domain, and flag attributes
• Script tag sources — src attributes of <script> elements injected into the page, to identify tag manager libraries
• Consent interactions — clicks on known consent management platform (CMP) buttons and writes to localStorage matching consent key patterns

This data is used only to populate the extension popup and dashboard displayed to you. It is held in memory for the duration of your browsing session and is never written to any remote server.

Data Storage

Local in-memory state

All observed tag fires, cookie records, and activity events are stored in the extension's service worker memory (chrome.storage.session equivalent). This data is scoped to the current tab and cleared when you click the Clear button or when the tab is closed.

No persistent external storage

The extension does not write any browsing data to chrome.storage.local, chrome.storage.sync, IndexedDB, or any remote database.

External Network Calls

Tag & Cookie Sentinel itself makes no outbound network requests. It only observes requests made by the web pages you visit — it does not initiate any connections of its own.

The extension does not contact any analytics service, crash reporting service, or update server beyond the standard Chrome Web Store extension update mechanism managed by Google.

Permissions Used

• webRequest + host_permissions (<all_urls>) — required to observe network requests on all pages and identify tag vendor endpoints
• cookies — required to read cookie metadata for the compliance analysis (cookie names, domains, flags)
• tabs — required to associate observed requests and cookies with the correct browser tab
• scripting + content_scripts — required to inject the page monitor that detects dynamically loaded script tags and consent interactions
• storage — used only for per-tab in-memory state; no data is persisted between sessions
• alarms — used to keep the service worker active so no network events are missed
• notifications — used to alert you when a pre-consent tag fire is detected on the current page

Third Parties

This extension does not share any data with any third party. It does not include any third-party analytics SDK, advertising SDK, or remote logging service.

Children's Privacy

This extension is not directed at children under the age of 13 and does not knowingly collect any information from children.

Changes to This Policy

If this privacy policy changes materially, the updated version will be published at this URL. The extension version number in the Chrome Web Store listing will be incremented to reflect the change.

Contact

Questions about this privacy policy can be directed to support@cchk.info.