Guide · September 1, 2026 · 3 min read
Recording a voice channel without trapping anyone
Recording a team meeting, a play session or an interview has perfectly legitimate uses. The only question that matters: do all the participants know, and can they opt out?
Contents
The framework, in two sentences
Recording a conversation you are taking part in is legal in most situations. Recording without the participants' knowledge is not, and what is done with the recording is the responsibility of whoever holds it.
That is enough to settle the technical rules: the recording must be announced, it must be refusable, and the file must be treated as personal data — because that is what it is.
The public announcement, no exceptions
Starting a recording must produce a message visible in the channel, not a private confirmation to whoever started it. Someone joining the voice channel partway through must also be told: they were not there when the announcement went out.
There is no good reason to disable that announcement. A silent recording feature has exactly one use, and it is not a moderation team's.
Individual refusal is the heart of the mechanism. A participant must be able to withdraw from the recording without leaving the voice channel: their voice is then not captured, and they carry on taking part in the conversation. Without that option, the announcement leaves only one choice — accept, or leave.
What must stay out of it
Two sources deserve to be excluded by default.
The bot's music. It takes up half the soundtrack, makes the recording unusable, and raises rights questions nobody wants to raise. Excluding it is set once, before the first recording.
The other bots. Notification sounds, automatic announcements: none of that is of any interest in a recorded meeting.
The file, and its lifespan
A voice recording is personal data: it contains the voices of identifiable people, and often the content of what they said in private. Three rules are enough to handle it properly.
- A retention period decided in advance. Long enough to write the minutes, not “just in case”. A week covers most needs.
- Restricted access. Those who have a use for it, not the whole team. A recording of a team meeting has no business circulating in a general channel.
- No redistribution without consent. Publishing an extract of a private conversation, however funny, however harmless, is done with the agreement of the people involved.
The uses that justify recording
Team meetings. The most common, and the most useful: those who could not attend catch up, and decisions no longer depend on what each person believes they remember.
Recruitment interviews. Useful for comparing several candidates several days apart. Provided you tell the candidate at the start of the interview, and accept a refusal without it counting against them.
Play sessions or events. To get an edit, a clip, a memento out of it. This is the case where redistribution is planned from the start: say so when you start the recording, not when you publish.
One use to rule out: recording “to have proof” in case of conflict. Permanently recording a voice channel turns server life into surveillance, and evidence obtained that way is rarely worth what it costs in trust.
Frequently asked questions
Do you need everyone's consent before starting?
The announcement and the ability to refuse are enough for a conversation you are taking part in. For a recording meant to be published, explicit consent is preferable.
Can the bot record without being in the voice channel?
No. It has to be connected to the channel, and its presence shows in the participant list — an extra signal, independent of the announcement.
What happens if somebody refuses partway through?
Their voice stops being captured from that moment. What was recorded before stays recorded: which is why the announcement must be immediate and visible.
Does the recording include the screen or video?
No, audio only. A screen share is not captured.
Read next : Temporary voice channels, Logging, Team rota.