Who we are
Dexter is a community project, not a company. The bots and this website are run by the owner of the Dexter AI community server on hardware they control, with help from the server’s staff team. In this policy, “we” means that owner and team.
We do not sell your data, show advertising, or use analytics or tracking services.
What we collect
The bots only see what Discord shows them in the server and in direct messages sent to them. What they keep depends on what you do:
Your Discord identity
- Your Discord user ID, username, display name and server nickname, when we first and last saw you, and a history of the names you have used in the server.
- Recent avatar and banner changes (the newest 20 of each) and display-name clean-ups made by the name filter.
Activity in the server
- Counts of the messages you send per day (with length and timing statistics), time spent in voice channels, who you were in voice with, and reply and mention counts between members. We do not store the text of ordinary messages for this; activity data is numbers only.
- When you were last active, which channels you are active in, which commands you run and how often, and which invite you joined through.
- Levels and XP, streaks, reminders you set, AFK messages, and your time zone if you set one.
- Your birthday if you save one with
/birthday: the month and day, the time zone it is celebrated in, the birth year only if you give it (it is never shown, and your age is never displayed), the last year it was announced, and when a 24-hour birthday role comes off./birthday removedeletes it; if this year’s birthday was already announced, only that fact is kept (no date) until the next year, so it can’t be announced twice. - Suggestions and reports you submit, including any text and image link you include.
- If the server gives roles for time spent in it: which of those roles you were given and when you joined, so each is given only once per stay.
- Your giveaway and lottery entries, starboard and suggestion votes, temporary voice rooms you own, forum help posts you open, temporary roles you are given, and when you boost the server.
- No voice audio is ever recorded. Where the voice word filter is on, speech is turned into text to check it and then dropped (see Events, votes and roles).
The economy
- Your wallet and bank balance, inventory, transaction history, job, pets, marriage, quests, achievements, cooldowns, and a log of economy commands you run with their options and results.
- Fair-play records: risk scores, human checks, flags, and links the anti-cheat system draws between accounts that appear to be the same person. These links are based on activity inside Discord (shared voice time, replies and mentions, coin transfers, and invite and join timing). We do not use IP addresses or device fingerprints for this.
Moderation and safety
- Moderation cases (warnings, timeouts, kicks, bans) with the reason and warning points, private staff notes, and automod actions with the text that triggered them (up to about 1,000 characters).
- Evidence staff keep on a case: the message a case is about (its author, text and link), messages they link to, and copies of the files they attach. It is kept with the case for as long as the case, and only staff see it: never the public mod log or the member.
- When staff lock a channel or set slowmode for a set time, who set it and when it ends, so it can undo itself.
- When staff change the reason on a moderation case: who changed it, when, and what it said before, kept with the case so the change can be reviewed.
- Announcements staff schedule for the bots to post, with who set them up.
- Channels staff set to be cleared on a schedule, and which staff member set it up. The deleted messages themselves are handled like any other deleted message (see above).
- The content of deleted and edited messages in logged channels, including messages automod removes and copies of attachments, kept so staff can review raids, scams and abuse. Discord’s own audit-log entries for the server are archived for the same reason.
- A temporary copy of images posted in the server, kept for 48 hours so a deleted image can still be reviewed in the logs.
- Staff log channels in Discord show what was edited or deleted, including the text and re-uploaded images. Those posts stay in Discord until staff remove them.
- When a log post can’t hold everything (a bulk delete of more than 10 messages, a long edit, or a deleted message with many files), a copy of the deleted or edited messages the bots still had, with their images, is kept as a staff-only page linked from the post. Only staff can open it, and it is deleted after 90 days.
- Trust and risk signals used to protect the server, such as new-account and raid indicators.
- If you message Steward, the full modmail conversation is stored so staff can follow up, with the images and files in it. Like ticket transcripts, it is visible to staff only.
- If you ask staff for help while verifying, the message you type is stored with your request.
- Scam reports you send in direct messages, with the evidence you provide.
- Blocks staff place on you, such as from modmail, appeals, AFK or the bots, with who placed them.
Tickets, the help desk and surveys
- If you open a ticket: the reason and any form answers you give, who claimed, closed or reopened it and when, and a full transcript of the ticket channel when it closes (every message with its images and files), so staff can review it later. Transcripts are visible to staff only.
- Questions you type into the help desk, or ask in a channel where it answers automatically: the question, which answer you were shown, and whether it helped or you opened a ticket.
- Survey answers. On a named survey your user ID is kept with your answers. On an anonymous survey we keep only a scrambled code (a keyed one-way hash of your user ID) that stops you answering twice.
Music
- The songs played in the server and who asked for each (the latest 500 per server), and the playlists you save with
/playlist: their names, tracks and whether they are public. - If you connect Spotify on the dashboard: your Spotify user ID and display name, the permissions you granted (reading your playlists and saved songs), and a refresh token, stored encrypted, so the music bots can load your playlists when you ask. Disconnecting deletes it.
/play listeningreads the song you are playing on Spotify from your Discord status at that moment, to play the same song. It is not stored.
Events, votes and roles
- If you sign up for an event pass, the Minecraft username you submit and whether Mojang confirmed it exists.
- When a new event starts and clears an event board (your event message count, voice minutes or chat drops won), the board as it stood is saved first, so staff can put it back if the reset was a mistake.
- During a voice event, the random activity checks we send you (when, whether you passed, failed or missed them) and the event voice minutes they confirmed or took back, which staff review before prizes are given. A check comes one of three ways: by DM (or in the voice channel’s chat), as a private link to a short check on our website (we keep only whether you answered it right, never what you typed beyond that), or as a code a bot says aloud in your voice channel; that speech is made on our server for the check and never kept. Accounts the verification check links to yours (through the scrambled connection and device codes described under Verification) don't count as each other's company in voice. No audio is ever recorded.
- During voice events, bots may join voice channels to see who is speaking and when; no audio is recorded or kept.
- Where the server turns on its voice word filter, bots in busy voice channels turn what is said into text on our own server and check it against the server’s word filter, the same list that applies in chat. Audio is never recorded, kept or sent to anyone else, and the text is checked and dropped. Only a line that matches a blocked word goes to staff as a private alert (who said it, the channel, the time and the line as it was heard), so a moderator can check it; nothing is done automatically. The alert stays in the staff channel like other moderation alerts.
- If you vote for the server on top.gg, top.gg sends us your user ID and the time of the vote, which we use to give the vote reward.
- If the server keeps certain roles for members who leave, the roles you held when you left, so they can be given back if you rejoin.
If you are on the staff team
- The staff monitor keeps a record of each staff member’s work: online status and device type, custom status text and the activities Discord shows (such as a game), time in voice channels, and for each message its length, word, mention and emoji counts (never the text), reactions, commands used, and how quickly questions addressed to staff were answered. Members who ask staff a question or mention them are recorded as the asker (user ID and time), not with their message.
- When the owners save a staff monitor result, a copy of that period’s figures for each staff member in the group (their user ID, the name shown then, their counts, times and score), with who saved it and when. A saved result is never changed afterwards.
- The permissions a staff member is given, and the words they ask Warden to highlight for them.
Verification
- When you verify, we record the method, the outcome, how long it took and how many attempts it needed. Image checks keep a short-lived session for 10 minutes.
- The web check at
/verifyuses Cloudflare Turnstile. Your browser loads Cloudflare’s widget, and our server sends Cloudflare your answer token and your IP address so it can confirm the check. - The web check also shows a picture code drawn on our server. While your link works (15 minutes) we keep only a scrambled copy of the current code (a keyed one-way hash), how many pictures were shown and how many wrong answers were given, never with your user ID; they are deleted when the link runs out.
- To stop ban evasion and alt accounts, the web check also keeps scrambled codes of your connection and device: keyed one-way hashes of your IP address, of its network range, and of a summary of your browser and device (browser type, platform, languages, time zone, screen size and colour depth, processor threads, device memory, and how your browser draws a test image and which graphics hardware it reports). We keep only these codes, never your IP address or the device details themselves, together with your user ID and the time. They are made with a secret key that only we hold, so nobody without that key can turn them back into the original values; they are still treated as your personal data. They are only compared with other members who verified in this server. If your codes match another account, staff see which account and how it matched, and may review your verification. They are deleted after 90 days. These details are read only when you complete the check, never just by opening the page. If you would rather not have them taken, press Need help and then Ask staff in Discord, and a staff member will verify you instead.
- Two more codes come from the same check. A browser code: when you complete the check, the page saves a random code in your browser, in a cookie (
verify_device, kept up to 400 days and sent only to the verification page) and in your browser’s local storage, so the same browser verifying another account can be recognised on any network. A hardware code: a keyed one-way hash of a summary of your device without the parts that belong to the browser (no browser type, version or languages): how it draws a test image, which graphics hardware it reports, the physical screen size and colour depth, processor threads, device memory, time zone and operating system family, so another browser on the same computer gives the same code. As with the other codes, we keep only the keyed hashes, never the browser code itself or the device details, together with your user ID and the time; they are compared only with other members who verified in this server and deleted after 90 days. You can delete the browser code at any time by clearing this site’s cookies and storage; staff verification through Need help works without either.
Staff applications (careers)
- If you apply for a staff role, we store your answers, including your legal first and last name, date of birth, time zone and availability, together with your Discord name and avatar. Your date of birth is used only to check your age. The careers privacy page covers this in detail.
Appeals
- If you appeal a ban or timeout, we store your Discord name and avatar, the case, your reason and answers, and the team’s decision.
The website and dashboard
- Signing in uses Discord’s
identifypermission only: your user ID, username and avatar. We never receive your email address, password or server list, and the access token Discord gives us is used once and not stored. - Staff who use the dashboard have their actions recorded in an audit log. The same log records commands run through the bots, case events, automod evidence and application decisions.
- Our server reads your IP address for a moment to apply rate limits against abuse. It is held in memory only and is not written to our database or logs.
Why we use it
- To run the features you use: levels, the economy, pets, marriage, giveaways, reminders, music, tickets, modmail and the rest only work if the bots remember them.
- To keep the server safe and fair: moderation records, automod, raid protection, verification and the economy’s fair-play checks.
- To review applications and appeals you choose to send us.
- To fix problems: short-lived performance samples and error logs, which may include your user ID.
We rely on our legitimate interest in running a safe, working community, and on your choice to use a feature (for example, applying or appealing). You can stop most collection by leaving the server.
Who can see it
- Server staff can see moderation records, modmail, logs and the dashboard, each according to their role. Only the owner can see everything.
- Other members see what the bots post publicly: leaderboards, level-ups, public case notices and similar messages.
- Anyone on the web can see the server’s leaderboards on dexterai.dev/leaderboard (the current display name of the top 100 members on each board, with their level, XP, message count or coins) and an event’s leaderboard on events.dexterai.dev (the display name and score of the top members, and the final standings once the event ends). Members who left the server are not listed. No user IDs, avatars, or any part of an ID are published; a member whose name isn’t known is shown as “A member”.
- Discord runs the platform the bots operate on; its own privacy policy applies to everything you do there.
- Cloudflare carries traffic to this website and runs the Turnstile check described above.
- Spotify, if you connect it: the music bots ask Spotify for your playlists and saved songs with the access you granted. Spotify’s own privacy policy applies to your account there.
- Mojang receives a Minecraft username you submit for an event pass, to check that it exists.
- Song sources: when you play a song, its title or link is looked up on the music services the music bots search (such as YouTube, Apple Music or Bandcamp). Your Discord identity is not sent with the search.
We do not sell, rent or trade your data, and we do not share it with advertisers or data brokers. We would only disclose it if the law required us to, or to Discord’s Trust & Safety team when reporting serious abuse.
How long we keep it
| Data | Kept for |
|---|---|
| Deleted and edited message archive, attachments, staff-only pages of deleted messages, Discord audit-log archive | 90 days |
| Messages a staff purge deleted, passed from Warden to Sentinel for the message log | 15 minutes |
| Daily message and voice activity, voice sessions | 90 days |
| Who was speaking and when during a voice event (timings only) | 30 days after the event |
| A voice word filter match waiting for Sentinel to post it (the line as heard) | Until it is posted, then one day (at most a week while Sentinel is offline); the alert itself stays in the staff channel |
| Reply and mention counts between members | 60 days |
| Verification records | 90 days; image-check sessions 10 minutes |
| Verification network, device, browser and hardware codes (alt-account check) and alt reviews | 90 days |
| The web check’s picture code (a scrambled copy) and its try counts | Until the link runs out (15 minutes) |
| Economy command log and item history | 180 days by default (the server can choose to keep it longer) |
| Images posted in the server (temporary copy) | 48 hours |
| Staff monitor records | 120 days by default (the server can set from 7 days to 2 years) |
| Staff monitor saved results | Until the owner deletes them |
| Music play history | The latest 500 plays per server |
| Action log (dashboard actions, bot commands, case events, automod evidence, application decisions) | 365 days by default |
| Staff application drafts | 90 days without activity |
| Decided or withdrawn applications | 12 months |
| Performance samples | 7 days |
| Identity and name history, levels, economy balances and transactions, moderation cases and notes, automod records, modmail, tickets and their transcripts, help desk questions, survey answers, saved playlists, event-pass names, top.gg votes, roles kept for rejoining, appeals, suggestions and reports, verification help messages, per-channel and interaction activity counts, event final standings, and event boards saved before a reset | While the server is running, until you ask us to delete them or the data is reset |
| Spotify connection | Until you disconnect it |
The database is backed up every 12 hours. Backups are kept on a rolling schedule (the latest 14, one a day for 30 days and one a week for a year), so a deleted record can remain in a backup for up to about a year before the backup itself is removed. Copies of these backups are also kept on separate storage we control, on a similar schedule, and the hosting panel keeps its own server backups. Backups are only used to recover from failures.
Your choices and rights
- See your data: ask us for a copy of what we hold about you.
- Correct it: ask us to fix anything that is wrong.
- Delete it: ask us to delete your data. Applicants can view, withdraw and delete their applications themselves at /careers/me.
- Object: tell us if you disagree with how we use something, and we will look at it.
We answer requests within 30 days. We may keep a minimal record where we need it to keep the server safe, for example a ban and its reason, or a note that you asked to be deleted. Depending on where you live, you may also have the right to complain to your local data protection authority.
Children
Discord requires users to be at least 13 (or older where local law sets a higher age), and so do we. Staff applicants must be at least 13. If you believe a child under that age has given us data, contact us and we will remove it.
Security
Data is stored on a private server reachable only through an encrypted Cloudflare tunnel. Sign-in sessions are signed, HTTP-only cookies sent only over HTTPS, and staff access is limited by role. No system is perfectly secure, but we take reasonable care and will tell affected members if something goes wrong.
Changes to this policy
When this policy changes, we update the version and effective date at the top of this page, and announce significant changes in the server.
Contact
Send a direct message to the Steward bot on Discord. It opens a private modmail thread with the server staff, and the server owner handles every privacy request personally. If you can no longer reach the server, use the appeal page when appeals are open, or ask a staff member you know to pass your request on.