Where Can You Record a Meeting Without Everyone’s Consent?
A practical guide to participant-recording and one-party-consent rules in Poland, selected countries, and US states—with GDPR and workplace caveats.
In Poland, can you record a call without asking everyone else first?
If you are a lawful participant recording information addressed to you, the recording generally does not constitute unlawful interception under Article 267 of the Polish Criminal Code. But that is not the same as saying the recording is lawful in every respect: even the act of secretly recording can infringe another person’s civil rights.
That does not mean “consent never matters.” Recording, storing, transcribing, sharing, publishing, or using the call at work are different legal acts. GDPR, employment rules, confidentiality duties, personal rights, and the law of another participant’s location may still require notice, a lawful basis, or permission.
The same distinction appears around the world. Some jurisdictions have a clear participant exception or one-party-consent rule. Others require everyone to agree. Several sit in between.
This guide gives a practical starting point as of September 24, 2026. It is not legal advice, and the country list is not exhaustive.
“One-party consent” and “participant recording” are not identical
“No consent required” is convenient shorthand, but it hides the legal mechanism.
In a one-party jurisdiction, one person who is actually part of the conversation can usually consent to the recording. If you are participating and operating the recorder, that consenting person is you.
Some countries instead exclude a participant’s own recording from a particular interception offence. That is a participant exception, not necessarily a rule allowing that participant to authorise any outside recorder. US federal law expressly permits prior consent from one party; do not assume every country has the same delegation rule.
Neither label is blanket permission to:
- leave a recorder in a room and capture other people’s private conversation without a valid legal basis;
- activate a bot in a meeting you do not attend without checking whether the applicable law recognises an actual participant’s authorisation and whether that authorisation covers the capture;
- bypass confidentiality, professional-secrecy, or trade-secret duties;
- publish private audio without considering separate privacy and personality rights; or
- ignore stricter law when another participant joins from a different country or US state.
Lawful participation, or valid participant consent where the applicable law permits it, is the starting point. Merely owning the meeting room, calendar event, company laptop, or conferencing account is not a general recording permission. Stop or reassess when you leave: permission for your conversation need not cover a later conversation between others.
Poland: participant recording is generally outside Article 267
Article 267 of the Polish Criminal Code addresses unauthorised access to information; §3 covers using a device or software to obtain information to which the recorder is not entitled.
Poland’s Commissioner for Human Rights has explained that this provision does not ordinarily apply when one participant records their own conversation: information spoken to that participant was intended for them.
The Polish Supreme Court drew the same distinction in case II CSK 478/15, judgment of April 22, 2016. A participant recording information they received lawfully is different from a third party illegally intercepting a conversation. This was a decision about evidence in civil proceedings, not a general licence for covert workplace recording.
The Court also explained that privacy and fairness can limit the use of a secretly made recording as evidence.
Civil liability is a separate question, even before publication. In I CSK 292/17, the Supreme Court recognised that covert recording can infringe freedom of expression, individual privacy, and a company’s sphere of confidentiality. A justification must be assessed in context; participant status alone does not establish one. See the court’s discussion of that ruling in a later civil case.
So the practical Polish rule is:
| Situation | Starting point |
|---|---|
| You lawfully participate and record information addressed to you | Generally outside Article 267; civil privacy rights and applicable data-protection duties still matter |
| You place a device or bot in a conversation you do not attend | Potential unlawful interception under Article 267 |
| You record a work call, locally or in the cloud | GDPR can apply from initial capture; an upload adds vendor, security, and transfer questions |
| You share or publish the recording | Separate personal-rights, privacy, defamation, confidentiality, and data-protection analysis |
| An employer systematically records workers | Employment monitoring and GDPR duties apply; participant status alone is not enough |
Poland is therefore a good example of a participant-recording country, not a country where recordings are legally consequence-free.
Countries with a participant or one-party starting point
The following countries have statutes or high-court authority distinguishing a participant’s own recording from third-party interception. The table concerns ordinary audio conversations received lawfully—not video, screen capture, unauthorised meeting access, or every form of surveillance. The final column is essential: “I was on the call” may still be insufficient for a business workflow.
| Country | Why a participant may record | Main qualification |
|---|---|---|
| Poland | Article 267 targets obtaining information not intended for the recorder; the Supreme Court distinguishes participant recording from illegal interception | Personal rights, GDPR, employment rules, confidentiality, and harmful use remain separate |
| Canada | Criminal Code §184(2)(a) provides an exception with express or implied consent from an originator or intended recipient; §183.1 says one is sufficient | Federal PIPEDA and provincial privacy laws are separate: businesses subject to PIPEDA generally must inform customers and obtain consent when recording customer calls, subject to limited exceptions |
| Denmark | Criminal Code §263 criminalises secretly recording conversations “between others” or closed meetings the recorder does not attend | Authorities, courts, workplaces, data protection, and later disclosure can be governed separately |
| Sweden | Criminal Code Chapter 4 §9a covers conversations between others and closed meetings the recorder does not lawfully attend | Unauthorised admission is expressly covered; GDPR, employment duties, confidentiality, and dissemination still require analysis |
| Norway | Criminal Code §205 targets secret recording of communication between others or a closed meeting the recorder does not attend | Datatilsynet’s guidance separately requires a data-protection basis and information to participants where those rules apply; workplace monitoring adds duties |
| Netherlands | Criminal Code Articles 139a–139c distinguish recording one’s own conversation from interception: Articles 139a–139b concern non-telecom conversations; Article 139c addresses telecom/computer data not intended for the recorder | Organisations still need a GDPR basis, transparency, minimisation, retention, and security; the legal analysis must match the communication type |
| Finland | Criminal Code Chapter 24 §5 protects speech not intended for the recorder’s knowledge; a participant is an intended recipient | Disseminating private information is separately restricted, and workplace processing has its own rules |
| Spain | The Constitutional Court has held that a participant recording a conversation does not, by that fact alone, violate communications secrecy | Core personal or family intimacy, data protection, employment surveillance, and disclosure can change the result |
| Italy | The Court of Cassation treats participant recording as memorialising information lawfully received by one interlocutor, rather than third-party interception | Recording in specially protected places, professional secrecy, workplace use, and dissemination require separate review |
This table is deliberately narrower than many global “recording laws” lists. It includes jurisdictions where an official statute or court source supports the participant distinction. It does not imply identical rules, identical evidentiary treatment, or permission to use a recording for any purpose.
New Zealand: possible does not mean automatically fair
New Zealand illustrates why a criminal-law label can be misleading.
Crimes Act §216B(2)(a) excludes a party to a private communication from the interception prohibition.
The Office of the Privacy Commissioner says the Privacy Act will often not apply to a genuinely personal or domestic recording. That exemption does not apply where collecting, using, or disclosing the information would be highly offensive to a reasonable person. Outside the personal setting, covert recording may also breach the Privacy Act, depending on its purpose and circumstances.
For workplace meetings, the Commissioner says recording with consent is generally best and that covert recording carries a strong presumption of unfairness unless compelling circumstances justify it. Participants may also have access rights to a recording made on behalf of an organisation. See the Commissioner’s meeting-recording guidance.
The useful classification is therefore not “New Zealand requires everyone” or “New Zealand requires nobody.” A participant may be able to make a personal recording, while an employer using the same device for systematic monitoring faces much stricter obligations.
US states where one participant is generally enough
US federal law supplies a one-party baseline. 18 U.S.C. §2511(2)(d) generally permits interception when the recorder is a party or one party has given prior consent, unless the purpose is criminal or tortious.
State law can be stricter. Using the Reporters Committee for Freedom of the Press state guide as a secondary reference, this guide groups the following 33 states under a broad one-party starting point for in-person and telephone communications. This is not an official statutory category or a claim that only 33 states permit participant recording; additional participant-friendly jurisdictions appear in the qualified table below.
Alabama, Alaska, Arizona, Arkansas, Colorado, Georgia, Idaho, Indiana, Iowa, Kansas, Kentucky, Louisiana, Minnesota, Mississippi, Nebraska, New Jersey, New Mexico, New York, North Carolina, North Dakota, Ohio, Oklahoma, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, West Virginia, Wisconsin, and Wyoming.
Washington, DC also generally follows one-party consent.
The recorder must still be a participant or have consent from a participant. Expectation of privacy, hidden-camera law, an unlawful purpose, workplace policy, biometric processing, and disclosure can create separate liability.
Seven states with participant-friendly but mixed rules
These states should not be placed in a simple green “one-party” bucket:
| State | Participant-friendly part | Stricter part |
|---|---|---|
| Connecticut | In-person conversations generally use one-party consent | §52-570d imposes a separate civil rule for private phone calls: specified all-party consent, recorded verbal notice at the start, or a prescribed repeating warning tone, subject to exceptions |
| Nevada | In-person conversations generally use one-party consent | Telephone calls are treated as all-party |
| Missouri | §542.402.2(3) provides one-party consent for wire communications | The oral-communication restriction in §542.402.1(2) specifically concerns devices that transmit by radio or interfere with transmission. RCFP recommends all-party consent for private in-person conversations as a cautious approach; it is not an unqualified statutory rule for every recorder |
| Oregon | Telephone calls generally use one-party consent | ORS 165.540(1)(c) generally requires all participants in an in-person conversation to be specifically informed of capture, subject to exceptions; notice is not the same as affirmative consent |
| Hawaii | Generally one-party | §711-1111 adds private-place surveillance restrictions requiring consent from those entitled to privacy there, not merely one conversation participant |
| Maine | Generally one-party | Title 17-A §511 adds consent requirements for surveillance in or into private places, including bathrooms and changing rooms |
| Michigan | A participant may generally record their own conversation | A third-party eavesdropper is subject to the stricter all-party rule |
For the remaining primarily all-party jurisdictions and detailed qualifications, use Summit’s complete US state-by-state meeting recording guide.
For video calls, check how the relevant statute defines oral, wire, and electronic communications. A remote meeting is not automatically governed by every exception written for a traditional telephone call.
GDPR does not turn Europe into one consent zone
GDPR does not create a single European rule about whether pressing Record is a criminal offence. National interception, privacy, and communications laws answer that first question.
GDPR can apply from initial capture, because collecting and recording identifiable speech is already processing personal data. Keeping everything on one device does not remove that obligation.
For a company, freelancer, employer, or professional practice, that commonly means:
- identifying a lawful basis under GDPR Article 6;
- providing transparent information about purpose, recipients, retention, and rights;
- collecting only what is necessary;
- protecting audio, transcripts, summaries, and speaker labels;
- identifying each vendor’s role, using Article 28 terms where it acts as a processor, and assessing international transfers where applicable;
- handling sensitive or special-category data with an additional Article 9 condition where required; and
- deleting the material when no lawful retention purpose or duty remains.
Consent is not the only possible GDPR lawful basis. But replacing consent with “legitimate interests” is not automatic. The organisation must identify a legitimate interest, show necessity, and balance it against participants’ rights, including whether manual notes would achieve the purpose with less intrusion. See the EDPB’s lawful-processing guidance. Local transcription can reduce disclosure to vendors; it does not by itself make the initial capture necessary or lawful.
Agreement to recording under an interception law is not automatically valid GDPR consent. Where GDPR consent is the chosen basis, it must be freely given, specific, informed, and unambiguous, with a real ability to refuse or withdraw. Employment power imbalances can make that basis unsuitable.
The personal or household exemption can remove genuinely private activity from GDPR’s scope. It does not normally cover a business recording customers or an employee building a searchable archive for work.
Recording and using are separate decisions
Even where participant recording is lawful, each later step needs its own answer.
Keeping it privately
A short-lived recording used to correct personal notes creates a different risk from a permanent searchable archive.
Transcribing it with an AI service
Uploading audio can disclose it to a transcription provider, foundation-model vendor, analytics service, and subprocessors. A lawful local recording does not automatically authorise those transfers.
Sharing it internally
A manager may be entitled to attend a call but not entitled to distribute every statement to an entire department. Apply purpose limitation and least-privilege access.
Publishing it
Publication can trigger personal rights, confidentiality, defamation, data protection, copyright, trade-secret, and professional-secrecy rules even when capture itself was lawful.
Using it as evidence
Courts distinguish how a recording was obtained from whether it is admissible, authentic, relevant, or outweighed by privacy and fairness concerns. Do not edit or destroy potentially relevant material after a dispute is foreseeable; obtain legal advice.
Cross-border calls: a conservative workflow, not a choice-of-law rule
Suppose a participant in Warsaw records colleagues in Berlin, Zurich, and California. Polish participant-recording law does not guarantee that Polish law is the only law a court or regulator will apply.
Relevant factors can include:
- where each participant was located;
- where the recorder and recording system were located;
- which organisation determined the purpose;
- where harm occurred;
- the employment or customer contract; and
- the forum hearing the dispute.
For routine international or interstate meetings, our conservative operational recommendation is to notify everyone and obtain affirmative agreement before capture. This is not a legal rule that the strictest jurisdiction always wins, and agreement alone does not satisfy every data-protection or employment requirement. A one-party rule is most useful for understanding a legal starting point—not for designing a silent multinational recording program.
A practical decision tree
Before recording, ask:
- Am I a lawful participant, or do I have valid authorisation under a law that permits third-party recording? A participant exception does not automatically authorise an unattended bot.
- Where is everyone located? For a cross-border call, use notice and agreement as a conservative workflow; obtain advice on which laws actually apply.
- Is this personal or organisational? Business and employment use brings data-protection and monitoring duties.
- Why is a recording necessary? Prefer a less intrusive method when it achieves the same purpose.
- Where will the data go? Include transcription, summarisation, integrations, backups, and model-training terms.
- Who will receive it? Capture permission is not publication permission.
- When will it be deleted? Set retention before pressing Record.
What local processing changes
Local processing can remove several third parties from the chain. With Summit and Local Models selected, capture, transcription, speaker separation, summarisation, storage, and search can stay on the Mac. There is no meeting bot and no automatic cloud repository.
That does not change Polish Article 267, a US state’s consent category, GDPR, or another participant’s privacy rights. A local recording can still be covert, excessive, insecure, or unlawfully shared.
Summit’s optional hosted summarisation and iCloud features create additional data paths when enabled. The exact boundaries are described in the security architecture.
The practical takeaway
In Poland, recording information addressed to you as a lawful participant generally falls outside Article 267. That is narrower than a general right to record secretly: civil rights, workplace obligations, and data-protection law can still prohibit or constrain the capture itself. Canada and several European countries also distinguish participant recording from third-party interception, while most US jurisdictions use a one-party baseline.
But “I may press Record” answers only the first question.
For a defensible workflow, assess capture, storage, AI processing, workplace monitoring, sharing, publication, and evidence separately. For routine cross-border calls, we recommend notice and everyone’s agreement even when the recorder’s home jurisdiction would permit silent participant recording. That precaution does not replace the separate legal checks above.
Sources
- Polish Criminal Code: Article 267, consolidated text
- Polish Supreme Court: II CSK 478/15, reproduced judgment text
- Polish civil-rights case law discussing I CSK 292/17
- Polish Commissioner for Human Rights: participant recording and Article 267
- Canada Criminal Code §184
- Denmark Criminal Code §263
- Swedish Criminal Code, Chapter 4 §9a
- Norway Criminal Code §205
- Netherlands Criminal Code Articles 139a–139c
- Finland Criminal Code, Chapter 24
- Spain Constitutional Court: STC 114/1984
- Italy Court of Cassation: participant recordings
- RCFP: Introduction to the Reporter’s Recording Guide
- New Zealand Privacy Commissioner: recording a workplace meeting
Try Summit on macOS for bot-free meeting notes with a fully local processing path.