asb / privacy
privacy policy
aubree's stupid bot — the discord bot and its web dashboard at bot.aubree.wtf.
last updated: 20 november 2026 (the previous version was dated 16 november 2026, before the message log, appeals, tickets, giveaways, suggestions, reminders, birthdays, afk, temporary voice rooms, translate, reaction roles, custom commands, auto responders, polls, levels and roblox scan were added)
this describes what the bot actually does with data. it was written by reading the source, not from a template, and it names the specific files and services involved so you can check it against the code yourself.
this is the policy for the rewritten bot (v1), which replaced the earlier javascript version on 16 november 2026.
---
the short version
- the bot does not keep the content of your messages, with these exceptions: a copy of a removed message is posted to the server's own log channel so its moderators can see it; ai moderation keeps a short evidence record of messages it acted on (section 3); applications: the answers you write are stored until staff decide; confessions: the text is posted to the confession channel (and to the server's log channel if that server switched one on).
- roblox scan is off unless a server turns it on. when it is on, the discord user ids of the members it checks are sent to a third party service (the all seeing eye) that says whether the accounts were seen in servers that break roblox's rules. the result can be wrong and is shown only to that server's staff (section 2 and 4).
- servers can also turn on a message log (deleted and edited message text is held in memory for a few hours and posted to the server's own log channel), tickets (a transcript is posted to the server's log channel), appeals, suggestions, reminders, birthdays (day and month only), giveaways, afk status and levels (xp totals per member, level up messages never ping), which each store the small records described in section 2, and translate, which sends the text you ask it to translate to a translation service the operator chose (section 4). all of these are off unless a server turns them on, except polls and reminders.
- server cleanup is run once, by a server's owner. while it watches, the bot records the discord id, not the content, of each member who sends a message, and deletes that list when the cleanup ends. members who stayed silent are kicked.
- ai moderation is off by default. where a server turns it on, message text is sent to nvidia to be judged. unlike older versions, the bot now keeps an evidence record of messages it acted on, for a limited time (section 3).
- ip addresses are never stored. verification stores a one-way digest of your ip (for ipv6, of its /64 network). your full ip is sent to a vpn-detection service while you verify, when the server's vpn check is on and the operator configured a key.
- confessions store no author identity on disk and the bot writes none to its logs. a server can switch on a private confession log channel, and where it is on its moderators see who wrote each confession and reply.
- network lookup commands send what you type to third parties (section 4). do not put anything private in them.
- a shared list of banned raiders exists between servers that opt in (section 2). it holds user ids, account tags and the reason a server gave.
- nothing is sold, rented, or used for advertising or model training.
---
1. who is responsible
the bot is operated privately by its owner ("we"). it is not a company.
data lives on a rented server in los angeles, united states, which runs the bot and the dashboard. it is administered only by the bot's owner and is not shared with anyone else. the dashboard sits behind cloudflare, which sees dashboard visitors' connections (section 4).
a second rented server used to be kept as a standby, in case the first one failed. it was used once, on 15 september 2026, when the primary server's network was taken offline by a denial-of-service attack: the bot ran on the standby for about eight hours, and the copied files were deleted from it the same day. that standby machine no longer exists, so no member data is held on it or anywhere else. if a standby is ever set up again, this section will say so.
when the bot was moved to the rewritten version, a one-off backup of the previous version's files was made on the same server, in a folder only the operator's administrator account can read, so the move could be undone. it holds the old data files, including the older weaker ip digests. it is kept for a few weeks and then deleted.
2. what the bot stores
everything below lives in plain files on the server running the bot (the "data directory"), readable only by the bot's user. discord ids (user, server, channel, role) are numeric and stored throughout, they are how discord identifies things, so nearly every feature holds at least some of them. the bot is the only process that writes these files; the dashboard writes no data file.
server settings
per-server configuration: command prefix, enabled features, channel and role choices, admin role ids, whitelisted user and bot ids, and lists of users blocked from specific features. kept while the bot is in the server. when the bot is removed from a server its settings are deleted after 30 days (adding the bot back within that time cancels the deletion).
message counts (the "yap" leaderboard)
a running count of how many messages each member has sent per server, a single number per person. no message content and no timestamps. bots, webhooks and system messages are not counted. can be disabled per server. a server keeps at most 100,000 counts (the lowest are dropped). deleted 14 days after the bot leaves the server.
moderation records
when the bot or a moderator warns, kicks, bans, times out or quarantines someone, it records the target's user id and tag, the moderator, the reason, the action and a timestamp. moderation cases are kept until removed by hand, up to 20,000 per server (the oldest finished cases are dropped past that). the bot's own audit trail of anti-nuke and anti-raid actions keeps the most recent 5,000 entries and discards older ones. a separate owner audit trail records changes to owners, blacklists and server settings made by bot owners (who, what, when; never the values), rotated at 1 mib with one older file kept.
ai moderation records
see section 3: when ai moderation or automod acts on a message, the bot keeps an evidence record, by default for 14 days.
roles saved for restoring
before the bot removes someone's roles or removes the member as a punishment (anti-nuke, anti-raid, honeypot), it saves the list of their roles so a moderator can give them back with a!restore if the action was a mistake. the entry is deleted when the roles are restored, and expires after 30 days otherwise (at most 20,000 are kept).
the shared list of banned raiders
when a server's anti-nuke system trips and the bot itself bans or kicks the culprit, the server may report that account to a list shared between servers that run the bot. an entry holds the account's user id and tag, whether it is a bot, and for each reporting server (at most 50) the server's name and id, the reason, the time and the trigger. servers share by default and can switch sharing off. a server only acts on the list if its admins opted in, and only for entries a bot owner confirmed or that at least two servers reported. a member never sees another server's reason. entries are kept until a bot owner removes them (at most 50,000 accounts).
server backups
a!backup saves a server's structure (roles, categories, channels, permission overwrites, server settings and the bot's own settings for that server) so it can be rebuilt. it holds no member lists and no messages. the three newest backups per server are kept. no automatic deletion when the bot leaves, and the same is true of the protection settings (whitelists, trusted roles, lockdown state) that belong to the server's anti-nuke and anti-raid features. ask and they are erased.
verification
if a server enables verification, you complete a check on a web page. the bot then stores:
- a one-way digest of your ip address (for ipv6, of its /64 prefix, so the many addresses of one connection count as one), and
- the link between that digest and your discord user id, the list of servers you verified in, and a timestamp.
your actual ip address is never written to disk, and never to the logs. the digest uses argon2id over an hmac, with a secret salt held only on the server. this exists to spot one person using several accounts. addresses from apple's private relay are never recorded or matched.
be clear about what this is: the digest is pseudonymous, not anonymous. it cannot be reversed back into your address, but it is still a stable identifier tied to your discord account, and anyone holding both the file and the secret salt could test whether a *specific* address they already suspect matches it.
other verification data on disk: a record of open and resolved alt flags (the flagged account, the accounts it was matched with, the signals, who decided), roles waiting to be granted again after a failure (given up after 3 days), a list of members a moderator approved, and a recent activity list for the server's staff (member id, outcome, short note; the last 50 entries per server). the verification link itself, the check's rate limits and the vpn cache hold addresses in memory only and are gone on restart.
optional extras, off unless the operator sets them up: discord sign-in during verification (only your user id is read and the token is revoked right after), and cloudflare turnstile, a captcha on the confirm button (cloudflare receives your ip and browser details to run the check).
retention: ip digests expire 400 days after they were recorded, or sooner if you ask for removal or a server's staff clear your record. an address group is capped at 50 accounts. flags are capped at 1,000 and the oldest resolved ones are dropped first.
confessions
for anonymous confessions the bot stores the posted message id, the confession number, a timestamp, and a pseudonymous reply handle (for example "quiet fox"). the author's identity is never written to disk in any form, and the bot does not log who ran a confession command or what a confession said. errors are logged without the message text.
the handle is derived from the confession number and the author's user id using a per-server secret. honestly stated: the link is not recoverable from the stored file alone, but someone with both the secret and a list of server members could test candidates against a handle. the secret never leaves the server and is withheld from the dashboard, including from the server owner. rate limits (cooldown between posts, posts per hour) are counted in memory only.
the important exception, the moderator log. a server can switch on a confession log channel. where it is on, every confession and every anonymous reply is posted to that channel with the author's real discord account next to it, and the full text. anonymity in that server is therefore anonymity *from other members*, not from its moderators. the confession dialog tells you whether the log is on in the server you are posting in. it is off by default; if you want to know whether a particular server logs confessions, ask its staff before you post.
retention: confession records (number, handle table) older than 90 days are deleted automatically, and all of a server's records 14 days after the bot leaves it.
applications
if a server sets up applications and you choose to apply, the bot stores the answers you wrote while the application is open, your discord id and tag, which form you applied to, when you applied, and once staff decide, whether you were accepted or denied, who decided and any reason they gave. the stored answers are deleted the moment staff decide, the application expires or you withdraw. the same answers are posted as a message in the server's review channel, where discord holds them like any other message and the server's staff can read them. images you send as answers are downloaded (at most 5, 8 mib each) and attached to that review message, because discord links expire.
by default the questions are asked in a direct message. while an application is in progress the bot reads the messages you send it in that dm, because those are your answers; it ignores your dms entirely when you have no application open. a server can instead ask the questions in a pop-up form, in which case no dm is involved. saying cancel throws away a part-finished application; one that could not be filed is kept for 30 minutes so you can retry.
retention: a pending application expires after 30 days (the server can change this). finished records (without answers) are deleted after 90 days, the per-person cooldown history after 400 days, and everything for a server 14 days after the bot leaves it.
server cleanup
a server's owner can run a one-time cleanup that kicks members who stay silent. for the period the owner chooses (two days unless they say otherwise) the bot records the discord id of each member who sends a message in that server, only the id, never what you wrote, and never anything for bots. when the period ends the owner reviews a preview, and members whose id is not on the list are kicked, apart from those the server marked exempt or who are still going through verification.
the list of ids is deleted the moment the cleanup finishes or is cancelled. after that the bot keeps only totals (how many were kicked, how many spoke) and the dates, so a server cannot run it twice by accident. if you are kicked, the bot sends you a direct message with the reason and, unless the server turned it off, an invite link back in. the server's owner also gets a file listing the ids and tags of everyone who was kicked.
welcome messages
the bot posts a join and leave message in a channel the server chose. it stores nothing about you for this.
music and radio
the bot keeps a cache of downloaded audio files and a list of which song title resolved to which link. neither is tied to a person. to get past youtube's bot checks the operator supplies a cookie file from their own account. it is used only for a retry after an anonymous attempt fails: youtube then sees that request as coming from the operator's account (section 4). the file belongs to the operator, holds nothing about members, and is readable only by the bot's user.
owner invites
this is off unless the owner turns it on (ownerInvites). when on, the bot creates a non-expiring invite to a server it joins and posts it in the owner's private log, so the owner can enter that server. the invite is a normal discord invite, anyone who has the link can use it. in older versions this happened in every server; it no longer does.
message log
when a server turns the message log on, the bot remembers the text of recent messages so it can show what was deleted or edited. this memory is in the bot's working memory only: it is never written to disk or to any file, it holds the author's id and name, the channel id, the text (cut at about 1900 characters), the names and links of attachments and the time, and each message is forgotten after the number of hours the server chose (1 to 72, default 24), when the bot restarts or stops, and when the server turns the log off.
when a message is deleted or edited, the bot posts the author, the channel and the text (before and after for an edit, and a text file for a bulk delete) to the staff log channel the server picked. that post is the one durable copy. it lives in discord, in a channel under the server's control, and the server decides who can read it and how long it stays. the bot does not keep another copy.
messages from bots, from members with a role the server marked as ignored, in ignored channels, in the log channel itself and in direct messages are not remembered or logged.
appeals
when a member is kicked, banned, timed out or warned by the bot in a server that turned on appeals, the dm they get has an appeal button. if they use it, the bot stores the appeal: the id of the member, the number of the moderation case, the reason the member wrote, the time, and later the decision (accepted, denied or closed), the id of the staff member who decided, the time of the decision and the optional note staff wrote for the member. the bot also posts the appeal, with the same details, in the review channel the server chose, so the server's staff can read it, and it keeps the time of the member's last appeal in that server to apply the waiting period between appeals. all of this is stored in the bot's data folder, which only the bot operator can read, and staff of the server can list open appeals with the appeals list command. the result is sent to the member by dm when the server has that turned on, and the dm never says who decided.
an appeal that is still open stays until staff decide or close it, and is closed by the bot after a year. 90 days after the decision the reason and the note are deleted and only the ids and the outcome are kept; a year after the decision the whole record is deleted. the waiting period stamp is deleted after 30 days. each server keeps at most 1000 appeals, and the oldest decided ones go first. all of a server's appeals are deleted 14 days after the bot leaves it. the moderation case itself, with a note of the appeal outcome added to it, follows the rules of moderation cases.
reaction roles
reaction roles let a server admin bind an emoji on a message to a role. the bot keeps these bindings in its data folder: the id of the server, the channel and the message, the emoji (a normal emoji or a custom emoji id) and the id of the role. a binding holds no member data. which members hold a role is kept by discord, not by the bot, and the bot does not remember who reacted.
when a member reacts, the bot gives the role and forgets the event. if the server turned on the log channel, one line naming the member and the role is posted in that channel, where the server's own staff can read it. if the server turned on dm notices, the member gets a dm about the change. the bot only holds the last few changes of a member in memory for about ten seconds, to slow down spam, and never writes them anywhere.
bindings are deleted when the message, the channel or the role is deleted, when an admin removes them, and 14 days after the bot leaves the server. they can be read only by the bot operator and by admins of that server through the bot.
tickets
when a member opens a ticket, the bot makes a private channel for them and the server's support team. to run it the bot keeps one small record per open ticket: the id of the channel, the id of the server, the ticket number, the id of the member who opened it, the id of the staff member who claimed it (if any), the time it was opened, the time of the last message in it and whether it is closing. it also keeps one counter per server so ticket numbers are never reused. this is stored in the bot's data folder, which only the bot operator can read. the record is deleted when the ticket closes or its channel is deleted, and all of a server's records are deleted 14 days after the bot leaves it.
when a ticket is closed and the server turned transcripts on, the bot reads up to the last 1000 messages of the ticket channel and builds a plain text file of them in memory: the time, the author's name and the message text, with the links of attachments. it posts that file, with a short summary (who opened it, who claimed it, how long it was open, how many messages), to the log channel the server chose, and, if the server turned that on, also sends it to the member who opened the ticket by direct message (a closed dm is skipped). the bot does not keep the transcript: it is never written to disk, and the posted copy lives in discord, in a channel under the server's control, which decides who can read it and for how long. the ticket channel itself is deleted a few seconds after the transcript is posted.
giveaways
when you press the enter button on a giveaway, the bot stores your discord user id in that giveaway's list of entrants, so it can draw winners and let you leave by pressing again. it also stores, per giveaway, the prize text, the ids of the server, channel and message, the id of the member who started it, the deadline and, after the draw, the ids of the winners. nothing else about you is kept: no name, no message content, no roles. the bot looks at your roles, the age of your account and the date you joined the server only at the moment you press the button and at the draw, to check the giveaway's requirements, and does not store them.
this is kept in the bot's data folder and can be read only by the bot operator. a giveaway that is cancelled is deleted at once. one that ends is kept for 30 days after it ends, so the winners can be rerolled, and then deleted with its entrant list. all of a server's giveaways are deleted 14 days after the bot leaves it. winners get a direct message when the server has that turned on; the bot does not keep it.
polls
when you start a poll with the bot, the poll is posted as a native discord poll. discord, not the bot, holds the question, the answers and every vote, and discord ends the poll and shows the result. the bot does not see or store who voted for what.
the bot keeps one small record per poll so that endpoll can tell who started it: the id of the poll message, the id of the server and the id of the member who started it, plus the time. it is stored in the bot's data folder, can be read only by the bot operator, and is deleted 800 hours (about 33 days) after the poll was made, which is longer than the longest poll (768 hours). all of a server's records are deleted 14 days after the bot leaves it.
suggestions
when you send a suggestion, the bot posts it in the server's suggestion channel and keeps a record of it so the vote buttons and staff decisions keep working. the record holds the server id, channel and message ids, the id of the member who wrote it, the text of the suggestion (an image is only attached to the discord message, the bot does not keep it), its status, who decided it and the reason, and the ids of the members who pressed the up or down button. an anonymous server hides your name in the suggestion, but your id is still stored so staff can look up who wrote it.
the records are stored in the bot's data folder and can be read only by the bot operator. server staff can see who wrote a suggestion with a command, and anyone can see the vote counts but not who voted. a suggestion is deleted when it is deleted with the command, when its message is found to be deleted, or when the server goes over 2000 suggestions (decided ones go first, oldest first). when staff decide a suggestion the bot can send its author a direct message, if the server has that turned on. all of a server's records are deleted 14 days after the bot leaves it.
reminders
when you set a reminder, the bot stores your discord user id, the text you wrote, the time you set it and the time it is due, and where you set it (the server, channel and message ids, or the dm), in a file on the bot's server. nothing else is kept. it is only used to send the reminder back to you.
the reminder is deleted from the file as soon as it has been delivered, or when you cancel it with reminders cancel. if it cannot be delivered it is tried once more and then deleted. if the bot leaves a server, the server and channel references of reminders set there are removed after 14 days; the reminders are still delivered by direct message. only you can list or cancel your reminders, and the bot owner can read the file on the server.
if your direct messages are closed and the server allows it, the reminder is posted in the channel where you set it, mentioning you. that is the only time the text appears anywhere but in your direct messages.
birthdays
when you set your birthday with the bot, it stores the day and the month, never the year, together with your user id and the id of the server you set it in. a birthday belongs to that one server: it is not shared with, or visible in, any other server. it is kept in the bot's data folder, which only the bot operator can read, until you remove it with birthday remove, a server admin removes it, or the bot leaves the server (all of a server's data is deleted 14 days after that).
other members of the server can see your birthday through birthday view and the birthdays list, unless a server admin has turned on the option that hides birthdays from members. on the day, the bot announces it in the channel the server chose, and mentions you in that message. if the server uses a birthday role, the bot also stores for 24 hours that it must take the role away again.
afk status
when you set an afk status, the bot keeps the id of the server, your member id, the reason you typed and the time you went afk. the reason is cleaned first: pings are removed and discord invite links are replaced with "[link removed]". it is stored in the bot's data folder and can be read only by the bot operator. the bot repeats your reason and the time to anyone who mentions you in that server while you are afk.
your status is removed when you send a message in the server, when you leave the server, and in any case 30 days after you set it. a server can hold at most 5000 afk members at once; the oldest is dropped first. all of a server's records are deleted 14 days after the bot leaves it.
the bot does not keep the messages that mention you or the ones you send while afk. its short notices ("is afk", "welcome back") are deleted by the bot after a few seconds, or when a server moderator removes them.
temporary voice rooms
when a member joins a hub voice channel, the bot creates a temporary voice room for them and keeps one small record of it so it can tell who owns the room and clean it up: the id of the room, the id of the server, the id of the member who owns it (it changes if the room is handed over or claimed) and the time it was made. it is stored in the bot's data folder and can be read only by the bot operator.
the record is deleted when the room is deleted, which happens a few seconds after the room is empty (the server chooses how long, up to 5 minutes) and when the bot starts and finds the room empty or gone. the bot does not store who else was in the room, what was said, or any audio. all of a server's records are deleted 14 days after the bot leaves it.
custom commands and auto responders
custom commands only stores the settings a server's staff write: the command names and their response texts, the cooldown, the ignored channels and the allowed roles. these live in the server's configuration, which staff can read and change in the dashboard or with the cc command. no member data is stored. when someone uses a custom command the bot does not record who used it, when, or what they typed after the command name.
while the bot answers, it keeps two short lived things in memory only: the time a member last used a command (to apply the cooldown, up to an hour) and the ids of messages that were just deleted (up to a minute). neither is written to disk. the arguments a member typed are used once to build the answer and then dropped.
settings are deleted 30 days after the bot leaves a server, like all other server settings.
auto responders only stores the settings a server's staff write: the rules (a trigger and the answer to give), the cooldowns, the channels and roles to ignore and the other options. these live in the server's configuration, which staff can read and change in the dashboard or with the ar command. no member data is stored.
the bot reads the messages of servers that turned this on, but only to compare them with the rules in memory. a message is never saved, logged or copied anywhere, and it is dropped as soon as the check is done. for the cooldowns the bot keeps in memory only (never on disk) the time a rule last answered in a channel and the time a member last got an answer (up to an hour), plus the ids of messages that were just deleted (up to a minute).
settings are deleted 30 days after the bot leaves a server, like all other server settings.
levels
when levels are turned on in a server, the bot keeps, for each member who has earned xp there, the id of the server, the member's user id, their xp total and the time they last earned xp. it does not keep what they wrote. it is stored in the bot's data folder and can be read only by the bot operator; the bot shows a member's level, xp and place to anyone who runs the rank or leaderboard commands in that server. a server can switch levels off, and its administrators can reset one member or everyone with the levels command.
when a member leaves a server, their xp is kept for 30 days in case they come back, and then deleted; a server can choose to delete it at once when a member leaves. a member who asks can have their xp deleted by a server administrator, also after they left. a server keeps at most 100000 members, the ones with the lowest xp are dropped first. all of a server's records are deleted 14 days after the bot leaves it.
level up messages are off by default. when a server turns them on, they use the member's display name as plain text and never mention or notify anyone. roles given as rewards are the server's own roles and are visible to the server like any role.
translate
when a member uses the translate command, the text to translate is sent to the translation service that the bot operator configured. this is a service run by the operator or by a third party the operator chose, not by the bot itself, and it sees the text and the language names. the bot does not store the text or the translation: they are kept in memory only while the request runs, and are not written to any file or log. a server owner should only turn the feature on if they accept that members' text, including the text of a message someone replies to with the command, leaves the bot for that service. the service's own retention is outside the bot's control and is governed by the operator's choice of service.
the bot keeps counters in memory only, to enforce the cooldown per member and the daily limit per server: member ids, server ids and how many translations were used. they are never written to disk, are cleared at midnight utc (the daily count) or within about 10 minutes (the cooldown), and are lost when the bot restarts.
roblox scan
when roblox scan is turned on in a server, the bot sends the discord user ids of the members it checks (every member who is not a bot during a scan, and a member who joins for the join check) to The All Seeing Eye, a third party service chosen by the bot operator. it never sends names, messages or roles. the service answers whether those accounts were seen in servers it classifies as condo, rule34, asset, tributes or bypassing servers, with the names of those servers and a score. the result comes from a third party and can be wrong: it is a lead for staff, not proof. the bot does not share a result with any other server.
the bot stores per server only what staff need to review a hit: the member's id and name at the time, the score, whether the account is appealing, how many servers counted, the names of the server types (not the names or ids of the servers), what the bot did about it and when. the names of the servers are shown in the report posted in the channel the server chose, and in a lookup staff ask for, and are not stored by the bot. results are also remembered in the bot's memory for up to 6 hours and never written to disk. the list of members staff marked safe is stored too. staff can see the hits (in chat, and in a report on the dashboard for the server's owner and administrators, where they can also ban a listed member), mark a member safe and undo what the bot did (a kick cannot be undone). if the server turned it on, the member gets a message before a kick, ban or timeout that says the action and the server, never the servers they were seen in.
hits and the safe list are kept until staff remove them or, for a hit, 90 days after it was recorded. everything of a server is deleted 14 days after the bot leaves it. the bot operator can read the data file.
logs
operational logs record start-up, errors, permission problems and the like, with numeric ids (server, channel, member) and timestamps, for debugging and abuse investigation. they do not record message content, confession text, ip addresses or who ran a command. they rotate daily, are compressed, and about 7 days are kept. to the best of our knowledge nothing in them records member names or tags, only numeric ids (the bot's own account name appears at start-up).
dashboard sessions
see section 6a.
3. ai moderation
this is the feature that sends the most data outward, so it gets its own section.
it is switched off by default and must be enabled per server. when it is off, nothing described here happens and nothing is sent anywhere. if the operator has no api key configured it is off for every server.
when a server enables it:
- messages are collected for roughly 30 seconds and sent as a batch to nvidia (
integrate.api.nvidia.com) to be judged. each batch contains the message text, the channel name, the names of any attachments or stickers, and the server's own written rules. authors are replaced by labels (user_a,user_b), your username and id are not in the request. - if image scanning is on, the url of a posted image may be sent to nvidia's vision model so it can be checked for pornography or gore. by default this only happens for accounts newer than 7 days.
- nvidia returns a verdict. messages that were not acted on are not kept by the bot.
- server administrators, bot owners, staff, members with an exempt role and exempt channels are never sent at all.
- the number of requests per server per day is capped.
what the bot keeps when it acts. if a message is actioned, the bot saves an action record: your user id and tag, the action, the category, severity and reason, the model used, a timestamp and up to 8 of the offending messages (up to 1,000 characters each) as evidence, so a moderator can review the decision and undo it. the same record is made for automod actions. records are kept for a configurable number of days, 14 by default (1 to 90), then deleted, at most 500 per server. this is also what powers the undo button and the appeal line in the notice you receive.
what the server sees: the bot posts an entry to the server's log channel containing the member, the action taken, the reason, and an excerpt of the offending message. this is visible to whoever can read that channel, so a removed message does not simply vanish, it becomes visible to that server's staff.
automated decisions: a verdict can lead to a message being deleted, a warning or a timeout without a human reviewing first. kicks and bans from an ai verdict are capped at a timeout and wait for a moderator to confirm, unless the server explicitly chose automatic mode, and even then only when several independent signals agree. a ban from this route deletes at most an hour of your messages by default. every action has an undo button for moderators. if you believe you were actioned wrongly, contact that server's moderators, they control the settings and can reverse it. we do not overrule individual servers' moderation decisions.
the drama detector that older versions of this bot ran in one server has been removed.
we do not use your messages to train any model, and nvidia's api terms apply to what they do with the request. if you are not comfortable with this, ask that server's staff to disable it, or do not use servers that run it. servers that enable this are expected to tell their members.
4. what is sent to other services
the lookup services below are contacted from the bot's own server, so they see the bot's address and not yours. nothing about the person running a lookup (id, name, server) is sent to any of them.
| service | what it receives | when |
|---|---|---|
| discord | everything the bot does | always, it is the platform |
| nvidia (integrate.api.nvidia.com) | message text, channel name, attachment names, server rules, image urls (labels instead of names) | only where ai moderation is enabled |
| vpnapi.io (verification) | your full ip address | when you verify, in a server whose vpn check is on, and only if the operator set a key |
| vpnapi.io (the ipinfo command) | the ip that was looked up | only if the operator set a separate osint key, and only as a fallback when akane did not answer. without that key it is never contacted |
| cloudflare | connection metadata and ip of dashboard visitors | whenever you load the dashboard |
| cloudflare turnstile | your ip and browser details, for the captcha | only if the operator enabled it for verification |
| discord oauth | the sign-in handshake (user id only is read) | only if the operator enabled it, at verification or dashboard sign in |
| the translation service the operator configured | the text to translate and the language names | only in a server that turned translate on, when a member uses the command |
| the all seeing eye (api.tasebot.org, or the address the operator set) | the discord user ids of the members being checked (never names, messages or roles) | only in a server that turned roblox scan on: every member who is not a bot during a scan, and a member who joins |
| youtube, soundcloud, bandcamp | search words and links, and the host of a direct audio link a member pasted. on a retry for youtube, the operator's own account cookies | when someone plays music or the radio |
| youtube, soundcloud and bandcamp cdn hosts (googlevideo.com, sndcdn.com, bcbits.com) | the stream request | when a track plays |
| ipinfo.akane.network | the ip that was looked up | ipinfo |
| ipwho.is | the ip that was looked up | ipinfo |
| internetdb.shodan.io | the ip that was looked up | ipinfo |
| rdap.org, and the regional registry or registrar server it redirects to (arin, ripe, apnic, lacnic, afrinic, verisign and others) | the ip or domain that was looked up | rdap, ipinfo |
| team cymru dns (origin.asn.cymru.com, origin6.asn.cymru.com, AS<n>.asn.cymru.com) | the ip, or the as number, as a dns query | asn, ipinfo |
| dns blocklists: zen.spamhaus.org, bl.spamcop.net, dnsbl.dronebl.org, all.s5h.net, dnsbl-1.uceprotect.net, psbl.surriel.com, bl.blocklist.de | the ipv4 address, as a dns query. these go through the server's own resolver, so its upstream resolver sees them too | dnsbl, ipinfo |
| check.torproject.org | nothing about the lookup: the public exit list is downloaded and cached for an hour | dnsbl, ipinfo |
| crt.sh, then api.certspotter.com as a fallback | the domain that was looked up | subdomains |
| urlscan.io | the domain or url that was looked up | urlscan |
| discord.com (invite lookup) | the invite code | invite |
| whois servers on tcp 43: the per-tld servers built into the bot (for example whois.verisign-grs.com, whois.pir.org, whois.nic.io, whois.denic.de, whois.nic.uk), whois.iana.org for other tlds, and the registrar server a registry names | the domain | whois |
| public dns resolvers: cloudflare (1.1.1.1, 1.0.0.1), google (8.8.8.8, 8.8.4.4), quad9 (9.9.9.9), opendns (208.67.222.222), adguard (94.140.14.14) | the name or ip that was looked up. in addition 1.1.1.1, 8.8.8.8 and 9.9.9.9 resolve every host before the bot connects to it | dns, propagation, asn, ipinfo, and every lookup that connects to a named host |
| the site you name, and every host in its redirect chain | an ordinary http(s) request or tls handshake from the bot's server (user agent asb-osint/1) | webping, headers, unshorten, ssl |
| rule34.xxx, e621.net | tags typed by a bot owner | the hidden owner-only nsfw commands, nothing else |
lookups identify themselves with the user agent asb-osint/1. earlier versions sent a different one that named the operator's website, which is no longer sent.
everything below the discord, nvidia and vpn rows happens only when someone runs that command, and only ever receives the domain, ip or url that was typed as the argument. ipinfo shows city, region, country and timezone to everyone, and postal code and coordinates only to bot owners.
exif goes nowhere: an image you attach is read for metadata on the bot's own server, in memory, and is never stored or uploaded. the slash version replies privately, and gps coordinates in a photo are shown only to the person who uploaded it. in a public reply the bot only says that location data is present.
punycode, cidr and snowflake contact nobody.
the dashboard loads no third-party fonts, scripts or trackers. there is no advertising and no analytics profile built about you.
5. why we handle it
- to run features you or your server asked for: settings, music, counts.
- to keep servers safe: moderation, anti-raid, anti-nuke and verification. this is the legitimate interest of server operators in preventing abuse, and it is the reason identifiers are retained.
- to keep the service working: logs and debugging.
6. how long it is kept
| data | retained |
|---|---|
| server settings | while the bot is in the server, then 30 days after it leaves |
| message counts | until the bot leaves, then 14 days |
| anti-nuke and anti-raid audit trail | most recent 5,000 entries |
| owner audit trail | rotated at 1 mib, one older file kept |
| moderation cases | until deleted by hand, at most 20,000 per server |
| ai and automod action records | 14 days by default (a server may choose 1 to 90) |
| saved roles | 30 days |
| shared banned raider list | until a bot owner removes the entry |
| server backups | newest 3 per server |
| ip digests | 400 days, or until you ask for removal or staff clear the record |
| verification flags, grants and activity lists | flags until resolved and dropped past 1,000, role grants given up after 3 days, activity last 50 per server |
| confession records | 90 days, and 14 days after the bot leaves |
| application answers | until staff decide, the application expires (30 days by default) or you withdraw |
| application records without answers | 90 days after the decision, cooldown history 400 days |
| server cleanup id list | only while a cleanup runs, deleted when it finishes or is cancelled (totals are kept) |
| message log text | held in memory only for 1 to 72 hours (default 24, the server chooses), never written to disk. the posted log entry stays in the server's own log channel until the server removes it |
| appeals | the reason and note 90 days after the decision, the rest 1 year after it (open appeals close after 1 year), waiting period stamps 30 days, and 14 days after the bot leaves a server |
| reaction role bindings | until removed, or until the message, channel or role is deleted, and 14 days after the bot leaves a server |
| tickets | until the ticket closes, and 14 days after the bot leaves a server. transcripts are not stored by the bot, only posted to the server's log channel (and by dm if the server chose that) |
| giveaways | 30 days after a giveaway ends (at once if cancelled), and 14 days after the bot leaves a server |
| poll records | 800 hours after the poll is made, and 14 days after the bot leaves a server |
| suggestions | until deleted, until its message is deleted, or until the server passes 2000 suggestions (oldest decided first), and 14 days after the bot leaves a server |
| reminders | until delivered or cancelled (at most the server's maximum, 365 days by default), and the server, channel and message ids 14 days after the bot leaves a server |
| birthdays | until removed by the member or an admin, and 14 days after the bot leaves a server |
| afk status | until the member talks again or leaves the server, otherwise 30 days, and 14 days after the bot leaves a server |
| temporary voice rooms | until the room is deleted, and 14 days after the bot leaves a server |
| custom commands and auto responders | settings only, until staff remove them, and 30 days after the bot leaves a server |
| levels (xp) | while the member is in the server, 30 days after they leave (or at once if the server chose so), and 14 days after the bot leaves a server |
| roblox scan | hits 90 days after the hit, the safe list until staff remove it, and everything of a server 14 days after the bot leaves it. results held in memory for up to 6 hours |
| translate text and results | not stored by the bot (they go to the operator's translation service). cooldown and daily counters are in memory only and cleared within a day and on restart |
| logs | rotated daily, about 7 days kept |
| dashboard change log | the newest 200 entries per server |
| one-off rollback backup of the previous version's files | a few weeks, then deleted |
| dashboard session | up to 7 days, ends after 24 hours idle, and when the bot's dashboard restarts |
when the bot is removed from a server, the data above marked "after the bot leaves" is deleted automatically after the stated time. ask if you want a server's data erased sooner.
6a. the dashboard
logging in sets a cookie that holds only a random token. your session itself (your discord id, name and avatar, and what the dashboard last showed you) is kept in the dashboard's memory, not on disk. a session ends after 7 days at most, after 24 hours without activity, when you log out, or whenever the dashboard process restarts. the cookie is HttpOnly and SameSite=Lax, and Secure on https.
there are two ways to sign in, both optional per the operator: the bot sends you a one-time code in a direct message (single use, valid for 5 minutes, stored only as a hash, limited attempts), or sign in with discord if the operator enabled it (only your user id, name and avatar are read, the token is used once and never stored). the dashboard never asks for your discord password. a server's settings can be opened by that server's owner and by members who hold the administrator permission there; the bot checks this live each time rather than storing it. bot owners can see every server the bot is in.
changes made in the dashboard are recorded in a change log kept by the bot (the file dashboard-changelog.json in its data directory): your discord user id and display name, the time, the server, and which settings changed. secret values are never recorded. the newest 200 entries per server are kept and older ones are dropped, so a server's admins can see who changed what. the dashboard is served through cloudflare, which sees visitors' connections (section 4).
7. your rights
you can ask us to:
- tell you what is held about your discord account,
- delete it, including your verification ip digest, message counts, moderation records and any application you submitted,
- correct anything wrong.
depending on where you live (for example in the uk, eu or california) some of these are legal rights rather than courtesies. we will honour them either way. there is no charge and we aim to respond within 30 days.
two honest limits:
- server-side moderation records may be kept where deleting them would let someone evade an active ban. if we refuse a deletion on that basis we will say so and why.
- we cannot delete anything from discord itself, or from a server's own log channels, those belong to discord and to that server's staff.
a server administrator can already remove most of their own server's data by changing settings or removing the bot.
8. security
verification ips are hashed with argon2id and a secret salt. confession secrets are withheld from the dashboard entirely. the dashboard is served over https with a strict content security policy. the bot and the dashboard are separate processes: the dashboard never holds the bot's token and can only reach the bot through a signed, loopback-only interface. data files are readable only by the bot's user. access to the underlying server is restricted to the operator.
no system is perfectly secure, and this one is run by one person on one server. if you find a vulnerability, please report it rather than exploit it, see contact.
9. children
discord requires users to be at least 13, or older where local law says so. the bot is not directed at children and we do not knowingly collect data from anyone below discord's minimum age. if you believe a child's data is held here, contact us and it will be removed.
10. changes
if this policy changes materially, the date at the top changes and a notice goes to the bot's support server. continuing to use the bot after a change means accepting the updated policy.
11. contact
for privacy requests, deletion requests, security reports or questions, any of:
> support server: discord.gg/aubree
> discord: @korona.lat
> email: koronalat@gmail.com
please include your discord user id so the right records can be found.
---
*this policy describes the software's actual behaviour to the best of our knowledge. it is not legal advice and has not been reviewed by anyone at all.*