From the journal

AI meeting assistants: whose consent is needed to record, transcribe and reuse a call?

An AI meeting assistant can listen to a call, turn speech into a transcript, assign tasks and put information into a customer relationship management (CRM) system. Each operation needs a lawful purpose and a permitted route. The business deploying the assistant must establish who can authorise its capture, what information every participant needs, and whether the vendor may use the material beyond that meeting.

29 min read

The host's invitation answers only part of that inquiry. An actual participant may be able to authorise interception under one law, while another requires permission from everyone whose conversation is captured. Privacy law then governs collection, use, retention and disclosure. Confidentiality duties and employment rules can add further conditions. External guests retain the protections that apply to them even when they have never opened an account with the vendor.

A controlled starting configuration is purpose-limited notes, an identifiable assistant, individual information before capture, affirmative permission as the product's chosen route, an unrecorded alternative, and separate switches for audio storage, CRM export, training and voice recognition. The countries compared here show where that configuration needs adjustment and where a consent screen cannot make a proposed use lawful.

Establish the actors, locations and data flow

Before enabling a tenant-wide default, the customer and vendor should answer six questions together.

  • Who participates, and where are they when speech is captured? Evidence needed: Actual participant and capture locations, customer/vendor establishments and relevant business connections. Configuration consequence: Determines which recording, privacy and employment rules require examination.
  • Who acquires the sound? Evidence needed: Whether the host records locally, the vendor receives delivered audio, or another service copies a live stream. Configuration consequence: Establishes which actor needs an interception or recording permission.
  • What does the product create and keep? Evidence needed: Audio files, temporary buffers, text, summaries, logs, embeddings and voice templates. Configuration consequence: Separates acquisition duties from retention and biometric conditions.
  • Who chooses each purpose? Evidence needed: Instructions for notes and CRM; vendor terms for evaluation, training and other reuse. Configuration consequence: Determines responsibility and whether additional permissions or bases are needed.
  • Who receives or can access the material? Evidence needed: Attendees, managers, CRM users, support staff, subprocessors and countries. Configuration consequence: Determines disclosure, confidentiality and international-processing conditions.
  • Can a participant refuse or stop the processing? Evidence needed: The actual guest, late-entry, pause, withdrawal and deletion flows. Configuration consequence: Determines whether the selected permission route works in practice.

The customer's governing-law clause cannot settle all these questions. A speaker's location, a vendor's independent activity or the place of acquisition can connect a mandatory law to the meeting. Nationality, account country and billing address should not substitute for the connecting factor in the relevant statute.

Capture and reuse need separate decisions

Deleting audio after transcription reduces what remains stored. The product has still acquired speech and processed its content. A named transcript, an attributed task or a summary of someone's health problem can remain personal or sensitive information. A reusable voice template adds a different identity function.

  • Stored audio. Permission and purpose question: May each actor acquire and retain this conversation, for this purpose? Product control: Gate capture, show bot identity, restrict listeners and set an audio-specific retention period.
  • Live transcription with no retained audio. Permission and purpose question: Does temporary listening or stream acquisition fall within the local interception rule, and what permits processing the text? Product control: Document buffers and remote streams; make pause stop acquisition and transcription.
  • Stored transcript. Permission and purpose question: Who may retain, search, share and correct identifiable speech in text form? Product control: Limit access and retention; provide guest-accessible rights handling.
  • Summary and action items. Permission and purpose question: Are the derived assertions necessary, accurate and disclosed to authorised recipients? Product control: Review important attributions and propagate corrections to tasks and CRM records.
  • Speaker identification. Permission and purpose question: Is this an account name, a meeting-local label, or recognition from voice characteristics? Product control: Describe the mechanism and avoid hidden persistence across meetings.
  • Voiceprint. Permission and purpose question: Is there a permitted biometric purpose, the required sensitive-data condition and any assessment or authorisation? Product control: Separate template creation from notes; disable it until those conditions are established.
  • Training reuse. Permission and purpose question: Who chooses the training purpose, whose data enters it, and what authorises that separate use? Product control: Separate training, evaluation and feedback settings; cover upstream providers and derived stores.

