We don't collect any metadata.
We are a company registered in Belize. Our entity details:
Yes, follow this link to participate.
We operate with two pools of addresses for BTC deposits and transfers - mixed and aggregated. In a mixed pool all received and sent transactions are mixed together and there is no way to discover how many people are behind certain addresses and traceability is extremely difficult, which is very good for privacy but bad for risk scoring. In the aggregated pool all transactions we receive from users are collected on a known single address which is also used to send payments, what will clearly show you have interacted with our exchange and it's good for interacting with other major exchanges to avoid any risks of frozen funds.
These are cons and pros of each pool:
Due to the fact we are using a single wallet for all incoming and outgoing Monero payments and its protocol limitations of UTXOs being spendable strictly after 10 confirmations, multiple orders involving Monero within our system may cause delay to your order, since we are only able to process one order once a UTXO from a previous order is fully confirmed.
Our communications framework consists mainly of desktop applications and Telegram doesn't support end-to-end encryption ("Secret Chats") in their desktop app since the initial release, thus we consider transmission of payment and other private data via Telegram insecure, including using bots and standard chats, since neither of them support end-to-end encryption. We do not use mobile devices due to risks associated with a wide exposure of manufacture supply chains to hardware backdoors. More details can be found here https://github.com/marcovelon/tdesktop/blob/NoSecretChats/README.md and in the following discussion https://github.com/marcovelon/tdesktop/issues/2
WARNING: We do not recommend any mobile wallets that are not included into the official F-Droid repository. Projects that do not have technical capabilities to accomplish the inclusion criteria or simply avoiding doing so should be considered risky. The main purpose of being included to F-Droid is to ensure the compiled binaries are built from the current release source code without any modifications, because any project included to F-Droid is compiled by F-Droid's infrastructure and not by the project's team that can be compromised any time (this concept is called "reproducible builds").