Privacy Policy
This policy is unusually short, because the service collects unusually little. It describes what exists, what deliberately does not exist, and where the public blockchain — not this service — is the visibility boundary.
What the service collects
Three categories, all tied to making deals work: your Telegram identity (the account that logs in and chats with the bot), deal records (requests, quotes, addresses, amounts, transaction hashes, statuses) and payout requisites that you enter yourself for the fiat side. Session data of the web application completes the picture.
What the service does not collect
No identity documents — the flow has no document upload at any stage. No passwords — login is handled by Telegram's signed identity. No private keys or seed phrases — the wallet side is watch-only, and no support agent will ever ask for key material. The absence of these categories is architectural, not policy-deep: data that is never collected cannot leak.
Where data lives and for how long
Operational records are stored while your account is active and for the retention period required for accounting and dispute resolution afterwards. Backups exist for continuity and are destroyed under the same rotation. When you ask for deletion, what is legally required to keep is kept and the rest is removed — the honest version of "delete everything" anyone can offer.
The public blockchain, stated honestly
Transfers in USDT are recorded on public blockchains, visible to anyone through block explorers. This visibility is a property of the technology, not a choice of this service, and it applies to every crypto transfer in existence. The history of the wallets involved is also the basis of the AML screening that incoming transfers pass before payout.
Rights and contact
You can request an explanation of what is stored about your account, a correction, or a deletion of what is not legally required to keep. The channel is the same one everything else runs through — the Telegram bot, from the account in question.