Crumble Chrome extension security report

**Crumble removes cookie consent banners from your browsing experience.** Most cookie banners aren't really about your privacy — they exist because regulators require *some* dialogue, but the actual choice they offer is usually take-it-or-leave-it. Crumble takes them off your screen so you can get on with what you came for. ## How it works Crumble combines three approaches, picking the most reliable one per site: 1. **Direct CMP integration.** Crumble talks to OneTrust, Cookiebot, Didomi, TrustArc and Quantcast Choice through their published JavaScript APIs. When a site uses one of those, dismissal is fast, clean and reliable. 2. **Per-site rules.** Thousands of sites are catalogued with specific CSS or click selectors built up over years of contributor effort. 3. **Generic fallback.** When no specific rule fires, a reactive default handler watches the DOM (via MutationObserver) and dismisses banners as they appear — including ones rendered inside Shadow DOM, which most extensions miss. ## Features - Banners hidden or auto-dismissed across thousands of sites - Consent flags persisted so banners don't reappear on revisit - Per-domain whitelist if you want Crumble to skip individual sites - Works on single-page apps (Reddit, X, YouTube, …) - Optional dark mode, keyboard shortcut (Alt+Shift+C), settings sync, 26-language UI auto-detected from your browser ## What Crumble doesn't do - No telemetry. No analytics. No accounts. No data sent to any server. - If you report a broken site, Crumble opens a pre-filled GitHub issue form in a new tab — *your* browser submits to GitHub directly, not us. - The optional Sync feature rides on Firefox Sync (no third-party endpoint). ## Open source GPL-3.0. Full source, rule database, and contributor guide: https://github.com/mntxsn/crumble Built on years of work by the contributors to the original *I don't care about cookies* projects — full credits in the repo README.