ChojioPrivacy Policy
Last updated 16 October 2026: added voice channel analytics (time in voice, sessions and the most members at once, per voice channel, as counts only) and Member activity, which a server’s owner can turn on to keep each member’s daily message count, time in voice and last activity. The 6 October update added editing forms (their pause, two-page, role, wait and profile-link settings), Q&A boards, where members ask and answer questions from a panel or sticky-message button, automatic channel access, and the record of a Lifetime Premium purchase. The 5 October update added Levels, personal reminders, the free Premium trial, the Add Chojio button on finished chat games, when Chojio last posted its getting-started card, editing blocked words on the chojio.com dashboard, and forms members fill in from a panel or sticky-message button. The 30 September update added the saved layout kept when a server is cleared before installing a template, Owner controls, buttons on sticky messages, the template answers held briefly while an admin customises a template, Chojio Arcade scores, and chat games and leaderboards. The 29 September update added changelogs, the Game studio starter template, community setups, the server directory and its website widget, events and RSVPs, member rewards (tenure roles, birthdays and Member of the month), bug reports and the GitHub and Linear integration, partners, ban appeals, lockdown, quiet hours, notification roles and content warnings. The 27 September update added what the support desk keeps about tickets. The 26 September update added seeing and deleting your data from inside Discord, automatic deletion after Chojio is removed, starter templates, install links and server referrals. The 24 September update added ticket form answers, raid defense, verification, the moderation log, applications, suggestions, giveaways and scheduled announcements.
This policy describes exactly what Chojio collects, why, and for how long. It is updated whenever a feature changes what Chojio stores, and the date above shows the latest change. If anything here is unclear, or you want to exercise a right it describes, email chojiobot@gmail.com.
What is collected
Server data: server ID, name, owner ID, locale, channel and role IDs, and the configuration you create — panels, forms, ticket categories, applications, reaction role groups.
Role menus: the menus an administrator builds are configuration, kept like the rest of a server’s setup. Each time a member presses a role button to take a role or give one back, Chojio notes their user ID, the role and whether it was given or removed. Each note is deleted after 30 days.
Panel editors: while an administrator is editing a panel, Chojio keeps a record of the editor they have open: their user ID, which panel, and what they have chosen so far, so a restart does not lose their place. An editor expires after a day, and its record is deleted 7 days after it expires.
Language: Chojio answers each member in the language their Discord app is set to, which Discord sends with every button press and command. It is used for that one reply and not stored. The language a server picks for Chojio’s public posts is part of the server data above.
Sticky messages: the text an administrator writes for a sticky message, any buttons they add under it (each button’s label and emoji, and the ticket category, application, form, Q&A board, role or web link it opens), the channel it belongs to, the ID of the copy Chojio last posted and when, whether it is paused, and the user IDs of the administrators who created it and last changed it. A role button works like a role menu, as described above. Menu launchers (Settings → Menu in channels) are stored the same way, with which buttons they show, an optional line of text, who may use them and, for one set to “Just me”, that administrator’s user ID. All of this is kept until the sticky message is removed or its channel is deleted, and otherwise like the rest of a server’s configuration.
Ticket form answers: a server can ask members a few questions before a support ticket opens. The answers are posted into the new ticket channel, where the server’s staff read them, and are not stored by Chojio. Chojio records only how many questions were answered. The answers may contain personal information, depending on what an administrator chose to ask, and once posted they are kept by Discord like any other message in that channel.
Ticket staff notes, saved replies and self-help: a server’s support team can add private notes to a ticket. Chojio stores each note’s text, the user ID of the staff member who wrote it and when. Notes are shown only to the support team, are never posted in the ticket channel, and are never shown to the member who opened the ticket — including in that member’s copy of the ticket archive. They are deleted with the ticket. Administrators can also write saved replies, which staff post into a ticket in one press, and self-help answers, which a member is shown before a ticket opens; Chojio stores their text, the categories they apply to, and the user IDs of the administrators who wrote and last changed them. For each self-help answer Chojio keeps two numbers: how often a member said it solved their problem and how often they opened a ticket anyway. It does not record who pressed. All of these are kept like the rest of a server’s configuration.
Ticket close reasons: a server can ask for a short reason, up to 300 characters, whenever one of its tickets is closed. The reason is posted in the ticket channel so the member can read it, and Chojio keeps it with that ticket’s record, together with the user ID of whoever closed it, for as long as the rest of the server’s ticket records. When Chojio closes a quiet ticket on its own, the reason it keeps says only that, and how many hours the ticket was quiet.
Applications: a server can let members apply for something — a staff team, a whitelist, a partnership — by answering a few questions. The answers are posted into a channel the server’s reviewers read, together with the applicant’s username, when their Discord account was created and when they joined the server, and are not stored by Chojio; once posted they are kept by Discord like any other message in that channel. So that each member has one application open at a time, waits the period the server set before re-applying after a decline, and can check the outcome themselves, Chojio stores a short record of each application: the applicant’s user ID, which application it was, when it was sent, its outcome (waiting, accepted, declined, withdrawn, or closed because nobody decided it or the applicant had left), who decided it and when, and — only if a reviewer chose to give one — the reason for a decline, which the applicant can read. When a decision is made, Chojio also tries to send the applicant a direct message with the outcome, and keeps no copy of it.
Scheduled announcements: when an administrator schedules an announcement, Chojio stores what it will post (the message they wrote, or which of their panels), the channel, the date, time, timezone and repeat rule, the roles it pings, and the Discord user IDs of the administrators who created it and last changed it, and of the administrator whose Mention @everyone permission is checked when it posts (whoever last added a ping or changed its message, channel or time). Each time it posts, Chojio keeps a short record — when it was due, the ID of the message it posted, and any error (which may name the administrator whose permission removed a ping) — for 30 days. When an announcement pings @everyone or a role that is not normally mentionable, Chojio checks at the moment of posting that the administrator who set those pings still has Discord’s Mention @everyone permission; that check is not stored. Nothing about the members who receive an announcement is read or kept. Finished or failed announcements are deleted 30 days after they last changed, unfinished drafts after 7 days untouched, and a deleted announcement is removed immediately. An announcement that is scheduled or paused, including one paused because Chojio was removed, is configuration and is kept as described under Retention. Messages already posted stay in the channel, like any other message, until someone deletes them.
Changelogs: when an administrator writes a changelog in the changelog composer, Chojio stores what they wrote (the version, an optional title, and the lines under Added, Changed, Fixed and Known issues), the channel, the role it pings, whether to publish it to following servers, and the Discord user IDs of the administrators who created it, last changed it and posted it. Once it is posted, Chojio also keeps the IDs of the messages it posted and when, so it can be edited from History. When a changelog pings @everyone or a role that is not normally mentionable, Chojio checks at the moment of posting that the person posting it has Discord’s Mention @everyone permission; that check is not stored. Nothing about the members who read a changelog is read or kept. An unfinished draft is deleted after 7 days untouched, and a discarded one immediately. Each server’s latest 10 posted changelogs are kept for History, and posting another deletes the oldest. The posted messages stay in the channel, like any other message, until someone deletes them.
Forms: a server can put a button on a panel or a sticky message that opens a short form of up to eight questions. Chojio stores the form’s name and questions, the channel its answers are posted in, the role pinged with each response, whether a member may answer once or as often as they like and how long they wait between responses, whether the form is paused, the role (if any) it gives members who submit it and the last reason that role could not be given, and the user IDs of the administrators who created it and last changed it. When a member submits it, their answers are posted into that channel with their username and a mention of them, and, unless the server turns it off, a link to their Discord profile made from the same user ID; the answers are not stored by Chojio; once posted they are kept by Discord like any other message in that channel. A form longer than five questions is asked over two pages: the first page’s answers are held in Chojio’s memory only, for at most 15 minutes, until the second is sent, and are never written to its database. The short wait between one member’s responses is kept in memory the same way and is gone after a restart. For a form set to once per member, Chojio keeps a short record that the member has answered — their user ID, which form and when, never the answers — so it can tell them they already have. That record is deleted when the form is deleted or switched back to allowing more than one response, when an administrator resets that member, and when the member deletes their data. A form that allows several responses keeps no record of who answered. Chojio also keeps the IDs of the panel messages it has posted, so administrators can update, move or delete them later.
Ticket archives: for a closed ticket, a timeline of what happened (opened, claimed, moved, closed, reopened, by whom and when), the reason given for closing it if the server asks for one, staff notes, participants, and Chojio’s own messages. Premium servers can export an archive; when the member who opened the ticket downloads it, the staff notes are left out. This is not a transcript: it does not contain what members typed in the channel, because Chojio cannot read that — see “What is not collected” below. It does not contain ticket form answers either, because Chojio does not keep them.
Ticket support hours and response times: a server can set when its support team is available, an away message shown to members who open a ticket outside those hours, and (on Premium) targets for how quickly tickets are answered and resolved, with the roles to notify when one is missed. These are configuration, kept like the rest of a server’s setup. For each ticket, Chojio also records when the support team first replied, whether the most recent message came from the support team (a yes or no, not who sent it), and when a missed target was escalated. These come from who sent a message and which roles they hold, never from what the message says, and they are part of the ticket’s own record, kept and deleted with it.
Timed roles: when a moderator gives somebody a role for a set time, Chojio stores that member’s user ID, the role, the moderator’s user ID and when the role ends, so that it can take the role back on time. The record is deleted when the role is removed — when the time is up, or when a moderator ends it early. If the member has left the server by then, the record is deleted when its time runs out. The longest time on offer is 90 days; if Discord refuses to remove the role, Chojio keeps the reason it gave and retries for about four more days, and then deletes the record either way. If Chojio is removed from the server, every timer there is deleted at once.
Member rewards never read or count messages. Tenure roles: in a server that gives roles for time in the server, Chojio reads the server’s member list from Discord about once a day, up to 1,000 members a page — each member’s user ID, when they joined, their roles and whether they are a bot — and adds or removes the milestone roles due. None of it is written to Chojio’s database: the only thing kept is the user ID of the last member checked, so the next check can carry on from there, and it is cleared when each daily check finishes. If the server turns announcements on, reaching a milestone is congratulated in its channel, which Discord keeps like any other message. Birthdays: a member who presses Set your birthday stores their user ID, a month and a day (never the year) and, if they pick one, a timezone. On the day Chojio records that they were celebrated and which birthday role it gave until the end of their day, so the role goes back on time and the day is celebrated once a year. A birthday is deleted when the member removes it, when they leave the server, and when the server’s data is deleted. Member of the month: for each monthly round Chojio stores each member’s one nomination and one vote (who chose whom, and when), the finalists, any nominee an admin takes out of the round, and the winner. Staff can see the counts while the round runs; other members see only their own choices until the results. The round, with every nomination and vote in it, is deleted 30 days after its results. Chojio also remembers who holds the winner’s role, so it can take it back when the next winner is chosen. When the vote opens, Chojio asks Discord for the five finalists’ display names to label the vote and does not store them.
Games are played with buttons and never read messages. When a member starts or joins a game, Chojio stores the game: which game, the channel and the message it is played on, the user IDs of its host and players, their seats and teams, the settings the host chose, the game’s state (the moves so far, and in games like rock, paper, scissors the picks not yet revealed; in word games this includes the words players type into the game’s forms, such as a Hangman secret word, a Secret Words clue or a Daily Word guess), and when it started and ended. A game nobody moves in ends by itself after the server’s idle timeout (10 minutes unless an administrator changes it). An open lobby takes players for its join window (an hour unless its host or an administrator chooses between 5 minutes and 24 hours), then starts or closes. Realm Explorer campaigns are the exception: they last the season their host chose (up to 14 days, or a number of rounds), and one with no turn timer that nobody touches for 7 days ends then. Their state holds each player’s character, position, inventory and the campaign’s log, all tied to user IDs, and nothing else about them. Every game, finished, timed out or cancelled, is deleted 7 days after it ends. What is kept is each member’s totals per game: games played, wins, losses and draws, points, best score, win streaks (for a daily puzzle, days in a row solved), a rating for two-player games, and this week’s and last week’s points; a member’s totals for a game are deleted after 365 days without playing it. If a server turns on the weekly Champion, Chojio remembers who holds the Champion role so it can take it back the next week. Game boards are drawn as pictures that show the players’ Discord avatars: Chojio fetches each avatar from Discord while drawing and keeps it in memory for up to an hour, and stores nothing about it. A coin flip or a dice roll is not stored at all, and a question asked of the Magic 8-ball is typed into a form, posted once with its answer, and not stored. Short game messages, such as “it’s your move”, are deleted after the time the server chooses (20 seconds unless an administrator changes it); until then Chojio stores only the message’s ID, its channel and when to delete it. To keep a game’s board at the bottom of its channel, Chojio notes in memory only the times of the last few messages there, never who wrote them or what they said.
Server analytics. So a server’s administrators can see its peak hours and how it is growing, Chojio stores counts, and only counts: for each channel and each hour, how many messages were sent; for the server and each hour, how many members joined and left and how many minutes were spent in voice channels; for each voice or stage channel and each hour, how many minutes members spent in it (added up across members), how many times somebody joined it, and the most members in it at once; and for each day, how many different members posted, and how many different members were in each voice channel. It never stores message content (it cannot read it), message IDs or user IDs for this. Messages from bots and webhooks, bots in voice, and the server’s AFK channel are not counted. To count different members without keeping who they are, each member’s ID is replaced in memory by a keyed hash under a random key made for that day; the key and the hashes are discarded when the day ends, within 24 hours, and only the number is stored. To time voice, Chojio holds a similar hash in memory, with the channel, while a member is in a voice channel and discards it when they leave; when Chojio restarts it reads who is already in voice from Discord’s own connection data, again as hashes in memory only. Hourly counts are kept 90 days and then kept as daily totals for 365 days. Administrators can turn this off under Settings → Your data → Collect analytics; turning it off stops the counting at once and deletes the stored counts, and Chojio then keeps only the fact that it is off, so deleting a server’s data does not turn it back on.
Member activity (only when a server owner turns it on). It is off in every server until the server’s owner turns it on under /menu → Analytics → Members, after a screen that explains what it records (the owner can let admins with Manage Server decide instead, under Owner controls). While it is on, Chojio keeps, for each member of that server and each day: how many messages they sent, how many whole minutes they spent in voice channels (not the AFK channel), and when they were last active that day; and, for members who join while it is on, when they joined. It comes only from the fact that a member sent a message or was in voice: never what a message said (Chojio cannot read it), never which messages, and never which channels. Bots and webhooks are not counted. The server’s administrators can see it in Discord and, if they have Manage Server, on the chojio.com dashboard, as lists (most active, newly inactive, not active since joining, and biggest drops) and one member at a time. Each member can see their own record with My data and delete it there with Delete my activity record. Each day is kept 90 days, or 180 days if the server has Premium, and then deleted, checked every hour. A member’s record is deleted when they leave the server or delete it themselves, and every record is deleted when Member activity is turned off, when Collect analytics is turned off, and with the rest of the server’s data, which also turns Member activity off.
Levels: only in a server whose administrators turn Levels on, Chojio keeps each member’s XP total and level there, with the time they last earned XP, so the server can show ranks, a leaderboard and level-up messages and give roles at chosen levels. XP comes from the fact that a member sent a message (who, in which channel, and when, at most once a minute unless the server chooses otherwise) and, if the server turns it on, from whole minutes spent in a voice channel. Chojio never reads or stores what a message says. The roles a member holds are looked at only to leave out roles the server chose not to count and to apply bonus-XP roles, and are not stored. XP earned in the last 30 seconds is held in memory before it is written, and time in voice is timed in memory only. A member’s XP is deleted when they press Remove my XP under Levels → My rank, when they leave the server, when an administrator resets them or everyone, and with the rest of the server’s data. The server’s level settings and role rewards are kept like the rest of its setup.
Suggestions: in a server that uses Chojio’s suggestion box, the title and details a member writes are posted in that server’s suggestions channel and are not stored by Chojio — the post is the only copy, and deleting it deletes the suggestion. Chojio stores, for each suggestion, the member who sent it, its number, its status, the vote totals, and which reviewer last changed the status and when. The sender is stored for anonymous suggestions too: their name is hidden from other members but shown to the server’s review team, so that abuse can still be dealt with. For each vote, Chojio stores the voter’s user ID and whether the vote was up or down, so that everyone votes once and can change their mind; no screen, export or log shows who voted. A reviewer’s reason is part of the post and is not stored separately.
Q&A boards: a server can put an Ask a question button on a panel or a sticky message. Chojio stores each board’s settings (its name, the channel questions are posted in, who may answer, whether askers and answerers are shown, whether a question takes one answer or several, whether the asker is sent a DM when it is answered, a role to ping and a wait between questions) and the user IDs of the administrators who created it and last changed it. When a member asks, their question is posted in the channel, and Chojio stores the question’s optional title and its text, the asker’s user ID, the channel and post it is in, its status, and when it was asked; for each answer, its text, the answerer’s user ID and when it was given or edited, so the post can be redrawn as answers arrive. A board can show askers or answerers as “Anonymous”: the post then shows no name to members, but Chojio still stores who wrote it, and the server’s Chojio-admins can see it for moderation with Who posted?, which is noted in the record of administrator actions. Staff can also record who closed a question. The text is checked against the server’s own blocked words before it is posted; it comes from a form the member fills in, so this needs no access to messages. When an answer arrives the asker may be sent a DM with a link to it, which is not stored.
Bug reports: in a server that uses Chojio’s bug reports, the answers a member types into the report form are posted as the report, in that server’s chosen channel, and are not stored by Chojio — the post is the only copy. Chojio stores, for each report, its number, a title of at most 100 characters taken from the first answer, the reporting member’s user ID, its status, whether the server’s team listed it as a known issue, which report it duplicates, and when it was made and last changed. When a member presses Me too on a report, Chojio stores their user ID, so each member counts once and can take it back; no screen, export or log shows who pressed it, only how many. The server’s bug team can add private notes to a report (their text, the author’s user ID and when), which are never posted and never shown to the reporter, and Chojio keeps a short history of each report: which status it moved to, who changed it, and when. When the team turns a support ticket into a bug report, the report is filed under the staff member’s name rather than the member who opened the ticket, and a note in the ticket links the two. When a report’s status changes, the server can have Chojio post a note in the report’s thread, with or without mentioning the reporter.
GitHub and Linear (Premium): a server’s administrators can connect their own GitHub repository or Linear team. Chojio stores the access token they paste, encrypted, and never shows it again beyond its last four characters, together with the repository or team, any default labels, whether the status sync is on, the user ID of the administrator who connected it, and, if the last request failed, a short description of why, written by Chojio. When the bug team presses Create issue, Chojio sends that service the report’s title, the answers as posted, its number and status, how many members are affected, the server’s name and a link to the report — never a Discord user ID or name — and stores the issue’s link on the report. If the server turns the status sync on, Chojio asks the service about each linked issue at most every 15 minutes and marks the report fixed when the issue is closed. Removing the integration deletes the token. What a server sends to its own GitHub or Linear account is then held by that service under the server’s own agreement with it.
Raid defense: when an administrator opens a raid-defense screen, Chojio reads the server’s member list (user IDs, when each member joined, whether they hold roles or moderation permissions, whether they are a bot, and the names of bots) to show who a raid response would affect. That list is held in memory for at most five minutes and is not written to Chojio’s database, except the user IDs of accounts an administrator bans with Raid Recovery, kept for at most seven days so the ban can be undone (see below).
Undoing a raid ban: when an administrator bans accounts with Raid Recovery, Chojio stores the Discord user IDs of the accounts it banned, and who ran it (their user ID and username) and when, so the same bans can be lifted again from the raid defense screen. That the run happened, who ran it and how many were banned is also kept in the record of administrator actions described below, without the banned accounts’ IDs. While an undo is running, it also stores the user ID of the administrator running it, so two people cannot undo the same run at once. Nothing else about the banned accounts is stored — no names, messages or profile details. The record is deleted as soon as an undo has dealt with every ban in it, and in any case seven days after the ban. While an administrator is reviewing a run, Chojio asks Discord for the usernames of up to ten of the accounts to show on screen, and does not store them.
Lockdown: when a manager locks the server from raid defense, Chojio records, for each channel it locks, whether @everyone had a permission entry there and what it said about sending messages and threads, so unlocking can put each channel back exactly as it was. It also records who started the lockdown, when, which categories it covers, and where its notice was posted. Nothing about members is stored. Each channel’s record is deleted as soon as that channel is unlocked; the chosen categories are kept as part of the server’s setup.
Raid Watch, if a server turns it on, looks at each member who joins: when their Discord account was created (which Discord encodes in the user ID), their username, whether they have a profile picture, and markers Discord itself attaches — whether they were in the server before, and whether Discord’s own AutoMod has already blocked their name. This is held in memory for about ten minutes and never written to Chojio’s database. The only thing stored is a number per day: the most joins seen in a single minute, kept for seven days, so Chojio knows what normal looks like for that server. When Raid Watch is off, none of this is looked at.
Verification, if a server posts a Verify button, uses what Discord sends with the button press: which roles the member already has, whether they have accepted the server’s rules screening, whether they are timed out, when they joined the server, and when their Discord account was created (which Discord encodes in the user ID). None of this is stored. If the server asks a question first, the answer is checked and discarded. Chojio keeps only the times of recent questions and wrong answers for each member, in memory, for at most about sixteen minutes after their last try, so it can briefly pause somebody who keeps guessing. The lasting record is the role itself, and the entry Discord’s own audit log makes for any role change.
Starter templates and the security check: installing a starter template from Server setup creates roles and channels in Discord and saves the same kinds of configuration an administrator could set up by hand — a ticket category, role menus, welcome and verification settings, and the moderation log’s channel — with the user ID of the administrator who installed it, as those features already record. While an administrator customizes a template or answers Fresh setup’s questions, their choices (options, and any role and channel names they type) are held in memory, under their user ID, for an hour after they last use those screens, and never written to the database. The security check reads the server’s own settings, its roles and their permissions, and, where Chojio may manage webhooks, how many webhooks the server has. It never reads the member list or any message, and nothing it finds is stored; it is worked out again each time the screen is opened.
Community setups: an administrator with Manage Server can share their server’s setup from Server setup. A shared setup is public: anyone can see it on chojio.com and install it. It holds configuration only — the names, topics and permissions of the channels and categories, the roles’ names and colours, and the wording of panels, role menus, ticket categories, verification and the welcome message, as far as the administrator chooses to include them — with a name, description and tags they write. It never holds a Discord ID, a member, a member’s mention (each is replaced with “@member”), a message, a ticket, or any record of what members did, and invite, webhook and referral links are removed. If the administrator chooses, it also shows “Shared by” and the server’s name. Chojio stores it with the server’s ID and the user ID of the administrator who last published it (neither is shown), and the time of each publish for one day, to allow five a day. It is kept until an administrator presses Unpublish, which deletes it and its link at once, or until the server’s data is deleted. Installing a setup counts it once per server: Chojio records which server installed which setup, and the public page shows only the total.
Clear Server & Install: a server’s owner can have Chojio delete the server’s channels and roles before installing a template. Just before anything is deleted, Chojio saves the server’s layout — the names, topics and settings of its channels and categories, its roles’ names, colours and permissions other than moderation ones, and which roles can see which channels — so the owner can put it back. It holds no message, no member and no member’s permissions, and it is never published. Chojio stores it with the server’s ID and the owner’s user ID, and deletes it 30 days after it is made, or sooner if the server’s data is deleted. The channels, roles and messages deleted by the clear are deleted in Discord; Chojio keeps no copy of any message.
Owner controls: a server’s owner can choose whether only they, or also administrators with the matching Discord permissions, may install templates, share the server’s setup, change automatic channel access and delete Chojio’s data for the server. Chojio stores those choices with the rest of the server’s settings, and records each change, with the user ID of the owner who made it, in the record of administrator actions.
Automatic channel access: when an administrator turns it on, Chojio gives its own role the channel permissions it uses (such as View Channel and Send Messages) in every channel and category it can see, including private ones, and in new channels as they are made. It changes only its own role, never @everyone or anyone else’s permissions. Chojio stores whether it is on, the channels an administrator excluded, and, for each channel where it added access, the channel ID, its own role ID and which permissions it added, so that turning the feature off can take back exactly that. Each change is recorded with the administrator’s user ID in the record of administrator actions and the moderation log. With it on, Chojio can see the names and settings of private channels and post there when an administrator sets something up. It still cannot read messages in them: it does not have the Message Content intent. Like any channel Chojio can see, these channels then count toward analytics and Levels where a server has those on, as described on this page. The records are kept while Chojio is in the server, deleted when the access is taken back or the channel is deleted, and deleted 30 days after Chojio is removed or when the server asks.
Reporting a setup: the Report form on a setup’s page records the setup, the reason chosen and any details typed. It is anonymous. To limit how many reports one connection can send, the visitor’s IP address is combined with a secret key into a one-way hash, and only that hash is stored, never the address itself. Reports are deleted 90 days after they are made.
Moderation log, if a server turns it on, posts a short record into a channel that server chooses whenever something its staff would want on file happens: a member joining or leaving (their user ID, username, whether they are a bot, and how old their account is, which Discord encodes in the user ID); a ban, kick, timeout, nickname or role change, with who did it and the reason they typed; a channel, role or server setting being changed; a moderator removing somebody’s messages (whose, in which channel, and roughly how many — never what they said); and everything Chojio itself does. Apart from joins, leaves and Chojio’s own actions, this comes from the server’s Discord audit log, which Chojio can read only where the server has given it the View Audit Log permission. Each record is held in memory for a few seconds so that bursts can be posted together, and, if Chojio cannot post for a while (for example during a Discord outage), for at most ten minutes before it is let go. During a raid it keeps a running count of joins and up to ten of the joining accounts’ IDs, for up to thirty seconds at a time, and after Chojio removes accounts in bulk it remembers which ones for ten minutes, so they are not each reported again as leaving. None of it is written to Chojio’s database; the only things stored are the channel, which kinds of event to post, whether the log is on, and, if Chojio had to pause it, why. Once posted, a record is an ordinary message in that channel, kept by Discord and removable by the server’s staff like any other. In servers that have not turned the log on, audit log notices are ignored as they arrive.
Voice rooms, if a server sets them up: when somebody joins the server’s Join to create channel, Chojio reads their display name once to name a new voice channel after them, moves them into it, and stores the room’s channel ID and the owner’s user ID so the room’s buttons answer to the right person. That record is deleted with the room, which happens as soon as the last person leaves, or within about four minutes if Discord does not report the leave or Chojio has been removed from the server. Discord tells Chojio whenever anybody in the server joins or leaves any voice channel; Chojio keeps track only of who is in the Join to create channel and its rooms right now, forgets each person within five minutes of their leaving those channels, and for voice rooms ignores every other voice channel (analytics counts time in voice as described under Server analytics, and Member activity where a server has turned it on). To stop repeated rejoining from creating a stream of channels, it also notes in memory when a member was last given a room, does not give them another within thirty seconds, and forgets the note within a few minutes. If a room’s owner or a moderator removes somebody from a room, Discord keeps a permission entry for that person on the room until the room is deleted, and the removal is recorded in the server’s moderation log if it keeps one. Nothing about who was in a room is kept afterwards.
Giveaways: when a member presses Enter on a giveaway, Chojio stores their Discord user ID and the time they entered, and nothing else about them. Pressing Leave deletes it. To check whether they may enter, Chojio uses what Discord sends with the button press — their roles, when they joined the server and whether they have passed its rules screening — and when winners are drawn it asks Discord again for those and whether each entrant is still in the server; those answers are used at that moment and not stored. When a giveaway ends, Chojio records the winners’ user IDs and the ID of the admin who ran it, plus counts of entrants who could not win and why (for example, how many had left the server) — never who they were. Entries are deleted seven days after the draw, which is how long a replacement winner can be drawn; the giveaway, its winners and the host’s ID are deleted thirty days after it ends. A cancelled giveaway is deleted immediately, entries included, and an unfinished one that is never started is deleted after a day. A giveaway whose winners could not be drawn, and that nobody ended by hand, is deleted with its entries a week after it was due to end. Starting a giveaway is also noted in the record of administrator actions below, with the prize and the host. If Chojio is removed from a server, a giveaway still running there is deleted, with its entries, when it was due to end. Winners are also announced in the server’s channel, and that message is kept by Discord like any other.
Events: when a server’s admins or event hosts post an event, Chojio stores what they set up — its title, description, time, place, seats, sign-up slots, which roles may answer and when to send reminders — the ID of the person who created it, shown on the post as its host, and of whoever last changed it. If the server has given Chojio permission to manage events and the host turns it on, the event is also listed in Discord’s own Events tab, where Discord keeps it. When a member presses Going, Maybe or Can’t go, or picks a sign-up slot, Chojio stores their Discord user ID, their answer, the slot, when they answered and, if the event is full, their place on the waitlist; nothing else about them. To check whether they may answer, Chojio uses the roles Discord sends with the button press and does not store them. If the event uses an event role, Chojio gives that role to members who are going, notes that it did so, and deletes the role when the event ends or is cancelled. Reminders and notices are posted in the event’s channel, or sent as direct messages if the event is set up that way; those messages are kept by Discord like any other. When staff export the attendee list, Chojio asks Discord for the display names of up to 100 attendees and sends the list privately to the person who asked; the file and the names are not stored. A member can remove their answer with Remove my RSVP until the event ends. Each event, with every answer to it, is deleted 30 days after it ends (or would have ended, if it was cancelled), and a draft nobody touches for 7 days is deleted. Posting, cancelling, messaging attendees, exporting and choosing the Event hosts role are also noted in the record of administrator actions below, with the event’s title and counts only.
Personal reminders: when a member sets a reminder for themselves under /menu → My reminders, Chojio stores their Discord user ID, the time it is due, the text they typed and the channel they set it from. At that time Chojio sends it to them as a direct message; if their direct messages are closed, it posts the reminder in that channel, mentioning only them. The reminder is deleted as soon as it is sent, when the member deletes it, if it is more than a day overdue because Chojio was offline, and when Chojio is removed from the server. Nobody else can see a member’s reminders.
Chojio Arcade: Chojio Arcade is a set of games played inside Discord as an Activity, served from chojio.com/arcade. When you open it, Discord asks whether Chojio may know who you are and read your membership of the server you are playing in (your nickname there, which is what the leaderboard shows). If you agree, chojio.com receives a Discord access token, checks with Discord who you are and that you are a member of that server, and keeps the token only in the Activity’s memory while it is open; it is never stored. The games themselves run in your Discord app; all chojio.com hears of a game is that it started and, at the end, its score. When a game ends in a server that has Chojio installed, Chojio stores your best score for that game there: your Discord user ID, the server’s ID, the game, the score, when you set it and the name the leaderboard shows. A lower score changes nothing. The server’s leaderboard shows members of that server by name; the all-servers leaderboard shows a player’s name only to people in the same server as them. Press Remove my scores on the Arcade’s leaderboard to delete yours for that server at any time. Your scores in a server are also deleted when you leave it, and with the rest of the server’s data. If you play outside a server, or decline Discord’s prompt, nothing is stored. The Arcade sets no cookies; it remembers your sound and motion settings in your own browser only.
Partners: a server can keep a list of partner servers, each with its name, an invite link, a short description and the user ID of the administrator who added it; Chojio asks Discord about each invite when it is added and once a week, to take broken links off the board. When somebody presses Apply to partner, Chojio stores their user ID, the invite, the server name Discord gives for it, the description and member count they typed, and the outcome with the reviewer’s user ID and any reason. The reason they gave for wanting to partner is posted to the server’s review channel and not stored by Chojio. They are told the outcome by direct message if their messages are open. A request is deleted 90 days after it is decided, or 60 days after it was sent if nobody decides.
Ban appeals: a server can let members it banned appeal at chojio.com/appeal/<server>. The appellant signs in with Discord, and Chojio stores their user ID and username, the questions they were asked and their answers, the outcome, and any question, reply or decline reason exchanged with the staff, with the user IDs of the staff who asked or decided. Chojio asks Discord whether that one account is banned, and reads the ban reason on record to show the staff; it does not store the ban reason. The answers are posted to the server’s chosen staff channel. An appeal is deleted 90 days after it is decided, or 180 days after it was sent if nobody decides; one sent by somebody Discord shows as not banned, or that could not be delivered, is deleted a day later. The wait before appealing again after a decline, which a server can set up to 90 days, is measured from the decision, which is why the record is kept that long. Somebody signed in can also report a server’s appeal page to Chojio’s team; Chojio stores the report, their user ID and the server, does not tell the server who reported it, and deletes the report 180 days after it is made. Reports are kept if the server has its data deleted, like Chojio’s other trust and safety records.
Quiet hours and ping roles: a server can set quiet hours, when Chojio posts without role or @everyone pings, and offer ping roles that members turn on and off themselves from a Notification settings post. Which pings a member wants is simply which of those roles they hold: Chojio does not store it. If a member pauses their pings, Chojio stores their user ID, the ping roles it took away and when it gives them back, and deletes that as soon as it has given them back, at most 7 days later. Content warnings on panels and announcements are part of the post and are stored like the rest of it.
Record of administrator actions: when an administrator or moderator does something through Chojio that changes the server — for example scheduling an announcement, starting a giveaway, cleaning up a channel, running or undoing Raid Recovery, changing who may use Chojio, or editing blocked words on the chojio.com dashboard — Chojio records the Discord user ID and username of the person who did it, what they did, the name of what it was done to (such as an announcement’s name or a giveaway’s prize) and counts such as how many messages were deleted. It never records the IDs of the members affected. These records are deleted 180 days after they are made.
Install links: a link to chojio.com/invite can carry a short tag saying where it was shared — a post on another site, say, or a server’s referral link. The “Add Chojio to your server” button on finished chat games is one of these links, tagged “game”. When somebody follows a tagged link, Chojio adds one to a count for that tag and that day. Nothing about the visitor is recorded: no IP address, no browser details, no cookie. If the link is then used to add Chojio to a server, Chojio records that server’s ID, the tag, whether Chojio was new to that server, and the time. The server ID comes from Discord at the end of the install; the access token Discord issues with it is not kept. To carry the tag through Discord’s install screen, Chojio stores a one-time random value (only as a hash) that works for 30 minutes and is deleted a day after that. Counts and install records are deleted 13 months after they are made.
Server referrals: a server whose administrators open Refer a server is given a random referral code. When a server that was added through a referral link pays for Premium for the first time, Chojio records which server referred it, which server it was, the ID of the Stripe invoice, when, and whether the referring server was given a free month, had already reached the yearly limit, or had the month taken back after a refund or dispute. To decide whether a referral counts, Chojio compares the two servers’ owner IDs, which it already holds, and checks whether the same Stripe customer pays for both; nothing new is collected for this. The referring server’s free Premium time — days saved for later and the dates it runs — is also stored. Referral records are deleted 13 months after they are made; saved Premium time is kept until it has been used, and deleted 13 months after it ran out.
Free Premium trial: when an administrator starts a server’s free 7-day trial, Chojio records the server’s ID, when the trial started and when it ends, the user ID of the administrator who started it and the channel it was started in. The user and channel IDs are used only to send two reminders (two days before the trial ends, and when it ends) — by direct message, or in that channel if the message cannot be delivered — and are removed once the trial has ended. The record that the server has had its trial (the server’s ID and the dates) is kept with the billing records, so each server can have one trial; it is kept when the server’s data is deleted or Chojio is removed. No payment details are collected for a trial.
Lifetime Premium purchases: when an administrator buys Lifetime Premium for a server, Chojio records the server’s ID, the user ID of the administrator who started the purchase, when it was bought, and the Stripe IDs of the checkout, the payment and the Stripe customer, so the purchase can be applied to the right server and matched to a later refund or dispute. If the payment is refunded or disputed, Chojio adds when that happened and the Stripe ID of the refund or dispute. Like other billing records, a purchase record is kept for accounting when the server’s data is deleted or Chojio is removed. Payment details such as card numbers and the buyer’s email are entered on Stripe’s checkout and never reach Chojio.
Server directory and widget: a server can choose to be listed on chojio.com/servers, and to show a widget — a small card with a Join button — on its own website. Both are off until somebody with Discord’s Manage Server permission turns them on under Settings → Directory & widget, and both are public once on. A listing stores what the server’s administrators chose: a description of up to 200 characters, up to five topic tags, the main language, a permanent invite link and the ID of its channel, and which channel the widget’s Get support button opens. It also stores the server’s name, icon and Discord’s approximate member and online counts, which Chojio reads again from Discord every six hours while the listing or widget is on. The site and the widget show copies of these that can be up to five minutes old. No member’s ID, and nothing a member wrote, is part of a listing, and the directory and widget set no cookie. Server icons are loaded from Discord’s image servers, so a visitor’s browser contacts Discord to show them. Removing the listing or turning the widget off takes it off the site within a few minutes. The listing’s record is kept like the rest of a server’s configuration: it is deleted when the server deletes its data under Settings → Your data, and 30 days after Chojio is removed, and the site stops showing it as soon as Chojio is removed. Chojio can hide a listing that breaks its terms; the server’s administrators see that it is hidden in Settings.
Reports of a listing: anyone can report a directory listing from its page. Chojio stores the reason, the optional note (up to 500 characters) and when it was sent, and nothing that identifies who sent it. To allow at most five reports per visitor per day, Chojio keeps a count against a one-way hash of the visitor’s IP address, made with a secret salt that changes every day, so the same visitor cannot be recognised from one day to the next; the IP address itself is never stored. The daily counts are deleted two days later, and reports 90 days after they are sent. Reports are kept when a server deletes its data, like Chojio’s other trust and safety records, until those 90 days are up.
Account data: if you sign in with Discord, Chojio receives your Discord user ID, username, avatar reference, and your list of servers with your permissions in each. The server list is requested fresh from Discord every time it is needed and is never stored — it is used only to decide which servers you may manage, and a stored copy would go stale the moment your permissions changed. Your user ID, username and avatar reference are held only inside the session cookie described below, unless you send a ban appeal or report an appeal page, described above, or change a server’s blocked words on the dashboard, which is noted in that server’s record of administrator actions like the same change made in Discord. Payment details are handled by Stripe and never reach Chojio’s servers.
Cookies
Chojio sets no advertising or analytics cookies, and there is no tracking on this site. Following a tagged install link adds one to a daily count for that tag and sets no cookie (see Install links above). Two cookies exist, both strictly necessary and both set only if you choose to sign in:
chojio_session — holds your Discord user ID, username, avatar reference and a Discord access token, encrypted so the contents cannot be read from your browser. It lasts at most seven days, and less if Discord issues a shorter-lived token. Signing out deletes it.
chojio_oauth_state — a random value that lives for ten minutes during sign-in and is deleted immediately afterwards. It exists to verify that the sign-in finishing in your browser is the one that started there.
What is not collected
Chojio does not request the Message Content intent. It cannot read ordinary channel messages, and does not. Discord enforces this rather than Chojio promising it: without that intent, message text, embeds and attachments arrive empty, both live and when asked for afterwards.
What it does see about messages. Chojio is told when a message is sent in a channel it can see, in which channel, and by whom — but not what the message says. That is used for six things. First, knowing when somebody last spoke in a support ticket, so a ticket set to close itself after a quiet period closes after real quiet rather than closing a conversation that is still going, and so the support desk knows when the team first replied and whether a ticket is waiting on the team or on the member. For that, the message’s author is compared with the ticket’s opener and their roles with the ticket’s support roles, and then dropped. Nothing is stored except, for an open ticket, the time of the most recent message and whether it came from the support team (overwritten each time rather than kept as a history), and the time of the team’s first reply. Second, only in servers that turn on Raid Watch: counting how many messages arrive, and which of them come from accounts that have just joined, as supporting evidence of a raid. Those counts are held in memory for about a minute and never stored.
Third, only in a channel where a server has set a sticky message (a menu launcher counts as one here): noticing that somebody posted there, so Chojio can move the sticky message back to the bottom once the conversation pauses. Who posted is looked at only to ignore other bots, and is not kept; the only thing held is the time of the most recent message in that channel, in memory, until the sticky message has moved.
Fourth, only in announcement channels a server has chosen for auto-publish: when a message arrives there, Chojio asks Discord to publish it to the servers that follow the channel. It decides from the fact that a message arrived, its type and whether it has been published already, and checks its author only to recognise Chojio’s own posts. It never reads what the message says, and it stores nothing about the message or its author. To stay within Discord’s limit of ten published posts per channel per hour, it counts publishes per channel in memory for an hour.
Fifth, unless a server turns it off: counting messages for that server’s analytics, as described under Server analytics above. Only the count per channel per hour is stored. Who posted is used only to leave out bots and to count how many different members posted that day, and is never stored.
Sixth, only in servers that turn Levels on: giving the member who posted XP, as described under Levels above. The author, the channel, the time and the author’s roles are looked at, and only the member’s XP total, level and when they last earned are stored.
Seventh, only in servers whose owner turned on Member activity: adding one to the member’s message count for that day, as described under Member activity above. The author, whether they are a bot, and the time are looked at; only the day’s count and the time of their last activity are stored.
Chojio is also told when a message is deleted, with the message’s ID. That is used for one thing: in a channel where Chojio has posted suggestions, bug reports, questions on a Q&A board, or the buttons and board that go with them, it checks whether the deleted message was one of those posts, so that its record of that suggestion, report or question is deleted with it (and a deleted known-issues board is posted again). Nothing about the deletion is kept.
AutoMod. Chojio is told when Discord’s own AutoMod blocks a message — which rule, in which channel, and whose message — but Discord withholds the blocked text, for the same reason as above. In servers where Raid Watch is on, Chojio counts how often it happens, in memory, for about a minute; everywhere else the notice is ignored. Nothing about it is stored.
Retention
Configuration is kept while the bot is in the server. If Chojio is removed, everything it holds for that server is deleted 30 days after Chojio is removed, apart from the records listed under “What a deletion keeps” below. Adding Chojio back before then cancels the deletion and brings the setup back as it was. A server can also have everything deleted at once, at any time, from inside Discord (see below).
Until 26 September 2026 this page said the removal clock was not yet running: the deletion date was recorded on removal but nothing read it. It runs now. A server removed before then, while this page said its setup would be kept, is given the full 30 days from the day the clock started rather than being deleted at once.
Ticket archives are a Premium feature, kept 90 days unless a server’s setup chose longer, and kept at most 180 days. Each is deleted when its window passes, checked every ten minutes across every server. Form answers are posted, not stored; the record that a member has answered a once-per-member form is kept until the form is deleted or that setting is turned off. Raid Recovery ban records are deleted seven days after the ban at the latest. Giveaway entries are deleted seven days after the draw, and the giveaway itself, with its winners, thirty days after it ends. Events and every RSVP to them are deleted 30 days after the event ends. The record of administrator actions is deleted 180 days after each entry is made. Install-link counts and install records are deleted 13 months after they are made, and referral records 13 months after the referred server’s first payment. Reports about community setups are deleted 90 days after they are made, and the time of each publish one day after it. A shared setup is kept until it is unpublished or its server’s data is deleted. Reports of a directory listing are deleted 90 days after they are sent, and the daily counts that limit them two days later.
Application records are deleted 30 days after the application is decided or withdrawn, or when the server’s waiting period before re-applying ends if that is later (a server can set at most 365 days). An application nobody decides is closed after 90 days and deleted 30 days after that. Deleting an application in Server setup deletes all of its records at once.
Suggestion records, including who voted, are deleted when the suggestion’s post is deleted, when the suggestions channel is deleted, 30 days after the suggestion is approved or declined, when nobody has voted on or reviewed an open or planned suggestion for 180 days, and when Chojio is removed from the server.
Q&A questions and their answers, with who wrote them, are deleted when the question’s post or its channel is deleted, when a staff member deletes the question, when the board is deleted, 180 days after the question last changed (asked, answered, edited, closed or reopened), and when Chojio is removed from the server. The posts stay in the channel. A board’s settings are kept like the rest of the server’s setup.
Member of the month nominations and votes are deleted with their round, 30 days after its results. Birthdays are kept until the member removes theirs or leaves the server, and so are Chojio Arcade scores and Levels XP (which an administrator can also reset).
Games, with their players and moves, are deleted 7 days after they end, checked every hour. A member’s leaderboard totals for a game are deleted after 365 days without playing it, and a server’s game settings are kept like the rest of its setup. A short game message waiting to be deleted is recorded until it is, and that record is dropped at the latest an hour after the message was due to go.
Server analytics counts are kept by the hour for 90 days, then as daily totals for 365 days, and are deleted after that, checked every hour. The daily count of different members who posted, and of different members in each voice channel, is worked out in memory and the hashes behind it are discarded within 24 hours. Member activity, where a server’s owner turned it on, is kept 90 days per day (180 with Premium), checked every hour; the record of when a member joined is kept at most 180 days.
Bug report records, including who pressed Me too, the team’s notes and the report’s history, are deleted when the report’s post is deleted, when the reports channel is deleted, and 180 days after the report is closed (fixed, won’t fix or duplicate). Open reports are kept like the rest of a server’s setup. A connected GitHub or Linear token is deleted when an administrator removes the integration, and otherwise with the rest of the server’s setup.
Ban appeals are deleted 90 days after they are decided, 180 days after they were sent if nobody decides, and a day after one that was never sent to staff; reports about an appeal page 180 days after they are made. Requests to partner are deleted 90 days after they are decided, or 60 days after they were sent if nobody decides. A lockdown’s record of a channel is deleted when the channel is unlocked, and a paused member’s ping roles when they are given back.
Copies of deleted records can remain in Chojio’s nightly database backups until those backups age out, which takes at most 30 days.
Seeing and deleting your data in Discord
Settings → Your data shows a server’s administrators everything Chojio stores for that server, one category at a time, with how many records there are and how long each kind is kept. The list is the same one the deletion below works from, so it cannot describe data the deletion would miss.
Deleting everything for a server. On the same screen, anyone with Discord’s Manage Server permission can delete everything Chojio holds for the server. Chojio explains what will happen first, and asks for the server’s name to be typed before anything is deleted. The server’s setup (including any GitHub or Linear token), panels, tickets and archives, applications, suggestions, bug reports, Q&A boards with their questions and answers, giveaways, events and RSVPs, personal reminders, role menus, scheduled announcements, changelogs, sticky messages, member rewards (birthdays and Member of the month), games and their leaderboards, Chojio Arcade scores, Levels settings and every member’s XP, server analytics counts, Member activity records and its setting, partners and requests to partner, ban appeals, raid and lockdown records, paused ping roles, the directory listing and the record of administrator actions are all deleted at once, and Chojio carries on in the server with an empty setup. Deleting everything also unpublishes and deletes any setup it shared on chojio.com, as does the deletion 30 days after Chojio is removed. Chojio-admin roles given through Access cannot do this; only Manage Server can.
What a deletion keeps. Billing and subscription records are kept, because payment records must be kept for accounting and tax, and a Premium subscription or Lifetime purchase carries on unaffected; none of them holds anything a member wrote. The server’s own entry is kept (its ID, name, icon, owner’s user ID, member count, when Chojio was added and when it last posted its getting-started card, which it posts at most once in 30 days), because billing and the record of the deletion point at it. Chojio’s own trust and safety records about a server, if any exist, are kept so that deleting data cannot erase a suspension; reports of its directory listing and of its appeal page are kept for the same reason, until their own deadlines of 90 and 180 days. Referral records are kept too (the server’s referral code, which link brought it to Chojio, rewards and saved Premium time) until their own 13-month deadline described under Server referrals, so that a reward cannot be claimed twice and earned Premium time is not lost. The same records are kept when a server is deleted 30 days after Chojio is removed.
What stays in Discord. Messages Chojio has already posted stay in their channels, and their buttons stop working; a server’s staff can delete them like any other message. Roles Chojio gave for a set time, and tenure, birthday, Member of the month and Levels roles, stay with their members, open voice rooms stay as ordinary voice channels, and AutoMod rules Chojio set up stay in the server’s AutoMod settings. A deletion cannot start while Raid defense is holding a channel’s slowmode or has paused invites, so that Chojio never forgets to put those back.
The record of a deletion. Every deletion, whether asked for or after removal, leaves one record: which server, the user ID of the person who asked (none for a deletion after removal), when, and how many records of each kind were deleted. It holds nothing that was deleted, and it is kept as proof that the deletion happened.
My data, for every member. Any member can press My data on /help, or on /menu when it has nothing else to show them, to see what Chojio holds about them in that server: their tickets and their statuses, applications, suggestions and votes, bug reports and Me toos, questions they asked and answers they gave on Q&A boards, giveaway entries and wins, event RSVPs, reminders they set, timed roles, role button picks, their birthday, their Member of the month nominations and votes, the games they played and their leaderboard totals, ban appeals they sent, requests to partner they sent, ping roles held while their pings are paused, their Chojio Arcade scores, their Levels XP, their Member activity record where it is on, voice rooms, Raid Recovery ban records that name them, and how many records name them as the person who set up or handled something. Only they see the answer. It gives counts, not content: it never shows another member, a moderator’s name or a staff note, and nothing about the lookup is stored. The same answer says what a member can remove themselves — a suggestion vote, a Me too, a giveaway entry before the draw, an event RSVP before the event ends, a reminder they set, their birthday, their Arcade scores, their Levels XP, their Member activity record, a waiting application — and that anything else is either the server’s to delete or can be requested by email below.
Subprocessors
Discord (the platform Chojio runs on, and the sign-in provider), Stripe (payments — card details go to Stripe directly and never reach Chojio), DigitalOcean (hosting and the database, in New York, United States), and Cloudflare (DNS only).
Chojio runs its own database on its own server rather than using a managed data service, so this list is short by design. It will be updated here if that changes — off-site backup storage is the next likely addition.
GitHub and Linear are not Chojio’s subprocessors: Chojio sends them nothing unless a server’s administrators connect their own account in Settings → Integrations, and then only what is described under GitHub and Linear above.
Your rights
In Discord, any member can see what Chojio holds about them with My data, and anyone with Manage Server can delete everything Chojio holds for their server under Settings → Your data, as described above. For anything else — a copy of your data, or deleting your own records in a server — email chojiobot@gmail.com and it is actioned within 30 days.
Email requests are handled by hand, by a person reading that mailbox. There is no self-service control for them on this site. That is worth saying plainly, because this page used to promise “through the dashboard” and there has never been such a control.
Contact
chojiobot@gmail.com, for anything on this page including access and deletion requests.