Flux AIOCookies & storage
Our public pages do not add optional analytics or advertising trackers. The signed-in service uses security, authentication, payment and preference storage described below.
Last updated: October 29, 2026
What the public website uses
The public marketing and legal pages are delivered as HTML with local images, styles and fonts. They do not load Flux analytics, advertising pixels, sign-in scripts or payment scripts. Our public-page renderer does not set cookies. Hosting or network-security providers may use necessary infrastructure technologies.
Visiting the dashboard, signing in or opening billing loads additional service providers. The inventory below distinguishes those requested services from the public website.
Cookies and storage in the service
| Item | Purpose and lifetime |
|---|---|
__Host-flux_session | Essential application security session. Secure, HttpOnly and SameSite=Lax, with session-expiry and idle safeguards. |
| Clerk / Google authentication | Sign-in, session continuity and account security when you request authentication. Cookie names and lifetimes are managed by those providers. |
| Stripe billing security | Billing operation and fraud prevention. Provider-managed cookies and device information may be used. See Stripe's Cookie Policy. |
flux.theme in local storage | Remembers the dashboard theme preference on this browser until changed or cleared. |
flux.returnTo in session storage | Remembers the operator return destination during sign-in; cleared by the flow or when the browser session ends. |
Provider implementations can vary by browser and region. Our inventory is not a promise that a third-party service will always use the same cookie names or duration.
Consent and optional tracking
We have not added optional marketing or analytics trackers to the current website. Necessary authentication and payment security are not presented as optional settings that an “Accept all” button would control. For that reason, the current public pages do not show a cookie-consent banner.
If non-essential tracking is introduced, it must be disclosed and, where required, blocked until consent is obtained, with an appropriate way to decline or withdraw. User preferences and provider behavior also need to be assessed under the laws that apply; this page is not a claim that every cookie is exempt everywhere.
Your controls
Your browser can show, block or clear cookies and site storage. Blocking essential cookies can prevent sign-in, secure sessions or payment features from working. You can change the dashboard theme or clear its stored preference through browser site-data settings. Closing or clearing a browser session removes session storage. A browser control does not necessarily delete provider-held account or transaction records.
SMS reminder choices are separate from cookies and can be changed in Settings. Contact support@hireflux.org for help or a privacy request.