AI uses for records
Recorded meetings in all-party consent states: can they be licensed?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Recorded meetings from all-party consent states can sometimes be licensed, but consent to record is not consent to reuse. Check what participants were told when recording started, where they were, and whether a buyer needs audio at all. The cautious path is often de-identified transcripts, with audio and unclear recordings left out.
Key takeaways
- Recording consent laws govern capturing a conversation; licensing raises a separate question about reuse.
- A notice about quality and training purposes was written with staff coaching in mind and may not clearly cover AI training by an outside developer.
- When participants sat in different states, many legal teams apply the stricter rule to the whole recording.
- Voice audio carries identity even after names are removed, so audio sets a higher bar than transcripts.
- Excluding a recording source is a legitimate outcome of review, not a failure.
- Keep dated copies of every call greeting and meeting banner, because the notice version often decides which recordings can be considered.
What do all-party consent laws cover?#
All-party consent laws, also called two-party consent laws, generally require everyone in a private conversation to agree before it is recorded. Federal law and most states follow a one-party rule, under which one participant's consent is enough, while a minority of states require every participant's consent. The details differ on what counts as consent, whether a notice at the start of a call is enough, and which conversations count as private.
These statutes focus on the act of recording or intercepting. They say less about what happens to a lawful recording afterward, which is shaped by the notice given, privacy laws, contracts with customers and employees, and in some cases provisions in the same statutes on using or disclosing recordings. A recording made lawfully can still be one the company should not license.
Reuse is also where litigation has moved. Recent class actions, many brought under California's Invasion of Privacy Act, have tested whether a vendor whose AI records, transcribes or analyzes calls for a business, and may use them to improve its own models, counts as an unauthorized third party listening in. Outcomes are still developing, but they show that AI uses of recordings draw scrutiny of their own.
The rules change and are interpreted by courts, so the list of states and the details belong in a current review by counsel, not in a static chart.
How does consent to record differ from consent to reuse?#
Consent to record and consent to reuse are different questions, and each relies on different evidence. The table separates them.
The phrase "for quality and training purposes" deserves particular care. It was written when training meant coaching staff. Whether it reaches licensing recordings to an outside AI developer is a question for counsel, and many companies treat it as insufficient on its own.
| Question | Consent at recording | Consent for licensing or reuse |
|---|---|---|
| What it covers | Capturing the conversation at the time | Later uses such as analysis, sharing or AI training |
| Typical evidence | Beep tone, platform banner, spoken notice, calendar invite text | Privacy notice, contract clause, separate written consent |
| Who gives it | Each participant, depending on state rules | Participants, and sometimes their employers under confidentiality terms |
| Common wording | This call may be recorded for quality and training purposes | Rarely addressed in older notices |
| Weak points | Participants who joined late or by phone without hearing a notice | Notices that never mention third parties or AI |
Which participants and locations matter?#
The participants who matter are everyone whose voice or words appear, and where they were when the recording was made can matter as much as where the company sits. Remote meetings complicate this: a customer in one state, a project manager in another and a contractor dialing in from a third.
Many legal teams take a conservative approach and apply the stricter rule when locations are mixed or unknown. Location evidence is often thin: phone systems log a caller's number rather than where the caller was, and area codes are weak evidence because mobile numbers move with people. Separate recordings by participant type before deciding anything: internal meetings among employees, calls with customers, calls with prospects, and calls with vendors or candidates each come with different notices and expectations.
Employee-only meetings are often the most workable, because handbooks, recording policies and platform settings can show what staff were told. Customer calls bring in customer contracts and, in some industries, sector privacy rules.
Why is voice a separate issue from words?#
Voice is a separate issue because audio carries identity even after names are removed from a transcript. A voice can be recognizable, and voice data used to identify a person may fall under biometric privacy laws such as Illinois's Biometric Information Privacy Act (BIPA), which lists voiceprints among biometric identifiers, as well as state privacy laws that treat biometric data as sensitive.
The potential exposure under BIPA is significant. The statute allows liquidated damages of $1,000 per negligent violation and $5,000 per intentional or reckless violation, and an amendment signed on August 2, 2024 limited repeated collection of the same identifier by the same method to a single violation per person.
Because of that exposure, a buyer asking for audio raises the bar considerably. Transcripts with names, companies and other identifying details removed are a different and usually more manageable package. Some buyers need audio for speech models; others need only the language of real business conversations.
Transcription quality and content are part of the same decision. Automated transcripts can mishear names and numbers, which affects both redaction and usefulness. Customer calls can also capture payment card numbers, account numbers and addresses read aloud; some phone systems pause recording during payments, but not every system did. A sample review of transcripts from each source belongs in preparation.
What are your options for licensing recorded meetings?#
The options for licensing recorded meetings run from full exclusion to audio with fresh consent, and most companies land somewhere in between.
| Option | What is delivered | Fits when | Trade-off |
|---|---|---|---|
| Exclude | Nothing from that recording source | Notices were unclear or participants were mostly outside parties | No value from the source, no residual risk |
| De-identified transcript | Text with names, companies and identifiers removed | The recording was lawful and reuse fits notices and contracts | Loses audio and some context |
| Internal meetings only | Transcripts of employee-only meetings | Employee notices and policies cover recording and use | Narrower scope, often cleaner |
| Role-labeled transcript | Text with speakers marked by role, such as customer or engineer | The buyer needs conversational structure | Free text still needs careful review |
| Audio with new consent | Original or processed audio | Participants give specific written consent | Slow and often impractical at scale |
What belongs on a pre-licensing checklist for recorded meetings?#
A pre-licensing checklist keeps the review factual and repeatable across recording sources. Work through it before any recording or transcript leaves the company.
Keep the checklist output with the inventory rather than in an email thread. When a buyer, an auditor or a participant later asks how a recording was handled, the dated decision for its source is the answer.
- List every recording source: video meeting platforms, phone systems, conversation intelligence tools and AI notetakers.
- Collect the notice scripts, call greetings, banners and invite text used by each source, with the dates each version applied.
- Classify recordings by participant type and, where known, participant location.
- Check customer, vendor and employee contracts for confidentiality and recording clauses.
- Read the recording platform's terms for export rights and the vendor's own uses.
- Decide per source: exclude, transcript only, or audio with fresh consent.
- Document each decision and the reasons, so the position can be shown later.
Illustrative: an HVAC company reviews its recorded calls#
Illustrative: a fictional HVAC and plumbing company operates in a state that requires all-party consent. Its call center records every inbound call behind a greeting that says calls may be recorded for quality and training purposes, and dispatchers and estimators record a weekly scheduling meeting in Microsoft Teams.
A model developer building voice agents for home services asks to license call audio. The general counsel pulls every version of the greeting and finds one change: a newer greeting, adopted with counsel's help, says recordings may be used to develop AI tools, including by outside developers. Calls before that date relied only on the older wording, and the phone system logs callers' numbers, not their locations.
Counsel concludes that, for this company, audio is out of scope, because voices are identifiable and no caller gave specific consent to outside AI use. Transcripts of calls made after the greeting changed move to de-identification, with names, addresses and any card numbers read aloud removed. Earlier calls are excluded. The Teams meetings stay internal for now, because the recording policy that staff signed never mentioned outside use.
How SourceX approaches recorded meetings#
SourceX reviews recording consent source by source in the Rights step of the SourceX five-step transaction and treats exclusion as a normal result. Applicable laws are assessed deal by deal with the supplier's counsel.
In the Preparation step, personal and confidential details are removed from transcripts, and audio is handled only where consent supports it. The privacy record in the SourceX Evidence Packet documents which sources and notice versions were included, which were excluded and why, and the supplier approves the release.
Frequently asked questions
Can we get consent for AI use after a meeting was recorded?
Sometimes, but it is hard at scale. Retroactive consent means reaching every participant, explaining the new use clearly and recording each answer. It is more practical for a small set of internal meetings than for years of customer calls, and silence should not be treated as agreement.
Does de-identifying a transcript solve the consent problem?
Not by itself. De-identification reduces privacy risk in what is shared, but it does not cure a recording that was not lawfully made, and it may not satisfy contractual confidentiality. It works best for recordings that were lawful and whose reuse fits the notices and contracts.
Are recordings made by AI notetakers treated differently?
The same recording rules apply, but notetakers add questions: whether the bot announced itself, whether every participant saw that notice, and what the notetaker vendor's terms allow. Notetakers that join automatically from calendars can record meetings where nobody gave a clear notice.
What if we cannot tell where participants were located?
Unknown locations are common with remote meetings. Many teams treat unknown as the stricter rule and decide on that basis, or limit scope to recordings whose participants can be placed. Write down the approach you take so it can be explained later.
Do one-party consent states remove the issue entirely?
No. Even where one participant's consent is enough to record, reuse still depends on notices, privacy laws, contracts and confidentiality duties. One-party consent speaks to whether the recording was lawful, not to whether licensing it is appropriate.
Should we change our recording notices now?
Many companies update call greetings, meeting banners and privacy notices to describe AI uses, including sharing with outside developers, so future recordings have a clearer basis. A new notice works going forward and does not reach back to recordings made under the old wording, so keep dated copies of every version and have counsel review the new text.
Sources
- BIPA (740 ILCS 14/20) allows liquidated damages of $1,000 per negligent violation or $5,000 per intentional or reckless violation; Illinois SB 2979, signed August 2, 2024, limits recovery to a single violation per person when the same biometric identifier is collected repeatedly by the same method. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.