PolyExhange uses cookies and similar storage so the exchange can remember your session, keep you signed in, and show the site in a stable way. We do not run a third-party advertising pixel on the public pages.
A cookie is a small file the browser stores for this domain. Local storage in the app (for example chart layout) works the same idea: it stays on your device so the terminal does not reset every refresh. Session cookies usually last until you close the browser or until a timeout we set. Persistent cookies last until they expire or you delete them.
| Purpose | Why it exists |
|---|---|
| Session / login | Keeps you authenticated on the exchange after you sign in. Without it, every click would ask for a password. |
| Two-factor challenge | A short-lived cookie while you complete an authenticator code so we do not leave a half-open login hanging. |
| Security | Flags we need to bind a session to the browser that created it and to expire idle logins. |
| Traffic source | If you arrived with a referral or campaign tag, a first-party cookie may remember that touch so a signup can be attributed. It is not an ad profile. |
| Preferences | App UI state such as a selected pair or chart interval may live in local storage on your machine. That data does not go to an advertiser. |
We treat these as strictly necessary to run a logged-in exchange, plus a small amount of first-party attribution. They are described further in the Privacy Policy.
Market data and some images may be requested from infrastructure we do not own (for example a price feed or a font CDN). Those hosts may see your IP the way any HTTPS request does. We do not embed third-party ad networks or social trackers on the marketing pages. Staff tools are separate and not part of your customer cookie set.
You can block or delete cookies in the browser. If you block the session cookie, you will not stay logged in. If you block all cookies, parts of the site will simply not work. There is no “accept marketing cookies” toggle because we are not selling a marketing-cookie product on this site.
Do Not Track signals are not a substitute for deleting cookies; we do not change the session model based on DNT. For access or deletion of account data, use the Privacy Policy contact path, not the cookie dialog — there isn’t one.
If we add a cookie that is not needed to run the account — for example a genuine analytics product — we will update this page before it goes live on the customer site. Continued use after an update means you have seen the new list. Questions: help center.