Cookies and Local Storage
Last updated: 25 July 2026
1. The short version
Fluxus does not use advertising or cross-site tracking cookies. The app works primarily with browser local storage, which stays on your device. The only third-party storage comes from PostHog analytics, and only when analytics is enabled and your browser does not send Do Not Track.
2. Local storage we set
Keys prefixed fluxus- hold your app state: wallet address and balances cache, transaction history, contacts, merchant and subscription settings, AI chat history, offline queue, theme, and UI preferences. These are functional (the app needs them to work) and they never leave your browser. Clearing site data removes them all.
3. Analytics storage
When analytics is active, PostHog's browser library stores its own identifiers (cookies and/or local storage entries prefixed ph_) to tell returning visitors apart. Analytics is feature-flagged and is skipped entirely when your browser sends the Do Not Track signal; in that case PostHog is never initialised and sets nothing.
4. No consent banner yet
Fluxus currently has no cookie consent banner. Whether one is required, and on what legal basis analytics may run before consent, is an open question for legal review, and this page will be updated with the outcome. Until then, this document honestly describes what is set today, and Do Not Track is respected as an opt-out signal.
5. Managing storage
You can inspect and delete everything described here from your browser's site-data settings for fluxuspay.app. Deleting local storage resets the app to a fresh state; your wallet itself is not affected, because it lives in your device's passkey store, not in local storage. Questions: legal@fluxuspay.app or the project GitHub (public; no personal data in issues, please).