Modbot Docs
Moderation

Purge a person

Erase the history records Modbot holds about one person, what it keeps, and what it leaves behind.

Settings → Purge a person erases the history records Modbot holds about one VRChat or Discord account. It exists for the day someone asks to be erased and the law where you live says they may.

A purge does not remove everything Modbot stores about a person. Read What stays before you press it. It cannot be undone.

It needs Administrator. It has no permission of its own on purpose: a new permission would be a way to hand the most consequential thing Modbot can do to somebody who holds nothing else.

How it works

Three steps on one card, each shown only after the one before it has an answer.

  1. Account. Choose VRChat or Discord, type the person's id in the box beside it, and press Look up. The id is used exactly as you type it.
  2. Read what would go. Nothing has been changed yet. The card shows the name Modbot last saw, whether they are in the group or the server, whether they are banned, and two lists. Removed is a count for each thing a purge erases. Kept is the case files and evidence files a purge leaves. If a proved account link ties the person to another account, that account is named too. A purge never follows the link: to erase the other account, purge it as well.
  3. Type the id to confirm. Type the id again, exactly as it is above, and Purge lights up. There is no "Are you sure?" and no box for a reason: the only thing you type is the id, and it is thrown away once it has been checked. Modbot does not keep a written reason, because a reason is the one place a moderator would type the person's name.

When it is done the card says Purged. and shows the same two lists as counts of what was removed and what was kept. The counts of what was kept are shown once and are not saved. The counts of what was removed are in the audit entry described below.

Purging somebody Modbot has never seen removes nothing and is not an error. Purging the same person twice is harmless: the second finds nothing.

What is erased

Everything is done in one go, or not at all.

  • Every history record that is about them. Joins, leaves, avatar changes, instance presence, bans and unbans, kicks, roles, notes, the records of flags raised about them, and every other record in the audit log whose subject is that person. Their names in those records go with them.

  • The counts kept only per person. Some daily totals have no history record behind them, so they would survive a purge. Those are erased.

  • Days are worked out again, so no total still counts the records that were erased.

  • Every watch on them, standing or ended, with its reason and any check-back day. Only watches on the account you purge go: a watch on the Discord or VRChat account it is linked to stays, because a purge does not follow a link.

  • Every appeal they made, decided or not, for a VRChat account. The yearly report counts one fewer.

  • The rows that say a record about them was imported from a file. Without them, uploading the same file again would skip exactly the records that were erased.

  • Their Discord messages, and every earlier version of them, for a Discord account. Messages that only mention them or reply to them are somebody else's words and stay.

  • Their entries in giveaways. Standing entries are deleted, so they cannot be drawn. In a draw that has already been made, their row keeps its place and weight and loses its name and ids, so anyone who kept the seed can still check the result. See Giveaways.

  • Their event alert sign-ups, and the way they chose to be told. They are told about nothing after a purge until they sign up again with /notify. The purge counts how many it deleted and names nobody. See Event alerts.

  • Pictures they posted for the group gallery, waiting or decided. See Gallery pictures.

  • Their place on an event's invites, whether they asked for event invites, and whether Modbot noted them as a friend of your group's VRChat account. A purged person gets no event invites until they ask again with /me. The event's Invited N of M counts one fewer. See Inviting people.

    That note is about the friends list of your group's own Modbot VRChat account, not anybody else's. If the person is still a friend of that account, VRChat lists them again the next time Modbot signs in, and Modbot notes them again. To stop that, remove them as a friend on that VRChat account.

  • The reminders they asked for with /remindme, whether waiting, sent or stopped. For a VRChat account, that means the reminders of the Discord account linked to it. A purged person gets no more reminders until they ask again. See What Modbot keeps for reminders.

  • Which invite they joined the Discord server with, and when, from invite tracking. For a VRChat account, that means the joins of the Discord account linked to it. The invite and everybody else's joins through it stay. The purge counts how many it deleted and names nobody.

  • Whether they were sent the link reminder, from Account links. For a VRChat account, that means the note of the Discord account linked to it. Without it, a later reminder would count them as never asked. The purge counts how many it deleted and names nobody.

  • Whether they were welcomed, from welcome steps: the note that they were sent their steps, or that their welcome is waiting for the join gate. For a VRChat account, that means the note of the Discord account linked to it. The purge counts how many it deleted and names nobody.

  • Their Ko-fi supporter record, from Ko-fi supporters: the supporter matched to the Discord account, with their payments, and the code they got from /supporter-code. For a VRChat account, that means the supporter matched to the Discord account linked to it. A supporter nobody matched is not found by a purge: Modbot keeps the name they paid under, their tier, their payment codes and a fingerprint of their email address, and none of it points to a Discord account. The purge counts how many it deleted and names nobody.

  • Their Patreon supporter record, from Patreon supporters: the supporter matched to the Discord account, with their payments, the same way as a Ko-fi one. A patron nobody matched is not found by a purge: Modbot keeps the name they pledged under, their tier and Patreon's member id, and none of it points to a Discord account.

    A supporter who is still paying comes back: a Ko-fi one with their next payment, and a patron at the next daily catch-up, matched to their Discord account again if they connected it on Patreon. To stop that, they end their membership or pledge, or a patron disconnects Discord on Patreon.

  • The birthday they set with /birthday: a month and a day, never a year. For a VRChat account, that means the birthday of the Discord account linked to it. If they still hold the birthday role, the row stays with no month and no day until the next daily check takes the role off, and then it is deleted. See Birthdays.

  • Their picks on votes made with Votes. For a VRChat account, that means the picks of the Discord account linked to it. The vote and its other counts stay; the count of the option they picked goes down by one, on the Votes page at once and on a message that shows counts the next time it is rewritten.

  • The events they came to, their last visit and their member milestones marks: the dates counted for them, the latest return and which moments were dealt with. The Regular role in Discord is not taken off. Dates already counted are not counted again, so they start from nothing at their next event.

  • Their profile answers, the ones they filled in with /profile and who they let see each. For a VRChat account, that means those of the Discord account linked to it.

  • Member reports, both ways: the reports they made with /report or Report to mods, and the reports made about them, open or closed, with the words, the message copy and the close note. For a VRChat account, that means those of the Discord account linked to it. Purging a reporter removes their report, so the reported person's record of it goes too. See Reports.

