Consent Guard av dan

Consent Guard helps reduce cookie-banner fatigue by looking for consent prompts and choosing the most privacy-preserving path available.

When a site shows a supported consent manager, Consent Guard clicks explicit reject or decline controls. If the prompt requires a preferences screen, it opens the settings view, turns off optional/vendor toggles where possible, and saves the rejected choices. For unfamiliar banners, it uses conservative text and visibility matching so it can reject obvious prompts without accidentally accepting cookies.

If Consent Guard misses a banner, the popup includes reporting shortcuts. Users can open the public Consent Guard support repository's Issues page and create a missed-banner report, or open an email draft to workshopx@proton.me.

The extension includes a simple popup for:

• Enabling or disabling the extension.
• Running the denial flow again on the current page.
• Pausing Consent Guard on the current site.
• Reporting a missed banner through the public GitHub support issue flow or an email draft.
• Viewing the last site handled.
• Viewing and clearing a local list of sites where consent was denied.

Consent Guard does not block network requests, hide banners as its primary action, clear existing cookies, read cookie values, or send browsing data to a remote service automatically.

Key Features

• Rejects common cookie consent managers.
• Opens settings and saves opt-out choices when direct rejection is not available.
• Handles consent prompts in frames where Firefox permits content-script access.
• Provides per-site pause controls.
• Lets users report missed banners through a public GitHub support repo or email.
• Stores only local settings and a capped denied-site list.
• Requests no cookie permission.

Permissions Explanation

activeTab: Used by the popup to rerun the consent-denial flow on the current active page when the user clicks Run.

storage: Used to save extension settings, paused sites, the most recent handled site, and the local denied-sites list.

Access to all websites: Consent prompts can appear on any website and inside embedded consent-manager frames. Consent Guard needs content-script access on HTTP and HTTPS pages to detect visible consent prompts and click reject, settings, toggle, and save controls.

Data Collection Declaration

This extension does not collect or transmit data outside the extension automatically. If the user chooses to report a missed banner, Consent Guard opens the public GitHub support issue flow or a prefilled email draft that the user can review before submitting.