These distinctions have direct statutory consequences. Kenya's cybercrime law expressly includes temporary interception. Germany's protection of non-public speech requires attention to the particular technical act. New Zealand's biometric code reaches defined automated identification, verification and categorisation. A label such as “text only” or “service improvement” cannot replace those tests. See Kenya's section 17, Germany's section 201 and New Zealand's biometric code.

Whose permission permits the assistant to listen?

The United States and Canada separate criminal permission from data use

Under the US federal Wiretap Act, a private actor ordinarily has a route where it is a party or one party has given prior consent, subject to the criminal-or-tortious-purpose qualification. The limited communications-provider exception has its own conditions. A provider acquiring speech for independent purposes must establish the exception on the actual facts. The statute also addresses knowing use or disclosure of unlawfully intercepted contents. 18 USC § 2511.

State law changes the deployment decision. California's section 632 generally requires all parties' consent for recording a confidential communication. Section 632.7 requires all parties' consent for its specified cellular, cordless and landline recording combinations. The device, transmission path and confidentiality requirement where applicable determine which provision governs. A national policy based solely on the federal one-party route leaves these state questions unresolved. California Penal Code § 632; § 632.7.

Washington provides a specific route through an effective announcement to all parties that recording is about to occur; when the conversation is recorded, the announcement must also be recorded. That can differ from a product's chosen affirmative-click process. Pennsylvania's general consent exception requires all parties' prior consent. Its narrower telephone marketing/customer-service route requires qualifying business personnel, one party's consent and interception solely for the business's training, quality control or monitoring. The business may use recordings only for training or quality control and must destroy them within one year unless federal or state law requires otherwise. A vendor's independent model training needs a separate legal route. New York's criminal definitions generally provide a one-party-consent route; covered employers also have prior notice upon hiring, acknowledgement and posting duties for specified electronic monitoring. Washington RCW 9.73.030; Pennsylvania § 5704(4),(15); New York Penal Law § 250.00; New York Civil Rights Law § 52-c.

These selected states demonstrate why “US compliant” needs a defined scope. A launch involving another state, a voiceprint feature or a different technical interception path needs the corresponding local assessment. Covered California businesses also face California Consumer Privacy Act (CCPA) duties for personal information, including relevant employee and business-contact information. Its “sharing” concept concerns cross-context behavioural advertising; ordinary disclosure to every service provider should not be described as that statutory category. CCPA, including §§ 1798.100,1798.140.

The 13 August 2026 Otter.ai order makes the non-user issue concrete. The court considered pleaded claims about meeting participants whose communications were captured through another person's use of the service, along with alleged vendor practices and state-law differences. It granted dismissal in part and allowed other claims to proceed. The court assessed allegations at the dismissal stage; the order supplies no final finding that the alleged practices occurred or that a classwide violation was proved. Product teams should use its claim-specific consent and interception analysis to examine their own architecture and disclosures. In re Otter.ai Privacy Litigation, document 68.

Canada also has separate criminal and privacy questions. Criminal Code sections 183–184 define the protected communication and provide a consent exception involving its originator or intended recipient. For businesses, the Personal Information Protection and Electronic Documents Act (PIPEDA) or an applicable provincial law can impose additional purpose, notice and consent duties. PIPEDA's employee coverage is tied to federal works, undertakings and businesses; provincial regimes need separate attention. Criminal Code § 183; § 184; PIPEDA §§ 4–5 and Schedule 1.

The federal Privacy Commissioner's customer-call guidance, updated 8 October 2026, permits informed continuation to support implied consent in appropriate circumstances. The organisation must explain the recording and its purpose. Where recording is not integral to the product or service, the guidance requires an alternative unless a PIPEDA consent exception applies. Biometric voiceprints or other sensitive personal information may require express consent. An explanation limited to quality assurance cannot silently authorise every later use of the recording. These are privacy guidance conditions for the relevant regime, alongside the criminal analysis. OPC guidance on recording customer telephone calls.

Québec adds decisions that belong in procurement: a privacy impact assessment for relevant information-system projects and an assessment before communicating information outside Québec, including to another province. The service-provider arrangement has specific contractual conditions. British Columbia has a distinct reasonable-purpose and notice route for employee personal information. A single “Canadian consent” setting needs to account for these differences. Québec private-sector Act §§ 3.3,17,18.3; British Columbia PIPA §§ 13,16,19.

