Cookies and browser storage

The exact browser storage used by FireUX-powered apps and when it begins.

Last updated: August 3, 2026

No tracking storage

FireUX does not use analytics or advertising identifiers, device fingerprints, or cross-App behavioural identity. An ordinary public visit does not need a consent popup because optional tracking is not active. Storage begins only when you ask an App to remember a choice, sign you in, retain a cart or order, or continue a conversation.

Storage used after a feature request

FeatureOwner and purposeLifetime and deletion
AppearanceCore remembers light or dark after you select it. Until you select System or clear site data. Selecting System removes it.
Authentication Firebase maintains sign-in and security state for the current App. One-hour tab values can complete a requested sign-up redirect or transfer the selected anonymous Workspace target after sign-in. Current browser session. Sign-out or ending the browser session clears local sign-in state; temporary values are removed after completion or expiry.
LanguageThe current App remembers the language you select. Up to one year. You can remove it with browser site-data controls.
Workspace The current App remembers the authenticated Workspace source and target you select. Browser session, or until the selection is cleared.
Cart and anonymous order The ordering App retains cart lines, duplicate-submission protection, and the capability and receipt details needed to recover the order in this browser. At most 24 hours; removed when cleared, completed where applicable, or found expired.
ChatThe current App remembers the conversation you started. At most 30 days; removed when found expired or through browser site-data controls.

Third-party features

Google Maps loads only after you request a map. Stripe may use storage on its hosted checkout after you choose checkout. An embedded FireUX tool runs on its named provider App origin after you open that tool. Those providers control storage on their origins; FireUX prohibits joining it into cross-App behavioural profiles.

Your controls

You can use the feature controls described above or your browser's site-data controls. Blocking essential storage may prevent the requested feature from remembering its state. See the Privacy Policy for personal-data handling, providers, rights, and contact details.