Privacy And Cookie Consent

1. 1

   Read the current version

   The client reads the versioned consent cookie and migrates a supported legacy local-storage decision once.

   Relevant Product code

   • src/features/privacy/shared/cookie-consent.ts
   • src/features/privacy/ui/cookie-consent.tsx
2. 2

   Present a reversible choice

   Customize opens a dialog without saving or closing the banner. Accept or save preferences records an explicit decision.

   Relevant Product code

   • src/features/privacy/ui/cookie-consent.tsx
3. 3

   Apply the choice at the request boundary

   The proxy fails closed for optional first-party attribution: no accepted decision means no new tracking cookies.

   Relevant Product code

   • src/proxy.ts
4. 4

   Keep preferences reachable

   The marketing footer dispatches the privacy event so visitors can review or change a saved choice later.

   Relevant Product code

   • src/features/privacy/ui/cookie-preferences-button.tsx
   • src/app/(marketing)/_components/marketing-footer.tsx

Use this example as a starting point, then adapt it to your product's rules and configuration.

Unknown and stale values resolve to no decision so optional attribution fails closed and the visitor can choose again.

export const cookieConsentValues = {
  accepted: `v${COOKIE_CONSENT_VERSION}:accepted`,
  declined: `v${COOKIE_CONSENT_VERSION}:declined`,
} as const;

export function parseCookieConsent(
  value: string | null | undefined,
): CookieConsentDecision | null {
  if (value === cookieConsentValues.accepted) return "accepted";
  if (value === cookieConsentValues.declined) return "declined";
  return null;
}

export function serializeCookieConsent(
  decision: CookieConsentDecision,
): string {
  return cookieConsentValues[decision];
}