Privacy Policy
What is stored, why, for how long, and how to get rid of it.
Last updated 21 October 2026. Previously published as Soundcord Utility.
The short version
- Nothing is recorded until a server administrator switches a feature on, except join and leave records, which retention and invite counts need from the start
- Message content is never written to our database
- Join and leave records are kept while the bot is in your server, because retention and invite counts are worked out from them
- Remove the bot and everything for that server is deleted after 30 days, apart from a short record of where it added the bot from
- A support ticket is yours rather than a server's, and is kept until you ask for it to go
- Card details never touch our systems; Stripe handles payment
- Nothing is sold, shared, or used for advertising
1. What is stored
Only what a feature needs, and only for features that are switched on. Join and leave records are the one exception: they start when the bot is added, because retention and invite counts are worked out from them.
| Feature | What is kept |
|---|---|
| Settings | Your server's ID, the channel and role IDs you pick, the welcome, goodbye and sticky message text you write, your counter name templates, your automod word lists and allowed sites |
| Retention and invite tracking | For each member: their user ID, the date they joined, the date they left if they have, how old their account was when they joined, whether they had been in the server before, and which invite they came in on, including its code, the user ID and display name of whoever made it, and whether that person was on the server's invite blacklist. When the invite couldn't be worked out, the reason why. Nothing about what they said or did |
| Invite counts | Bonus invites and resets an admin gives: who they were for, the amount, the reason typed, who gave them and when. The names you give your invite links, and the role each one hands out |
| Ratings | The score from 1 to 10 a member gave, against their user ID. One per member; a new score replaces the old one |
| Moderation | Each ban, kick, timeout or warning: who it was for, who did it, the reason typed, and when. Automod actions are recorded the same way |
| Role buttons | The panels you build and which roles are on them |
| Survey reminders | That a reminder was sent, to which joining group, and how many members it reached. No individual member IDs |
| Support tickets | Your user ID and username, the server you picked if you picked one, the subject and message you wrote, and every reply on the thread afterwards |
| Premium | Whether a server has an active subscription, the identifiers Stripe assigns it, and the email address given at checkout, which Stripe passes on, against the server's ID. Never a card number |
| Birthdays | The day and month a member sets, and the year only if they choose to give it, against their user ID and the server |
| Sticky roles and freezes | If a server switches sticky roles on: the role IDs a member had when they left, so they can be given back on return. A frozen member's removed role IDs are kept the same way until they are unfrozen |
| Fun commands | Counts of hugs, pats and the like given and received, marriages between two members, and would-you-rather polls, against user IDs |
| Mog battles | The two members' user IDs and display names, their scores, the winner and the judge's one-line reason. Never the photos |
| Levels | If a server turns levels on: each member's XP, how many of their messages and voice minutes counted, their display name and their rank card colour, against their user ID and the server. Never what the messages said. If an administrator imports from MEE6, the server's ID is sent to MEE6 to read its public leaderboard |
| Giveaways | The prize, who started it, the user IDs of everyone who entered, and the winners' user IDs and display names |
| Ticket channels in your server | Who opened each ticket, who claimed it, who was added, and when each of those happened. Never what anybody wrote in it |
| Direct messages to the bot | For each person: their user ID, name and avatar, and when the last message was, so a reply can be sent. Never what the message said |
| Welcome card pictures | A background image a server administrator uploads on the dashboard |
| Newt coins | Once somebody uses a coin command: their user ID, coin balance and daily streak. Each payment and daily claim is logged against their user ID, with the other person's user ID and any note typed on a payment. Chatting earns coins, but only the time of the reward is used, never the message. Bumping a server on Disboard keeps their keys, the crates they hold, their key streak and how many crates they opened, and buying keys in the crate shop keeps how many they bought that day, against their user ID. Buying a role in a server's role shop keeps which role they bought there, the price and when, until they throw the role away or the bot leaves that server |
| Pond Empire | Once somebody uses a pond command: their user ID and their pond, meaning its upgrades, flies, shells, pearls, items and eggs, their newts and the names they give them, their streaks, achievements and settings, and the colony they are in. Somebody who turns on pond reminders also has when Newt last reminded them and when they last played kept, to space the reminders out. A colony keeps its name, its members' user IDs, its bank and who gave how much. Raids, snatches, trades and colony donations are logged against the user IDs involved, to look into cheating |
| Blocks | If somebody abuses Newt: the user or server ID that was blocked, the reason, and which of Newt's developers blocked it |
| Usage counts | How many times each command ran each day, and how many servers added or removed the bot. Totals only, with no user or server IDs |
| Error reports | Where in the bot's code an error happened, how often, and when. Never the error's message, and nothing about who ran the command |
| Developer log | What Newt's developers changed from their own panel or on a server's dashboard, with the server's ID and which developer did it |
| Counting | If a server turns counting on: the counting channel, the current number, the server's best, and the message ID, number and user ID of each of the last 50 counts, so an edit or delete can be spotted. For each member, how many numbers they counted and got wrong, and their display name, against their user ID and the server. If the server gives a role for a wrong number, when to take it off again. Never what the messages said |
| Suggestions | The title and idea a member sends with /suggest new, their user ID and display name, the user IDs of everyone who voted and which way, and each status staff set, with who set it, the reason typed and when |
| Anti-nuke counts | If a server turns the anti-nuke on: each ban, kick, timeout, purge or delete it counts, with the user ID of who did it and the ID of what it was done to, and who it stopped. Kept so a restart doesn't reset its limits |
| Messages kept for the logs | If a server logs deleted or edited messages, or deleted media: what each message said, the names of its files and the files themselves up to 8 MB, all encrypted, against the message, channel, server and author IDs. Section 3 has the detail |
| Votes for Newt | Once somebody votes for Newt on a bot list website: their user ID, when they last voted on each website, how many times, their vote streak, and whether they asked for a reminder. The website tells us their user ID, name and avatar. Only the ID is kept |
| Where a server added the bot from | When a server adds the bot: the server's ID and name, how many members it had, when it was added, and which link it came through, such as a link on our website, a bot list, or the /invite command (with the ID of the server /invite was used in). Then when it removed the bot if it does, whether anybody used the bot in its first week, and how many commands ran in its first 30 days. Also the user ID of whoever added it, read from the server's audit log, so we know who to talk to about that server. Never who ran the commands. Clicks on those links are counted per day, with no IDs |
| Logging in to the dashboard | Your user ID, the login key Discord gives the website, and the list of servers you manage (each one's ID, name, icon and your permissions there), so the dashboard can show them without asking Discord on every click |
| Pond Empire's Activity, Pond World and Explore | Opening the game inside Discord starts a session: your user ID, display name, and the server, channel and Activity you opened it in. In Pond World and Explore, against your user ID: your inventory, what you bought in its stores, boosters you are using, and Explore's finds you have not banked yet and the receipts waiting to be paid into your pond. Placed blocks and dropped items are saved with the room, not against anybody. Others in the room see your display name and your server's icon. Chat is passed on to the room and never kept |
2. What is not stored
- Message content, unless your server switches message logging on. Section 3 says what is kept then, and for how long
- What direct messages say. Only who and when is kept, as in section 1
- Real names or IP addresses. Neither is collected. The only email kept is the one given when buying Premium
- Card numbers. Buying Premium happens on Stripe's own pages, and your card details go to Stripe, never to us
- Voice audio. The voice log records only that somebody joined, left or moved between channels, never anything said
3. Message content, and where it goes instead
Three features handle message content. Two post it to a channel in your own server, and to do that the bot keeps a copy for a short time first. One sends photos to an AI judge.
The server log
Discord tells a bot nothing about a deleted message except that it is gone, so to show you what it said the bot has to have kept it beforehand. If you switch on the deleted, edited or bulk deleted message logs, each message in your server is kept in our database for 24 hours, or 30 days on Premium: what it said, who sent it, where and when, and the names of its files. Messages in the channels you tell the logs to ignore, and in the log channels themselves, are never kept. Each one is encrypted with AES-256, and it is erased as soon as its deletion has been logged or its time is up, whichever comes first. Switching those logs off erases everything kept for your server. If the bot is removed from your server, or its Premium ends, what is kept is cut back within 48 hours. The log entries themselves are posted in your server, under your control, and are yours to delete.
The deleted media log
Discord destroys an attachment the moment its message is deleted, so to show you a deleted image at all the bot has to hold a copy beforehand. Files of up to 8 MB are kept on the bot's server, encrypted with AES-256, for as long as the message they came with: 24 hours, or 30 days on Premium. They are never written to the database. When a message is deleted, the copy is posted into your log channel and erased.
Mog battles
Both fighters post a selfie in the channel. The bot takes each photo, shrinks it, and sends the pair to Google's Gemini AI to be judged, then posts one result image. The photos are held in memory only while the battle runs and are never stored. Google's handling of what it receives is covered by Google's own terms.
4. Support tickets
A ticket opened on the dashboard is the one place where you write something to us and it is stored. What is kept is your Discord user ID and username, the server you chose if you chose one, the subject and message you wrote, and everything either side has said on the thread since.
Only Newt's developers can open, read or answer tickets, and nobody in your server sees them. A ticket may be copied into a private channel in our own Discord server so it can be read and answered there. Replies come back to you on the support page, and may also arrive as a direct message from the bot.
A ticket is yours rather than a server's, so removing the bot from a server neither closes it nor deletes it, and the 30 day rule in section 6 does not apply to it. Tickets are kept until you ask for them to go, including the closed ones, so that a conversation can be picked up again months later.
5. How long it is kept
| What | How long |
|---|---|
| Join and leave records | While the bot is in your server. The dashboard shows the last 180 days, or a year on Premium |
| Survey reminder log | 30 days, then deleted automatically |
| Messages and files kept for the logs | 24 hours, or 30 days on Premium. Sooner once a deletion is logged, and within 48 hours of the bot being removed |
| Mog battle photos | Only while the battle runs, in memory |
| Giveaways | 60 days after they end, then deleted automatically |
| Daily joining-group roles | About 9 days, then removed |
| Settings, ratings, moderation cases, suggestions, bonus invites and resets | While the bot is in your server |
| Premium subscription records | While the subscription exists, and afterwards as long as bookkeeping requires |
| Support tickets | Until you ask for them to be deleted |
| Newt coin history (payments, daily claims) | 90 days, then deleted automatically |
| Newt coin wallets | Until you ask for yours to be deleted |
| Pond Empire's log of raids, snatches, trades and donations | 30 days, then deleted automatically |
| Ponds, newts and colonies | Until you ask for yours to be deleted |
| Blocks | Until the block is lifted, even after the bot leaves that server |
| Usage counts | Kept as totals, since they hold no IDs |
| Error reports | 30 days after the error last happened, then deleted automatically |
| Developer log | 180 days, then deleted automatically |
| Bump keys and the key streak | Until you ask for yours to be deleted |
| Anti-nuke counts | An hour at most, then deleted automatically |
| Vote records | Until you ask for yours to be deleted |
| Where a server added the bot from | Kept, also after the bot is removed. Section 6 explains |
| Dashboard logins, with your list of servers | Until you log out, or 7 days at most, then deleted automatically |
| Activity sessions | 12 hours, then deleted automatically |
| Pond World inventories, Explore's finds and receipts | Until you ask for yours to be deleted. A receipt goes once it is paid in full |
6. When you remove the bot
Everything belonging to that server is deleted 30 days after the bot leaves: settings, join and leave history, ratings, moderation cases, role panels and the reminder log.
The delay is deliberate. Bots get removed by accident, or kicked and re-added while somebody sorts out permissions, and erasing a server's whole history the instant that happens would be its own kind of problem. Add the bot back inside those 30 days and nothing was lost.
Messages the bot already posted into your channels, such as log entries and moderation cases, stay in your server. They are yours, and only you can delete them.
Support tickets are the one thing left out of this, because they belong to the person who opened them and can be about no server at all. Section 4 covers them.
Newt coin wallets are left out too. A wallet is one person's and the same on every server, so one server removing the bot doesn't take it away.
Ponds are the same. A pond, its newts and its colony belong to people rather than to a server, so they stay when one server removes the bot.
Bump keys are the same too: one person's, on every server.
Vote records are as well.
One short record about the server stays too: when it added the bot, where from, and how that went, as section 1 lists. It holds the server's ID and name and the user ID of whoever added the bot, and nothing about its other members. It is how we learn which places bring servers that keep the bot.
Pond World inventories and Explore's finds are one person's too, so they stay.
7. Asking for your data to be deleted
Ask and it will be done, sooner than the 30 days above.
- A whole server. A server administrator can ask for everything to be erased immediately
- One person. Anybody can ask for their own records to be removed: their rating, their join and leave dates, and their moderation cases
- Your tickets. Ask and every ticket you have opened is deleted, including the replies on it. Say so in the ticket itself if that is easiest
- An invite you made. Ask and your name is cleared off the joins recorded against your invites, which leaves the join counts intact and the name gone
- Your Newt coins. Ask and your wallet, coin history and bump keys are deleted
- Your pond. Ask and your pond, your newts and your part of the Pond Empire log are deleted, and you are taken out of your colony
- Your votes. Ask and your vote record is deleted, and any reminder with it
- A server you added the bot to. Ask and your user ID is cleared off the record of that add
- Your Pond World. Ask and your inventory, your Explore finds and your receipts are deleted
Please include the server ID, and your Discord user ID if you are asking about yourself, so the right records can be found. Contact details are at the bottom of this page.
8. Who else sees it
Data is not sold, rented, shared with advertisers, or used by us to train anything. The bot, this website and the database run on a server we operate ourselves, so no hosting company holds your data.
Four outside services are involved: Discord, which the bot talks to and whose own privacy policy covers everything on their platform; Cloudflare, which carries traffic to this website and so sees visitors' IP addresses the way any web host does, without us storing them; Google, whose Gemini AI judges mog battles and receives the two photos of each battle; and Stripe, which handles payments and sees what a payment needs, not your server's data. Each handles only what its part needs, under its own privacy terms.
Server statistics such as member counts, roles and activity are read live from Discord when you run a command and are not stored afterwards. The one exception is each server's name, icon and member count, which the bot keeps up to date for its developers and replaces as they change.
With Premium, a server administrator can download that server's own records as CSV from the dashboard. That is your data going to you, not to anyone else.
9. Security
The database runs on the same private server as the bot. It cannot be reached from the internet, and it asks for a password even from inside. Visitors reach this website only through Cloudflare, over an encrypted connection. The dashboard signs you in through Discord, so it never sees your password, and it re-checks with Discord on every request that you still administer a server before showing or changing anything about it. Newt's developers can also open any server's dashboard, to help with support and to test fixes, and everything they change there is logged.
No system is completely secure. If you find a problem, please report it privately using the contact details below rather than publicly.
10. Children
Newt is not aimed at children. Discord sets its own minimum age, which varies by country, and you must meet it to use Discord at all. If you believe a record exists for somebody below that age, ask and it will be removed.
11. Changes
This policy may be updated. The date at the top shows when it last changed. If a change means collecting something materially new, it will be announced before it takes effect.
12. Contact
For anything on this page, including deletion requests, open a ticket on the Support page. Tickets are private: only Newt's developers read them.
Or email [email protected], which reaches the same people.
A server ID, or a Discord user ID if you are asking about yourself, is all that is needed.