Privacy notice
How no1.exchange uses exchange records, private-order cookies and support requests, including Telegram notifications.
→Your route, amount, and destination are shared with the exchange processor to create your order and keep its status available. Private-order access uses a browser cookie or the original destination address.
Effective date: 2026-10-23. This notice covers quote requests, order creation, private exchange status and support requests at no1.exchange. The exchange form does not ask you to register an account or provide your name, email address, identity documents, seed phrase, or private key. The separate support form asks for an email address so we can reply.
A quote request contains the selected sending and receiving assets and networks, the amount, and whether that amount is for the sending or receiving side. Creating an order also supplies a destination address and any memo or tag included in the request. The provider response becomes part of the exchange record.
The exchange processor receives the estimate and order details needed to calculate and process the exchange. no1.exchange stores the order record to retrieve status, match processing updates, and verify private access. Separate keyed hashes are stored for the destination-address access check and browser access token. Those hashes do not remove addresses or transaction data from the stored response. Authenticated processing updates can change the stored status and transaction details; event identifiers, order references, event types, and versions are stored to avoid processing the same event twice.
Creating an exchange or restoring access sets an essential cookie whose name begins with no1_exchange_access_. It contains a random access token and expires after 30 days. The cookie is HttpOnly and SameSite=Lax; it is marked Secure when the site runs in production mode. Without a valid cookie, access requires the exchange ID and the destination address used for that order. Clearing the cookie removes the browser token, not the stored exchange record.
When Telegram notifications are configured, exchange creation, deposit detection, and completion can trigger a message through the Telegram Bot API. Messages contain the private exchange ID, provider order number, asset pair, sending and receiving amounts, status, and a link to the deposit address in a blockchain explorer. If an explorer link is unavailable, the message links to the private exchange page instead. Notification records store the event type and claim or delivery timestamps to avoid duplicate messages.
Submitting the support form sends your chosen topic, reply email, message, and any order ID or transaction hash you supply to the no1.exchange support chat through Telegram. Telegram processes the message under its own privacy policy. This form does not create a support record in the exchange database or send an automatic email acknowledgement. Short-lived in-memory hashes help limit repeated submissions; they are not a permanent ticket history. A successful form response confirms that Telegram accepted the message, not that a person has reviewed it. Do not include passwords, seed phrases, private keys, identity documents or unrelated financial details.
Operational errors may be logged with an exchange ID and notification event type. The exchange flow does not add analytics or advertising cookies, or save form data in localStorage or sessionStorage. Addresses and transaction IDs can reveal activity on public blockchains; private order access does not conceal those transactions. Use only the order details needed to check a request, and keep unrelated wallet information out of screenshots or messages.
