The Marketplace uses browser storage mainly to keep the authenticated experience working and to reduce repeated reads. This page distinguishes essential session mechanisms from client-side caches and onboarding markers.
Essential cookies
- An opaque, HttpOnly, Secure, SameSite session cookie identifies the server-side authenticated session. SAML assertions and full identity claims are not stored in that cookie.
- A short-lived FMU/session context cookie may be used for an authorised lab-operation flow.
Local and session storage
- React Query persists only successful public catalogue and metadata queries in localStorage for up to 72 hours. User-scoped provider, reservation and booking queries are not persisted in that public cache.
- A browser passkey marker is stored in localStorage to avoid repeatedly showing the institutional WebAuthn advisory for the same institution and stable user identifier.
- A temporary onboarding session is held in sessionStorage while the institutional ceremony is completed and is removed when the flow ends.
Choices and limitations
Blocking essential cookies or storage can prevent SSO, onboarding, reservations or lab access from working. Clearing browser data removes local caches and markers, but does not remove server-side or on-chain records.
Optional analytics, advertising cookies and third-party tracking should not be enabled without a separate reviewed configuration and consent mechanism.