DataPacts

Telecom Operators Licensing Data to AI

Checked

At a glance

A telecom operator can license some of its records to AI companies, but customer proprietary network information rules in the United States and the ePrivacy Directive in the EU decide which subscriber, call and location records can leave the company.

Independent reference. Every buyer is covered on the same terms, every figure carries its source and check date, and no buyer pays to be listed or placed higher.

Request an independent introduction

Tell us what data your company holds. We reply with the buyers that fit and what their terms leave out. Your details reach a buyer only after you agree to a named introduction.

IndependentYour details stay with us until you agreeNot selling is a valid outcome

None of the five programs and vendors checked names telecom operators among the companies it wants (checked 2026-11-09 and 2026-11-17), none publishes a telecom price, and this page records no operator licensing deal for AI training.

Every figure below is a dated claim or a regulator's statement. The page sits within AI training data licensing, where telecom is one sector among many.

How we checked this page: every clause and figure was compared with its primary source on the date shown, and the method is set out under how we source, date and check every figure.

What Telecom Operators Hold That AI Buyers Might Ask For

Operators hold three kinds of records that can interest an AI buyer: subscriber and call records, customer-care call recordings, and network logs.

Subscriber, Call Detail and Location Records

Subscriber records are the account, usage, call detail and location data an operator holds because it provides service, and in the United States most of it is CPNI.

Under 47 U.S.C. 222(h)(1), read 2026-11-17, CPNI is information on "the quantity, technical configuration, type, destination, location, and amount of use" of a service that the carrier holds solely by virtue of the carrier-customer relationship, plus information in bills.

Call detail information (47 CFR 64.2003(d)) covers the number called or calling and the time, location or duration of specific calls.

In the EU, the same records are traffic data and location data under Directive 2002/58/EC, and these records identify customers by nature.

Customer-Care Call Recordings

Customer-care recordings are the calls between subscribers and an operator's agents or its outsourced contact center, and they are a separate record type from call detail records.

A care call that reads out bill details can contain CPNI, because 47 U.S.C. 222(h)(1)(B) counts information in bills. The data type itself is covered under selling call recordings for AI training.

Mercor states in its Call Center or BPO listing, checked 2026-11-17, that it wants "Recorded calls with consent that covers reuse" and lists "Recordings made without consent" as not a fit. The listing names no operator.

In N.D. Cal. 3:23-cv-05437-RFL, callers allege that Google's Contact Center AI recorded customer-service calls with companies including Verizon (docket as of 2026-11-17).

Network Logs and Operations Data

Network logs record how traffic flows through an operator's systems, and whether a log is licensable depends on whether it identifies a customer or a device.

A log tied to a subscriber carries the technical configuration, destination, location and amount of use that 47 U.S.C. 222(h)(1) lists, and in the EU it is traffic data under Art. 6. A log with no customer or device identifier falls outside those definitions, a plain reading and not a regulator's statement.

Precise geolocation of more than 1,000 US devices in the preceding 12 months is a bulk threshold under 28 CFR 202.205, so device-level location logs can reach the DOJ rule's threshold even when held for network purposes.

Buyer and Vendor Statements Checked for Telecom

Five programs and vendors were checked for telecom on 2026-11-09 and 2026-11-17, and none of them names telecom operators among the companies it wants.

The table compares what each names, as of 2026-11-17, in alphabetical order, with B for a buyer or licensee program, M for a marketplace and V for a data-services vendor.

Program Role What it names, and whether it names telecom Source
Handshake AI B 11 industries named, checked 2026-11-09: finance and insurance; hardware and engineering; healthcare; legal; logistics and supply chain; manufacturing; pharmaceuticals and life sciences; professional services; real estate; retail and e-commerce; software. Telecom not named joinhandshake.com/ai/data-partnerships
HUMXN M 24 industry cards and 8 data types, re-read 2026-11-17; "Email, chat & calls" is a data type; the "Energy & utilities" card names "sensor and grid data"; no telecom card; legal name not stated humxn.io/sell-company-data
Mercor Data B program page names 8 target industries (legal, healthcare, finance and insurance, professional services, manufacturing, retail and e-commerce, real estate, logistics), telecom not among them; its Call Center or BPO listing asks for "Recorded calls with consent that covers reuse" and lists no telecom operators (re-read 2026-11-17) mercor.com/data; api.data.mercor.com listings/call-center
micro1 B six functional areas named, checked 2026-11-09: software and engineering; finance and accounting; customer support; sales and CRM; legal and contracts; operations and logistics. Telecom not named micro1.ai/data-partnerships
TELUS Digital V offers data for "GenAI, automotive, physical AI, search and ads, and off-the-shelf datasets", no public program to buy company data found, checked 2026-11-09; parent TELUS Corporation is a Canadian telecom group telusdigital.com

Mercor's Call Center or BPO listing is the nearest match to an operator's care calls, and TELUS Corporation is the parent of a vendor, not an operator running a licensing program. "Not named" does not mean not allowed, and each program's terms sit under payouts and program terms compared.

