← Назад до блогуПриватність

What an exchange actually sees about you: cookies, fingerprints, IPs

Cover

“No logs” is an easy claim to make and a hard one to verify. So instead of claim-by-adjective, here's the actual surface a crypto exchange gets to observe about a visitor, and what Mistex chooses to do with each.

IP address

Every HTTP request ships your IP to the server. It's the single highest-value identifier a service gets for free. Mistex's reverse proxy — the only component that ever sees raw IPs — strips the

X-Forwarded-For
header before handing the request to the application, which means the business logic literally can't see where you're coming from. The only code path that holds an IP is rate-limiting, and it keeps the value only long enough to count requests in a rolling window. Nothing is persisted.

If you want to remove the IP entirely from the picture, use the Tor hidden service we run at

...onion
. Requests arriving via Tor don't have an exit-side IP at all; the network layer physically can't tell you where they came from.

Cookies

We set three kinds of cookies — and none of them are analytics or tracking.

  1. Session cookies for cabinet login (HttpOnly, SameSite=Strict, secure).
  2. Refresh-token cookies for rotating JWTs.
  3. A short-lived referral-attribution cookie if you clicked through a
    /r/<code>
    link.

That's it. No third-party scripts dropping tracking IDs, no analytics beacons, no ad-network tokens.

Browser fingerprints

Fingerprinting is passive: the server observes what the browser volunteered. Every request exposes your User-Agent, Accept-Language, screen size (indirectly via media queries), rendering quirks. The only defense is what the client sends.

We don't run a fingerprinting script. We don't hash your fingerprint and store it as a shadow identifier. On the Tor mirror, fonts, canvas, and WebGL are already constrained by Tor Browser's fingerprint-resistance features, which is another reason the onion mirror is the strictest version of Mistex.

Referer and Origin headers

These tell us where the request came from. For ordinary navigation that's harmless (a link from Reddit, a bookmark, direct typing). We don't log Referers.

Third-party embeds

This is where most exchanges leak. A live-chat widget, a marketing pixel, a help-center iframe — each one is a third domain that sees your IP and sets its own cookies. We run zero third-party embeds. Our support chat is self-hosted: the widget talks only to our own API, which relays the message text — never your IP — to our operators. Because no foreign script ever loads, the same chat works identically on clearnet and on the .onion mirror, with nothing to disable.

What we actively collect, temporarily

Just the per-order working data — deposit address, recipient address, amount, order status, timestamps. This is the minimum needed to run a swap and nothing more.

Takeaway

Privacy isn't a policy, it's the set of things you do and don't do in the code. IP strip at the edge, no fingerprint script, no third-party trackers, no analytics beacons. The Tor mirror is available for the subset of users who want to skip even the IP question. Everything listed here is something you can verify for yourself with a browser's dev-tools network tab.

Поділитися статтею
X / TwitterTelegram
Готові до обміну?Спробувати Mistex →
← Попередня статтяБезпекаNon-custodial vs custodial: why your exchange should never hold your keysНаступна стаття →ПриватністьWhat happens to your deposit address after a swap