Skip to the document

Legal

Privacy Policy

Version 1.2 · October 2026 · swapzy.cc

In short

Swapzy has no users table. Your Discord or Telegram account id is the account, and it is what balances and history attach to — no email, no password, no identity documents. Your username is cached for thirty days so a support screen can show a name instead of an eighteen-digit number, and nothing that moves money is allowed to read it. In a Discord server that turns on the Scam Shield, the bot reads messages to remove scam links, leaked keys and whatever else that server's guards are set to catch — in memory, and the text is never kept. A server's moderators can warn members, and those warnings are kept until they clear them. What we do keep is the ledger, because a custodial service has to be able to say what it owes you. Nothing is sold, and deposits and withdrawals are permanent public transactions that nobody — including us — can erase.

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.

WhatExampleWhy we hold itWhere
Your platform account idA Discord snowflake, or a Telegram id written tg:12345It is the account. Balances and history attach to it.PostgreSQL
Commands you send the bot$tip @swapmax 25 USDCTo carry out the instruction you gave.Processed in memory; the result is a ledger row
Ledger entriesuser id, chain, asset, amount, direction, status, counterparty id, optional noteThe record of what you are owed. It is the book.PostgreSQL
Transaction logson-chain hash, chain, token, amounts, fees, explorer linkTo reconcile what left the platform against what the chain did.PostgreSQL
Your deposit addressesOne derived address per chainSo a deposit can be recognised as yours.PostgreSQL
Withdrawal destinations you typeAn address you asked us to send toTo send it, and to show it back to you in history.PostgreSQL
Username, display name, avatar URLWhatever Discord or Telegram currently saysSo an operator looking at a support ticket sees a name and not an eighteen-digit number. Noted for anyone who posts or is mentioned where the bot is, because a tip can name someone who never ran a command — Section 5.Redis, 30-day expiry
Your display currencyUSD, EUR, INRSo amounts are shown in the currency you picked.PostgreSQL
Your vault PIN, hashedA salted scrypt digest, failed attempts, lock-out timeTo check the PIN you type. The PIN itself is never stored, logged or shown back.PostgreSQL
Server settingsServer name, icon, member count, owner id; switched-off channels; Scam Shield settings and banned words; moderators' warningsSo the bot behaves the way each server's administrators set it up — Section 5.PostgreSQL
Server and chat idsThe guild or chat a command came fromRate limiting, abuse handling, and sending the reply back to the right place.Logs
Ordinary service logsIP address, timestamp, endpoint, errorSecurity, 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 messages to find its commands and, in servers that turned on the Scam Shield, to catch scams and leaked keys. It keeps none of that text. It is not a log of your server — Section 5 says exactly what it reads and why.
  • Nothing used to train AI. No message, name or record is used to train a machine-learning or AI model, ours or anyone else's.
  • 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

Figure 1Two stores with different jobs. The book is durable and lives in PostgreSQL; the name cache is a copy of something Discord owns and expires by itself.

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.
  • Nobody, for the Scam Shield. The bot downloads MetaMask's public phishing list to check links against. Nothing about you, your messages or your server is sent to get it, and no message is sent anywhere to be checked.
  • 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

This section is the whole of what the Discord bot sees, what it does with it, and what is kept.

What Discord sends the bot

The bot asks Discord for four kinds of event, called intents. It does not ask for the member list of any server or for anyone's online status or activity.

IntentWhat it deliversWhat the bot uses it for
ServersThe servers the bot is in, their channels and its own permissions thereKnowing where it can reply, and what it is allowed to do
Server messagesMessages posted in channels the bot can see, and edits to themFinding its commands, and running the Scam Shield where a server turned it on
Message ContentThe text of those messagesThe same. Without it Discord sends the bot only messages that mention it
Direct messagesMessages you send the bot privatelyCommands sent by DM

Commands

When you use a slash command, or type a command after the bot's prefix or a mention of the bot, the bot receives your account id, the command and its arguments, and the server and channel it came from. It sends the instruction to the Swapzy backend, which carries it out. The command text is not stored; what is stored is the result — a ledger row for a tip or a withdrawal, a changed setting for a settings command.

In a server where the Scam Shield is off, the bot looks at each message only to see whether it is a command, and ignores the rest.

Names

For the author of each message the bot sees, and anyone that message mentions, the bot notes their username, display name and avatar link in the name cache described in Section 2. That is so a balance received as a tip can be shown with a name, even when its owner has never run a command. It expires after 30 days. The message itself is not noted.