CPNI Approval Comes Before Any License in the United States

In the United States a telecommunications carrier needs the customer's approval before it discloses individually identifiable CPNI, and a license to an AI developer is a disclosure. That is a plain reading of section 222(c)(1), and this page found no FCC statement on AI licensing of CPNI.

What 47 U.S.C. 222 and 47 CFR 64.2001 to 64.2011 Require

Section 222(c)(1) bars a carrier from using, disclosing or permitting access to individually identifiable CPNI beyond providing the service without customer approval or legal requirement, and the FCC's rules make opt-in approval the default for other disclosures.

The table compares the provisions that matter for licensing, as of 2026-11-17 (eCFR title 47 current to 2026-11-13).

Provision What it says Source
47 U.S.C. 222(c)(1) except as required by law or with the customer's approval, a carrier uses, discloses or permits access to individually identifiable CPNI only to provide the service it comes from or services necessary to it govinfo.gov
47 U.S.C. 222(c)(3) a carrier may use, disclose or permit access to aggregate customer information for other purposes; a local exchange carrier may do so only if it provides the aggregate information to other carriers or persons on reasonable and nondiscriminatory terms on request govinfo.gov
47 U.S.C. 222(h)(1), (h)(2) CPNI is information on the quantity, technical configuration, type, destination, location and amount of use of a service, made available to the carrier solely by the carrier-customer relationship, plus information in bills; aggregate customer information is collective data from which individual identities and characteristics have been removed govinfo.gov
47 CFR 64.2003(d) call detail information is information on the transmission of specific calls: number called or calling, and time, location or duration ecfr.gov
47 CFR 64.2005(a) no approval is needed to use CPNI to provide or market offerings in the categories of service the customer already buys from the carrier ecfr.gov
47 CFR 64.2007(a)(3), (b) approval records kept at least one year; except for uses allowed without approval or for marketing communications-related services to agents and affiliates, individually identifiable CPNI may be used, disclosed or accessed only on opt-in approval ecfr.gov
47 CFR 64.2009(c), (e) records of all instances where CPNI was disclosed to third parties, kept at least one year; annual officer certificate filed with the Enforcement Bureau in EB Docket No. 06-36 by March 1 ecfr.gov

Stored message content that a provider holds for the public falls under 18 U.S.C. 2702, which bars divulging it without lawful consent (2702(b)(3)). The statute is set out under ECPA, the Wiretap Act and Stored Communications.

What the FCC's Location Data Fines and the 2026 Supreme Court Ruling Show

On 2024-04-29 the FCC announced fines on the four largest wireless carriers for sharing access to customers' location information without consent, which makes location data the clearest CPNI enforcement record for operators.

The FCC's press release states the amounts as more than USD 57 million for AT&T, more than USD 12 million for Sprint, more than USD 80 million for T-Mobile and almost USD 47 million for Verizon, and says each carrier sold access to location information to aggregators who resold it to location-based service providers.

The Sprint order, FCC 24-42 (adopted 2024-04-17, released 2024-04-29), sets a penalty of USD 12,240,000 and states in paragraph 2 that location information is CPNI under section 222. The Supreme Court took up the Fifth Circuit and Second Circuit appeals as Nos. 25-406 (FCC v.

AT&T, Inc.) and 25-567 (Verizon Communications Inc. v. FCC), granted certiorari on 2026-01-09, heard argument on 2026-04-21 and decided on 2026-06-04. The docket shows the judgment affirmed in No. 25-567 and reversed and remanded in No. 25-406, with rehearing denied in No. 25-567 on 2026-08-17 (dockets read 2026-11-17).

The Court's own summary states that because forfeiture orders under 47 U.S.C. 503(b)(4) "do not definitively resolve the parties' legal obligations" and the FCC's findings "are not conclusive", it "does not violate the Seventh Amendment for the FCC to issue forfeiture orders without the involvement of a jury".

None of these matters concerns AI training; they show how the FCC treats a sale of access to location data.

Traffic, Location and Call Content Under the ePrivacy Directive

In the EU, Directive 2002/58/EC binds providers of public communications services to erase or anonymize traffic data and to process location data only anonymized or with consent.

The table compares the operator-side articles, as of 2026-11-17.

Article What it says Source
Art. 5(1) Member States prohibit listening, tapping, storage or other interception or surveillance of communications and related traffic data by persons other than users without the users' consent, except when legally authorized under Art. 15(1) legislation.gov.uk/eudr/2002/58/article/5; CELEX 02002L0058
Art. 5(2) does not affect legally authorized recording in lawful business practice "for the purpose of providing evidence of a commercial transaction or of any other business communication" same
Art. 6(1)-(2) traffic data must be erased or made anonymous when no longer needed for transmission; billing and interconnection payment processing allowed until the bill can no longer lawfully be challenged legislation.gov.uk/eudr/2002/58/article/6
Art. 6(3) marketing or value added services only with the user's prior consent, withdrawable at any time same
Art. 9(1) location data other than traffic data may be processed only when made anonymous or with consent, for the duration necessary for a value added service legislation.gov.uk/eudr/2002/58/article/9

