- Connected mode. Load a CookieChimp project’s scanner categories, dashboard copy and translations with config sync, and send decisions with the platform consent-log adapter. Your code config can remain the fallback.
- Category and vendor preferences. Render banner layouts, vendor details, cookie disclosures, themes and languages from the platform JSON. A complete service consent map and consent ID are available through React hooks.
- Local mode, no account. Consent lives in a first-party
cc_consentcookie. Your code owns the config. - No banner flash. The Next.js providers read the consent cookie on the server, so the first HTML already matches the visitor’s choice.
- Blocks before consent. Script and iframe gating, runtime blocking, a network blocker, Google Consent Mode v2 and presets for common vendors.
- IAB GPP (US) and TCF (EU), both opt-in and lazy.
- Small. Size budgets are enforced in CI (docs/size.md).
Where to start
- Connect to CookieChimp: dashboard configuration, platform consent delivery and the complete backend-connected example.
- Getting started: install and show a banner.
- React Native: the native banner, preferences, consent records and vendor control for React Native and Expo apps, available on npm.
- React Native vendor SDKs: presets for common mobile SDKs, Firebase Consent Mode and App Tracking Transparency.
- Banner and vendor preferences: shared JSON, appearance, consent state and the full variation playground.
- Next.js or the core and React reference.
- Examples you can run.
- AI skills for coding agents and the documentation index.