In one glance
- We do not know who you are, and we never ask: no account, no name, no ID, no phone number.
- No IP log, no analytics, no trackers, no third-party resources. Fonts, scripts and images come from the lab itself.
- A batch keeps only what the exchange needs, and only while it matters: 30 days after it settles, its addresses and transaction hashes are wiped. An order that never received anything is wiped after 2 days.
- An email exists only if you ask for one, and is deleted after the single message it was for.
- Each swap goes through the cross-chain protocol chosen for the pair, named on the estimate (“via …”) and on the batch page. The service that relays the order receives what an exchange cannot do without, nothing else.
1 · What we never collect
- Your name, identity documents, selfie, phone number, postal address or payment details.
- Your IP address in any log. The reference server configuration keeps no access log; rate limits count requests under a keyed fingerprint that expires within the hour and cannot be turned back into an address.
- Analytics, fingerprinting, tracking pixels or advertising identifiers.
- A list of your batches. Nothing links two batches together on our side once your visit ends (the session that remembers them expires), unless they came through the same partner link or the same API key.
2 · What a batch needs
| Data | Why | Until |
|---|---|---|
| The batch: pair, amounts, fee, the collection address, the refund address if you gave one, the deposit address, transaction hashes, status and timestamps, the order reference and the route it took. | To run the exchange, deliver, return a deposit and answer you if something goes wrong. | 30 days after it settles, then wiped (section 3). |
| The letter of guarantee: the batch’s terms and addresses, signed with the lab’s PGP key, downloadable only with the batch key. | So you can prove what the lab promised and that the deposit address is the lab’s. | Wiped with the batch. |
| A fingerprint of the batch key, never the key. | To check that a change comes from whoever started the batch. | Wiped with the batch. |
| An email, if you ask to be told when the batch is delivered. | To send that one message. | Deleted once it is sent, or when the batch settles otherwise. |
| A support message: what you write, the reply address, the batch number and hashes you give. | To answer you. | Deleted 30 days after the last exchange. |
| Partner link: the public code of the partner link you followed. | To credit the partner. Partners only ever see totals, never your batch. | Kept with the anonymous figures. |
| Partner accounts: a fingerprint of the login code, the public referral code, the payout address, API-key fingerprints, last login time. | To run the account and pay the share. | As long as the account is used. |
What remains of a batch after it is wiped: the pair, the amounts, the fee, the outcome and the dates, attached to no address, hash or reference. That is all we could hand over about a past batch, to anyone.
3 · When we forget it
- Settled batches (delivered, returned or failed): 30 days after the last event, a daily job erases every address, transaction hash, deposit address, order reference, key fingerprint and the order snapshot. The batch page and the API stop answering for that number.
- Orders that never received anything: erased 2 days after expiry.
- Emails: deleted after the one message. Support messages: deleted 30 days after the last reply.
- What we cannot erase: transactions on public blockchains are public and permanent by design, and the routing service and the venues it uses keep their own records under their own terms.
Download or note anything you want to keep (amounts, hashes) before the period ends: afterwards the lab cannot rebuild it.
6 · Requests about your data
You can ask to see, correct or erase what relates to a batch before the retention period ends. Since the lab does not know who you are, a request needs the batch number and its batch key (or must come from the browser that started the batch): that is how we know it is yours, without asking for any identity. Write through the contact page.
A batch still running cannot be erased before it settles, because its deposit could otherwise be lost. Depending on where you live, you may also complain to your data-protection authority.
7 · Security
Traffic is encrypted (HTTPS, or end to end through the onion mirror). The credential that lets the lab act on an order with the routing service is stored encrypted and never appears in a page, a URL or a log. Batch pages are never cached by browsers or proxies, and addresses are shown masked. The batch key and the partner login code are stored only as fingerprints and cannot be recovered, even by us.
8 · Staying private
- Use the onion mirror (http://alchimxleabtpyryaqza3gowpx3apsm6cx5gofjcr36n7sxhkhqtrhqd.onion) or a VPN if you do not want any network-level link between you and the lab.
- Use a fresh receiving address for each batch.
- If you need an email, use a dedicated or aliased mailbox, or skip it: the batch page tells you everything.
- Keep the batch number and key offline, not in a cloud note.
9 · Who runs the lab
Alchimex is run by the Alchimex operators. They are responsible for the processing described here. Contact: contact page, PGP key (B396 F909 0D85 D062 44B8 4885 AD23 8398 69BA A3D9).
10 · Changes
If this notice changes, the date at the top changes. A change never applies backwards to make the lab keep more about a batch than was promised when it was started.