France, Germany and the UK have different communications rules

The EU GDPR supplies common rules on purposes, lawful bases, transparency, processors, sensitive data, security and rights. A controller can sometimes use a basis other than consent. It must still meet the elements of the selected basis and any additional Article 9 condition. Each country's communications law remains a separate part of the capture decision. GDPR Articles 5–6,9,13–14,28.

In France, Penal Code Article 226-1 addresses intentional interference with privacy through capturing, recording or transmitting private or confidential words without their speaker's consent. It contains a presumption where the act occurs openly with the person's knowledge and that person can object but does not. The presumption belongs to that criminal rule; a GDPR consent route has its own requirements. Article 226-2 also addresses retaining, disclosing or using material obtained through the unlawful act. A banner that a guest never sees provides a poor basis for claiming knowledge and opportunity to object. Code pénal Articles 226-1–226-2.

French workplace deployment requires prior employee information. Within the Labour Code's framework for enterprises with at least 50 employees, the social and economic committee (CSE) must be informed and consulted before the decision to introduce means capable of monitoring employee activity. Retention should follow the actual purpose and applicable duties; old call-recording guidance should not be turned into a universal period for every AI transcript. Code du travail L1222-4; L2312-38.

In Germany, StGB section 201 protects non-public speech against specified unauthorised recording and technical listening. The route for a stored sound recording differs from the architecture-specific question presented by a service that creates text without a retained sound recording. The Bavarian data-protection authority's 2025 activity report discusses circumstances in which live transcription can be assessed under legitimate interests. That supervisory analysis still requires necessity, expectations and the exact technical design; it supplies no permission for default recording of every meeting. StGB § 201; BayLDA 2025 activity report, transcription discussion.

German employee data rules and works-council codetermination can independently constrain deployment. If the tool can monitor conduct or performance, the customer must assess the relevant works-council right before rollout. Ordinary transcription should remain separate from staff scoring and reusable voice recognition. BDSG § 26; BetrVG § 87(1)(6).

In the United Kingdom, the business-interception regulations can permit specified monitoring and record-keeping on a business telecommunications system. The route requires the system controller's express consent, an enumerated purpose and all reasonable efforts to inform all potential users that interception may occur. The customer must establish that its proposed use meets those conditions; adding an independently operated training service needs its own analysis. Investigatory Powers Act § 44; SI 2018/356, regulations 3–4.

UK data-protection duties apply separately. Use the UK GDPR as amended when assessing a new purpose, worker assessment or foreign processing: the amended text includes Article 8A on compatibility and Articles 22A–22D on significant automated decisions. An older template referring only to the former Article 22 can miss the amended structure. The actual basis, safeguards and role allocation need to fit the selected processing. UK GDPR.

India and Singapore require different launch assumptions

India's Digital Personal Data Protection (DPDP) Act is phased. The official commencement instrument, as stated in the November 2026 announcement of the Ministry of Electronics and Information Technology (MeitY), schedules the principal processing duties for 13 May 2027. The one-year phase that began on 13 November 2026 does not put every substantive obligation into operation. A November 2026 deployment must assess the Information Technology Act (IT Act) and 2011 sensitive-data rules while preparing for the forthcoming DPDP requirements. G.S.R. 843(E); MeitY announcement of 14 November 2026.

The 2011 sensitive-data rules address collection, consent, purpose, disclosure, security and transfers. Their biometric definition includes voice patterns used for authentication. The Ministry's clarification distinguishes certain processing under a contract with a legal entity from direct collection under a natural person's contract. The customer and vendor therefore need to identify the actual relationship before assigning duties. Foreign activity involving a computer or network in India can also engage the IT Act's territorial provision. The Telecommunications Act 2023 separately criminalises unlawful interception of a message in section 42(2)(b), in force since 26 June 2024. Section 50 can reach overseas conduct involving a telecommunication service provided in India or equipment or a network located there. Identify the actual acquiring actor, audio-feed authority and locations before approving a participant-authorised bot. The statutory wording requires a lawful-acquisition analysis; it supplies no universal party-count label. Telecommunications Act, sections 42 and 50; official commencement announcement. SPDI Rules 2011, rules 2–8; Ministry clarification; IT Act §§ 43,43A,66,75.

