Legal · document 2 of 4

Privacy policy

Written to be checked, not to reassure. It includes the parts that are not flattering, because a privacy page that only flatters is worthless.

  • Updated 19 September 2026applies to orders created from that date
  • 7 sections · about 4 minor read only the “In short” notes: under a minute
01

What we ask you for

To perform an exchange we need exactly one piece of information from you: the address that should receive your payout, plus a memo or tag where the receiving chain requires one. That is the whole form.

You may optionally add a refund address, used only if the exchange cannot complete. It is stored with the order, at the desk, for that purpose alone.

We never ask for a name, an email address, a phone number, a document, a selfie, a proof of address or a source-of-funds statement — at any amount. There is no account to attach them to and no threshold above which we start asking.

02

What our servers write down

Nothing about your requests. That is a configuration, not a promise, and it is a short one:

  • access_log off;the web server records no request line, no IP, no user agent, no referrer
  • access.log = /dev/nullthe application server records no request either — this one is easy to forget, and it logs the same data

What remains is an error log, which exists so that a broken page can be fixed. It records the file and line of a fault, not who triggered it.

There is no analytics, no tracking pixel, no session recording, no third-party script and no advertising network on this site. Everything the page loads — fonts, icons, the coin logos, the background video — is served from this domain, which is enforced by a strict Content-Security-Policy that forbids any external host.

No cookies are set, at all. There is nothing to consent to, which is why you have never seen a banner here.

One honest caveat: this describes what we do with a request. It does not, and cannot, prove what any machine between you and us does with the connection itself. Which is the subject of the next section.

03

Who else is in the path

Any exchange service that tells you it is alone in the path is lying. Here is who else is involved, and what each one necessarily learns:

  • The liquidity desk. Your swap is routed to and settled by a wholesale exchange partner. It receives what an exchange is made of: the pair, the amounts, the deposit address it generates, and the payout address you gave. It is the party that actually moves the coins, and it operates under its own policies, which we do not control.
  • The network edge. Traffic to this site passes through a content delivery network before reaching our server. Like every such service, it terminates the connection and therefore sees connecting IP addresses, regardless of what we log.
  • The blockchains. Both sides of your swap are public ledgers. The deposit and the payout are permanently visible to anyone, by design. No exchange service can change that — the only thing that varies is how much extra information is attached to those transactions, and here the answer is: your payout address, and nothing else.
  • Block explorers, if you click one. The order page links to explorers so you can verify a transaction. They are third-party sites, and opening one tells them which transaction you are looking at. The hashes are copyable precisely so you do not have to.

If you want to reduce what any of them can correlate, the effective levers are yours, not ours: the network you connect from, the wallet you deposit from, and the asset you choose.

04

What stays on your device

Because there is no account, the only history that can exist is a local one. When you create or open an exchange, your browser stores its order ID — and the pair, for readability — in its own local storage, under the key btcswap.orders. That is what lets Track offer your recent orders.

It is kept by your browser, for your browser. It is never transmitted to us, and we have no way to read it. Clearing it takes one click on the Track page, or clearing site data in your browser. If local storage is unavailable — private window, blocked site data — the site works exactly the same, minus that convenience.

05

If you write to us

Support is the one place you can hand us more than an address, and only because you choose to. A message contains what you put in it: usually an order ID and a description, sometimes a return address so we can answer.

We keep a support message for as long as the question is open, and we do not use it for anything else. Send the minimum that lets us help — an order ID is almost always enough, and it is not linked to your identity anywhere.

06

Your rights, and their honest limit

Depending on where you live you may have a right to access, correct, export or erase personal data held about you. We will honour any such request we can honour.

The limit is real and worth stating plainly: we cannot connect a person to an order, because we never collected anything that would allow it. If you ask us to erase « your data » without an order ID, there is nothing we can find to erase. That is the intended outcome of the design, not an evasion — but it also means we cannot help you retrieve or delete an exchange you cannot identify.

Data attached to an order at the liquidity desk is governed by that desk’s own policy, and a request about it has to go through us with the order ID.

07

Changes to this policy

If what we do changes, this page changes with it, and the date at the top moves. We would rather publish an uncomfortable line here than keep a comfortable one that stopped being true.

The claims on this page are technical and checkable. If you find one that no longer holds, tell us — that is a bug, and we treat it as one.

A question about this document? Write to support — an order ID is enough, no account is needed, and we answer in the same plain language we write in here.

Next document AML policy No KYC — and the one case a swap is held