A call recording can be licensed for AI training only if it was lawfully recorded and the consent given covers that use. Federal law needs one party's consent, but several states need everyone's. A quality and training notice may not extend to licensing. Voiceprint and payment card rules add limits. General information, not legal advice.
This page is general information, not legal advice. Whether your company can license a given dataset depends on your contracts, your privacy notices and the law where you and your customers are. Review it with your own counsel before signing anything.
Two separate questions
Recorded calls are among the most requested kinds of company data. They show real conversations, real problems and how trained staff resolve them. They are also among the most regulated.
Two questions have to be answered separately. The first is whether each call was lawfully recorded. The second is whether the permission that made the recording lawful also covers handing the audio or transcript to a third party for model training. A yes to the first does not settle the second.
Employees are on every call too. The agent's voice, name and performance are in the recording, and the employee's position has to be considered alongside the caller's.
This guide is general information, not legal advice. Recording laws vary by state and country and are enforced through private lawsuits as well as by regulators. Verify the current law in every state where your callers are located, with counsel.
The federal one-party rule
The federal Wiretap Act, at 18 U.S.C. 2511, generally prohibits intercepting telephone and electronic communications. It contains an exception where one of the parties to the communication has given prior consent, provided the interception is not for the purpose of committing a crime or a tort.
A company that records its own calls is a party, so its consent satisfies federal law. Most states follow the same one-party approach. Federal law is a floor, though. States may require more, and several do.
The federal statute covers the contents of a communication, and it applies to interception while the call is in progress. Stored recordings raise different questions, mainly under privacy and contract law. The exception also has a limit that matters for vendors. The consenting person must be a party to the communication. Whether a company that supplies recording or analytics software counts as a party, or as an outsider listening in, has been argued both ways.
All-party consent states
A minority of states require the consent of every party to a call, at least where the conversation is confidential or private. The states below are commonly cited as all-party consent states. The list is not complete, statutes differ in what they cover, and laws change. Treat it as a prompt to check, not as a reference.
Interstate calls are the trap. A caller's location decides which law they can invoke, and a business often cannot tell where a mobile caller is. California's Supreme Court has applied California's rule to an out-of-state business that recorded calls with California residents. Most national call centers therefore announce recording on every call and treat the announcement, followed by the caller staying on the line, as consent.
Penalties vary. Some states make unlawful recording a crime, and several, including California, allow the recorded person to sue for statutory damages for each violation without proving harm. Class actions built on those provisions are the main source of exposure for a business with a large call archive.
- California
- Florida
- Illinois
- Maryland
- Massachusetts
- Pennsylvania
- Washington
Why a quality and training notice may not cover licensing
The familiar announcement says the call may be recorded for quality and training purposes. It was written to cover supervisors reviewing calls and coaching staff. A caller who hears it would not obviously understand that the recording could be supplied to another company to train AI models.
Whether the announcement stretches that far is uncertain, and no single rule answers it. The argument against is that consent is read by what a reasonable person would have understood. The risk is higher in all-party states, where consent is the whole basis for the recording. Some recent lawsuits under California's privacy statutes have also argued that a technology vendor able to use call content for its own purposes is a third party to the call, not a tool of the business.
Privacy law adds a second layer. Recordings hold names, account details and sometimes health or financial facts. The notices and contract terms that govern that personal information apply to audio and transcripts exactly as they do to text records.
Outbound and callback calls are a common gap. A recording announcement plays on the inbound line, but when an agent calls a customer back from a desk phone the notice is often missing. Calls transferred between departments and calls that began with an automated system can have the same problem. An archive that looks covered at the level of policy may hold many individual calls that are not.
Voiceprints and biometric privacy laws
A voice can identify a person. The Illinois Biometric Information Privacy Act lists a voiceprint as a biometric identifier. It requires informed written release before a private entity collects one, bars selling, leasing, trading or otherwise profiting from a person's biometric identifier, and gives individuals a private right to sue. Texas and Washington also have biometric statutes, enforced differently.
An ordinary recording is not automatically a voiceprint. The concern arises when a voice is analyzed to produce an identifying template, or when raw audio is supplied to a party that could do so. Sellers reduce the exposure by licensing transcripts in place of audio where the buyer's purpose allows it, by restricting voice identification and voice cloning in the license, and by excluding calls where a voice was used for authentication.
Voice is also personal information under general privacy laws. California's statute lists biometric information among its categories, including voice recordings from which an identifier template can be extracted. In Europe, a recording of an identifiable speaker is personal data whether or not any template is made.
Payment card data in audio
Callers read card numbers aloud. The Payment Card Industry Data Security Standard, known as PCI DSS, is a contractual standard imposed through the card brands, not a statute. It bars storing sensitive authentication data, such as the card verification code, after authorization, and that includes audio recordings. Full card numbers that are stored must be protected.
Many contact centers pause recording or mask keypad tones during payment. Those controls sometimes fail, and older archives may predate them. Any recording set that includes payment calls needs a check for spoken card details before it goes anywhere.
Card numbers are not the only spoken data to look for. Callers confirm identity by reading out dates of birth, account numbers, security answers and the last digits of government identifiers. These sit in the audio and in any transcript made from it, and they are personal information even where PCI DSS does not apply.
The issues side by side
The table lists the main issues, the rule behind each and the usual control. More than one will apply to most archives.
| Issue | Where the rule comes from | Usual control |
|---|---|---|
| Lawful recording | Federal Wiretap Act and state recording statutes | Recording announcement on every call, with scripts and dates kept |
| Scope of consent | Consent as the caller would have understood it | Updated announcement going forward; counsel's view on older calls |
| Personal information | State and foreign privacy laws, privacy notices | Redaction of names, numbers and account details in audio and transcript |
| Voiceprints | Illinois BIPA and similar state laws | Transcripts in place of audio, or license limits on voice identification |
| Card data | PCI DSS, by contract | Exclude or redact payment segments; scan for spoken numbers |
| Client ownership | Outsourcing and service contracts | Exclude calls handled on behalf of clients unless the client agrees |
Practical steps
A company with a call archive can work through the following before treating it as licensable. Outrich Data checks recording notices and call ownership as part of its data title search, and calls a company took on behalf of its clients are treated as the clients' data.
- Collect every version of the recording announcement and the dates each was in use.
- Identify which lines, queues and call directions had no announcement, such as outbound calls and transferred calls.
- Work out where callers were located, as far as records allow, and flag all-party states.
- Separate calls handled for clients from calls about your own business.
- Remove payment segments and scan the rest for spoken card numbers.
- Decide between audio and transcripts, and redact personal details in whichever is delivered.
- Ask counsel whether older calls are covered, and change the announcement for future calls if licensing is planned.
Common questions
Is it legal to sell call recordings for AI training?
Does a recording announcement count as consent?
Are transcripts safer to license than audio?
What about calls with people outside the United States?
Sources