@c15t/nextjs 2.2.0 → 3.0.0-alpha.0

package/docs/frameworks/next/styling/slots.md

@@ -1,94 +0,0 @@
----
-title: Component Slots
-description: Target individual component parts with styles using the slot system
-  - className strings or inline style objects.
-group: frameworks
----
-## What are Slots?
-
-Slots let you target specific parts of consent components with styles. Each component is built from named slots such as `consentBannerTitle` and `consentDialogTag`.
-
-Use slots after the stock component APIs and design tokens:
-
-* If the change is semantic, prefer tokens first. For example, the stock banner footer background comes from `theme.colors.surfaceHover`.
-* If the component part is correct but you need a local tweak, use a slot.
-
-Common banner slot choices:
-
-* `consentBannerCard` for card radius, shadow, width, and local background treatment
-* `consentBannerFooter` for spacing, borders, and local footer styling
-* `consentBannerTitle` for title typography
-* `buttonPrimary` and `buttonSecondary` for shared button classes
-
-## Using Slots
-
-Pass slot styles in the theme's `slots` object:
-
-```tsx
-const theme = {
-  slots: {
-    consentBannerFooter: 'border-t border-black/10 px-6',
-    consentBannerTitle: 'text-xl font-bold tracking-tight',
-
-    // Object value = className + inline styles
-    consentBannerCard: {
-      className: 'rounded-xl shadow-lg',
-      style: { maxWidth: '600px' },
-    },
-  },
-} satisfies Theme;
-```
-
-## Slot Style Types
-
-Each slot accepts either a `string` (treated as className) or a `SlotStyle` object:
-
-```tsx
-// String: treated as className
-consentBannerTitle: 'my-custom-class'
-
-// Object: className + style + noStyle
-consentBannerFooter: {
-  className: 'border-t border-black/10',
-  style: { paddingBlock: '1rem' },
-  noStyle: false, // Set true only when you want to remove this slot's default styling
-}
-```
-
-`noStyle` on a slot is an advanced escape hatch. Start with className and style overrides first.
-
-## Example: Style the stock banner without changing markup
-
-```tsx
-const theme = {
-  colors: {
-    surface: '#fffdf8',
-    surfaceHover: '#f6f3ee',
-  },
-  slots: {
-    consentBannerCard: 'rounded-[28px] shadow-xl',
-    consentBannerFooter: 'border-t border-black/10 px-6',
-    consentBannerTitle: 'tracking-tight',
-  },
-} satisfies Theme;
-```
-
-## Available Slots
-
-Use the typed API reference below for the full slot list and descriptions. It stays in sync with the actual component slot surface.
-
-## API Reference
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ComponentSlots\`|
-|Source Path|\`./packages/ui/src/theme/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "ComponentSlots" from "./packages/ui/src/theme/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`SlotStyle\`|
-|Source Path|\`./packages/ui/src/theme/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "SlotStyle" from "./packages/ui/src/theme/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*

package/docs/frameworks/next/styling/tailwind.md

@@ -1,137 +0,0 @@
----
-title: Tailwind CSS
-description: Use Tailwind CSS utility classes to style consent components via
-  the slot system.
-group: frameworks
----
-c15t works with Tailwind CSS out of the box. Use the `slots` theme option to apply Tailwind utility classes to any component part.
-
-## Setup
-
-Import the standard c15t stylesheet once in your app-level CSS entrypoint:
-
-```css
-/* React: src/index.css */
-@import "@c15t/react/styles.css";
-
-/* Next.js: app/globals.css */
-@import "@c15t/nextjs/styles.css";
-```
-
-Keeping the c15t stylesheet in your global CSS entrypoint makes layer and cascade order explicit. JS/TSX side-effect imports can load in a different order across framework and Tailwind tooling, which makes style regressions harder to debug.
-
-With Tailwind v4, keep c15t at the end of the top-level `@import` block so Fumadocs, `tw-animate-css`, and other preset imports do not override c15t theme tokens.
-
-### Tailwind v4
-
-Tailwind v4 automatically scans your source files. Import Tailwind normally, then keep the c15t stylesheet last in the top-level `@import` block so Fumadocs, `tw-animate-css`, or other preset styles load first. c15t component styles join Tailwind's `components` layer automatically, so no extra c15t-specific layer declaration is needed:
-
-```css title="src/index.css"
-@import "tailwindcss";
-@import "tw-animate-css";
-@import "@c15t/react/styles.css";
-```
-
-```css title="app/globals.css"
-@import "tailwindcss";
-@import "tw-animate-css";
-@import "@c15t/nextjs/styles.css";
-```
-
-### Tailwind v3
-
-Import the Tailwind 3-compatible c15t stylesheet after `@tailwind components;` and before `@tailwind utilities;`:
-
-```css title="src/index.css"
-@tailwind base;
-@tailwind components;
-@import "@c15t/react/styles.tw3.css";
-@tailwind utilities;
-```
-
-```css title="app/globals.css"
-@tailwind base;
-@tailwind components;
-@import "@c15t/nextjs/styles.tw3.css";
-@tailwind utilities;
-```
-
-## Troubleshooting: Fumadocs Overrides c15t Styles
-
-If c15t components render partially unstyled or lose their theme tokens inside a Fumadocs site, check the order of the imports in `app/globals.css`.
-
-**Cause:** Fumadocs preset imports can load after c15t and override the tokens and layer output that c15t components depend on.
-
-**Fix:** Keep `@c15t/nextjs/styles.css` at the end of the top-level `@import` block:
-
-```css title="app/globals.css"
-@import "tailwindcss";
-@import "tw-animate-css";
-@import "fumadocs-ui/css/shadcn.css";
-@import "fumadocs-ui/css/preset.css";
-@import "@c15t/nextjs/styles.css";
-```
-
-If you use other preset or docs-site stylesheets, apply the same rule: load them first, then import c15t last in the top-level import block.
-
-## Using Tailwind with Slots
-
-Apply Tailwind classes via the theme's `slots` object:
-
-```tsx
-import { type ReactNode } from 'react';
-import { type Theme, ConsentManagerProvider } from '@c15t/nextjs';
-
-const theme = {
-  slots: {
-    consentBanner: 'fixed bottom-0 inset-x-0 z-50',
-    consentBannerCard: 'mx-auto max-w-2xl rounded-t-2xl bg-white p-6 shadow-2xl',
-    consentBannerTitle: 'text-lg font-semibold text-gray-900',
-    consentBannerDescription: 'mt-2 text-sm text-gray-600',
-    consentBannerFooter: 'mt-4 flex flex-wrap gap-3',
-    buttonPrimary: 'rounded-full bg-indigo-600 px-6 py-2.5 text-sm font-medium text-white hover:bg-indigo-700',
-    buttonSecondary: 'rounded-full border border-gray-300 px-6 py-2.5 text-sm font-medium text-gray-700 hover:bg-gray-50',
-    toggle: 'data-[state=checked]:bg-indigo-600',
-  },
-} satisfies Theme;
-
-export function ConsentManager({ children }: { children: ReactNode }) {
-  return (
-    <ConsentManagerProvider options={{ theme, mode: 'hosted', backendURL: '/api/c15t' }}>
-      {children}
-    </ConsentManagerProvider>
-  );
-}
-```
-
-## Dark Mode with Tailwind
-
-Combine Tailwind's dark mode with c15t's `dark` tokens:
-
-```tsx
-const theme = {
-  colors: {
-    primary: '#6366f1',
-    surface: '#ffffff',
-    text: '#1f2937',
-  },
-  dark: {
-    primary: '#818cf8',
-    surface: '#1f2937',
-    text: '#f9fafb',
-  },
-  slots: {
-    consentBannerCard: 'bg-white dark:bg-gray-900 shadow-lg dark:shadow-gray-900/30',
-    consentBannerTitle: 'text-gray-900 dark:text-gray-100',
-  },
-} satisfies Theme;
-```
-
-## Optional: noStyle Mode
-
-If you want Tailwind to own all layout and visual styling, use `noStyle: true`.
-
-> ℹ️ **Info:**
-> When using noStyle: true with Tailwind, you're responsible for all layout and visual styling. Start with slots first, then switch to noStyle only when you need full control.
-
-For full custom markup (not just styles), see [Headless Mode](../headless).

package/docs/frameworks/next/styling/tokens.md

@@ -1,156 +0,0 @@
----
-title: Design Tokens
-description: The six base token categories that control colors, typography,
-  spacing, radius, shadows, and motion, plus optional dark-mode overrides.
-group: frameworks
----
-## Color Tokens
-
-Color tokens define the palette for all consent components. Set `colors` for light mode and `dark` for dark mode overrides.
-
-When `textOnPrimary` is omitted, c15t derives it automatically from `primary` to keep text readable on primary-filled surfaces such as stock branding tags and buttons. Set `textOnPrimary` explicitly when you need a specific foreground color.
-
-```tsx
-const theme = {
-  colors: {
-    primary: '#6366f1',
-    primaryHover: '#4f46e5',
-    surface: '#ffffff',
-    surfaceHover: '#f9fafb',
-    border: '#e5e7eb',
-    borderHover: '#d1d5db',
-    text: '#1f2937',
-    textMuted: '#6b7280',
-    textOnPrimary: '#ffffff',
-    overlay: 'rgba(0, 0, 0, 0.5)',
-    switchTrack: '#d1d5db',
-    switchTrackActive: '#6366f1',
-    switchThumb: '#ffffff',
-  },
-  dark: {
-    primary: '#818cf8',
-    surface: '#1f2937',
-    text: '#f9fafb',
-    textMuted: '#9ca3af',
-    border: '#374151',
-  },
-} satisfies Theme;
-```
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ColorTokens\`|
-|Source Path|\`./packages/ui/src/theme/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "ColorTokens" from "./packages/ui/src/theme/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
-
-## Typography Tokens
-
-Control font family, sizes, weights, and line heights.
-
-```tsx
-const theme = {
-  typography: {
-    fontFamily: 'Inter, system-ui, sans-serif',
-    fontSize: { sm: '0.875rem', base: '1rem', lg: '1.125rem' },
-    fontWeight: { normal: 400, medium: 500, semibold: 600 },
-    lineHeight: { tight: '1.25', normal: '1.5', relaxed: '1.75' },
-  },
-} satisfies Theme;
-```
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`TypographyTokens\`|
-|Source Path|\`./packages/ui/src/theme/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "TypographyTokens" from "./packages/ui/src/theme/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
-
-## Spacing Tokens
-
-Five-step scale for internal padding, margins, and gaps.
-
-```tsx
-const theme = {
-  spacing: {
-    xs: '0.25rem',  // 4px
-    sm: '0.5rem',   // 8px
-    md: '1rem',     // 16px
-    lg: '1.5rem',   // 24px
-    xl: '2rem',     // 32px
-  },
-} satisfies Theme;
-```
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`SpacingTokens\`|
-|Source Path|\`./packages/ui/src/theme/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "SpacingTokens" from "./packages/ui/src/theme/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
-
-## Radius Tokens
-
-Border radius scale for rounded corners.
-
-```tsx
-const theme = {
-  radius: {
-    sm: '0.25rem',  // 4px
-    md: '0.5rem',   // 8px
-    lg: '0.75rem',  // 12px
-    full: '9999px', // Pill shape
-  },
-} satisfies Theme;
-```
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`RadiusTokens\`|
-|Source Path|\`./packages/ui/src/theme/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "RadiusTokens" from "./packages/ui/src/theme/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
-
-## Shadow Tokens
-
-Box shadow scale for depth and elevation.
-
-```tsx
-const theme = {
-  shadows: {
-    sm: '0 1px 2px hsla(0, 0%, 0%, 0.05)',
-    md: '0 4px 12px hsla(0, 0%, 0%, 0.08)',
-    lg: '0 8px 24px hsla(0, 0%, 0%, 0.12)',
-  },
-} satisfies Theme;
-```
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`ShadowTokens\`|
-|Source Path|\`./packages/ui/src/theme/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "ShadowTokens" from "./packages/ui/src/theme/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
-
-## Motion Tokens
-
-Animation duration and easing presets.
-
-```tsx
-const theme = {
-  motion: {
-    duration: { fast: '100ms', normal: '200ms', slow: '300ms' },
-    easing: 'cubic-bezier(0.4, 0, 0.2, 1)',
-    easingOut: 'cubic-bezier(0.215, 0.61, 0.355, 1)',
-    easingInOut: 'cubic-bezier(0.645, 0.045, 0.355, 1)',
-    easingSpring: 'cubic-bezier(0.34, 1.56, 0.64, 1)',
-  },
-} satisfies Theme;
-```
-
-|Property|Value|
-|:--|:--|
-|Type Name|\`MotionTokens\`|
-|Source Path|\`./packages/ui/src/theme/types.ts\`|
-
-\*ExtractedTypeTable: Could not extract "MotionTokens" from "./packages/ui/src/theme/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*

package/docs/shared/concepts/client-modes.md

@@ -1,103 +0,0 @@
----
-title: Client Modes
-description: Reference page for client modes.
-group: reference
----
-c15t supports three client modes that determine how consent data is stored and synchronized. Choose the mode that matches your infrastructure:
-
-* **Hosted mode** - Recommended for production. Backend-backed consent with geolocation, centralized policy resolution, audit history, and offline fallback.
-* **Offline mode** - Browser-only storage with no network requests. Best for local development, demos, static deployments, or controlled fallback scenarios.
-* **Custom mode** - Bring your own backend with custom endpoint handlers
-
-> ⚠️ **Warning:**
-> If you need durable consent records, server-side enforcement, or automatic jurisdiction detection, use hosted mode. Offline mode cannot provide those guarantees because consent lives only in the browser.
-
-<span id="c15t-mode" />
-
-## Hosted Mode (Recommended)
-
-The default mode. Connects to a c15t backend for full consent lifecycle management. We recommend using [inth.com](https://inth.com) for a fully managed experience, but you can [self-host](/docs/self-host) as well.
-
-> ℹ️ **Info:**
-> mode: 'hosted' is the preferred value. The legacy alias mode: 'c15t' is still supported for backward compatibility.
-
-**What happens:**
-
-1. On page load, the client calls `/init` to fetch geolocation, jurisdiction, localized translation strings
-2. When the user grants or changes consent, it is saved locally before being synced to the backend.
-3. If the backend is unreachable, it falls back to Offline mode and re-syncs with the backend when it's available
-
-**Configuration:**
-
-* `backendURL` (required) - API endpoint path
-
-**Why it is the default for production:**
-
-* The backend stays the source of truth for policy, translations, and jurisdiction logic
-* Consent decisions can be stored beyond the current browser session for audit and support workflows
-* Server-side systems can preload consent-aware behavior instead of waiting for client-only storage
-* If the backend is temporarily unavailable, c15t can fall back locally and re-sync later
-
-**Best for:** Production apps that need geolocation-based jurisdiction detection, consent record storage, and compliance audit trails.
-
-## Offline Mode
-
-No network requests. Consent is stored entirely in the browser using localStorage and cookies.
-
-**What happens:**
-
-1. Default jurisdiction is GDPR unless manually set via `overrides`
-2. Consent preferences persist locally only
-3. No server-side consent records or analytics
-
-> ℹ️ **Info:**
-> Important: Offline mode still stores consent locally (cookie + localStorage). It only skips backend storage and sync.
-
-### Consequences of Browser-Only Storage
-
-If consent is not stored at all (for example, storage is blocked or frequently cleared):
-
-* Users are treated as new visitors and must re-consent repeatedly
-* Preferences are lost across browser resets, private sessions, and device changes
-* You have no reliable audit evidence to prove prior consent choices
-* Support and compliance teams have no centralized visibility into consent history by default
-* Server-side systems cannot apply prior consent decisions before client initialization
-
-**Trade-offs:**
-
-* No automatic geolocation or jurisdiction detection
-* No consent audit trail
-* No centralized policy or translation updates without shipping frontend changes
-* No cross-device sync
-* No server-side visibility before client initialization
-* Works without any backend infrastructure
-
-**Best for:** Local development, Storybook/static demos, resilience fallback, or simpler sites that explicitly accept browser-only consent storage.
-
-## Custom Mode
-
-Bring your own backend. You provide handler functions for each consent endpoint, and c15t calls them instead of making HTTP requests.
-
-**What happens:**
-
-1. On page load, the client calls your endpoint handler to fetch geolocation, jurisdiction, localized translation strings
-2. When the user grants or changes consent, it is saved locally before being synced to the backend.
-3. If one of your handlers fails, c15t returns a handler error and keeps local consent state, but automatic offline fallback and retry queue behavior is not provided for custom handlers by default
-
-This lets you integrate c15t with any existing API - your CRM, your own consent database, or a third-party compliance service.
-
-**Best for:** Teams with existing consent infrastructure that want c15t's frontend without its backend.
-
-## Choosing a Mode
-
-|Feature|Hosted|Offline|Custom|
-|--|--|--|--|
-|Geolocation|Automatic|Manual via overrides|Your implementation|
-|Policy source of truth|Backend-managed|Bundled into the frontend|Your implementation|
-|Consent sync|API|Local only|Your implementation|
-|Audit trail|Backend records|Not available|Your implementation|
-|Server-side consent awareness|Supported|Not available|Your implementation|
-|SSR data|Supported|Not available|Your implementation|
-|Analytics|Built-in|Not available|Your implementation|
-|Infrastructure|c15t backend|None|Your backend|
-|Setup effort|Minimal|Zero|Moderate|

package/docs/shared/concepts/consent-categories.md

@@ -1,41 +0,0 @@
----
-title: Consent Categories
-description: Reference page for consent categories.
-group: reference
----
-c15t organizes tracking technologies into five consent categories that align with GDPR and ePrivacy Directive requirements. Rather than asking users to approve or deny individual cookies or scripts, each category groups related tracking purposes together so users can make meaningful, informed choices about how their data is used.
-
-> ℹ️ **Info:**
-> Why categories, not cookie lists? Many consent banners list individual cookie names like \_ga, \_gid, or \_fbp. This is counterproductive:Technical names are meaningless to users — nobody knows what \_gid does by reading its name.Information overload drives "accept all" — a wall of cookie names pushes users toward dismissing the banner as fast as possible, which is the opposite of informed consent.Purpose is what matters — privacy regulations (GDPR, ePrivacy) require clear information about the purposes of data processing, not a cookie-by-cookie inventory.Cookie lists go stale — third-party scripts change their cookie names across versions, creating a maintenance burden that provides no real transparency.c15t's category-based approach — "measurement", "marketing", "experience" — communicates purpose directly. Users understand why data is collected, not how it is stored.
-
-## The Five Categories
-
-|Category|Default|Toggleable|Description|
-|--|--|--|--|
-|`necessary`|`true`|No|Strictly necessary to operate or deliver the service|
-|`functionality`|`false`|Yes|Basic interactions and functionalities|
-|`experience`|`false`|Yes|Improve quality of user experience|
-|`measurement`|`false`|Yes|Measure traffic and analyze behavior|
-|`marketing`|`false`|Yes|Deliver personalized ads or marketing content|
-
-The `necessary` category has `disabled: true` set internally, which prevents the user from toggling it off in the consent UI. All other categories can be freely toggled by the user.
-
-Note that all categories except `necessary` have `display: false` by default. A category appears in the consent UI only if you include it in `consentCategories`. Categories not listed are hidden from the UI, but they still exist in consent state and may be affected by model-level behavior (for example, auto-grant in `opt-out` or `null` model flows).
-
-## Configuring Categories
-
-The `consentCategories` array controls which consent categories are presented to the user in the consent UI. Only categories you list in this array will appear as toggleable options in the consent banner or modal.
-
-The `necessary` category is always implicitly included even if you do not add it to the array. You never need to worry about accidentally omitting it -- c15t ensures it is always present and always enabled.
-
-For example, if you set:
-
-```
-consentCategories: ['necessary', 'measurement', 'marketing']
-```
-
-then only those three categories will show toggles in the consent UI. The `functionality` and `experience` categories will not appear as user-configurable toggles.
-
-In `opt-in`/`iab` flows, hidden categories usually remain `false` unless you explicitly set them. In `opt-out`/`null` flows, categories may be auto-granted even when hidden.
-
-This gives you precise control over which consent choices to present to your users. A simple blog that only runs an analytics script might only need `measurement`. A media site with ad integrations would include `marketing`. A SaaS application with personalization features might add `experience` and `functionality` as well. You choose what is relevant to your site and c15t handles the rest - storing consent state, exposing it through hooks, and ensuring the right categories are active based on the user's choices.

package/docs/shared/concepts/consent-models.md

@@ -1,72 +0,0 @@
----
-title: Consent Models
-description: Reference page for consent models.
-group: reference
----
-c15t supports four consent models that control how consent defaults, banner visibility, and category gating behave:
-
-|Model|Philosophy|Banner|Categories default to|
-|--|--|--|--|
-|`opt-in`|Explicit consent required|Blocking banner|`false` (except `necessary`)|
-|`opt-out`|Processing allowed by default|Non-blocking notice|`true` (all granted)|
-|`iab`|IAB TCF 2.3 for programmatic ads|TCF banner|Managed by TCF framework|
-|`null`|No regulation detected|No banner|`true` (all auto-granted)|
-
-There are two ways c15t determines which model applies:
-
-1. **Policy packs** (recommended) — you explicitly set the model per region in a `PolicyConfig`. This gives you full control over which regions get which model. See [Policy Packs](/docs/frameworks/react/concepts/policy-packs).
-
-2. **Automatic jurisdiction mapping** (legacy default) — when no policy pack is configured, c15t detects the visitor's jurisdiction via geolocation and maps it to a model using the table below. This still works but gives you less control over categories, UI, and scope.
-
-> ℹ️ **Info:**
-> When using policy packs, the consent.model field in each policy directly sets the model — the automatic jurisdiction mapping is bypassed for that request.
-
-## The Four Models
-
-### Opt-in
-
-The strictest consent model, used for GDPR and similar regulations that require explicit, affirmative consent before any non-essential data processing occurs. All consent categories except `necessary` default to `false`. A consent banner must be shown before any tracking scripts load.
-
-Applies to: EU (GDPR), UK (UK GDPR), Switzerland, Brazil (LGPD), Japan (APPI), South Korea (PIPA), Quebec (Law 25). Also the fallback for unknown jurisdiction codes.
-
-### Opt-out
-
-Used for CCPA-style regulations where data processing is permitted by default until the user exercises their right to opt out. All consent categories default to `true`. A blocking banner is not required — the typical pattern is a non-intrusive notice or footer link.
-
-Applies to: California (CCPA), Canada (PIPEDA), Australia.
-
-When the policy has `consent.gpc: true`, the browser's Global Privacy Control signal (`Sec-GPC: 1` or `navigator.globalPrivacyControl`) is respected — `marketing` and `measurement` are denied while other categories remain granted. The built-in California presets enable this by default. See [Policy Packs — GPC](/docs/frameworks/react/concepts/policy-packs#gpc) for details.
-
-### IAB
-
-IAB Transparency and Consent Framework (TCF) 2.3 mode for programmatic advertising compliance. Only activates when two conditions are met: the jurisdiction is `GDPR` or `UK_GDPR`, and `iab.enabled` is `true` in your configuration.
-
-When active, IAB mode generates TC strings, registers the `__tcfapi` CMP API, and works with the Global Vendor List (GVL) for machine-readable consent signals. If `iab.enabled` is not set, GDPR jurisdictions fall back to standard opt-in.
-
-### null
-
-Returned when no jurisdiction is detected (`NONE` or `null`). No banner is displayed. On first visit, all categories are auto-granted.
-
-## Jurisdiction Mapping
-
-When no policy pack is configured, c15t maps jurisdictions to models automatically:
-
-|Jurisdiction Code|Region|Consent Model|
-|--|--|--|
-|`GDPR`|European Union|opt-in|
-|`UK_GDPR`|United Kingdom|opt-in|
-|`CH`|Switzerland|opt-in|
-|`BR`|Brazil (LGPD)|opt-in|
-|`APPI`|Japan|opt-in|
-|`PIPA`|South Korea|opt-in|
-|`PIPEDA`|Canada (excl. Quebec)|opt-out|
-|`QC_LAW25`|Quebec, Canada|opt-in|
-|`CCPA`|California, USA|opt-out|
-|`AU`|Australia|opt-out|
-|`NONE`|No jurisdiction|null|
-|*(unknown)*|Any other|opt-in|
-
-**IAB override:** If `iab.enabled: true` and the jurisdiction is `GDPR` or `UK_GDPR`, the model becomes `'iab'` instead of `'opt-in'`. This override only applies to those two jurisdictions.
-
-> ℹ️ **Info:**
-> With policy packs, you set the model explicitly per policy — the automatic mapping above is only used as a fallback when no policy pack is configured, or for non-policy-pack features like auto-granting in opt-out jurisdictions.