The Scam Shield

The Scam Shield is a moderation feature for crypto servers. It is off unless a server's administrators turn it on, guard by guard, with /shield, and they can turn any guard off again at any time. Where a guard is on, the bot reads every new or edited message in that server, apart from other bots':

  • Leaks — a recovery phrase or private key, recognised by the recovery word list and by key checksums, so addresses and transaction hashes are left alone. This applies to everyone, moderators included, and the author is sent a private warning.
  • Scams — a link on MetaMask's public phishing list, which applies to everyone; a link made to look like a known site; or a link posted with wallet-scam wording such as a fake airdrop claim.
  • Impersonation — a name made to look like Swapzy staff, a request for someone's recovery phrase or private key, or an offer of "support" by private message.
  • Links — a link to a site the server has not allowed. Discord message links, Discord's own images, GIF sites and swapzy.cc are always allowed.
  • Spam — the same message three times in thirty seconds from one person, which is what a hijacked account does with a drainer link. Every copy is removed.
  • Words — a word or phrase the server's administrators have banned, matched as a whole word in any case. The notice says a banned word was used, not which.
  • Mentions — @everyone or @here, or five or more members and roles pinged in one message.
  • Invites — an invite link to another Discord server.
  • Caps — a message written mostly in capitals, or one with ten emoji or more.

Members who can manage messages, manage the server, kick, ban or time out are trusted by every guard except Leaks and the phishing list.

When a guard objects, the bot removes the message if it has permission, posts a short notice in the channel that deletes itself after fifteen seconds, and — if the server chose a log channel — posts an entry there. The notice and the entry say who posted, in which channel, which guard acted and why. They never quote the message. A link is named by its site alone, written so that it cannot be clicked.

How the text is handled. Messages are checked in the bot's memory, by fixed rules rather than any AI model, and the text is dropped as soon as the check is done. It is not written to a database, a file or a log, it is not sent to anyone — the phishing list is downloaded to the bot, never the other way — and it is not used to train anything. The spam guard is the one exception to "nothing is kept", and a narrow one: it holds a one-way fingerprint of each message, which cannot be turned back into the text, with its channel and message id, in memory, for thirty seconds.

Moderation commands

The bot also gives a server's moderators commands to delete recent messages (/purge), time a member out, kick or ban them and lift either, slow a channel down or make it read-only (/slowmode, /lockdown), and warn a member (/warn, /warnings, /clearwarnings). Each one works only for a moderator who holds the Discord permission it uses, and only on members whose roles are below the bot's, and below the moderator's unless the moderator owns the server. Nothing happens unless a moderator runs one.

When a moderator acts on a member, the bot tries to tell that member by private message which server it was and the reason given, if any — before a kick or ban, and after a timeout or warning. If the server chose a Scam Shield log channel, every moderation command is also posted there, with who ran it, on whom or which channel, and the reason. A reason is also passed to Discord, which shows it in the server's audit log. Messages removed with /purge are not kept. Warnings are the only thing these commands store, as shown below.

What is kept about a server

WhatWhyUntil
Server id, name, icon, member count and owner id, and when the bot joined or leftSo operators know where the bot is, and can answer a server ownerKept, marked as left when the bot is removed
Channels where an administrator switched commands off, and who did itSo the bot stays quiet thereAn administrator switches them back on
Scam Shield settings: the guards that are on, the log channel, the allowed sites, the banned words, and who last changed themSo the shield does what the server askedAn administrator changes them
Warnings: the warned member's id, the moderator's id, the reason, and whenSo moderators can see a member's record in that server with /warningsA moderator clears them with /clearwarnings
Airdrop rounds: the host, the channel and message, the pot, who joined and who wonTo pay out the round and keep its recordKept, as part of the ledger

What Discord data is never used for

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, it is not sold, it is not used to train AI, and it is not passed to a third party for their own purposes.

Removing the bot

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. A server's administrators can ask us to delete its settings at the address in Section 14.

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

Figure 2Three different clocks. The name cache expires on its own; logs rotate; the book is kept because a custodial ledger has to be.
  • Message text — not kept. Commands and Scam Shield checks are done in memory and the text is dropped; the spam guard's one-way fingerprints last thirty seconds.
  • Username cache — 30 days from the last time a bot wrote it, then it is gone unless you use the service again.
  • Server settings — until a server's administrators change them, or ask us to delete them.
  • Warnings — until a server's moderators clear them, or its administrators ask us to delete them.
  • 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.