Singapore's Personal Data Protection Act (PDPA) provides several conditional routes. Deemed consent by notification requires an assessment of adverse effects, mitigation, adequate notice and a reasonable opportunity to opt out. A banner shown as capture starts cannot be assumed to satisfy that process. Legitimate interests and specified employment purposes have different conditions; employment-related exceptions still carry relevant notice duties. PDPA §§ 15A,20; First Schedule, Part 3.

A vendor relying on business improvement must establish the First Schedule's actual necessity and reasonable-person conditions, including the restrictions governing related-company sharing. The research exception has its own public-benefit, decision-use and publication requirements. Neither term should become a general licence for an off-the-shelf assistant's training dataset. Singapore's Computer Misuse Act also makes knowing unauthorised interception a separate technical-authority issue. First Schedule, Part 5; Second Schedule, Part 2; Computer Misuse Act §§ 2,6,13.

United Arab Emirates (UAE) and Saudi Arabia: privacy, transfer and interception rules

For the UAE, identify whether the relevant processing is under the federal personal-data law, Dubai International Financial Centre (DIFC) law or Abu Dhabi Global Market (ADGM) regulations. The applicable establishment and processing connections decide that question. Financial free-zone incorporation leaves the application of federal criminal law to be examined. Federal Law 8/2004, Article 3.

The federal Crimes and Penalties Law addresses specified private-place or telephone listening, recording and transmission. Article 431 contains a qualified presumption for acts during a meeting within the attendees' hearing or sight. The federal cybercrime law separately addresses unlawful interception and specified invasions of privacy, including the relevant intent and consent conditions in Article 44. A customer should therefore establish visible, informed participation and the actual capture route before activation. Crimes and Penalties Law, Article 431; Cybercrime Law, Articles 12–13,44–45.

The federal personal-data law provides consent and listed exceptions, without a general GDPR-style legitimate-interest basis. DIFC and ADGM have their own bases, processor obligations, rights and transfer rules. Their special provisions for retaining data for lawful AI training are conditional retention rules; the initial training purpose still needs a valid basis and the other applicable protections. The federal law took effect on 2 January 2022. Federal PDPL, Articles 4–6,13,21–23,29,31; DIFC Law, Articles 6,10,22; ADGM Regulations, sections 3,5,31.

DIFC Regulation 10 also requires specific transparency for autonomous or semi-autonomous systems. Defined commercial high-risk uses carry additional audit/certification, human-approved-purpose and Autonomous Systems Officer requirements. The Commissioner’s approved framework and guidance updated 10 August 2026 provide the certification process; assess the regulation’s precise trigger before enabling that mode. In ADGM, section 34 requires a prior impact assessment where processing is likely to create high risk, and notification to the Commissioner before processing if that assessment indicates high risk. DIFC Regulations, 10.2.2 and 10.3.2–10.3.3; DIFC certification materials; ADGM section 34.

In Saudi Arabia, the Personal Data Protection Law (PDPL) can reach relevant processing of residents' personal data by entities outside the Kingdom. Consent has evidential and, for specified sensitive or automated-decision processing, express-consent requirements. The legitimate-interest route excludes sensitive personal data. Commercial voice identification and sensitive speech therefore need a more specific analysis than ordinary meeting notes. Saudi PDPL, Articles 2,5–6; Implementing Regulation, Articles 11,16,25.

Saudi Arabia's replacement international-transfer regulation was published in September 2024. The controller must match the purpose, destination and protection mechanism to the regulation's provisions. A standard contractual clauses (SCC) route requires the actual transfer to fit an applicable Article 4 case and satisfy its safeguards, data-type restrictions and Article 7 risk-assessment requirement. Separately, Anti-Cyber Crime Law Article 3(1) addresses interception, listening or reception of network/computer transmissions without a valid lawful justification. Establish that justification for the vendor’s actual acquisition and assess criminal jurisdiction for an offshore configuration. The PDPL’s residence rule answers a different territorial question. Anti-Cyber Crime Law, Article 3; official Arabic scan. Official Gazette, Decision 1840 and replacement transfer regulation.

South Africa and Kenya make the vendor's act consequential

