Privacy
Where Modbot's privacy policy lives, and what a self-hosted Modbot sends to Modbot Cloud and how to turn each part off.
Modbot's privacy policy is modbot.co/privacy. The same document is
PRIVACY_POLICY.md in the Modbot
repository, and that file is what the page is built from.
It answers two sets of questions: one for people in a group whose moderators run Modbot, and one for operators running it. It is the full list; this page is the short one for operators.
What a self-hosted Modbot sends to Modbot Cloud
A Modbot you run yourself sends four things to Modbot Cloud. Three have a switch and one is a
tickbox on a person's account. The switches are on when Modbot is installed, and MODBOT_CLOUD_DISABLED turns everything off at once.
The facts about your members — bans, joins, messages, case files, evidence — are not in any of them.
| What | How often | Switch |
|---|---|---|
| Open instances. Which of your group's instances anyone can join, so they can be listed on modbot.co. | Every five minutes, and when one opens or closes | Settings → Server, This install: List this group's public instances on modbot.co |
| A usage report. Your server's address, version and operating system; your group's id, name, description, icon and banner; whether a Discord bot is connected and AutoMod is on; the shared word lists you imported; two counts of trouble. | Two minutes after start, then every six hours | Settings → Server, This install: Send usage report to Modbot Cloud |
| Modbot's own log. The lines on the Modbot's log page. | About once a minute | Settings → Server, Keep for (days): Send logs to Modbot Cloud, then Save |
| An email address. Only if somebody ticked Receive emails from Modbot about new features and updates when making an account. | Once | Leave the box unticked |
- The usage report names your server and your group. It is the one thing that is not anonymous. There is no field in it for the number of members, any person's name or id, any moderation record, any credential or any log line. See Modbot Cloud for the whole list.
- The log is sent unchanged. The same lines you can read on the Modbot's log page:
Information level and above, with the message, the time, which part of Modbot wrote it, the
exception if there was one, and the values the line carried. Not warnings only, and not
anonymised. If you set
LOG_LEVELlower, the extra detail is sent too — the lines for every request answered and every database query run. Setting it back stops that. - Log lines can name a member. They are Modbot talking about its own work, and that work is about people. A VRChat user id can appear in a line, and so can a name or an action taken on someone. Only credentials are taken out: names and ids are not.
- Requests Modbot sends to VRChat and Discord are not in the log. Those are a separate stream and are never sent.
- Credentials are taken out before a line is stored at all, so they are never sent: a property whose name looks like a password, a secret, a token, an API key, an authorisation header or a cookie is replaced, and a bearer token or a connection-string password written into a message is removed from the text.
- Modbot Cloud keeps the usage report with the address it came from. Each report is a row of its own, and nothing deletes them on a schedule. Cloud keeps logs 180 days by default. Only a Modbot Cloud administrator can read them, and the Cloud account that claimed your server with a link code can read its logs. See Logs.
- Your deployment is identified by a random id Cloud gives it the first time it registers. That is not your group, your domain or your name, but the usage report carries all of those.
- The switches are separate. Turning the usage report off does not turn the log or the instance list off. Turning it off also means a Modbot that has not registered yet sends no log, because the log is sent under the id registration makes. Get link code registers it, sending only the address, the version and the operating system.
Modbot also asks what the newest Modbot release is, every six hours. That request sends nothing about
you, and MODBOT_CLOUD_DISABLED does not stop it; the Check for updates switch on the same card
does.
What a self-hosted Modbot stores
A Modbot you run yourself keeps its data in your own PostgreSQL database, and evidence files wherever you choose to store them. These pages describe what is kept and how it is protected:
- Data and retention: the kinds of records Modbot keeps (moderation facts, presence facts such as instance joins and avatar changes, stored Discord messages, daily totals, case files and evidence), how long each is kept, and how to set a retention window. By default nothing is deleted except Modbot's own log and the AI call log.
- Purge a person: what removing one person's records erases, and what it keeps.
- New staff checklist: a new staff member's written answers, their buddy's sign-offs and note are stored with the checklist, readable only by that person, their buddy and people with Manage users or See the operational log. They are deleted when the checklist is removed or the account is deleted.
- Security: how passwords, sessions, stored secrets, API keys, webhooks, evidence and companion tokens are protected, and what Modbot sends to VRChat.
- AI settings: with AI switched on, text your members wrote — Discord messages, VRChat display names, bios, status lines and pronouns — and, when a rule is set to look at them, pictures, is sent to the AI provider the operator chooses, and that page lists exactly what goes where.
What leaves your server
- Modbot Cloud: the usage report, the word lists and the credits, and how to claim your server with a link code.
- Open instances: which of your group's instances anyone can join, what is sent, and how to turn it off.
- Calendar pictures: a picture chosen as an event's VRChat picture is uploaded to VRChat, to the VRChat account Modbot signs in as for your group, and stays there as a file on that account. It is off until you turn it on, with Settings, Modbot's VRChat login, Pictures, Upload VRChat pictures, and it needs VRChat+ on that account. Modbot reads whether the account has VRChat+ from its own tags when it signs in to VRChat, and again when you press Check again there (one request to VRChat, for the account's own user, nothing else sent). If the account has no VRChat+, Modbot turns the switch off by itself. Even when it is on, nothing is uploaded unless someone with Manage calendar chooses a picture. The picture is cropped and turned into a PNG or JPEG in that person's browser; only the cropped picture is sent.
- Gallery pictures: when you choose a Picture channel, each PNG or JPEG a member posts there is copied into Modbot's database and kept while it waits for staff. It goes to VRChat only when someone with Manage the group gallery presses Add, and only while Upload VRChat pictures is on; the copy is deleted once the picture is added or declined. Who posted it, and the link to their message, stay. A purge deletes them.
- The Discord picture: a picture cropped for an event's Discord cover is kept in Modbot's database, sent to your Discord server as the event's cover and on its channel post, and deleted when the event is deleted or given another picture. One that was never saved with an event is deleted once it is a day old, within the hour after.
- Picture links: to crop an event's picture link, and to give
Discord's event its cover, Modbot's server fetches the link, so the website it points at sees a
request from your server. It fetches only
https://links on public websites, never an address on your own network, and keeps nothing. A VRChat file link is fetched with Modbot's VRChat login, only while Proxy VRChat images through Modbot is on. - The public calendar feed: off until someone with Manage calendar turns it on, with the Public feed switch on the Calendar page. While it is on, anyone with the address can read your events that are visible to everyone on VRChat's calendar: their titles, descriptions, times, repeats and worlds, and the join link of those anyone can join. Nothing about your members, and no events visible only to your group. Turning it off makes the address answer "not found" at once.
- Google Calendar: nothing until someone with Change settings
gives Modbot a key file and a calendar in Settings, Google Calendar. Then each Check
sends Google a sign-in request signed with the key, naming Modbot's Google address, to
oauth2.googleapis.com, and askswww.googleapis.comfor that calendar's name, time zone, who it is shared with and what Modbot may do on it. The key's private part never leaves the server; only signatures made with it do. Once someone turns Keep Google updated on, Modbot also sends that calendar the events ticked for it, each time one is made, changed, cancelled or removed: its title, description, start, end, time zone, repeat and cancelled dates, a date's own times and words, the world's name and its page on vrchat.com, the group's name, and an id Modbot uses to find its own copy again (kept in the calendar's private copy). Google shows them to everyone the calendar is shared with, and to the public if the calendar is public. Events only your group's members can see are never sent. Never sent: member names, VRChat or Discord ids, head counts, the join link or Modbot's own address, the event's picture, and anything about moderation. - Event invites: for an event set to invite people, Modbot
sends VRChat invites from the group's Modbot VRChat account, and Discord direct messages from the
server's Modbot bot, to the host, staff and list the organiser picked, and can post in the group
and the event's channel when the first person is in. Off unless an event asks for it. Only people
who asked get an invite: a member by pressing Get event invites under
/me(and Stop event invites to stop), a staff account by its Get event invites switch on the Account page (on until they turn it off). The choice is kept with when it was made, and a purge deletes it. To know who can get a VRChat invite, Modbot keeps a note of who is a friend of the group's own Modbot VRChat account (nobody else's friends): from the invites it sends, and from the friends list VRChat sends with that account when Modbot signs in. A purge deletes a person's note, but if they are still a friend of that account, the next sign-in notes them again. - Event reminders: off until you turn on /remindme on the Commands card. A member who runs it with an event gets two Discord direct messages from the server's Modbot bot: a confirmation at once, and the reminder before the event, naming the event and its time, with a join link only for an event anyone can join whose instance is open. Modbot keeps the member's Discord id, the event, the date, when the reminder is due and its state. Every reminder is deleted in the end: sent, stopped, skipped and failed ones 30 days after they last changed, one stuck while sending after a day, and one nobody handled (while the command was off) 30 days after it was due. A purge deletes all of a person's, and nothing is sent to Modbot Cloud. A member whose direct messages are closed is told so and nothing is kept.
- Birthdays: off until you turn on /birthday on the Commands card. A member who
runs
/birthday setgives Modbot a month and a day. Modbot never asks for the year, so it holds no age. It keeps the member's Discord id, the month and day, when they set it and, while they hold the birthday role, which role and which day it was given. The daily post in your channel names the member with a mention that does not ping them. It is kept until the member runs/birthday remove; a purge deletes it, and nothing is sent to Modbot Cloud. - Votes: off until you turn on /vote on the Commands card; the Votes page needs See posts. A member who presses a button on a vote gives Modbot their pick. Modbot keeps the member's Discord id and the option they picked, and when, for as long as the vote exists, because that is how a member gets one vote and can change it. It keeps this on an anonymous vote too; Anonymous only decides whether staff see who picked what on the Votes page. Discord never shows who voted. A purge deletes a person's picks, and nothing is sent to Modbot Cloud.
- Event recaps: off until you turn on On on the Event recaps card. When the instance Modbot opened for an event has closed, a card in the channel you picked names the people seen there as VRChat shows them, so nobody is pinged, with the head count and the next date, and a public thread is started on it. Modbot keeps only the time the recap was posted, for each date. Nothing is sent to Modbot Cloud. Discord sees the post and the thread.
- Event dates over time: always on, with no switch. For each date of an event that is on Discord's events or on your group's VRChat calendar, Modbot keeps the number of people interested on Discord and on VRChat, read once while the date is running, and when it read each. These are counts, with nobody named. They show on the event's page for staff who can see the calendar and the analytics, and a purge has no one to remove from them. Nothing is sent to Modbot Cloud.
- Monthly event summary: off until you turn on On on the Monthly event summary card. Once a month a card in the channel you picked gives each event's averages of those counts for the month before; it names events, not people. Discord sees the post. Turning it off or on changes only the post, not what Modbot keeps.
- Invite tracking: off until you turn on On on the Invite tracking card in Settings → Discord. Once on, when somebody joins your Discord server Modbot compares the use counts of the server's invites and keeps which invite they joined with (or that it could not tell), with their Discord id and the time they joined. It also keeps each invite's code, the name staff gave it, who made it and whether it is gone. The page shows only counts per source, never who joined. The bot's invite link asks for Manage Server and Create Invite only while it is on. A purge deletes a person's joins; no retention window touches them. Nothing is sent to Modbot Cloud.
- Welcome steps: off until you turn on Welcome new members in Settings → Discord. Once on, Modbot keeps for each Discord member it welcomes, or is holding the welcome for until the join gate lets them in, their Discord id, whether it was sent or is waiting, and when, so nobody is welcomed twice. A purge deletes that note; no retention window touches it. Nothing is sent to Modbot Cloud, and Discord sees the direct message or channel post.
- Ko-fi supporters: off until you turn on Ko-fi in Settings. Once on, Ko-fi sends
Modbot a message for each payment. For each supporter Modbot keeps the name they paid under, their tier, their
Discord account when matched, when they paid, which roles it gave, and the transaction id of each payment. Their email
address is never stored: only a one-way fingerprint of it, to tell one person's payments from another's. A
person who types
/supporter-codegets a short code, kept with their Discord account. A purge deletes the supporter matched to that Discord account, and their code; no retention window touches it. Nothing is sent to Modbot Cloud, and Discord sees the direct message and the roles. - Patreon supporters: off until you turn on Patreon in Settings. Once on, Patreon sends Modbot a message when a pledge is made, changed or ended and when a charge goes through or fails. For each patron Modbot keeps the name they pledged under, their tier, their Discord account when matched, when they were charged, which roles it gave, and Patreon's member id with the date of each charge. Their email address is never read or stored. If you save the four keys of a Patreon client, Modbot also asks Patreon for each new patron's Discord account (the one the patron connected to Patreon) and, once a day, for every patron of your first campaign, and keeps the campaign's id, when your access token runs out and when the last catch-up finished. Those requests go to Patreon only and carry your own tokens and Patreon's own ids; the keys are kept encrypted. A purge deletes the supporter matched to that Discord account; no retention window touches it. A patron who is still pledging comes back at the next daily catch-up. Nothing is sent to Modbot Cloud, and Discord sees the direct message and the roles.
- Account links: the tab shows only counts. When staff press Start reminder, the bot sends each Discord member who has not linked one direct message with the link page, one every 30 seconds, and keeps for each person their Discord id, whether the message was sent or could not reach them, when, and Discord's reason if it failed, so nobody is ever sent it twice. A purge deletes that note; no retention window touches it. Nothing is sent to Modbot Cloud, and Discord sees the direct messages.
- Server snapshots: saved only when staff press Take snapshot or turn on a schedule on the Server snapshots card in Settings → Discord. A snapshot keeps the server's role names, colours and permissions, and the channels' names and what each role may do in them, and who took it. It keeps no members and no member ids. At most 100 are kept. The bot's invite link asks for Manage Roles only while Allow restore is on. Nothing is sent to Modbot Cloud.
- Member milestones: the count is always on. Modbot keeps, for each person seen in an instance where a moderator's Modbot app was present, the dates of the events they came to, when they were last seen arriving in a group instance and their latest return, and shows them on the profile. The posts and the Regular role are off until you turn them on in the Member milestones card; a post names the people as VRChat shows them, so nobody is pinged. Nothing is sent to Modbot Cloud. Discord sees the post and the role. A purge deletes the counts, but can't remove a post already in Discord.
- Event alerts: off until someone with Manage calendar turns on On
in the Alerts card on the Event categories page. A member who signs up with
/notifyor the Notify me button gets a direct message from the server's Modbot bot before a matching event, naming the event and its time, with a join link where/eventswould show one. If Ping is on too, a post in the channel you picked mentions the members who chose to be pinged instead. Modbot keeps the member's Discord id with the categories or events they signed up for and the way they chose, until they change it, the category or event is deleted, or a purge removes them. For each alert sent it keeps the event, the date and the member's Discord id and whether it was sent, closed, failed or skipped; those rows are deleted 30 days after the alert was queued. The operational log records only counts, never who was told, and nothing is sent to Modbot Cloud. Discord sees the messages and the pings. - Member reports: off until you turn on /report and Report to mods on the
Commands card. A member who reports someone sends Modbot what they wrote (up to 1,000 characters)
and, from the message menu, the message they reported. Modbot keeps the reporter's Discord id and name,
the reported person's Discord id, name and linked VRChat account, what was written, and for a message:
its id, channel, time, words, the names (never the files) of its attachments, and its link. Staff who hold
See reports read all of it on the Reports page, including who reported; nobody else sees the
reporter, and no Discord reply, notification or audit log entry names them or carries their words. Closed
reports keep the words for 365 days after they were closed (Closed reports, in Settings → Server →
Keep for (days); 0 keeps them forever), and then the text and the message copy are removed and the bare
record stays: who, about whom, when, and the close note. A purge deletes every report
a person made and every report about them. A report about a staff account is shown only to people who also
hold Review tickets. When staff close a report they may choose to tell the reporter: Modbot then sends
the reporter a Discord direct message with the words staff picked or wrote, and keeps only whether it went
or why not (
reporter_message_result), never the words. What leaves your server: staff are told "Modbot: new report" with no names and no words, by email, Discord direct message or push as each set up; that direct message to the reporter, only when staff choose to send it; and nothing goes to Modbot Cloud or to an AI chat tool. - Tickets: off until someone with Change settings adds a ticket type and posts a
panel. A member who presses a button gets a private Discord thread with staff. Modbot keeps the
ticket type's name, the member's Discord id and name, the thread's id, and when it was opened, closed
or deleted and by whom. When a ticket is closed and a transcript channel is set, Modbot posts a text
transcript of the thread there: every message with its time and author, and its attachments by name
and link. For a type with Private images on, the transcript says
[image removed]instead, and Modbot keeps no attachment names or addresses from those threads. Nothing is sent to Modbot Cloud. Discord sees the threads and the transcript. - Posts: a post written on the Marketing page goes only to the sites ticked on it, and every site starts unticked. For Discord, Modbot's bot sends the post's title, text and picture to the channel picked, mentions the role picked if any, and publishes it to the servers that follow the channel if Publish to followers is ticked. Its readers, and those servers' readers, see it. For VRChat, Modbot's VRChat account posts the title and text in your group, for the group (or only the roles picked) or for everyone on vrchat.com, as picked, and has VRChat notify the members only if Notify members is ticked. The picture goes to VRChat only while Upload VRChat pictures is on: it is then uploaded to the VRChat account Modbot signs in as and stays there as a file on that account; while it is off, VRChat gets the text only. Nothing about your members goes in a post: no names, no ids, no counts. The picture is kept in Modbot's database while a post uses it. Pause all posting, Discord posts, VRChat posts and Bluesky posts, under Settings, Posts, stop posts from going out.
- Bluesky: nothing until someone with Change settings saves a handle and
an app password in Settings, Bluesky. Then each Check sends the handle to Bluesky's
public API at
public.api.bsky.app(or to the handle's own website) to find the account, reads the account's public record fromplc.directory(or the account's own website), and sends the account's id and the app password to the account's own server to sign in; it never posts. Modbot keeps that sign-in and renews it with the same server. Once someone turns Posting on, a post with Bluesky ticked sends that server the post's text (its own text, or the title and text), the time it was sent, and either small copies of the post's pictures made in the browser (up to four for a calendar event, each with the alt text you wrote, or the post's title when you wrote none) or, when it has no picture and the text has a link, a link card with the post's title and that link. From there the post is public on Bluesky, and copied by other services; deleting it removes it from Bluesky, not from copies others already took. Modbot never mentions anyone in a Bluesky post, so nobody is notified. Never sent: member names, VRChat or Discord ids, head counts, and anything about moderation. Posting, Bluesky posts and Remove stop it; Remove also forgets the app password. A calendar event with Bluesky on sends the same kind of post for each of its dates, made by Modbot itself a set time before the date, and later deletes it from Bluesky when the event changes, is cancelled or is deleted. The post's text is the event's title, the date's time, the world's name, the description, a link and the tags (one for each of the event's categories, made from its name unless the group set another, and any tags the group set to go on every post; all public), and its picture is the event's cover picture when that is 1 MB or smaller, or, when the event has a video or a GIF, that video or GIF instead. A video file you choose is kept by Modbot (in its database, with the event's pictures) until no event, template or post still to be sent uses it, and goes to the Bluesky account's server only as the post is made; a video link is kept only as an address, and Modbot downloads the video from it when the post goes out, which sends that address's website a request from Modbot's own server. A GIF chosen with the GIF button is kept only as its Klipy address and alt text, and goes to the Bluesky account's server as the post's link card; the GIF itself is never copied. When a moderator searches for a GIF, that moderator's own browser asks Klipy, with the Klipy key you set under Settings, Bluesky, GIF search, the words searched for, a random number that stays in that browser, and the browser's region and address, and loads the pictures from Klipy; Modbot's server is not in between and sees none of it. Everyone who can manage the calendar or its templates gets the Klipy key. When the event has languages picked, they go in the post; when it limits who can reply or turns quote posts off, Modbot also makes a small record next to the post saying so (public on Bluesky, with the post's address) and deletes it with the post. For each such post Modbot keeps in its database, with the other posts, the post's address on Bluesky and the start of the date it is about, so that a restart never posts a date twice and the right post is the one deleted. With Announce on Bluesky when the first person joins ticked on the event, Modbot also sends one reply under the date's post when the first person is in the instance: "We're live in" the world's name and a link to join the instance (when anyone may join) or to the group's page on vrchat.com, with the address and content id of the post it answers. No member name, id or head count is in it. With Pin the next event on, Modbot also reads the account's profile record on Bluesky (its name, description, pictures and pinned post) and writes it back with only the pinned post changed: the next date's post (its address and content id), or none when no date has a post. A post someone pinned by hand is left alone. The profile is public. With Weekly line-up on, Modbot also sends one post a week that lists the next seven days: the group's name, the title and time of each calendar date whose event is visible to Everyone, whether or not its Bluesky chip is on and including a public event that goes only to Discord (members-only events and cancelled dates are not in it), and the public page of the group's Google calendar as a link when there is one. The post is public on Bluesky and copied by other services, and it is not changed or deleted when a date changes afterwards. No member name, id or head count is in it, and it mentions nobody. About every 30 minutes, Modbot also asks Bluesky's public API, with no sign-in, for the likes, reposts and replies of the posts it made in the last 30 days, sending only those posts' addresses (up to 25 at a time). Nothing about a person is sent. About every 3 minutes, Modbot also asks the account's own server for the account's new replies, mentions and quotes (a request for its own notifications, which that server passes on to Bluesky). It keeps each one in the audit log as an entry holding the author's handle, name and Bluesky id, what they wrote and the link to their post, and, for a reply, the title of the Modbot post it answers. These are public posts by people outside the group; the entries are kept like the other audit log entries. Likes, reposts and follows are not kept. A Sign in with Bluesky needs one more permission for this, the read of the account's notifications, and a sign-in made before it was added has to sign in again. With Sign in with Bluesky (only when your Modbot has a publichttps://address), there is no app password: Modbot finds the account the same way, then asks the sign-in server the account's own server names for a sign-in, with the handle and Modbot's public address, and sends you to Bluesky's page to allow it. That server reads Modbot's client document on your public address (Modbot's name, its address and the public half of its signing key), and Modbot renews the sign-in with it. - Twitch: nothing until someone with Change settings saves a client id, a
client secret and a channel in Settings, Twitch. Then each Check sends the client id and
secret to
id.twitch.tvto get an app token, and asksapi.twitch.tvfor the channel by its name and whether it is live. It never changes anything on Twitch, and nobody signs in to Twitch. Once someone turns Live on, Modbot asksapi.twitch.tvabout once a minute whether the channel is live, sending the app token, the client id and the channel's id. Twitch sees your server asking about that public channel, and nothing else. What comes back (the stream's title, category and viewer count) is Twitch's own public information. It is shown to people with See live instances, and Modbot keeps a row for each stream in its database: its Twitch id, title, category, start, end, most viewers, and the event it was linked to. Nothing is sent to Modbot Cloud. A We're live on Twitch post goes nowhere until someone ticks a site under Settings, Twitch, Live post; every site starts unticked. A ticked site gets an ordinary post through the same sending as the Marketing page, with the words you wrote and the stream's title, category and the channel's link filled in, so the readers of that Discord channel, VRChat group or Bluesky account (which is public) see them. Nothing about your members goes in it. Live, each site's tick, Pause all posting and Forget stop it; Forget also deletes the client secret. If Twitch limits Modbot, nothing more is sent to Twitch until the time Twitch names. - Logs: what is in the log Modbot sends, and how to turn it off.
- Environment variables:
MODBOT_CLOUD_DISABLED, which stops your server talking to Modbot Cloud at all. - Companion settings: what the Windows client sends to Modbot Cloud from a moderator's own PC, and how that person turns it off. The client's window does not mention this backup, so the policy and that page are where it is written down.
What a moderator's own PC keeps, and the one clip that can leave it
-
Clips: the companion can keep the last two to ten minutes of VRChat's own window and VRChat's own sound, so a moderator can save those minutes as a video file. It is off unless that person switches it on, it follows VRChat's own log to know whether VRChat is running, it records nothing outside VRChat's window, and a recording never leaves their PC except in the one case below — never to Modbot Cloud. A clip they save themselves becomes evidence on a case only if they choose that file in a browser, the same as any other attachment.
The one case: a clip your server asked for. Since 24 October 2026, if that person ticks a further box that is off by default, Send clips for my actions automatically, your server can ask their companion for a clip of a ban, kick or warning they made, but only if their companion was in the same instance as the person in the last 10 minutes, and only if your group chose to ask for a clip on that kind of action. The companion cuts a copy holding 30 seconds after the action and as much before it as fits under 100 MB, and sends it to your server as the answer to that request. Your server takes a file only as the answer to a request it sent to that one device, for that request, within 15 minutes, once. The clip is kept as evidence on the action, with where and when it was saved, whose PC it came from and its SHA-256, and a status is kept for the request (such as Clip attached or Companion didn't answer). The companion writes each clip it sends to its own Audit Log page. A stolen device sign-in can answer a request your server already sent to that device; it cannot upload anything unasked, ask for a clip, or read anything new.
Separately, that a clip exists can reach your server. A second box, Tell the group's Modbot when I save a clip, off unless that person ticks it, sends your server when and where a clip was saved in your group's instance, and the file's SHA-256 and size — never the clip. Your server keeps that as a presence entry, lists the clip on the case files of people who were there — with the moderator's Modbot username, for every moderator who can see those case files — and uses the fingerprint to recognise the file if it is attached. A clip attached that way keeps when, where and by whose companion it was saved.
A clip has sound in it, and in an instance that sound is people's voices. Until 19 September 2026 it had none, and this says so plainly rather than leaving it to be found out. Discord's sound can go in as well, on a separate switch that is off until that person turns it on. Nothing else their PC is playing is ever recorded — not music, not a browser, not another chat program — because Windows is asked for one named program's sound rather than for what the speakers are playing, and the route that would hand over the speakers is banned everywhere in the client. No microphone is opened for a clip.
-
Listening: the companion can open that person's microphone while VRChat is running so that saying "Modbot, clip that" saves a clip. It is off unless that person switches it on. Nothing the microphone hears is recorded, kept or sent — the sound is checked against a short list of phrases and thrown away as it arrives. Nothing is written to disk, nothing reaches your server or Modbot Cloud. The microphone is shared the way a voice chat program shares it, and the companion says on screen that it is open for as long as it is. Turning Listening on makes the companion download its speech model from GitHub once. While it is on, the companion also asks Windows which microphones that PC has, so the person using it can pick one — a name and an id for each device, used to fill a list on their own settings screen and never sent anywhere. With it off, no microphone is listed or opened.
-
Dictate: on the headset panel or the desktop overlay, a Dictate button (or a key they record) opens that person's microphone between two taps so they can speak a question to AI Chat. It only shows when AI Chat is on and that person is allowed to use it. The sound is turned into text on their own PC, is kept in memory only until the words are written out, and is never saved to disk or sent anywhere. Only the written words are sent, to the Modbot server they paired with, the same as if they had typed them into Chat. A recording stops by itself after 60 seconds. The first tap makes the companion download its speech model, about 108 MB, from GitHub once; nothing about the person goes with that request.
-
Crash details: Copy crash details puts the instance, who was in it with their avatars' names, and VRChat's own log lines from the last ten minutes on that person's clipboard, for a report they write to VRChat themselves. Nothing is sent, and the companion never reads the clipboard.