Buyers ask for calls, meetings, chat and product logs, and the liability for an unlawful recording follows the contents to whoever discloses or uses them knowingly, which makes this the communications layer of AI training data licensing.
The statute text is cited as in force on govinfo, checked 2026-11-09, and court status is stated as of 2026-11-17; state recording rules and employee rules have their own pages.
Two Titles of ECPA and the Party Each Binds in a Data Sale
The two ECPA titles that matter for a data sale bind different parties: Title I binds whoever intercepts a communication and whoever later discloses or uses it, and Title II binds the provider that stores it for the public. The table lists the five provisions this page relies on, as of 2026-11-09.
| Title | Provision | What it says for a data sale | Binds | Status | Source |
|---|---|---|---|---|---|
| I (Wiretap Act) | 18 U.S.C. 2511(2)(d) | interception is lawful for a party or with one party's prior consent, unless for a criminal or tortious purpose | whoever records | in force | govinfo.gov |
| I | 18 U.S.C. 2511(1)(c)-(d) | intentionally disclosing or using contents known to come from an unlawful interception is a violation | seller who discloses, buyer who uses knowingly | in force | govinfo.gov |
| I | 18 U.S.C. 2511(4)(a) | fine, imprisonment up to 5 years, or both | violator | in force | govinfo.gov |
| II (Stored Communications Act) | 18 U.S.C. 2702 | providers of communication or remote computing services to the public may not divulge stored contents without lawful consent | provider to the public | in force | govinfo.gov |
| II | 18 U.S.C. 2702(b)(3) | exception: lawful consent of the originator, an addressee or intended recipient, or the subscriber for remote computing | provider to the public | in force | govinfo.gov |
One archive can raise both titles, for example a support platform that records calls (Title I) and stores customer chats (Title II).
Wiretap Act: Interception, the One-Party Exception and the Purpose Test
Federal law makes an interception lawful when the person intercepting is a party to the communication or one party has given prior consent, unless the interception is for the purpose of committing a criminal or tortious act (18 U.S.C. 2511(2)(d)).
For a seller, a company that took part in its own calls can be the consenting party at recording time, but the purpose test stays live.
Plaintiffs in the Otter case plead AI training as that purpose, which is an allegation, not a ruling, and no record here decides whether training use defeats the exception. One-party consent at recording therefore does not by itself settle a later sale.
Onward Disclosure and Use: Why Licensing Cannot Cure an Unlawful Interception
Disclosing or using the contents of a communication while knowing it was obtained through an unlawful interception is itself a violation (18 U.S.C. 2511(1)(c)-(d)), punishable by a fine or imprisonment up to five years (2511(4)(a)).
The liability travels with the recording to the seller who discloses it and to a buyer who uses it knowingly, so a license cannot repair a failed recording, and the same point shapes what buyers ask of call recordings licensed for AI training.
Buyers write the consent requirement into their own listings, each a claim by the buyer checked 2026-11-09:
- Mercor states that its Call Center or BPO listing asks for "Recorded calls with consent that covers reuse" and lists "Recordings made without consent" as not a fit.
- Mercor states that its Digital Health Company listing asks for recorded patient-clinician visits "with consent that covers secondary use" and lists "Recordings made without consent" as not a fit.
The buyer's requirement moves the consent proof to the seller before scoping begins.
All-Party States Above the Federal Floor
The federal rule is a floor: California requires the consent of all parties to record a confidential communication (Cal. Penal Code 632(a)), and other states set their own rules, which a multi-state archive meets at the strictest one. The state-by-state comparison has its own page on all-party recording consent rules by jurisdiction.
Stored Communications Act: Providers to the Public Versus a Company's Own Systems
Under 18 U.S.C. 2702, a provider of a communication or remote computing service to the public may not divulge the contents it stores, such as users' messages offered for AI training, without lawful consent, while a company's internal systems are generally not services to the public (in force). The table sets three holder types side by side as of 2026-11-17.
| Holder | Example data | Which ECPA question comes first | What the record shows | Source |
|---|---|---|---|---|
| company licensing its own internal systems | staff mail, chat, tickets (Mercor Game Studio listing asks for studio-owned chat, checked 2026-11-09) | recordings: 2511; stored messages: internal systems generally not services to the public | employee rules decide the rest | govinfo.gov; Mercor listing |
| provider of a service to the public | users' messages, product session logs (Mercor AI Product Company listing asks for user terms allowing licensing or a way to get consent, checked 2026-11-09) | 2702: lawful consent of originator, addressee, recipient or subscriber | consent route 2702(b)(3) | govinfo.gov; Mercor listing |
| vendor recording or processing a client's calls | contact-center calls, meeting notes | 2511(2)(d) purpose test; state rules | ECPA claim proceeds in Otter (ECF 68); consent through the client's privacy statement under CIPA in the Google contact-center case (Dkt. 141) | govinfo.gov court orders |
A company licensing its own staff mail or chat is therefore generally outside 2702, and the questions shift to employee notice, consent and state or foreign employee rules.
Mercor states that its Game Studio listing asks for "Company records the studio owns: chat, tickets, code and shared drives" (checked 2026-11-09), and such records meet employee data rules for AI training by jurisdiction next, not a free pass.
Lawful Consent Under 2702(b)(3) and What Buyers' Listings Require
Section 2702(b)(3) lets a provider divulge stored contents with the lawful consent of the originator, an addressee or intended recipient, or, for a remote computing service, the subscriber.
The consent belongs to a sender, recipient or subscriber, not to the provider alone. Mercor states, checked 2026-11-09, that its AI Product Company listing:
- asks for "User terms that allow licensing de-identified usage data, or a way to get consent";
- lists "Logs that can't be stripped of personal information" as not a fit.
Whether de-identified or aggregated content leaves 2702, and how a terms-of-service clause counts as lawful consent, are not settled in the record used here. A platform licensing what its users posted or sent meets this rule first, as described for platforms licensing user content to AI.
Provider Terms That Sit Beside the Statute
Communications providers also restrict training by contract, which binds their customers regardless of how the statute applies.
Zoom's Terms of Service s.10.2 say Zoom does not use audio, video, chat or other communications-like Customer Content to train Zoom or third-party AI models (page effective date 2023-08-11, checked 2026-11-09).
Slack's API Terms (effective 2025-10-10, re-read 2026-11-17) say apps distributed outside the organization may not use API Data to train a large language model nor bulk export message data except under an additional agreement.
A customer's own export for its own licensing is a separate question handled on the system pages, and neither clause is an ECPA requirement.
Court Records on ECPA Claims and AI Training
One federal court has let an ECPA claim tied to AI training proceed past a motion to dismiss: in In re Otter.AI Privacy Litigation (N.D. Cal. 5:25-cv-06911-EKL) the order of 2026-08-13 (ECF 68) kept the ECPA claim (Count 1) alive, as of 2026-11-17. The same order is covered in full in the Otter.AI privacy litigation over meeting recordings.
The plaintiffs allege that meetings were recorded without all-party consent and that conversations and voiceprints were used to train speech-recognition and machine-learning models, which is an allegation.
CIPA 631, BIPA, unjust enrichment, UCL and declaratory relief claims also proceed, while the CFAA, CDAFA and Washington Privacy Act claims were dismissed with leave to amend. Nothing is decided on the merits.
The Google Cloud Contact Center AI case (N.D. Cal. 3:23-cv-05437-RFL) is a California CIPA case, not an ECPA case.
Dkt. 141 of 2026-10-22 held that two accountholders consented through the client's privacy statement and that training use alone is not a 631(a)(3) claim without a predicate violation, with leave to amend by 2026-11-12, and Dkt. 140 of the same date sent three plaintiffs to arbitration.
No later opinion appears on govinfo as of 2026-11-17, and the case is not decided on the merits.
Questions a Seller Answers Before Licensing Recorded or Stored Communications
A seller can sort most ECPA questions before a buyer sees a file by answering five questions in writing:
- who consented to each recording, when, and whether that consent named reuse;
- whether any recording might have been captured without a party's consent, which keeps it out of scope;
- whether the company offers a communication or storage service to the public or holds only its own internal systems;
- what its user terms or privacy policy said when the messages were sent;
- which provider terms limit training or export of the archive.
The same answers serve the buyer's side of due diligence in an AI data deal, though answering them does not clear any liability.
Benefits, Risks, Downsides and Alternatives for Communications Data Under ECPA, Including Not Licensing
Recorded calls, meetings and stored messages can be licensed when consent and the provider question are settled first, and licensing a smaller consented set, or not licensing at all, remain valid choices.
Benefits
- One-party consent is the federal floor for recording.
- A company's internal systems are generally outside 2702.
- Buyers state their consent requirements in advance.
Risks
- Onward disclosure or use of unlawfully intercepted contents is a separate violation with up to 5 years, which is why some archives are among the company data that cannot be licensed for AI training.
- Plaintiffs plead training as a tortious purpose, and an ECPA claim survived dismissal in Otter.
- A provider to the public needs lawful consent under 2702.
Downsides
- Consent is traced per recording or per user cohort.
- State all-party rules apply on top of the federal floor.
- Provider terms can limit training or export.
Alternatives
- License only recordings with documented reuse consent.
- License transcripts stripped of identifying details where the buyer accepts them, which does not remove the ECPA questions.
- Collect fresh consent before licensing.
- License non-communications data instead.
- Not licensing at all.
Each route is compared in alternatives to selling data to AI labs, including not selling.
Beyond ECPA: Employee Rules, State Statutes and Other Federal Layers
ECPA is one federal layer on a communications data deal. The page on United States AI training data law sets it beside copyright, sector privacy, FTC, trade-secret and state rules.
- Outside the US: AI training data law by jurisdiction.
- Staff messages: employee notice and consent for internal communications.
- Client conversations: customer consent and confidentiality clauses.
- Privacy policy changes made to obtain consent: FTC rules on AI training data.
- State rules: California CCPA, AB 2013 and CIPA, Florida all-party recording consent and Washington all-party recording consent.
- The Google contact-center case: Google Cloud Contact Center AI privacy litigation.
- Data types: company email archive for AI training, chat messages (Slack, Teams) for AI training, meeting recordings and transcripts for AI training and contact centers licensing call and chat data.
- Systems: Slack data and AI training, Zoom recordings and consent and Microsoft Teams data export.
- Germany: German telecom secrecy and work email.
How This Page Is Sourced and Dated
Every rule here cites the text of 18 U.S.C. 2511 or 2702 as published on govinfo, every court status is dated to the order it rests on, and every buyer requirement is the buyer's own statement with the date it was read.
The method is set out under how we source and date every rule. This page is general information about the Electronic Communications Privacy Act, not legal advice on any recording, archive or deal.
Frequently Asked Questions
What is the Stored Communications Act?
The Stored Communications Act is Title II of ECPA. Its voluntary-disclosure rule, 18 U.S.C. 2702, bars providers of communication or remote computing services to the public from divulging stored contents without lawful consent.
Which section of the ECPA deals with stored communications?
Title II, the Stored Communications Act, deals with stored communications. This page relies on 18 U.S.C. 2702 and its consent exception, 2702(b)(3).
What constitutes a violation of the Stored Communications Act?
For a provider to the public, divulging stored contents without lawful consent is a violation. The consent must come from an originator, addressee, intended recipient or, for remote computing, the subscriber; unlawful access rules are not covered here.
Can a company sell recordings made with one party's consent?
Recording with one party's consent is lawful under 2511(2)(d) unless the purpose is criminal or tortious. State all-party rules can still apply, and disclosing unlawfully intercepted contents is a separate violation.