Our launch approach
Quizidium uses cookies and browser storage required for account security, checkout safety, event control, recovery and features a user asks us to provide. Advertising, cross-site behavioural tracking and optional analytics storage stay off unless a separate clear choice is introduced first.
Cookies
__Host-Quizidium-Authkeeps a signed-in Host session. It is HTTP-only, secure in production, same-site Lax and normally expires within 14 days.__Host-Quizidium-Antiforgeryprotects a browser request against cross-site request forgery after the browser asks for a request token. It is HTTP-only, secure in production and same-site Lax.- The public legal, registration-entry and contestant join pages do not set advertising, cross-site tracking or optional analytics cookies.
Local and session storage
The contestant join page does not create its room-session value until the contestant submits the join form successfully. Removing essential storage may sign you out, discard an unsaved draft or prevent recovery of an active event. If we add non-essential storage, it remains off until you actively choose it and you can later change that choice.
quizidium:show-builder:v2:{quiz-or-draft-id}recovers an unsaved Host draft in that browser until final save or local removal.quizidium:d8b-h4:checkout-key:{product-version-id}prevents an uncertain Checkout attempt from silently creating a duplicate order.quizidium:player-session:v1:{room-code}retains the contestant's room-scoped recovery state for that browser session after they join.quizidium:host-control-token:v1:{room-code},quizidium:controller-token:v1:{room-code}andquizidium:presenter-token:v1:{room-code}retain authorised room-control state for the browser session.quizidium:resilience-device:v1:{role}:{room-code}retains a room-scoped device correlation value used for bounded recovery and reliability handling during the browser session.
