Eat My Cookies vs Consent-O-Matic
Consent-O-Matic is an excellent open-source project from Aarhus University. Philosophically, we're closely aligned — no backend, no tracking, privacy-first. The differences are in scope, maintenance pace, and features built around real-world edge cases.
| Feature | Eat My Cookies | Consent-O-Matic |
|---|---|---|
| Open Source | ✓ | ✓ |
| No Backend / No Cloud Component | ✓ | ✓ |
| No Tracking / No Analytics | ✓ | ✓ |
| Properly Rejects via CMP API | ✓ | ✓ |
| Accept All Automation | ✓ | ✓ |
| Custom Per-Category Preferences | ✓ | Limited |
| Per-Site Exceptions | ✓ | ✗ |
| Transparent Failure Warnings | ✓ | ✗ |
| CCPA Support | ✓ | Partial |
| GDPR Support | ✓ | ✓ |
| Shopify Customer Privacy API | ✓ | ✗ |
| Activity Log & Badges | ✓ | ✗ |
| Language Support | 6 languages | Multiple |
| Active Real-World Maintenance | ✓ | Less frequent |
| Price | Free | Free |
Where Consent-O-Matic excels
Consent-O-Matic was one of the first rigorous, API-based consent automation tools. It pioneered the approach of using CMP APIs rather than brute-force selector clicking. The Aarhus University team has done genuinely important work in this space, and the academic rigor shows in the tool's design.
Where Eat My Cookies goes further
Eat My Cookies adds per-site exception management, transparent failure warnings (so you always know when automation couldn't succeed), a five-layer fallback architecture for resilience, CCPA coverage for US publishers, Shopify Customer Privacy API support for storefronts, and an activity log with collectible badges. It's also more actively maintained for the kinds of real-world edge cases that break other tools — geo-specific flows, A/B tested banners, paywall-style consent gates.