Storage and policy versions

Storage adaptersCopy Anchor Link

Consent Cuisine stores one JSON record through a small adapter interface:

interface ConsentStorage {
  get(key: string): string | null;
  set(key: string, value: string): void;
  remove(key: string): void;
}

In browser applications, use createLocalStorage().

import { createLocalStorage } from "@consent-cuisine/core";

createConsentCuisine({
  storage: createLocalStorage(),
  storageKey: "my-product-consent"
});

For server-backed preferences, an encrypted client store, or a framework-specific cookie abstraction, provide an adapter that implements the same three methods.

Policy versionsCopy Anchor Link

Every record stores the policyVersion used when it was created. If the controller receives a different version, getConsent() returns null instead of an outdated record.

createConsentCuisine({
  policyVersion: "2026-10"
});

Increment the version when the categories, purposes, or policy meaning change enough to need a renewed choice. Do not change it for purely cosmetic copy edits.

Record shapeCopy Anchor Link

{
  version: "2026-10",
  updatedAt: "2026-10-11T12:00:00.000Z",
  categories: {
    necessary: true,
    preferences: false,
    analytics: true,
    marketing: false
  }
}

Labels are intentionally absent from the record. They can evolve without breaking your stored consent data.