Consent-gated sessions (cookieless day-rotating id)

Generated from mcp/patterns.registry.json — do not edit by hand; change the registry and run bun run patterns:build.

Index card — the docs below are the canonical explanation; deep-tier pattern pages additionally carry invariants and emulation notes.

Category: Analytics · Tier: light · Risk: low — reads a consent cookie only, no external service

Session identification switches between a cookie-based id under the analytics consent tier and a cookieless hash(visitorId + UTC day) id under the necessary tier, so both tiers still produce a countable session.

When to use: Use when session tracking must stay legally gated by consent tier (TDDDG/ePrivacy) while still counting unique sessions at the lowest tier.

Docs

• docs/blueprint/analytics/activation.md (GitHub · GitLab)
• docs/stack/capabilities/gdpr.md (GitHub · GitLab)

Code

• src/lib/server/analytics/consent.ts (GitHub · GitLab)

Proof

• /showcases/analytics/privacy

Machine-readable record: analytics-consent-sessions in mcp/patterns.registry.json.