Sometimes. A company can license recordings that were made lawfully, where everyone recorded was told how the recording could be used, and where no customer contract forbids it. Federal law allows recording with one party's consent, but California, Washington, Florida and other states require all parties to agree. Consent to be recorded is not consent to have the recording licensed. Internal meetings are easier to clear than customer calls.
- Consent to record and consent to reuse are two different things. Buyers ask for the second.
- On a multi-state call, the strictest state's rule is the safe one to follow.
- Internal meetings turn on employee notice. Customer calls turn on the customer contract.
- A voice identifies a person. Removing names from a transcript does not clear the audio.
Can a company license recorded Zoom meetings and sales calls?
Sometimes. Three things have to be true: the recording was lawful when it was made, the people on it were told about reuse or agree to it now, and no contract with a customer or a tool vendor forbids it. Many archives fail the second test.
A public listing for call centers and voice businesses (one buyer's public listing, read 15 November 2026) asks for "consented recordings of real conversations" and names "meeting and podcast platforms" among its industries. Its requirements are "Recorded calls with consent that covers reuse", "1,000+ hours of recordings" and "Each speaker on a separate channel". It lists "Recordings made without consent" as not a fit.
No public listing read that day names a company's internal meeting recordings as its own category. The published demand is for conversational audio with consent that covers reuse, and a meeting archive either meets that description or does not.
Internal meetings versus customer calls
The two look alike in a recordings folder and are cleared in different ways.
| Question | Internal meetings | Customer and sales calls |
|---|---|---|
| Who is on the recording | Employees and sometimes contractors | Employees and people outside the company |
| What decides reuse | Employment terms, monitoring notices and privacy law | The above, plus the customer contract and what the customer was told |
| Typical consent on file | A policy that says meetings may be recorded | A banner or an announcement that the call is recorded |
| Gap to close | Notice that recordings may be licensed outside the company | The customer's agreement to reuse, call by call or by contract |
| Sensitive content | Personnel matters, legal advice, strategy | Customer confidential information, prices, personal data |
| Usual result | Clearable with new notice and an opt-out, for selected meeting types | Excluded unless the contract and consent cover reuse |
Contact-center recordings are covered in the call recordings guide. Written archives are covered in the Slack and email archives guide.
Do all participants have to consent to the recording?
In some states, yes. Federal law and most states allow a recording when one party to the conversation consents. California, Washington, Florida and several other states require every party to agree. Where callers are in different states, following the strictest rule is the safe course.
The federal statute says it "shall not be unlawful under this chapter for a person not acting under color of law to intercept a wire, oral, or electronic communication where such person is a party to the communication or where one of the parties to the communication has given prior consent" (18 U.S.C. 2511).
State law can be stricter. California penalizes a person who records "intentionally and without the consent of all parties to a confidential communication" (Penal Code 632). Washington makes it unlawful to record a private communication "without first obtaining the consent of all the participants in the communication" (RCW 9.73.030). Florida makes interception lawful "when all of the parties to the communication have given prior consent" (Florida Statutes 934.03).
These statutes are about making the recording. They do not say the recording may then be licensed. That needs its own basis: a notice that said so, a contract term or a fresh consent. This page is general information, not legal advice.
Do employees have to be told?
Yes, in practice. Some states require written notice of monitoring by statute, privacy laws require people to be told what their data is used for, and a recording licensed without notice is the kind a buyer turns down.
New York requires that an employer who monitors "telephone conversations or transmissions, electronic mail or transmissions, or internet access or usage" must "give prior written notice upon hiring to all employees who are subject to electronic monitoring" (Civil Rights Law 52-c). Delaware bars an employer from monitoring "any telephone conversation or transmission, electronic mail or transmission, or Internet access or usage" of an employee unless it gives daily electronic notice or a one-time written notice (19 Del. C. 705).
Voices are personal data. California's privacy law counts as biometric information "voice recordings, from which an identifier template, such as a faceprint, a minutiae template, or a voiceprint, can be extracted" (Civil Code 1798.140). EU law defines biometric data as data from technical processing of a person's characteristics that "allow or confirm the unique identification of that natural person" (GDPR). Staff in the EU and UK need a lawful basis and clear information before their recordings go anywhere.
A notice that covers licensing says three things: recordings of named meeting types may be shared outside the company for developing AI systems, what is removed first, and how to opt out. The guide to employee screen recordings covers notice and consent in more depth.
Does the recording tool's vendor claim rights in the recordings?
Usually not ownership. The large meeting and call-recording tools treat recordings as the customer's content and take a licence to run the service. Read the current terms for two points: what the vendor may do with your recordings, and whether you can export them in bulk.
Zoom's terms define Customer Content to include content you provide "together with any resulting transcripts, recordings, outputs, visual displays, or other content", and state: "Zoom does not use any of your audio, video, chat, screen sharing, attachments or other communications-like Customer Content (such as poll results, whiteboard and reactions) to train Zoom or third-party artificial intelligence models" (Zoom Terms of Service).
Gong's trust page answers the same question for its product: "Is customer data used to train generative AI? No. Your data is never used to train generative AI models, and it's never shared with or exposed to the public domain" (Gong Trust Center).
Those statements are about what the vendor does. They do not stop you licensing your own recordings, and they do not clear the rights of the people on them. Check the export limits of your plan before promising a volume.
Are transcripts enough without the audio?
For some uses. Transcripts serve models that learn from text, such as how a negotiation or a support call unfolds. Models that learn speech need the audio, and the published demand is mostly for audio.
The listing describes its deliverables as "Call audio by channel" and "Transcripts and call metadata", and lists "Transcripts" as nice to have, not as a substitute. It says "The most useful calls have each speaker on a separate channel", which a mixed meeting recording does not give.
Transcripts are easier to clear. Names, companies and numbers can be removed from text. A voice cannot be removed from audio without changing the audio. If consent is the obstacle, a transcript-only set of internal meetings may be the part that can be offered.
Checklist: removing names, voices and deal terms
Clean the transcript and the audio together, so that a name bleeped in one is also gone from the other.
- Meetings to exclude outright: legal advice, personnel and disciplinary matters, board sessions, health or family topics.
- Speaker labels: replace names with roles, such as Account executive or Buyer.
- Spoken names of people and companies: remove from the transcript and mute in the audio.
- Customer confidential information: prices, volumes, roadmaps, contract terms.
- Screen shares in video: documents, email inboxes and chat panels shown on screen.
- Participant lists, email addresses and calendar titles in the metadata.
- Chat messages and files attached to the meeting.
- Anyone who opted out: remove their channel, or drop the recording if speakers are mixed.
- Voices: decide whether audio is delivered at all, and only for people whose consent covers it.
Where the recordings sit in Google Meet or Drive, the Google Workspace export guide covers getting them out.
Example: a sales call with its outcome labels
A fictional software company prepares one discovery call. The customer contract allowed reuse of de-identified call data, and both sales staff had agreed in writing.
| Field | Value | Source |
|---|---|---|
| Call type | Discovery, first meeting | Calendar and CRM |
| Speakers | Account executive, Sales engineer, Buyer 1, Buyer 2 | Recording tool, names replaced with roles |
| Deal stage before and after | Qualified to Technical evaluation | CRM history |
| Objections raised | Security review, price per seat | Tagged by the sales manager |
| Next step agreed | Security questionnaire by Friday | Call notes |
| Outcome | Closed won, 74 days later | CRM |
| Deal size | Band C | CRM, exact value removed |
Fictional example. The outcome fields come from the CRM, not the recording. A call tied to whether the deal closed is worth more than the same call alone, which is why outcome labels are the first thing to add.
Common mistakes with meeting recordings
Most of them confuse permission to record with permission to reuse.
- Treating the "this meeting is being recorded" banner as consent to license.
- Applying the one-party rule to a call with someone in an all-party state.
- Including customer calls without reading the customer contract.
- Removing names from transcripts and delivering the audio untouched.
- Forgetting what was shared on screen.
- Counting hours before checking how many have separate speaker channels.
- Letting the recording tool's retention setting delete the archive before it is exported.
Meeting and call recordings as a data asset
One published company range applies to recorded conversations (one buyer's public listings, read 15 November 2026). The listing for call centers and voice businesses runs from $20,000 to $250,000 and says the figure "Depends on hours and languages". Read it as a published ceiling for consented, channel-separated call audio, not a typical outcome for a meeting archive.
For most companies the realistic first step is narrow: pick one meeting type, give notice, collect opt-outs and prepare a small sample with outcome labels. There is no standard timetable. The order is usually the same: a written description of the archive, a small sample, a rights review, agreed terms, then delivery. The rights review sets the pace. Recordings in more than one language are covered in the multilingual call recordings guide. Origin Data Partners is an independent data partner that helps companies get their data bought. A buyer may pay Origin when a deal closes.
Does your company hold records like these? See what your data is worth.
Common questions
Can we license recorded Zoom meetings to AI companies?
Only where the recording was lawful, the participants were told about reuse or agree to it, and no contract forbids it. One public listing read on 15 November 2026 asks for recorded conversations with consent that covers reuse.
Do all meeting participants have to consent before recordings are licensed?
Recording law varies: federal law needs one party's consent, while California, Washington and Florida need all parties. Licensing needs more than recording consent. Each person should have been told the recording could be shared, or agree now.
Does Zoom or Gong claim rights to our call recordings?
Their published terms treat recordings as customer content. Zoom's terms say it does not use customer audio, video or chat to train AI models, and Gong's trust page says customer data is never used to train generative AI. Check your plan's export limits.
Are meeting transcripts enough without the audio?
For text models, often yes, and transcripts are easier to de-identify. Speech models need audio, and one public listing asks for call audio with each speaker on a separate channel, with transcripts as a nice-to-have.
Are customer calls excluded from a recording licence?
Usually, unless the customer contract and the consent given on the call cover reuse. Customer calls carry the customer's confidential information and the personal data of people outside your company, so most companies start with internal meetings.
Who owns sales call recordings: the company or the rep?
The company, in most cases, as a business record made on its systems. Ownership does not settle reuse. The rep's voice is personal data, and the customer on the call has rights under recording-consent law and the contract.
Sources and further reading
- 18 U.S.C. 2511: interception and disclosure of wire, oral, or electronic communications
- California Penal Code section 632: recording confidential communications
- Revised Code of Washington 9.73.030: recording private communication, consent required
- Florida Statutes 934.03: interception and disclosure of communications
- New York Civil Rights Law section 52-c: employers engaged in electronic monitoring; prior notice required
- Delaware Code title 19, section 705: notice of monitoring of telephone transmissions, electronic mail and Internet usage
- California Civil Code section 1798.140: definitions (biometric information)
- Regulation (EU) 2016/679 (GDPR), Article 4
- Zoom: Terms of Service, section 10 (data usage, licenses and responsibilities)
- Gong: Trust Center