South Africa's Regulation of Interception of Communications and Provision of Communication-Related Information Act (RICA) distinguishes an actual party's interception under section 4 from interception by another person under section 5. Section 5 can supply a route through prior written consent from one actual party, subject to its conditions. An absent administrator's tenant setting should not be treated as that participant act. Section 6 contains a separate conditional business-monitoring route. The vendor and host should document which route permits each acquisition. RICA §§ 4–6.

The Protection of Personal Information Act (POPIA) then governs personal-information processing, with several possible bases, purpose and notice requirements, and special-information rules. Its biometric provisions include conditions beyond a simple consent slogan. An operator must process within authority and meet the applicable written security arrangement. The customer should separate service notes, later CRM use and the vendor's own training purposes, and assess foreign processing under section 72. POPIA §§ 11,15,18,20–21,26–33,72.

Kenya's Data Protection Act can apply to a foreign controller or processor handling data of people located in Kenya. Section 37 adds an express-consent requirement for commercial use unless a written-law route applies with the required information. The General Regulations define commercial purposes broadly. A business relying on legitimate interests under section 30 must also address section 37 where engaged; the relationship between a paid instructed note-taking service and this provision needs analysis on the actual use. Data Protection Act §§ 4,29–32,37; General Regulations, regulation 14.

Sensitive data require the additional statutory condition, and section 49(1) combines consent and appropriate safeguards for processing sensitive personal data outside Kenya. A voiceprint feature or sensitive transcript sent to an overseas model provider can therefore change the required configuration. Temporary interception remains covered by the separate cybercrime provision. Sections 44–49; ODPC 2026 cross-border guidance; Cybercrimes Act § 17.

Brazil and Mexico distinguish participant access from subsequent processing

Brazil's Supreme Federal Court Tema 237 concerns the admissibility of a recording made by a participant without the other person's knowledge. The ruling's evidential setting must be preserved when assessing an enterprise bot. The customer's collection, dissemination and commercial reuse still need analysis under the General Data Protection Law (LGPD) and applicable personality protections. STF Tema 237; Civil Code Articles 20–21.

Under the LGPD, ordinary personal data can have an Article 7 basis, including a properly assessed legitimate interest. Sensitive data require an Article 11 condition. Biometric data linked to a natural person fall within the sensitive-data definition; text can independently reveal health or other sensitive facts. General-model training, worker evaluation and unrelated CRM profiling need an identified purpose and basis that fits the actual information. Article 20 gives a review right for specified solely automated decisions affecting interests. LGPD Articles 5–11,20.

Mexico's replacement private-sector data law took effect in March 2025. It permits tacit consent for ordinary personal data after the privacy notice is made available and the person does not oppose, unless express consent is required. Financial or patrimonial data generally require express consent. Sensitive data generally require express written or authenticated consent, subject to the statutory exceptions. An ordinary spoken agreement to notes may therefore be insufficient for a sensitive voice-identity use. LFPDPPP 2025, Articles 7–9.

Mexican Supreme Court authorities distinguish a participant's disclosure from outsider interference with communications, while preserving separate intimacy interests. The customer's personal-data duties remain part of the deployment decision. A new purpose differing from the privacy notice requires fresh consent under Article 11. As at 21 November 2026, the private-sector authority is the Secretaría Anticorrupción y Buen Gobierno; notices should reflect the replacement statute. SCJN, registry 159859 and 2013199; Articles 2,11,35–39.

Mexico's cloud rules also affect vendor selection. Articles 50–54 of the 2011 Regulations address instructed purposes, security, confidentiality, contractual evidence, subprocessing and conditions for standard-term cloud services. Those conditions include transparency about subprocessing, limits on processing, return and deletion, and avoiding terms that assume ownership of the information. A processor that independently changes the purpose can acquire controller responsibilities for that use. Regulations, Articles 50–54.

Australia requires a state-level capture decision; New Zealand adds specific biometric controls

Australia's federal interception law distinguishes acquisition while a communication passes over a telecommunications system from the receipt of that communication. Knowledge of the person making the communication matters under the statutory definition. The customer's and vendor's actual technical roles need to be established alongside state and territory surveillance laws. Telecommunications (Interception and Access) Act, §§ 5F–7.

