Overview
A headless consent engine with stable data and replaceable language.
Consent Cuisine is a headless, multilingual consent manager. It keeps consent state predictable while letting your product decide how that state is explained to people.
The technical record always uses category IDs such as necessary and analytics. Locale packs only decide what people see. This keeps integrations, reporting, and policy migrations independent from the language in your interface.
What belongs where
| Layer | Responsibility |
|---|---|
@consent-cuisine/core | Categories, consent state, persistence, policy versions, and subscriptions. |
@consent-cuisine/cuisines | Optional technical and cuisine-themed copy for each locale. |
| Your UI | The banner, modal, controls, design system, and accessibility decisions. |
The consent lifecycle
- Create a controller with a policy version and storage adapter.
- Render
getCategories()in your own UI. - Save a user choice with
save,acceptAll, orrejectOptional. - Read the stable record whenever a vendor or feature needs a decision.
- Change
policyVersionwhen an existing choice must be requested again.
necessary is always enabled. Optional categories are opt-in and can be reset at any time.
Choose your copy
Each bundled locale has conventional cookie copy plus cuisine variants. Choose a named variant for a consistent theme, use true for the locale default, or set cuisine: false when your interface should use conventional cookie labels.
Continue with Getting started to create a controller.