Art. 5(1) bars interception of call content without the users' consent, and Art. 5(2) names recording for evidence of a business communication without mentioning licensing. Recording consent by jurisdiction is set out under call and meeting recording consent rules.

Operators in Germany and Austria carry a further duty. Section 3(2) of the TDDDG, renamed effective 2024-05-14, binds providers of publicly available or commercially offered telecom services and operators of public networks to communications secrecy and section 161(2) of the Austrian TKG 2021 binds every provider of a public communications network or service.

The Directive applies through national legislation (in force since 2002-07-31), so the transposing law of each Member State governs. Reform status and UK rules are not stated here.

Aggregate and Anonymized Data Are the Narrow Route

Both rule sets leave a door open for aggregate or anonymized data, and the door is narrower than it looks.

Section 222(c)(3) allows aggregate customer information, which section 222(h)(2) defines as collective data from which individual customer identities and characteristics have been removed, and a local exchange carrier may use it only if it offers it to other carriers or persons on reasonable and nondiscriminatory terms on request.

In the EU, Art. 6(1) and Art. 9(1) allow traffic and location data that are "made anonymous".

Whether a given dataset is anonymous is a de-identification question that the seller path steps below treat, because the statutes test what has been removed.

The DOJ rule at 28 CFR 202.205, in force since 2025-04-08 under 202.216, sets bulk thresholds, among them precise geolocation of more than 1,000 US devices.

It prohibits a sale or license of bulk data to countries of concern (China, Cuba, Iran, North Korea, Russia, Venezuela) or covered persons even if the data is anonymized or de-identified, as the DOJ bulk sensitive data rule sets out.

Benefits, Risks, Downsides and Alternatives for an Operator

Licensing can earn income from archives an operator keeps anyway, but CPNI approval, ePrivacy limits and the FCC's enforcement record shrink what can go, and not licensing is a valid outcome.

Benefits

  • Aggregate and anonymized data have a statutory route (47 U.S.C. 222(c)(3); Arts. 6(1) and 9(1) of the ePrivacy Directive).
  • Care-call archives made with consent that covers reuse match a stated buyer requirement.

Risks

  • Disclosure of CPNI without customer approval under section 222(c)(1).
  • FCC fines of the kind announced on 2024-04-29 for location data.
  • Traffic and location duties under Arts. 6 and 9 of the ePrivacy Directive.
  • The DOJ bulk data rule for device-level location logs.

Downsides

  • No buyer checked names telecom, and none publishes a telecom price.
  • Disclosure records must be kept for at least a year under 47 CFR 64.2009(c).
  • Anonymization work can leave little of an archive to license.

Alternatives

Where Telecom Licensing Meets the Seller Path, the Law and Other Industries

Telecom operators share customer-care recordings with contact centers, network records with energy and utility companies and managed service providers, and customer-privacy duties with banks, and each industry page sets out its own limits.

This page is one entry in data licensing by industry, next to contact centers licensing call and chat data, energy and utility companies licensing data and managed IT service providers licensing data.

Device records sit under sensor, IoT and telemetry data, and the Google Cloud Contact Center AI lawsuit has its own record.

EU rules sit under EU law on AI training data, with German telecom secrecy and Austria rules for licensing data for the two national duties above. Consumer data is compared under privacy law and AI training data, and the full map is AI training data law by jurisdiction. This page is information, not legal advice.

  1. Check data sale readiness.
  2. Review subscriber terms and customer consent and confidentiality clauses.
  3. Decide what PII removal and de-identification before licensing achieves.
  4. Work through choosing a buyer for your data.
  5. Negotiate the clauses of AI data licensing agreements.

Buyer, Vendor and Law Pages Named on This Page

Each buyer and vendor above has its own page where one exists, with dates and sources.

Frequently Asked Questions

Can a telecom operator license subscriber or call detail records to AI companies?

Only with the customer's approval for individually identifiable CPNI. Section 222(c)(1) of 47 U.S.C. and 47 CFR 64.2007(b) require it, and in the EU traffic data must be erased or made anonymous under Art. 6(1) of Directive 2002/58/EC. Aggregate customer information has a separate route in section 222(c)(3).

Can an operator license customer-care call recordings?

Only if the recordings were lawfully made and the consent covers reuse. Mercor's Call Center or BPO listing asks for recorded calls with consent that covers reuse (checked 2026-11-17), and a care call can contain CPNI under section 222(h)(1).

How do telecom operators monetize data for AI?

No operator licensing deal for AI training is on record here, and none of the five programs checked names telecom operators. No operator release is cited here. The general models are compared under AI data monetization models.