What this bot remembers

Identifiers and counters, not conversations

QuantLab stores Discord IDs and the numbers attached to them — your level and the warnings against you — plus, where a server uses the giveaway entry check, one-way hashes that tell two accounts apart (section 02). It does not keep a copy of your conversations, it never asks for an email or a password, and it does not sell or share anything with advertisers.

Everything it keeps, in one list

Discord user ID

The number that identifies your account. It is the key every record below hangs off.

Server & channel IDs

Which server a setting belongs to, and which channels a feature posts in.

Retired features

Balances, shop purchases, collected cards and lottery entries left over from the coin economy, which has been removed. The bot no longer reads or adds to them; ask the operator to have them deleted.

Levelling

XP, level, a count of messages that earned XP, and the timestamp of the last one — the count only, never the messages.

Moderation records

Warnings, kicks, bans, timeouts and reports: who, by whom, when, and the reason a moderator typed.

Giveaways

Who entered which giveaway, and who won.

Giveaway entry check

If a server uses it, the verification page records three one-way hashes per member: of a random ID kept in your browser, of your browser's characteristics (screen, timezone, graphics), and of the internet address the page was opened from. The raw values are never stored and cannot be read back; the hashes are keyed per server, so they mean nothing anywhere else. They exist only to tell whether two accounts in the same server are the same person, and are deleted when you leave that server.

Server configuration

Everything an administrator sets — embed templates, scheduled posts, auto-replies, feeds, message wording and colours.

Panel session

Your user ID, display name, avatar reference, and the list of server IDs you can manage. Held in a signed token in your browser.

Data is held either in a database or in files on the server the bot runs on, depending on how the operator has deployed it.

The three times text is written down

Message content is otherwise processed and dropped. It is only retained when a server has deliberately switched on one of these:

Moderation logging

If a server enables message logging, a deleted or edited message's text is copied into that server's log channel so its moderators can see what happened. It lives in that channel, under that server's control.

Ticket transcripts

If a server enables transcripts, the contents of a support ticket are saved when the ticket closes.

Reports

When a member files a report, the reason they write and any link they attach are stored with it.

In all three cases the server's administrators chose to turn the feature on, and they can turn it off.

Each thing has one job

• To make the features work at all. A level that resets every restart is not a level.
• To enforce fairness. Cooldowns and ticket limits need to remember what you already did.
• To give moderators a record. A warning nobody can look up later is not moderation.
• To keep you signed in to the panel between visits.

There is no profiling, no advertising, and no automated decision with a legal effect on anyone.

The panel asks Discord, not you

The control panel signs in through Discord's own OAuth. It requests two scopes — identify and guilds — which tell it who you are and which servers you are in.

The access token Discord returns is used once and discarded. It is never written to storage. The panel cannot post as you, read your messages, or act on your account in any way; it only ever acts as the bot.

What remains is a signed session token in your browser holding your ID, display name, avatar reference and manageable server IDs. Signing out discards it.

Your server's staff, and nobody else

Anyone with Manage Server on a server can see that server's data through the panel — levels, warnings, tickets and configuration. That is the same group who could already see it through Discord's own tools.

Data is not sold, rented, or shared with third parties for their own purposes. It leaves the bot only in these ways:

• Discord, which is where every message the bot sends necessarily goes.
• The hosting provider the operator runs the bot on, and its database provider if one is used.
• Public sources the bot reads from — news feeds, an economic calendar, YouTube and similar. These are fetched from; nothing about you is sent to them.
• Where the law requires it.

Until it stops being needed

• Levels stay while the bot is in the server, so your progress survives.
• Cooldowns expire on their own.
• Moderation records stay until a moderator clears them.
• Panel sessions expire, and signing out ends them immediately.
• Removing the bot ends all processing for that server. Ask the operator if you also want the stored records deleted.

Seeing it, and deleting it

Much of your own data is readable from Discord right now: /rank for level and /warnings for moderation history.

For a copy of everything held about you, or for deletion, contact the operator of the bot through the support server or the contact route published where you added it. Ask your own server's administrators first for anything they control directly — levels, warnings and configuration are theirs to change.

Deleting a record may reset progress tied to it. That is the trade, and it is yours to make.

Discord's minimum age applies

Discord requires users to be at least 13, or older where local law sets a higher age. This bot is not intended for anyone below that, and no data is knowingly collected from them. If you believe a younger user's data is held, contact the operator and it will be removed.

When this page moves

If what is stored or why it is stored changes, this page changes with it and the effective date at the top is updated. Continuing to use the bot after that means accepting the current version.