What stays

  • Records where they were the one acting. A moderator's ban is a record about the person who was banned. Erasing it because the moderator asked would delete somebody else's moderation history.
  • Case files about them, and the evidence on those case files. These are kept, with the profile copy each case file holds. The card counts them so you can see what is left. A purge does not destroy evidence; somebody with Destroy evidence does that, one file at a time, from the case file. The audit log's entries about evidence (who attached, viewed, downloaded or destroyed a file) are about the case file, so they stay too. A file attached as a companion clip keeps, with it, the VRChat id and Modbot username of the moderator whose PC saved it, even when that moderator is purged.
  • The rows that say who someone is now: their VRChat profile, their place in the group, their entry on the ban list, their Discord member row and their account link. A purge of somebody who is still in the group or the server does not remove them from it, and the next sync writes those rows again.
  • Flags themselves, which still name the person and carry the words that matched, reviews, entries in the AI call log, and sign-in records.
  • The repeat-offender row, with how many times they were kicked, banned, removed or rejected, the dates and the last moderator's id. A purge does not delete it. The daily review job rebuilds these rows from the history records, so it goes the next time the job refreshes it or is rebuilt in full, not at the moment of the purge.
  • What staff typed on the Partners page: the contacts, envoy and notes are free text that is not tied to a person, so a purge does not look through them.
  • What staff typed on the Terms and rules page: the terms, their meanings, the rules and their text are free text that is not tied to a person, so a purge does not look through them.
  • Modbot's own log and its log files. See Logs.
  • Copies elsewhere: anything already sent to Modbot Cloud, to an AI provider, to a Discord channel by an event route, to a Discord channel in an event recap (it names the people who came, and a purge can't remove that post or its photo thread), to a Discord channel in a member milestones post (it names the people, and a purge can't remove it), to a Discord channel in a monthly event summary (it names events, not people, and a purge does not remove it), to a webhook or to Seq, and any backup of your database. A purge only reaches this Modbot's database.

The record it leaves

A purge writes one entry to the audit log, User data purged: which account did it, when, which platform, and how many of each thing were erased. It does not say who the person was. That is why there is no id in it and no reason. It is an operational entry, so it shows to people who hold See the operational log.

Where it is on the API

GET /api/settings/purge is the look-up and POST /api/settings/purge is the purge, both for Administrators. The POST needs confirmation to equal subjectId exactly; nothing is trimmed and case counts. See the API reference.

Modbot is not endorsed by or affiliated with VRChat Inc. or Discord Inc. VRChat is a trademark of VRChat Inc. Discord is a trademark of Discord Inc. SteamVR is a trademark of Valve Corporation. Windows is a trademark of Microsoft Corporation. Docker is a trademark of Docker, Inc. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Railway is a trademark of Railway Corp. Other names are trademarks of their respective owners; see Legal. Modbot and its logo are trademarks of the Modbot project. Open source under AGPL-3.0.

On this page