The eight state and territory systems use different participant, consent, interest and dissemination rules. The following contrasts explain why an Australian default needs more than the host's location.

  • New South Wales. Capture question that changes the design: Section 7 distinguishes non-party listening/recording from a party's recording. “Party” can include an authorised listener; principal parties are the actual speakers/addressees. Consent and the specified lawful-interest or restricted-publication routes have different conditions. Separate downstream question: Section 11 regulates communication of unlawfully obtained material.
  • Victoria. Capture question that changes the design: Section 6 focuses on use of a listening device for a private conversation by a person who is not a party. Establish whether the vendor itself falls within the statutory party definition. Separate downstream question: Section 11 can restrict communication even after lawful recording.
  • Queensland. Capture question that changes the design: Section 43 contains a party exception; section 42 includes specified authorised listening in the party definition. Separate downstream question: Section 45 places separate conditions on communication or publication.
  • Western Australia, South Australia, Tasmania and the Australian Capital Territory. Capture question that changes the design: The statutes have different all-principal-party consent and qualified alternative routes. Test the actual lawful-interest, private-purpose or public-interest condition in the relevant statute. Separate downstream question: A permissible capture route can still leave restrictions on dissemination.
  • Northern Territory. Capture question that changes the design: Section 11 addresses non-party listening-device use; consent and statutory status matter. Separate downstream question: Section 15 separately regulates communication or publication, including reports of a conversation.

Sources: NSW §§ 4,7,11; Victoria §§ 3,6,11; Queensland §§ 42–45; WA §§ 5,9; SA §§ 4,6,9–12; Tasmania §§ 3,5,9–10; ACT §§ 4–6; NT §§ 11,15.

Where the federal Privacy Act applies, the Australian Privacy Principles (APPs) govern collection, notification, use, disclosure, security and rights. The employee-record and small-business exemptions have specific limits; an external vendor should establish its own coverage. The AI guidance of the Office of the Australian Information Commissioner (OAIC) recommends consent for meeting transcription where sensitive information may be collected unexpectedly. Australia's serious-invasion-of-privacy tort, operative since June 2025, has its own elements and can matter beyond APP coverage. Privacy Act, §§ 6C–6E,7B(3), Schedule 1 and Schedule 2; OAIC commercial-AI guidance; OAIC privacy-tort guidance.

New Zealand's Crimes Act contains an interception exception for a party to the private communication, including the defined authorised-recipient situations. The Privacy Act then applies purpose, fair-collection, notice, retention, use and disclosure principles. Since 1 May 2026, information privacy principle 3A (IPP3A) also addresses indirect collection, subject to its specified exceptions, and can require information as soon as reasonably practicable after collection. The customer's information process should therefore reach people whose data enters notes through someone else. Crimes Act §§ 216A–216B; Privacy Act, §§ 4,11,22; IPP3A.

The Biometric Processing Privacy Code began applying to new processing in November 2025 and its existing-processing transition ended on 3 August 2026. Necessity, effectiveness, less intrusive alternatives, safeguards and proportionality are central to its defined biometric processing. The code also restricts specified categorisation and inference purposes, subject to defined exceptions. Consent to meeting notes cannot by itself authorise every emotion, personality or health inference from a voice. Keep a meeting-local name label distinct from the actual biometric mechanism. Biometric Code, rules 1,3,3A,10 and commencement provisions.

Training, analytics and worker assessment require purpose-specific controls

The customer's service instructions should say what the assistant may produce, who may receive it and how long each form of data remains. A disclosed CRM update about the transaction discussed in the meeting can fit that purpose where the applicable basis and necessity conditions are satisfied. Sending a complete transcript into an unrelated enrichment database needs a separate assessment.

A vendor can act on the customer's behalf for notes and make its own decisions about another use. EU GDPR Article 28(10), Singapore's data-intermediary rules, Mexico's processor regulations and New Zealand's agency provisions each make actual use consequential. The contracts and privacy information should identify these separate roles. Verify actual data use against the instructions and identify every independent provider purpose. GDPR Article 28(10); PDPA §§ 2,4; Regulations Article 53; Privacy Act § 11.

