Eat My Cookies vs I Still Don't Care About Cookies
I Still Don't Care About Cookies is an independent, open source continuation of the original I Don't Care About Cookies extension, created after concerns grew about that project's corporate ownership. It keeps the same filter-list approach to hiding cookie banners.
| Feature | Eat My Cookies | I Still Don't Care About Cookies |
|---|---|---|
| Open Source | ✓ | ✓ |
| No Backend / No Cloud Component | ✓ | Unclear |
| No Tracking / No Analytics | ✓ | Unclear |
| Properly Rejects via CMP API (not just hides) | ✓ | ✗ |
| Accept All Automation | ✓ | Primarily |
| Custom Per-Category Preferences | ✓ | ✗ |
| Per-Site Exceptions | ✓ | ✗ |
| Transparent Failure Warnings | ✓ | ✗ |
| CCPA Support | ✓ | Unclear |
| GDPR Support | ✓ | Banner-hiding only |
| Shopify Customer Privacy API | ✓ | ✗ |
| Activity Log & Badges | ✓ | ✗ |
| Independent / Not Acquired | ✓ | ✓ |
| Language Support | 6 languages | Multiple |
| Price | Free | Free |
Why this fork exists
I Still Don't Care About Cookies emerged as a community-maintained alternative after the original I Don't Care About Cookies extension was acquired and questions were raised about its direction. Being independent and open source addresses that ownership concern, but the underlying mechanism is unchanged: a curated filter list hides banners visually. Eat My Cookies was built around a different premise — that consent should be recorded with the site's own consent platform, not just removed from view.
What I Still Don't Care About Cookies does well
It's open source and independently maintained, with no corporate acquisition behind it — a direct response to the ownership concerns around the original IDCAC. It inherits a broad, community-curated filter list and hides banners quickly with little configuration needed.
Where Eat My Cookies differs
Instead of hiding a banner's visual presence with filter rules, Eat My Cookies speaks to each site's actual consent platform API to record a structured choice — reject all, accept all, or custom categories — the way the site's own privacy infrastructure expects. It also adds per-site exceptions, transparent failure warnings, a CCPA opt-out toggle, and an activity log, none of which a pure filter-list approach provides.