Privacy policy

Account data: email address, optional Telegram handle, display name, password hash, and sign-in timestamps. Deal data: amounts, networks, deposit and payout addresses, transaction hashes, descriptions you write, and the event log of state changes. We do not collect identity documents, selfies or proof of address — BM Escrow is a no-KYC service. Technical data: IP address, browser and device information, and error logs.

To operate the escrow and settle funds correctly; to detect fraud, sanctions exposure and abuse from on-chain activity; to resolve disputes on evidence; and to meet legal record-keeping obligations.

There is no document upload anywhere on the platform and no identity file store. The most sensitive data we hold about a trade is a wallet address and a public transaction hash.

The other side of a deal sees your display name, the deal terms, the deal's state history, and the wallet addresses relevant to that deal. They do not see your email address, your documents, your other deals, or your account history.

Transactions we broadcast are permanently public on the relevant blockchain. We cannot delete, alter or hide on-chain records, and any address you give us becomes linked to those public transactions.

We share data with the infrastructure providers that run our database, storage and hosting, and with blockchain explorer services used to verify deposits. We disclose data to law enforcement or regulators where we are legally required to, or where necessary to investigate fraud or prohibited use. We do not sell data or share it with advertisers.

Deal records and the associated event log are retained for as long as required for compliance and dispute purposes. Account data is deleted on request, except where we must keep it to meet a legal obligation.

You may request a copy of the personal data we hold about you, ask for inaccurate data to be corrected, or ask for deletion where no legal obligation requires us to keep it. Make requests through the support channel in your account so we can verify the request comes from you.

Data is protected by row-level access control, private storage buckets, hashed credentials and server-side authorisation on every state change. No system is perfect; we work to minimise the data we hold so that a breach exposes as little as possible.

We will update this page when our practices change. Continued use of the platform after an update constitutes acceptance of the revised policy.