Authentication state
Firebase and related authentication tooling may use cookies, local storage, and browser-managed state to keep signed-in sessions working securely.
Trust Center / Cookies
Cookie, local storage, and app-state disclosures.
Caseflow uses browser storage and service-worker capabilities to support authentication, preferences, PWA behavior, localization, security posture, and workspace reliability.
Operational storage model
Caseflow is a browser-based and installable web application. Some browser storage is necessary for sign-in state, localization, theme and accessibility preferences, app installation behavior, and performance.
Preferences
Language, text size, theme, and workspace preference signals may be stored locally so the interface remains consistent across visits.
PWA behavior
Service workers and cached assets support installable-app behavior, faster loading, and offline-tolerant shell behavior where supported by the browser.
Data handling boundaries
- Browser storage should be treated as part of the user-controlled device environment.
- Workspace records remain governed by application permissions, but local device access can affect who sees an open session.
- Users should sign out on shared devices and protect browsers, operating-system accounts, and installed app instances.
- Caseflow does not use this page to claim a completed cookie-law or consent-management determination for every jurisdiction.
Enterprise review note
Cookie banners, analytics classification, consent mechanisms, and jurisdiction-specific notices should be finalized through legal review before regulated or region-specific commitments are made.