Cookie Banner Auto-Rejecter

WHAT IT DOES

This script automatically rejects cookie consent banners on any webpage, saving you from manually clicking "Reject" or "Decline" on every site you visit. When a cookie banner appears, the script scans the banner for reject buttons, decline buttons, or settings/preferences links that allow you to refuse non-essential cookies. It automatically clicks the appropriate button, dismissing the banner. A toggle lets you enable or disable the auto-rejection. You can whitelist specific sites where you don't want the script to interfere. A manual "Reject cookies now" button lets you trigger the rejection at any time. The script updates dynamically as new banners load, and it works across all websites.

WHERE IT RUNS

The script runs on all websites (*://*/*), making it truly universal. It works on any page with cookie consent banners—news sites, e-commerce, blogs, corporate sites, and more. It supports both desktop and mobile views.

HOW TO USE

After installation, the settings panel appears on the left side of the screen with the gear emoji (⚙️). Open the panel to configure the script:

- The "Enable auto-rejection" toggle enables or disables the automatic rejection.

- Add domains to the whitelist (one per line) to prevent the script from rejecting cookies on specific sites.

- Click "Reject cookies now" to manually trigger rejection on the current page.

- Click "Clear processed banners" to reset the list of processed banners and re-scan the page.

The script works automatically—just browse the web and cookie banners will be rejected when they appear.

TECHNICAL SECTION — REAL MECHANISM

The script detects cookie banners by scanning the page for elements with common cookie-related class names and IDs (.cookie-banner, .cookie-notice, .gdpr-consent, #cookie-popup, .cc-window, .privacy-banner, and many others). It also scans all div, section, aside, footer, and main elements for text containing "cookie" or "cookies" combined with "accept," "reject," "consent," or "privacy." When a banner is found, the script searches for reject buttons by looking for elements with text or aria-label containing "reject," "decline," "deny," "refuse," "no," or "necessary only." It also looks for settings or preferences buttons as a fallback, and finally for close or dismiss buttons (X). If a reject button is found, the script simulates a click on it using both click() and a MouseEvent with proper bubbling to ensure React/Vue event listeners are triggered. A WeakSet tracks processed banners to avoid duplicate work. A MutationObserver watches for DOM changes and re-scans for new banners.

THE PANEL

The settings panel is built with BotGentz's BGPanel component. It is draggable via its header, allowing you to reposition it anywhere on the screen. The panel snaps to the left edge by default but can be moved freely. Click the gear emoji to collapse the panel into a small bubble, and click the bubble to expand it again. The panel remembers its position per page session. Press the Escape key to quickly close or minimize the panel. The panel includes a status flash bar that provides visual feedback when settings are changed or actions are performed. All settings and the whitelist save automatically via GM_setValue.

PLEASE NOTE

This script requires the free BotGentz browser extension to run. It does not function as a standalone Chrome extension and does not use chrome.* APIs. Some cookie banners may use non-standard button labels or require multiple clicks to fully reject. The script attempts to find the most appropriate button but may not work on all banners. Some sites may require you to make choices before rejecting—the script will try to find settings buttons if reject buttons are not available. The whitelist allows you to disable the script on sites where you want to manage cookies manually. The script stores only your preferences and whitelist via GM_setValue. No data is sent externally—all processing is performed locally in your browser. The script never reads or writes password fields, hidden inputs, or file inputs. All DOM operations use safe methods (style properties, textContent, appendChild) and never use innerHTML.