Inspect quality review, benchmarking, abuse monitoring, feedback and product-improvement clauses as well as the clause called training. Identify whether humans inspect transcripts, another model provider retains prompts, speaker identities persist, or “anonymous” data can reasonably be linked back to participants. Each use needs to fit its claimed purpose and legal route. A feature switch must reach the relevant upstream provider and derived stores to implement the contractual promise.

Employee assessment adds employment and automated-decision conditions to the meeting purpose. Ordinary notes should not silently generate performance scores or send them to managers. Consent can be impaired by employment power. In the EU, the AI Act prohibits AI systems used to infer emotions in the workplace, subject to its medical or safety exception; the defined emotion-recognition function concerns inference from biometric data. Establish the actual function, data inputs and effect on the employee before enabling a voice-analysis feature. EU AI Act, Articles 3(39),5(1)(f),113; Regulation (EU) 2026/1744, Article 1(40). EDPB consent guidance on employment; German codetermination rule; LGPD Article 20; New Zealand biometric restrictions.

Foreign processing needs a mapped route

There is no single worldwide clause that authorises every overseas meeting-data flow. The customer must identify the exporter or collecting entity, recipient, actual role, access country and onward use before selecting the applicable mechanism.

The transfer regulation of Brazil's National Data Protection Authority (ANPD) distinguishes a transfer between processing agents from a foreign agent's direct collection from the data subject. Direct foreign collection can still fall within the LGPD's territorial scope. Mexico distinguishes a genuine controller-to-processor remission from a transfer to another controller. New Zealand similarly treats storage or processing solely on an agency's behalf differently from a recipient's own-purpose use. These distinctions make the architecture and role schedule part of the legal evidence. ANPD Resolution 19, Annex I Articles 3–9; Regulations Articles 4,53–54; New Zealand OPC overseas guidance; IPP12.

Other rules require additional conditions: Québec's assessment before communication outside the province; Kenya's combined consent and safeguards for sensitive offshore processing; Saudi Arabia's transfer rules; and the relevant EU, UK, DIFC or ADGM export mechanism. A provider's chosen hosting region should be checked against remote support, logging, onward models and backups. Québec § 17; Kenya § 49; Saudi replacement transfer regulation; GDPR Chapter V; UK GDPR Article 46.

Build the participant journey before enabling automatic capture

The customer supplies meeting-specific facts and the selected permission route. The vendor must make that route operable for every relevant participant. A guest should be able to understand the processing and exercise applicable rights without creating a vendor account.

  • Before the invitation. Customer or host action: Select purposes, locations, recipients, retention and the applicable capture/privacy route. Required system behaviour and evidence: Store the approved configuration; make notices accessible to guests.
  • Invitation and admission. Customer or host action: Explain who operates the assistant, what it captures, purposes, recipients, retention and available choices. Required system behaviour and evidence: Identify the bot and prevent acquisition before required notice and permission; record their version and timing.
  • Late arrival. Customer or host action: Give the entrant the material information and obtain any required permission. Required system behaviour and evidence: Pause or isolate acquisition before capturing that person's speech; preserve entry, response and resume events.
  • Refusal. Customer or host action: Apply the relevant right and selected legal route; offer an unrecorded meeting where consent is required and absent. Required system behaviour and evidence: Stop sound acquisition and hidden transcription; avoid forcing the guest to leave to stop optional capture.
  • New sensitive topic or purpose. Customer or host action: Reassess authority, basis and any special-data condition. Required system behaviour and evidence: Make pause accessible; keep CRM, training, voice identity and worker evaluation separately controlled.
  • Withdrawal. Customer or host action: Stop future consent-dependent processing and identify any specific lawful retention duty. Required system behaviour and evidence: Provide a working guest channel; apply the request to relevant recipients and stores under local law.
  • After the meeting. Customer or host action: Review important attributions, control distribution and honour retention and rights. Required system behaviour and evidence: Search, correct, export and delete relevant data; document backup treatment and genuine retention exceptions.

Keep a proportionate permission record: participant event, notice version, basis or consent route, response where required, and start, stop and resume times. Retaining the entire conversation solely to prove that recording was permitted can defeat the intended minimisation. Where a particular rule requires the announcement itself to be recorded, configure that evidence specifically.

Put the controls into the contract

