Cookie policy

FortuneX sets no cookies of its own — not for sessions, not for preferences and not for analytics. Nothing about your visit is written to a cookie by us.

We also run no advertising pixels, no tag manager and no third-party analytics. There is no Google Analytics, no Meta pixel and no session-recording tool on this site. Nobody is being sold your browsing behaviour, because we are not collecting it.

Signing in requires the browser to remember something, so the platform uses local storage rather than cookies. Local storage differs from a cookie in one way that matters: it is never transmitted automatically with requests. It stays in your browser until it is read deliberately or cleared.

• fx_access — your short-lived access token, which authorises requests while you are signed in.
• fx_refresh — a longer-lived token used to renew the above without making you sign in again.
• fx_admin_refresh — the equivalent for an operator signed into the admin console.
• fortuneX-theme — whether you chose the light or dark theme, so it is applied before the first paint.
• fx_support_view — set only when an operator is viewing an account through the support desk, so the interface can say so plainly.

That is the complete list. All five are strictly necessary for the platform to function or to honour a preference you set yourself.

Consent requirements under the ePrivacy Directive and similar regimes apply to storage that is not strictly necessary — chiefly tracking and advertising. We do none of that, and the five items above are either required to sign you in or are a setting you chose. There is nothing to ask permission for.

If that ever changes — if we add analytics, or anything that profiles visitors — we will ask first, and this page will say so before it happens rather than after.

Fonts are self-hosted and served from our own domain, so loading a page does not make a request to a font provider. Page assets are served from our own infrastructure and our content delivery network, which may process your IP address in order to deliver the page and to absorb malicious traffic. That is a network function rather than tracking, and it does not build a profile of you.

Deposits and withdrawals settle on a public blockchain. Transactions there are permanently public by design, and that is outside the control of this website — see the privacy policy for what that means.

Signing out removes your tokens from this browser and ends the session on our servers, so a copy of the token elsewhere stops working too.

You can also clear site data for this domain from your browser settings at any time. Doing so signs you out and resets your theme preference; it affects nothing about your account, your balances or your ledger, all of which live on the server.

Blocking local storage entirely is possible in most browsers, but the platform cannot keep you signed in without it.

This document describes the platform as it is built today. If we introduce anything that stores or reads data in your browser beyond the list above, we will update this page and the date on it. Questions can go to our team.