1What this covers
This policy covers the Swapzy Discord bot, the Swapzy Telegram bot, and swapzy.cc. It describes what Swapzy collects when you use them, why, where it goes and how long it stays.
It does not cover Discord, Telegram, or any blockchain. Those are run by other people under their own policies, and two of them are public ledgers that nobody can edit. Section 7 is about that.
Swapzy is custodial: it holds the keys to the wallets your balance settles from. That is a fact about the product rather than about privacy, but it shapes this document, because a custodial service has to keep a record of who is owed what.
2What we collect
Less than you would expect, because of a design decision rather than a promise: there is no users table. Your chat platform's account id is the identity. Every balance, tip and withdrawal is attributed to that string, and nothing else about you is required to run the service.
| What | Example | Why we hold it | Where |
|---|---|---|---|
| Your platform account id | A Discord snowflake, or a Telegram id written tg:12345 | It is the account. Balances and history attach to it. | PostgreSQL |
| Commands you send the bot | $tip @mina 25 USDC | To carry out the instruction you gave. | Processed in memory; the result is a ledger row |
| Ledger entries | user id, chain, asset, amount, direction, status, counterparty id, optional note | The record of what you are owed. It is the book. | PostgreSQL |
| Transaction logs | on-chain hash, chain, token, amounts, fees, explorer link | To reconcile what left the platform against what the chain did. | PostgreSQL |
| Your deposit addresses | One derived address per chain | So a deposit can be recognised as yours. | PostgreSQL |
| Withdrawal destinations you type | An address you asked us to send to | To send it, and to show it back to you in history. | PostgreSQL |
| Username, display name, avatar URL | Whatever Discord or Telegram currently says | So an operator looking at a support ticket sees a name and not an eighteen-digit number. | Redis, 30-day expiry |
| Server and chat ids | The guild or chat a command came from | Rate limiting, abuse handling, and sending the reply back to the right place. | Logs |
| Ordinary service logs | IP address, timestamp, endpoint, error | Security, debugging, and abuse investigation. | Logs, short-lived |
The username cache deserves its own sentence, because it is the one piece of personal data here that is not part of the book. A username is not a fact about Swapzy — it is a fact about Discord, owned there and changed there without telling us. So it lives in Redis behind a 30-day expiry, it is written by the bot rather than collected by us, and nothing on the money path is allowed to read it. It decorates an operator's screen. It is not a permission and not a balance.
3What we do not collect
- No email address and no password. You do not create an account with us. Your chat platform already authenticated you.
- No seed phrase of yours, because you do not have one here. Swapzy holds the keys — which is the trade, and it is stated in the terms and on the homepage.
- No identity documents. Swapzy does not currently run identity verification. If that changes — and for a service of this kind it may — this document changes first, and you will be told what is being asked for and why.
- No payment card or bank details. There is no fiat rail.
- Not the contents of your conversations. The bot reads what is addressed to it. It is not a log of your server.
- Nothing is sold. Swapzy does not sell personal data, does not share it with advertisers, and does not run advertising or third-party analytics profiling on the bots.
4Where it goes
Swapzy shares data with the infrastructure it runs on, and with nobody else for marketing purposes:
- Blockchain nodes and deposit-webhook providers, which necessarily see addresses and transactions — that is what they are for.
- A market data provider, which sees that a price was requested, not who requested it.
- Hosting and database infrastructure, which stores what is described in Section 2 on our behalf.
- Discord and Telegram, to the extent that sending you a message means handing them the message.
- Law enforcement or a regulator, where a valid legal order requires it, and to the extent it requires.
- A buyer, if the service is ever sold or merged — in which case this policy travels with the data and you are told before anything changes.
5Discord
The Discord bot receives what Discord sends it: the id of the account that ran a command, the command and its arguments, and the server and channel it came from. It uses the Message Content intent, which means it can read messages in servers it has been added to — it reads them to find its own commands, and keeps nothing else.
Swapzy uses Discord data only to operate the bot, as the Discord Developer Terms of Service and Developer Policy require. It is not used to build a profile of you, it is not combined with data from anywhere else, and it is not passed to a third party for their own purposes.
Removing the bot from a server stops it seeing anything in that server. It does not delete your balance, because your balance is yours and not the server's — see Section 8 for how to close an account.
6Telegram
The Telegram bot works the same way and receives the same kinds of data through the Telegram Bot API: your Telegram user id, the command you sent, and the chat it was sent in.
Telegram ids are stored namespaced — written tg: followed by the id — so that a Telegram account and a Discord account can never be mistaken for each other. Swapzy does not link your Telegram identity to your Discord identity, and transfers between the two platforms are refused rather than guessed at.
7What the blockchain keeps
Deposits and withdrawals are transactions on public blockchains. Once broadcast, they are permanent, world-readable and outside anyone's control, including ours. Amounts, addresses and timestamps are visible to anybody who looks.
Your chat identity is not written on-chain. But a deposit address is issued to one account and reused, so anyone who learns that an address is yours can read its history. If that matters to you, treat a deposit address as semi-public information and do not post it beside your name.
Nothing in this policy can promise deletion of on-chain data. No one can.
8How long we keep it
- Username cache — 30 days from the last time a bot wrote it, then it is gone unless you use the service again.
- Service logs — kept only as long as they are useful for security and debugging, then rotated out.
- Ledger and transaction records — kept while your account exists. A custodial ledger that forgets entries cannot say what it owes, so these are not deleted on request while a balance exists.
- After closure — withdraw your balance and ask us to close the account. Identifiers are detached from records where that is possible; the underlying financial record is retained where accounting or legal obligations require it.
9Your choices, and their limits
Ask us and we will tell you what is held against your account, correct anything wrong about it, hand it to you in a portable form, or close the account. Write to [email protected] or ask in the support server, from the account in question.
Two honest limits, stated rather than buried:
- We cannot erase a ledger while it still owes you money. Withdraw first; then the record can be reduced to what accounting rules require us to keep.
- We cannot touch the blockchain. See Section 7.
Depending on where you live, you may have statutory rights of access, correction, erasure, portability, restriction or objection, and a right to complain to a data protection authority. Swapzy honours those requests within the limits above.
10Security
- Client applications authenticate with an API key that carries a tenant identity: a key can act only for its own users. Administrative access is a separate credential system entirely, and every administrative route is read-only.
- User deposit addresses are swept empty into a master wallet and are never signed from again.
- The ledger is reconciled against on-chain holdings, with alerts to operators on any mismatch.
- Rate limiting per user and per key, with velocity controls on the paths that move money.
- Transport is encrypted; data at rest sits on managed infrastructure with access limited to the operators who need it.
No system is beyond compromise, and a custodial service is a target. The terms say plainly what you are trusting. If we ever suffer a breach affecting your data, we will say so, in the support server and to any regulator that must be told.
11Age
Swapzy is not for children. You must meet the minimum age in the terms to use it, and Swapzy does not knowingly collect data from anyone below it. If you believe a minor is using the service, tell us and the account will be closed.
12Where the data lives
Swapzy runs on infrastructure that may be located outside your country, and the chat platforms and chain providers it talks to are international. Using the service means your data is processed in those places. Swapzy applies this policy to it wherever it sits.
13Changes
This policy changes when the system changes. The version and date at the top of this page say which one you are reading. Material changes are announced in the support server before they take effect; continuing to use Swapzy after that is acceptance of the new version.
14Contact
Privacy questions, access requests and complaints: [email protected], or the Swapzy support server. Write from the account you are asking about, or be ready to prove control of it — we will not hand one person's history to another.
This policy describes the system as it runs today. It is not legal advice. Where local law gives you stronger rights than this document describes, the law wins.
Questions about this document: the Swapzy support server.