Is it legal to record a meeting? Consent rules in the EU, Germany and the US, and what changes when you transcribe instead
Consent from everyone in the room answers the criminal-law question. It does not give you a lawful basis under the GDPR, and it does not settle works-council involvement. Three layers, two jurisdictions, and an honest answer on whether a transcript without audio changes anything.
In most places you may record a meeting when the people in it know and agree. What changes by country is how many of them have to agree. In Germany, recording the spoken word of a private conversation without authorisation is a criminal offence under § 201 StGB. Under US federal law a participant may record, but several states require every party to consent. And in the EU, consent settles only the first of three questions: you still need a lawful basis under the GDPR, and in a German workplace you may also need the works council.
This article is general orientation, not legal advice. Check your specific case with your legal team or your data protection officer.
Three separate questions, not one
Most articles on this answer one question and leave the reader believing they are done. There are three, and they are independent.
| Layer | Where it lives | What it asks | If you get it wrong |
|---|---|---|---|
| Criminal law on the spoken word | Germany: § 201 StGB. US: 18 U.S.C. § 2511 plus state wiretap law | Did the people speaking agree to being recorded | Fines or imprisonment, and in the US a civil claim as well |
| Data protection | GDPR Art. 6 and Art. 13, plus national employment rules such as § 26 BDSG | Do you have a lawful basis, did you inform people, when will you delete it | Complaints to the supervisory authority, fines, access and erasure requests |
| Workplace co-determination | Germany: § 87 Abs. 1 Nr. 6 BetrVG, and similar bodies elsewhere in the EU | Is a technical system being introduced that can monitor conduct or performance | The works council can block the rollout |
Solving one does not solve the others. A signed consent form does not create a lawful basis. A well-argued legitimate interest does not make the recording authorised under criminal law. Neither replaces works-council involvement.
Germany: everyone who speaks has to agree
§ 201 Abs. 1 Nr. 1 StGB punishes whoever, without authorisation, records the non-publicly spoken word of another person onto a sound carrier, or uses or passes on such a recording. The penalty is up to three years' imprisonment or a fine. The attempt is punishable, and for public officials the range rises to five years.
Three details decide most real cases. The whole provision turns on "without authorisation". Consent removes the offence. It does not have to be written, but you should be able to evidence it, so a line in the transcript or in the recurring invitation is the simplest route.
Passing a recording on is its own offence. If someone forwards a transcript that a colleague produced without asking the room, the forwarding is punishable in its own right. That is where circulated meeting summaries fail, not at the moment of recording.
An announcement is not consent. It informs, it does not ask. Someone who keeps speaking after an unmistakable notice is commonly read as agreeing by conduct, but do not rely on that where there is a power imbalance: employees, students, candidates.
Other European countries protect the spoken word in comparable ways, with different statutes and penalties: Austria under § 120 öStGB, Switzerland under Art. 179bis to 179quater StGB. Where a meeting spans borders, follow the strictest rule in it.
The United States: one party federally, all parties in some states
Federal law prohibits intentionally intercepting a wire, oral or electronic communication, 18 U.S.C. § 2511(1)(a). Subsection (2)(d) then carves out the case that covers most business meetings: it is not unlawful for a person not acting under colour of law to intercept a communication "where such person is a party to the communication or where one of the parties to the communication has given prior consent", unless the purpose is a criminal or tortious act.
That is the federal one-party rule, and it is only the floor. Several states require every party to consent, some with criminal penalties as well as a civil claim, and they differ on whether the rule covers in-person conversations, calls, or both.
Rather than reproduce a state list that will be out of date within a year, use the Reporters Committee for Freedom of the Press Reporter's Recording Guide, which summarises all fifty states and the District of Columbia and links to each state's own page (checked September 2026).
For a distributed team the practical answer follows from that. If one participant sits in an all-party-consent state, get agreement from everyone. That also makes the German answer and the US answer the same.
What the GDPR adds on top
Even with consent from everyone, the data protection layer is untouched. A transcript contains identifiable statements by identifiable people, so it is personal data. That is true of the text alone, with no audio file. Deleting the audio does not change it.
So the ordinary duties apply, under Regulation (EU) 2016/679:
- A lawful basis under Art. 6. In practice consent, performance of a contract, or legitimate interests. Decide before you record and write the reasoning down. A legitimate interest reconstructed after a complaint convinces nobody.
- Information under Art. 13. At the point of collection, which means before you start, and not buried in a linked privacy policy. Controller, purpose, legal basis, recipients, retention period, and the rights of the people recorded.
- Purpose limitation. A transcript created for minutes is not a basis for performance review. That is where a data protection issue becomes an employment dispute.
- Retention and deletion. Set a period before you begin and keep to it. "Until further notice" is not a retention period.
Where an AI tool does the transcription, responsibility stays with the organisation deploying it. The German supervisory authorities' guidance on that is the DSK Orientierungshilfe "Künstliche Intelligenz und Datenschutz" of 6 May 2024, addressed to controllers and covering selection, deployment and legal basis.
In a German workplace there is one more step. § 87 Abs. 1 Nr. 6 BetrVG gives the works council co-determination over technical systems suited to monitoring employee conduct or performance, where no statutory or collective rule already covers it. A transcription tool records who spoke and for how long, so expect the council to claim that right at rollout. It is not bad news: a works agreement can supply the lawful basis that consent in an employment relationship often cannot. More on that in works councils and AI transcription.
Does a transcript without a recording change anything?
This is the hopeful question, and it has two layers. Only one of them is even interesting.
On criminal law there is an argument, and nothing more. § 201 StGB requires a recording "onto a sound carrier". German commentators have argued that purely transient processing in working memory, never written anywhere, does not meet that element. The position is set out in a criminal-law firm's analysis of AI transcription and § 201 StGB. It is an opinion, not settled case law. It is contested, no court has ruled on it, and it collapses the moment a tool buffers audio, which nearly all of them do if only to survive a dropped connection. Do not build a decision on it.
It does not apply to Kalima. Audio recorded in the browser is processed for transcription and stored against your plan's storage quota so you can play the session back and jump to any word. There is a stored recording. Recording with Kalima needs the same consent as recording any other way.
On data protection nothing changes at all. The text is personal data, it needs a lawful basis, an Art. 13 notice and a retention period. Leaving out the audio reduces the volume of data and the risk, but not one obligation. There is more detail in transcription without recording.
What to do before the next call
Where Kalima stands
Kalima records the audio on your own device, from the microphone, the system output, or both mixed together. It does not connect to Zoom, Teams or Meet, and nobody extra appears in the participant list. That is a fact about how the audio is captured, not a way around anyone's consent. Announce it at the start of the meeting as you would with any other tool.
What Kalima can contribute is the practical part: servers in Germany, audio and transcripts never used to train models, sessions private until you share them, and self-service export and deletion. What is stored and how deletion works is set out in your data and privacy and on the trust page.
Frequently asked questions
Can I record a Teams meeting without telling everyone?
No. Microsoft Teams showing a recording indicator to participants is information, not consent. In Germany the criminal-law question turns on whether the people speaking agreed, not on what the software displays. In the US it depends on the states involved, and where any participant is in an all-party-consent state you need everyone.
Is it illegal to record a meeting without consent?
In Germany it can be: § 201 Abs. 1 Nr. 1 StGB carries up to three years' imprisonment or a fine for recording the non-publicly spoken word without authorisation, and using or passing on such a recording is punishable too. Under US federal law a participant may record, but state law can require all parties to agree.
What is two-party consent, and which states require it?
Two-party or all-party consent means every person in the conversation has to agree, rather than just one. Which states require it, and whether the rule covers in-person conversations as well as calls, changes over time, so check the Reporters Committee state guide rather than a summary.
Can my employer record Teams meetings?
Only with a basis, and in an employment relationship that is rarely consent, because consent given by an employee is assessed against the dependency inherent in the relationship (in Germany, § 26 Abs. 2 BDSG). In practice it comes down to a works agreement. Where there is a works council, § 87 Abs. 1 Nr. 6 BetrVG gives it co-determination over the rollout.
Is a transcript with no audio recording safe under the GDPR?
No. The text identifies people and what they said, so it is personal data in its own right. You still need a lawful basis, an Art. 13 notice and a retention period. Less data means less risk, not fewer obligations.
Does a notice in the calendar invitation count as consent?
As Art. 13 information it is a good start. As consent it is not enough on its own, because consent requires a response from the person. Repeat the notice out loud at the start and give people a chance to object before the recording begins.
Related
Try Kalima on your next call.
Live transcription and translation, no bot in the meeting. Free to start.
Keep reading.
Your Company Blocked AI Notetakers. What You Can and Cannot Do Next
A blocked notetaker is either a switched-off transcription policy, a lobby that refused a bot, or a network that refuses the service itself. Only one of those is about something joining your call, and only one is a question you can answer without asking somebody first.
Can you record a job interview? Consent, state law and the AI Act question nobody answers
Five vendor blogs answer this with a state list and a consent form. None of them mention that a voice recording can trigger a biometric statute, none cover an EU employer interviewing a US candidate or the reverse, and none say what happens to the recording after the decision is made.
The Google Meet Transcript Exists and You Still Cannot Open It
You were in the meeting, the transcript was made, and Drive still shows you a Request access screen. Meet ties the transcript to the Calendar invite, cuts off meetings with more than 200 invitees, and leaves external guests out entirely. Here is each rule, and why the file came out in the wrong language.