Is it legal to record a meeting?
Usually yes, if you are in the meeting and everyone knows. The two things that decide it are which consent standard applies and where every participant happens to be sitting — and the second one is the part people get wrong.
- US federal law sets a one-party floor. 18 U.S.C. §2511(2)(d) says it is not unlawful for a private person 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”, except where the purpose is criminal or tortious.
- States can be stricter, and several are. California Penal Code §632(a) reaches anyone who records “without the consent of all parties to a confidential communication” — with “confidential” defined by whether the circumstances reasonably indicate a party wanted it kept between them.
- The applicable rule follows the participants, not the host. Practitioners apply the strictest standard present on the call, because you rarely know which state or country everyone is dialling in from.
- Under the GDPR the question is not “did they consent” but “do you have a lawful basis” — consent is only one of the six in Article 6(1), and Article 4(11) requires it to be “freely given, specific, informed and unambiguous”.
- Saying it out loud at the start takes about ten seconds, and it is what practitioners recommend whichever standard applies. It is not a substitute for knowing the rule where the participants are. Narada’s own onboarding puts it bluntly: “the legal responsibility is yours.”
Usually yes, if you are in the meeting and everyone in it knows. What turns that “usually” into a real answer is which consent standard applies, and that depends on where every participant is — not on where you are, and not on who booked the meeting.
This page explains the concepts so you know what you are looking at. It is not legal advice, and nobody selling recording software is qualified to give you any. It could not be advice even in principle: a web page has no idea whether the four people on your Thursday call are in Austin, Sacramento, Munich and a hotel in Toronto — which is the fact the answer turns on.
One-party and all-party consent
Almost every argument you will read about this is really about which of two standards applies.
One-party consent means the recording is permitted if one person in the conversation agreed — and if you are in the meeting, that person can be you. This is the US federal floor. The federal Wiretap Act says it is not unlawful for a private person 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 to such interception unless such communication is intercepted for the purpose of committing any criminal or tortious act”
That last clause matters and gets dropped from most summaries. One-party consent is not a blanket permission; it evaporates if the recording is a tool for something unlawful.
All-party consent means everyone in the conversation has to agree. The federal statute is a floor rather than a ceiling, so a state can demand more, and some do. California is the standard example — Penal Code §632(a) reaches a person who records “without the consent of all parties to a confidential communication”. Note the qualifier. That statute defines a confidential communication by whether it is “carried on in circumstances as may reasonably indicate that any party to the communication desires it to be confined to the parties thereto”, so even inside an all-party state the question is not a mechanical one about the number of consents.
There is deliberately no fifty-state table on this page. Those tables exist, they disagree with each other on the borderline states, and every row is a statute plus the case law interpreting it. If your recording matters — a client call, an interview, anything that might be read out later — the correct move is reading the code section for each jurisdiction involved, or paying someone to.
The rule follows the participants
Here is the part that surprises people. You are not asking “am I allowed to record”, you are asking “is this recording lawful for everyone in it”.
A one-party-consent state and an all-party-consent state on the same call is an ordinary Tuesday, and the usual professional approach is to apply the strictest standard present. Worse, you often cannot enumerate the jurisdictions at all. Somebody joins from an airport, somebody’s calendar says one office while their laptop is in another country, and a recurring meeting picks up an attendee you have never met.
This is the actual argument for announcing it, and it has nothing to do with being nice: an announcement is the one action that works without knowing where anybody is.
Notice is not the same as consent
Two distinct things get flattened into the word “consent”.
Notice is telling people. Consent is their agreement. In some jurisdictions notice plus continued participation is treated as agreement — the reason those recorded-line messages exist at the start of support calls. In others an explicit yes is required. Silence is the ambiguous case, and how it resolves is jurisdictional.
European law reframes the question entirely. A recording of identifiable people is personal data, and so is the transcript generated from it, so the GDPR asks whether you have a lawful basis under Article 6(1) — consent is only one of six, alongside contract, legal obligation, vital interests, public task and legitimate interests. Legitimate interests is not a free pass: it applies “except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject”. And GDPR consent is a defined term with teeth — Article 4(11) requires it to be “freely given, specific, informed and unambiguous”. And in some European countries the criminal code applies on top of data protection: in Germany, §201 StGB — on the confidentiality of the spoken word — carries up to three years' imprisonment or a fine. That is a different kind of exposure, and which code section applies where is a question for local counsel.
A private call and a workplace recording are different questions
Even a recording that breaks no statute can still cost you.
Company policy, an NDA, a client engagement letter, professional conduct rules, works-council agreements in parts of Europe — any of these can prohibit what the criminal code permits. Being fired is not a wiretap question, and “it was legal” is not a defence to a policy you agreed to.
Then there is the asymmetry problem, which gets far less attention than the state-by-state tables. Consent from someone who cannot comfortably refuse is weaker than it looks. A candidate asked mid-interview whether they mind being recorded is being asked whether they would like to seem difficult. GDPR’s “freely given” language exists because of exactly this dynamic in employment relationships. If you are the one with the power in the conversation, disclose in advance and in writing — in the invitation, not on the call — so the other person can decline privately and without a cost.
The ten seconds worth spending
“I am recording this for my notes — everyone okay with that?”
That is it. It creates notice, it gives everyone the chance to agree or refuse, and it is on the recording itself, so you have evidence of it later. Whether it satisfies the consent standard where each participant is sitting is the question this page opened with — a sentence on a call cannot answer it for you. For asymmetric situations, put the same sentence in the calendar invite so anybody can say no where nobody is watching.
If somebody objects, that is an answer rather than the opening of a negotiation. Take notes by hand.
What Narada does about it, and what it does not
Narada records your Mac’s audio locally with no bot joining the call. On the legal question it does exactly two things, and it is explicit about both. Onboarding says:
“Recording laws vary by country, state, and workplace. Before recording a meeting, make sure every participant knows and agrees. Narada always shows a recording window with a reminder, but the legal responsibility is yours.”
And the recording window itself carries the line “Remember to notify participants about recording” for the whole session.
Now the limits, stated plainly, because this is the page where hedging would be worst:
- It does not tell anyone. No automated chat message when recording starts, no watermark, no in-call banner — several cloud notetakers offer those and Narada has none of them. The reminder is on your screen, for you. It is also invisible in a screen share by design, so it cannot function as disclosure to anybody else even by accident.
- It cannot make a recording lawful, and no software can. It has no idea who is on your call or where they are.
- Files are unencrypted on purpose, as plain
.m4a,.txt,.mdand.jsonin a folder you pick, so they open in anything. Access control is your Mac’s disk encryption and login, not the app’s. - There is no compliance certification of any kind — no SOC 2 report, no HIPAA claim, no GDPR badge. What the architecture gives you is a factual answer to a questionnaire rather than a certificate: transcription runs on-device, and raw audio is never uploaded in any mode. In the Pro AI and bring-your-own-key modes the transcript text does go to OpenAI after you explicitly consent, which is a fact your own confidentiality analysis needs.
- Removing the bot removed a disclosure signal. Nothing appears in the participant list because nothing joined, which is the point — and the visual cue that used to announce a recording is gone with it. That makes the announcement more your job, not less.
Where the software runs does not change who has to agree
One thing worth being explicit about, because it cuts against the product on this page: all-party consent attaches to the recording, not to the architecture. A recorder running quietly on your own laptop is in exactly the same position as a bot sitting in the attendee list. Keeping the audio on your Mac changes who receives it — it does not change who had to say yes.
That is the whole reason this page exists rather than a page about how private Narada is.
Sources
- 18 U.S.C. §2511(2)(d), via https://www.law.cornell.edu/uscode/text/18/2511.
- California Penal Code §632, via <https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=PEN§ionNum=632>;.
- GDPR Article 6(1), lawful bases: https://gdpr-info.eu/art-6-gdpr/.
- GDPR Article 4(11), definition of consent: https://gdpr-info.eu/art-4-gdpr/.
- Germany, §201 StGB (Verletzung der Vertraulichkeit des Wortes), code text: https://www.gesetze-im-internet.de/stgb/__201.html.
- Narada’s own consent wording, quoted from the shipping app’s onboarding and recording window.
All checked 4 August 2026. Statutes are amended and case law moves; check the current text before relying on any of this.
Questions people ask about this
Do I have to tell everyone I am recording a meeting?
Where one-party consent applies and you are a participant, the law may not require it. Where all-party consent applies, it does. Because you often cannot tell which rule covers the whole call, announcing it is the practical answer regardless — it is also the step any consent, express or implied, has to start from.
Is it legal to record a meeting at work?
That is two questions. The recording statute is one; your employment contract, NDA, client engagement letter, professional conduct rules and company policy are the other. A recording can be perfectly lawful and still be a disciplinary matter, because a policy can be stricter than the law.
What if participants are in different states or countries?
Then more than one rule is potentially in play, and the common practitioner approach is to follow the strictest standard among the jurisdictions present. This is why announcing beats researching: the announcement works no matter who turns out to be on a train in another state.
Does recording without a bot change the legal position?
No. Consent obligations attach to the recording, not to whether an extra participant appeared in the attendee list. What changes is practical: the bot in the participant list was an accidental disclosure signal, and without it the disclosure is entirely yours to make.
Try it on your next call
Narada records your Mac's audio and your microphone, transcribes on-device, and hands you the decisions and follow-ups. Free to use, no account, no bot in the meeting.