CookieMaster Privacy Policy
Last updated: 23 April 2026
CookieMaster is a Chrome extension published by PRIME AXIS LLP, a limited liability partnership registered in Singapore ("we", "us"). It auto-dismisses cookie consent banners and cleans up third-party tracker cookies. This policy explains exactly what the extension does with data on your device.
Short version: CookieMaster does not send any of your data anywhere. It runs entirely in your browser.
Your use of the Software is also governed by our Terms and Conditions.
Chrome Web Store disclosure summary
For the Chrome Web Store data-practices form we declare:
• Personally identifiable information — not collected.
• Health information — not collected.
• Financial or payment information — not collected. The Software is free and does not process payments.
• Authentication information — not collected.
• Personal communications — not collected.
• Location — not collected.
• Web history — not collected.
• User activity (clicks, mouse, keystrokes) — not collected.
• Website content — read locally by the content script to find cookie banners, but never stored, copied, or transmitted off the device.
We further affirm:
• We do not sell user data.
• We do not transfer user data to third parties outside of the approved use cases.
• We do not use user data for purposes unrelated to the extension's single stated purpose: auto-dismissing cookie-consent banners.
Data we collect
CookieMaster collects no personal data and does not transmit any information to our servers or to any third party. We do not run analytics, telemetry, crash reporting, or A/B testing inside the extension.
The extension stores the following locally on your device only:
• Your settings — enabled/disabled state, default mode, per-site overrides, and debug flag — saved via Chrome's "chrome.storage.sync" API. If you are signed in to Chrome with sync turned on, Chrome (not us) mirrors this to your other signed-in devices. We never see it.
• Aggregate counters — number of banners dismissed, tracker cookies cleaned, and sites handled today — saved via Chrome's "chrome.storage.local" API. Shown as stats in the popup. Never leaves your device.
No browsing history, URLs, page contents, form inputs, credentials, clipboard data, or personally identifying information is stored, logged, or sent anywhere by the extension.
What the extension actually does on pages you visit
When you load a web page, CookieMaster runs a content script that:
(1) Reads the DOM to detect a cookie consent banner (by CSS selectors and heuristic text matching against button labels).
(2) Clicks the "reject all" or "only necessary" button on your behalf.
(3) In a last-resort mode (configurable), hides banners it could not dismiss via a CSS class.
Additionally, the background service worker:
(4) Uses the browser's "declarativeNetRequest" API to strip Cookie and Set-Cookie headers on requests to a fixed list of known third-party tracker domains (Google Analytics, Facebook Pixel, Hotjar, etc.).
(5) After a banner is dismissed, removes any cookies already set by third-party tracker domains via the "chrome.cookies" API.
These operations happen entirely inside your browser. The extension makes no outbound network requests.
Permissions, and why they are requested
Chrome asks for each permission at install time. Here's why each is needed:
• storage — to save your settings and stats locally (see Section 1).
• cookies — to remove third-party tracker cookies already set in your browser (see Section 2, step 5).
• tabs — to read the current tab's URL so per-site rules and the popup can show which site is active.
• declarativeNetRequest — to strip Cookie and Set-Cookie headers on known tracker domains (see Section 2, step 4). Rules are static, bundled in the extension, and inspected by Chrome itself — the extension cannot see the traffic they match against.
• alarms — to reset the "sites handled today" counter at the start of each day.
• host permissions on all URLs — required so the content script can run on any site you visit and interact with whatever banner appears. The script only looks at DOM elements that match cookie-banner patterns; it does not read, copy, or transmit page content.
Network requests
CookieMaster does not make any network requests to servers it controls. Specifically:
• It does not phone home on install, update, or uninstall.
• It does not fetch remote block or allow lists.
If a future version adds a network-dependent feature, this policy will be updated and Chrome will display any new permission prompt before the feature is enabled.
Third parties
The extension does not bundle any third-party analytics, advertising, tracking, or fingerprinting code. It does not share data with third parties because there is no data leaving your browser to share.
Children's privacy
CookieMaster is not directed at children under 13. We do not knowingly collect data from anyone, including children, because we do not collect data.
Security
Because no data leaves your device, there is no transit or server-side exposure surface. Your local storage is protected by Chrome's standard profile isolation. Uninstalling the extension removes its local data; sync'd settings are cleared if you remove them from chrome.storage or reset Chrome sync.
Your choices
• Disable the extension at any time from the popup's toggle.
• Add per-site rules in the options page to exempt specific sites.
• Uninstall the extension to stop all behavior and wipe local data.
Changes to this policy
If we change what CookieMaster does with data, we will update this document and bump the "Last updated" date above. Material changes will also be noted in the extension's release notes on the Chrome Web Store.
Contact
Data controller: PRIME AXIS LLP, Singapore.
For questions or concerns, email the contact address listed on the Chrome Web Store product page.