Privacy Policy

TalciGrade is a Discord bot, so nearly everything it holds is Discord data: IDs, and the records your own settings produce. We never ask for your real name, your address, or anything sensitive.

The short version

• We store Discord IDs and the records your server's settings produce.
• We do not store your email, your password, or any payment details.
• We do not sell or share your data. There is no advertising, and nothing on this site reports you to anyone else: no third-party analytics, no tracking script, no cross-site tracking.
• We do keep our own aggregate counts of how busy the service is, described further down. They are totals, not a record of what any one person did.
• The only feature that stores what people actually said is tickets, and only while the ticket is being handled.

Signing in

The dashboard signs you in with Discord. Discord tells us your user ID, username, avatar, and which servers you are in along with your permissions there. The server list is used for one thing: deciding which servers to show you.

Your login lives inside the cookie itself, as a signed and encrypted token, rather than in a table of sessions here. The access token Discord gives us is carried in that cookie too, which is how the dashboard can ask Discord for your server list without us keeping a database of logins. Signing out, or the cookie expiring, is the end of it: there is no row left behind to delete.

What the bot stores

Only what a switched-on feature needs.

For any server the bot is in we keep the server's ID, name, icon and member count, along with whatever you have configured. After that it is the records the features themselves produce: moderation cases (who was actioned, by whom, and why), XP and levels, invite counts, quarantine records, periodic snapshots of your server's roles and channels, and a log of changes made from the dashboard. None of those hold message content.

Two of them clear themselves out: the dashboard change log after 30 days, and captured ticket messages after at most 180 days.

Leveling also keeps the username and avatar it last saw for each member. That is so the public leaderboard still works while the bot is offline, when the alternative is a list of numbers.

Tickets, the one exception

Tickets are the only feature that stores what people said, and even then only what Discord could not tell us later: the text a message used to have before it was edited, and messages that were deleted. Everything else is read back out of the channel when the ticket is closed, so an open ticket is not sitting in our database as a copy of your conversation.

When the ticket closes, the transcript is assembled from that and saved on the ticket, and the few records kept along the way are deleted. If the channel is deleted before the ticket is closed, the ticket ends with no transcript and those records go too.

Logging

The logging module posts entries into your own Discord channels. We do not keep a copy of them.

So that it can tell you what an edited or deleted message used to say, the bot briefly holds the most recent messages in its own working memory. They are never written to the database, there is a hard limit on how many it holds at once, and it forgets every one of them whenever it restarts.

Two-factor authentication

If you turn it on, your setup key is stored scrambled and your backup codes are stored as one-way fingerprints. Neither can be read back out, by us or by anyone who somehow got hold of the database.

The status page

The public status page measures our own machines: processor, memory and network use, and whether each part of the service was up. It holds no user data at all. Full-detail measurements are kept about 14 days, hourly averages about 2 years, and daily averages are kept indefinitely, so the page can go on showing its own history.

Counting how it is used

We count aggregate numbers about the service itself, so we can tell when something is slow or broken: how many dashboards are open, how many requests and commands there were, how long the bot took to answer. They are totals for a period of time, not a record of what any one person did. There is no tracking script, it needs no extra cookie, and none of it goes to anyone else.

We also count how many times each public page was opened, and roughly where visits came from: a search engine, Discord, a social site, a link somewhere else, or straight to us. The address you arrived from is sorted into one of those groups and then forgotten, so it is never written down.

To tell one visitor from two we work out a short code from your network address and browser, mixed with a secret that changes every day. It is not a cookie, nothing is stored in your browser, and it cannot be turned back into your address. Because the secret changes daily, the same person tomorrow is a completely different code, so the records cannot be joined up across days and nobody can be followed. That also means we can never tell whether someone has been here before. We keep these visit records for 90 days and then delete them; the daily totals they add up to are kept.

Who else sees it

Discord, necessarily, since that is where the bot runs. Our hosting providers, who run the machines the bot and the database sit on: they are on this list because the hardware is theirs, not because they are shown anything. We send them nothing, they have no account on any of it, and nobody there is looking at your server. And bot listing sites, but only if you vote for us on one: they send us your user ID so the reward can be applied, and nothing travels the other way.

That is the whole list. No analytics companies, no advertisers, no data brokers.

Deleting your data

Removing the bot from a server stops collection for that server straight away, and the rest goes on its own after that. Anything the bot was in the middle of (open ticket messages, pending reminders, transcript links) is deleted within days, and the server's history is compressed into a single archive after a month. Add the bot back and the history comes back with it.

To have a server's data deleted, ask in the support server as someone with Manage Server on it. The bot has to have been removed from the server first, otherwise it is still in use and would simply start recording again. This we can do completely: everything belonging to that server goes.

It does not all happen the moment you ask, and we would rather say so than imply otherwise. The server disappears from our staff tools straight away and nothing can be looked at any more, but the records themselves are cleared out on a weekly batch, and for 3 months after that a compressed copy is kept so the deletion can be undone if it turns out to have been a mistake. Nobody browses that copy; the only thing it can be used for is putting the data back, and after 3 months it is destroyed.

If you add the bot back before that copy expires, your data is not restored automatically. You asked us to delete it and we would rather not quietly undo that, so the server starts fresh; ask us and we can put the old data back while the copy still exists. Adding the bot back before the weekly batch has run simply cancels the deletion, since the server is obviously in use again.

For up to 12 months from the day you ask, we keep one small record of the deletion itself: the server's id, its name, who owned it, the ticket it was asked in and the reason. That is so we can tell you what happened if you come back and ask why your data is gone, which we cannot do if we have deleted the fact that we deleted it. After that the record goes too, and nothing about the server remains here at all.

Your own data is a harder question, and we would rather be straight about it than promise something we cannot do. Almost everything we hold exists inside a server's records rather than in a profile about you: a moderation case names a moderator and a member, your XP belongs to the server that granted it, a ticket transcript is a conversation with several people in it. Those records are the server operator's, and pulling your half out of one would destroy someone else's.

So there is no button for this, and it is not something that happens automatically: ask in the support server and it is handled by hand. We will tell you, record by record, which are yours alone and which belong to a server. The ones that are yours alone we remove. For the rest the request belongs to the server operator, who can have the whole server's data deleted the way this page already describes.

Changes

The date at the top of this page is when it last changed. Anything significant is announced through the updates feed.