The customer should obtain a data-use schedule that covers audio, text, summaries, tasks, CRM fields, logs, embeddings, feedback and voice templates. For each, identify the purpose, responsible entity, recipients, countries, retention and deletion behaviour. The vendor should state which uses it controls independently.

  • Roles and instructions. Term and implementation evidence to require: Separate instructed assistance from independent purposes; align customer, vendor and upstream-provider terms.
  • Secondary use. Term and implementation evidence to require: Identify permitted quality checks and prohibited or separately authorised training, benchmarking, profiling and identity uses.
  • Capture and permission. Term and implementation evidence to require: Allocate notices, meeting facts and required participant permissions; require functioning guest, late-entry, refusal and pause flows.
  • Confidentiality. Term and implementation evidence to require: Restrict access and onward disclosure; address the customer's client and professional obligations.
  • Subprocessors and foreign access. Term and implementation evidence to require: Name entities, roles and countries; provide the applicable authorisation, change and transfer processes.
  • Retention and deletion. Term and implementation evidence to require: Cover raw audio, text, derivatives, logs, templates and backups; state specific legal-hold exceptions and data return.
  • Rights and accuracy. Term and implementation evidence to require: Support access, correction, deletion, objection and withdrawal as applicable, including requests by non-users.
  • Security and incidents. Term and implementation evidence to require: Allocate safeguards, incident information and cooperation needed for each party's statutory duties.
  • Audit and changes. Term and implementation evidence to require: Supply evidence of data-use settings and deletion; require review when purposes, providers or locations change.

The schedule must match the product's actual behaviour. If a vendor cannot stop capture when required or cannot implement the agreed use restriction through its upstream model provider, the customer must choose another configuration or service. Mexico's cloud conditions and the applicable processor rules can make parts of this procurement exercise mandatory. Regulations Articles 50–54; GDPR Article 28.

For the wider supplier agreement, Licentium's AI supplier contracts service covers the agreement and data-use allocation. Data Protection & GDPR for AI addresses the associated privacy documentation and assessment work. The meeting-specific task is to connect those documents to the actual permission and processing flow.

Choose a deployment route

Internal meetings

Use a defined administrative purpose, an appropriate privacy basis, employee information and any required consultation before rollout. Keep recipients limited and disable general training, persistent voice identity and staff scoring. Establish the vendor's own capture route as well as the host's authority.

Change the configuration where consent would be coerced, the discussion contains sensitive information without the necessary condition, a works-council process is outstanding, or the chosen foreign route is unsupported. An unrecorded meeting can preserve participation while those issues are resolved. Human notes remain subject to applicable confidentiality and personal-data duties.

External sales and customer calls

Provide information that a non-account guest can use and obtain each required permission before capture. The common affirmative-permission configuration can simplify operation across several regimes, with local alternatives only after their statutory conditions have been established. Restrict CRM output to the disclosed transaction and authorised recipients.

Change the configuration when a late guest has not received the information, a required permission is refused, sensitive content calls for a different consent form, or a business-monitoring exception limits use to specified purposes. Keep an unrecorded customer route available where recording is optional or required permission is absent.

Meetings across conflicting locations

Establish actual participant and capture locations, organisations, subprocessors and purposes before activating the bot. Apply every law with a relevant connection. Common affirmative permission can satisfy several capture conditions, while employment, sensitive-data, forbidden-purpose and international-processing rules still require separate decisions.

If the product cannot satisfy the applicable conditions together, disable the conflicting feature or run the meeting without automated capture. Reassess when a new participant location, purpose, voice feature or access country is introduced. A worldwide tenant default should enforce this process rather than leave every host to reconstruct it during a call.

A recording can also contain confidential business information or legal advice. The consequences of uploading secrets are addressed in Employee use of AI and trade secrets; preservation and legal privilege are addressed in AI chat history discovery, privilege and preservation. Those issues should be considered when defining permitted meeting types and retention.

For a scoped assessment, assemble the vendor terms and settings, participant and processing locations, data-flow diagram, intended purposes, sample invitation and guest notice, retention schedule, and upstream-provider terms. Those documents allow the capture route, participant choices and contract commitments to be assessed against the same operation.

Planning a launch somewhere new?

Prefer email? Write to hello@licentium.io. By sending, you accept our privacy policy.