Fact-checked by Grok 2 weeks ago

Customer proprietary network information

Customer proprietary network information (CPNI) refers to data generated and collected by carriers through the provision of services to individual customers, including specifics on the quantity, technical configuration, type, destination, location, duration, and amount of usage, as well as billing details and subscribed optional features such as or . Enacted under Section 222 of the , CPNI protections impose a statutory duty on carriers to safeguard this information's confidentiality against unauthorized access or disclosure, distinguishing it from publicly available data like names and addresses while permitting limited internal use for service provision and billing. Carriers may use CPNI without for purposes directly tied to the categories of from which the data derives—such as local, long-distance, or —but require affirmative opt-in approval for unrelated services or with third parties, with aggregate anonymized data exempt from these restrictions. (FCC) rules under 47 CFR Part 64 Subpart U further mandate reasonable data security measures, including breach notifications for inadvertent access to sensitive CPNI elements like geolocation or call records, reflecting ongoing adaptations to cybersecurity risks in telecom networks. Defining characteristics of CPNI regulation emphasize causal linkages between carrier-customer relationships and data generation, prioritizing empirical privacy harms from misuse—such as targeted scams or competitive tracking—over broader surveillance concerns, though has involved fines for violations like unauthorized disclosures amid evolving digital threats. These provisions apply to wireline, , and interconnected VoIP providers, underscoring a framework that balances operational efficiencies for carriers with individual control over proprietary usage patterns.

Definition and Scope

Core Elements of CPNI

Customer Proprietary Network Information (CPNI) is statutorily defined in Section 222(h)(1) of the , as amended, as information relating to the quantity, technical configuration, type, destination, location, and amount of use of a subscribed to by a of a carrier, as well as the types of services the has obtained. This definition encompasses data generated through the carrier- relationship, such as call detail records including dialed numbers, call durations, and service usage patterns, but excludes publicly available information like basic subscriber lists (names, addresses, and telephone numbers) unless aggregated with CPNI elements. The quantity element refers to the volume of usage, such as the number of calls made or transferred over a given period. Technical configuration includes details on the setup of the customer's service, like equipment types or network features enabled, such as caller ID blocking or . The type of service covers categories like , , or interconnected VoIP, distinguishing between local, long-distance, or offerings. Destination pertains to the endpoints of communications, including phone numbers or addresses called or messaged. data involves geolocation derived from network use, such as cell tower pings for mobile services, though not real-time tracking absent additional . Amount of use measures specifics like total minutes, bytes, or sessions, often reflected in billing but protected beyond mere financial records. Finally, types of services obtained aggregates subscribed features, such as or calling plans, without including non-network details like history unless tied to usage. Federal Communications Commission (FCC) rules in 47 CFR § 64.2003 incorporate this statutory definition verbatim, applying it to carriers' obligations to safeguard such information against unauthorized disclosure. Carriers must derive CPNI solely from their provision of services, excluding data from unrelated sources like credit checks. This framework ensures CPNI protection focuses on network-derived insights that reveal customer behavior patterns, distinct from aggregate or anonymized analytics permissible under certain conditions.

Distinctions from Other Customer Data

Customer proprietary network information (CPNI) differs from other customer data collected by carriers in its specific emphasis on proprietary details of usage, while excluding both the substantive content of communications and subscriber list information (SLI). Under Section 222(h)(1)(A) of the , as amended by the , CPNI is defined as information relating to the quantity, technical configuration, type, destination, location, and amount of use of a subscribed to by a customer, including data on configurations made available to the carrier, and billing information tied to such service usage. This excludes the actual content of calls, text messages, or data transmissions, which receives independent safeguards against interception or disclosure under statutes like the of 1986 and Title III of the Omnibus Crime Control and Safe Streets Act of 1968. A primary distinction lies in the exclusion of SLI, defined in Section 222(h)(3) as any contained in a or obtained in connection with the or provision of , such as a customer's name, , and number. Unlike CPNI, which carriers must generally protect from unauthorized use or disclosure without customer consent, SLI may be published in telephone directories or disclosed for purposes, subject to rights for non-published listings, as carriers can treat it as presumptively public unless customers request otherwise. This separation ensures that basic identifying details are not conflated with sensitive usage patterns that could reveal behavioral or locational insights, such as calling destinations or service volumes, which form the core of CPNI. CPNI also stands apart from non-network-related customer data, such as general account preferences or demographic information not derived from telecommunications service provision, which may fall under broader privacy frameworks like the Gramm-Leach-Bliley Act for but lack the telecom-specific confidentiality duties imposed by Section 222(a). For instance, while billing aggregates for non-usage elements (e.g., taxes unrelated to call volumes) might overlap with customer records, only usage-tied billing qualifies as CPNI, highlighting its causal link to network operations rather than mere transactional records. interpretations in proceedings, such as those implementing 47 CFR Part 64 Subpart U, reinforce that CPNI's protections apply narrowly to enabling of habits, distinguishing it from aggregate or anonymized customer metrics used for internal analytics without individual identifiability.

Historical Development

Early FCC Proceedings

The Federal Communications Commission's early efforts to address customer in arose during its Computer Inquiries, which sought to foster by separating regulated basic services from unregulated enhanced () services while preventing carriers from leveraging proprietary data for anticompetitive advantage. In the Second Computer Inquiry (Docket No. 20828), concluded with a Final Decision on August 31, 1980, the FCC imposed structural separation requirements on dominant carriers like , mandating safeguards to protect confidential customer information obtained through basic services from misuse in enhanced services markets. These safeguards prohibited carriers from using such data—encompassing details on service quantities, destinations, and technical configurations—to discriminate against competitors or cross-subsidize offerings, thereby laying the conceptual groundwork for what later became customer proprietary network information (CPNI). Building on this, the Third Computer Inquiry, initiated in the late 1980s and advanced through phases in the early 1990s, extended similar protections to Bell Operating Companies (BOCs) following the divestiture. Phase I, adopted June 15, 1989, refined nondiscrimination rules via (CEI) arrangements, requiring BOCs to provide rivals access to network features without disclosing proprietary customer usage data that could reveal . Phase II, implemented through (ONA) requirements by 1992, explicitly incorporated customer proprietary network information safeguards, allowing customers to request withholding of their data from BOCs' enhanced service affiliates while mandating internal firewalls and audit mechanisms to prevent unauthorized access or sharing. These rules applied primarily to , BOCs, and , focusing on operational separations to ensure confidentiality of call records, billing patterns, and network usage details that carriers acquired solely through service provision. Related proceedings, such as the Open Network Architecture and BOC (CPE) Relief dockets in the early 1990s, further operationalized these protections by relaxing some structural separations but retaining strict limits on CPNI disclosure to affiliates or third parties , emphasizing verifiable customer opt-outs and accountability for breaches. Collectively, these pre-1996 measures addressed causal risks of data misuse in a monopolistic environment transitioning to competition, prioritizing empirical concerns over self-regulation by requiring documented approvals and periodic reporting, though coverage was limited to major incumbents rather than all providers. This framework influenced congressional codification in Section 222 of the Communications Act, extending duties to a broader class of amid .

Enactment in the Telecommunications Act of 1996

The , signed into law by President on February 8, 1996, introduced the framework for protecting customer proprietary network information (CPNI) by amending the through the addition of Section 222. This provision, enacted as Section 702 of the 1996 Act, established a federal duty for telecommunications carriers to safeguard the of customer information, extending prior obligations to all such entities in a deregulatory environment aimed at promoting competition. Section 222(a) imposed a general requirement on every telecommunications carrier to protect the of proprietary information relating to other carriers, services, or customers, marking a shift from fragmented state-level protections to uniform national standards. Under Section 222(c), carriers were permitted to use, disclose, or permit access to CPNI for purposes directly related to providing the subscribed service—such as billing, service quality assurance, or internal fraud prevention—without customer consent, but faced stricter limits on marketing uses. For marketing communications to the same customer base, carriers could access CPNI on an opt-out basis, requiring affirmative notice to customers and a reasonable opportunity to object, while disclosures to third parties or affiliates for non-service purposes generally demanded affirmative consent. The statute defined CPNI narrowly in Section 222(h)(1) as "(A) information that relates to the quantity, technical configuration, type, destination, location, and amount of use of a telecommunications service offered by the carrier," excluding subscriber list information like names and addresses unless linked to usage data. This definition targeted sensitive call-detail records and usage patterns generated by telephone exchange or toll services, reflecting congressional intent to curb potential abuses in an era of emerging data-driven marketing amid local exchange competition. The enactment responded to privacy concerns heightened by the Act's broader pro-competitive reforms, which dismantled between local, long-distance, and cable services, potentially increasing incentives for carriers to monetize customer data. Unlike pre-1996 practices reliant on judicial interpretations of duties or voluntary industry codes, Section 222 codified explicit prohibitions on unauthorized disclosures and mandated safeguards against breaches, with exceptions for under Section 222(d). Carriers were also required to disclose CPNI to customers or their authorized agents upon written request, promoting while balancing operational needs. These rules applied solely to services, not information services, a distinction that later influenced FCC interpretations but originated in the statutory text to prioritize voice privacy. The provision delegated authority to the (FCC) to prescribe implementing regulations, leading to subsequent rulemakings that operationalized the statutory baseline without altering the core enactment.

Section 222 of the Communications Act

Section 222 of the Communications Act, codified at 47 U.S.C. § 222, imposes a general duty on every carrier to protect the confidentiality of proprietary information belonging to or relating to other carriers, equipment manufacturers, and customers, extending protections beyond prior requirements that applied only to communications between carriers. This provision, enacted via the and effective immediately upon the Act's signing on February 8, 1996, aims to balance carrier access to customer data for legitimate operations with restrictions on unauthorized use or disclosure that could enable competitive harms or invasions. The statute defines "customer proprietary network information" (CPNI) as individually identifiable data revealing the quantity, technical configuration, type, destination, location, and amount of use of services provided to a specific customer or , including but not limited to telephone numbers dialed, call duration, and service usage patterns, while excluding subscriber list information and aggregate customer data. Carriers are prohibited from using, disclosing, or permitting access to CPNI without customer approval or as required by law, with "approval" interpreted by the FCC to include mechanisms for certain internal uses but stricter opt-in for disclosures to third parties. Subsection (c) delineates permitted exceptions to the mandate, allowing to use CPNI without prior approval for communications related to the provision of or other services to the customer, such as billing, repairs, or emergency services, and for internal purposes like prevention or operations. For purposes, may use CPNI to offer additional services from the same or affiliates under an regime, but disclosures to unaffiliated third parties require affirmative opt-in consent, reflecting congressional intent to curb unsolicited while permitting limited commercial reuse. exchange face additional restrictions, permitted to use aggregate CPNI for purposes beyond service provision only if it cannot be traced to individual customers, and must obtain opt-in for non- disclosures. These exceptions underscore a statutory prioritizing customer service continuity over broad absolutism, though subsequent FCC interpretations have clarified ambiguities, such as treating equivalently to wireline ones despite technological differences. To enforce these obligations, subsection (d) mandates that carriers implement reasonable safeguards against unauthorized , use, or of CPNI, proportionate to the nature of the information and risks involved, with the FCC empowered under subsection (e) to investigate violations, impose forfeitures up to $113,000 per violation (adjusted for inflation as of 2023), and seek injunctive relief. Subsection (g) authorizes the FCC to promulgate implementing regulations, leading to rules in 47 CFR Part 64 Subpart U that operationalize processes, limits (e.g., no longer than necessary for purposes), and notification requirements. The provision's scope applies to all carriers as defined in Section 153, encompassing wireline, wireless, and interconnected VoIP providers, but excludes services following the FCC's 2017 reclassification of under Title I, which removed Section 222 applicability to those services. Overall, Section 222 establishes CPNI as a protected category distinct from mere details, requiring carriers to treat it as presumptively confidential unless explicitly excepted, thereby fostering in an era of increasing post-1996 deregulation.

FCC Rulemaking and 47 CFR Part 64 Subpart U

The (FCC) implemented Section 222 of the Communications Act through rulemaking proceedings initiated under CC Docket No. 96-115 following the , adopting the initial rules for customer proprietary network information (CPNI) in the First Report and Order released on February 26, 1998. These rules, codified in 47 CFR Part 64, Subpart U (§§ 64.2001–64.2009), establish a framework requiring carriers to protect the of CPNI, defined as information about the quantity, technical configuration, specific locations, and types of services a customer obtains from the carrier, excluding publicly available subscriber list information. The subpart's basis and purpose, as stated in § 64.2001, directly enforce the statutory duty under 47 U.S.C. § 222 to safeguard proprietary information acquired through services. Subsequent FCC orders refined these rules to address evolving practices and compliance challenges. In the Second Report and Order adopted August 15, 2002 (FCC 02-214), the clarified permissible uses of CPNI for by affiliates and joint ventures, requiring consent for internal sharing while prohibiting disclosure to unaffiliated third parties without affirmative approval, and mandated annual customer notifications detailing procedures. Further amendments in 2007, via Memorandum Opinion and Order (FCC 07-22, released April 2, 2007), enhanced safeguards against —fraudulent impersonation to access CPNI—by requiring carriers to authenticate customers before disclosures based on phone or online contacts and to monitor for unauthorized access patterns. These updates responded to documented incidents, such as the 2006 scandal, emphasizing verifiable identity checks without relying on self-reported data alone. Core provisions in Subpart U delineate strict obligations under § 64.2002, permitting CPNI use without approval solely for provision, billing, operations, prevention, and legal , but mandating customer approval—via opt-in for third-party disclosures or for intra-company —for other purposes. § 64.2004 requires explicit for disclosures, with carriers prohibited from contracting away these protections, while § 64.2005 mandates clear, conspicuous annual notices to customers explaining CPNI and access denial methods. § 64.2006 outlines approval mechanisms, including "total opt-out" where failure to object after notice implies for service-related uses but not , and § 64.2007 addresses status changes like mergers, requiring prompt customer notifications. Safeguards and enforcement rules in §§ 64.2008–64.2009 compel carriers to maintain auditable systems for tracking CPNI approval status, implement reasonable measures, and report breaches or unauthorized uses, with the FCC retaining authority for investigations and penalties up to $130,000 per violation as of adjustments in 2015. These requirements apply to wireline and commercial mobile radio service (CMRS) providers but exclude interconnected VoIP initially, though later proceedings extended similar principles. The rulemaking emphasized empirical evidence from carrier practices and complaints, rejecting broader defaults for marketing to balance commercial interests against statutory mandates, without deference to claims lacking verifiable efficacy.

Permitted Uses by Telecommunications Carriers

Service Provision and Internal Operations

Telecommunications carriers may use, disclose, or permit access to customer proprietary network information (CPNI) without customer approval to initiate, render, bill, and collect for telecommunications services. This exception, outlined in Section 222(d)(1) of the Communications Act, encompasses core activities necessary for service delivery, such as routing calls, maintaining network connectivity, and processing usage data in real time to ensure uninterrupted telecommunications functionality. Carriers rely on CPNI derived from these operations—such as the quantity, technical configuration, and type of services provided—to fulfill contractual obligations without triggering consent requirements, as such uses are inherent to the carrier-customer relationship established at subscription. Internal operations permitted under these rules include protecting the carrier's rights or property and safeguarding users from fraudulent, abusive, or unlawful service use, as specified in Section 222(d)(2). This authorizes activities like fraud detection algorithms that analyze calling patterns, anomaly monitoring for , and internal audits to prevent unauthorized access or billing disputes, all without prior customer opt-in or opt-out mechanisms. FCC regulations in 47 CFR § 64.2005 further implement these statutory exceptions by allowing CPNI use for inside wiring , , and repair—services integral to sustaining telecommunications infrastructure—thereby extending protections to operational necessities beyond mere billing. These provisions balance privacy safeguards with the practical demands of reliable service provision, ensuring carriers can respond to operational risks without undue regulatory hurdles. While marketing uses within subscribed service categories (e.g., local or ) require approval under 47 CFR § 64.2005(a), pure service provision and protective internal functions remain exempt to avoid impeding essential . For instance, carriers may disclose CPNI to affiliates solely for delivering subscribed services across categories, such as coordinating billing across wireline and commercial mobile radio services (CMRS), provided it aligns with these exceptions. Violations of these boundaries, however, can lead to enforcement, as the rules prohibit leveraging service-derived CPNI for unrelated competitive tracking. Telecommunications carriers may use customer proprietary network information (CPNI) derived from providing telephone exchange service or commercial mobile service to market telecommunications service offerings within the same service category to the originating customer, subject to opt-out approval mechanisms. This opt-out process requires carriers to provide clear notice to customers of their intent to use CPNI for such marketing, including an opportunity to prohibit or limit the use, typically via a 30-day waiting period after notice before assuming approval unless the customer objects. For example, a carrier providing local exchange service may leverage call detail records to market additional local calling plans to that customer without affirmative consent, provided opt-out notice has been given and no prohibition is received. Disclosure of CPNI to affiliates for purposes follows similar consent rules, but only for affiliates offering products or services within the carrier's corporate family. Carriers must notify customers annually of their rights regarding CPNI use and affiliate sharing, and maintain records verifying with requests. In contrast, any of individually identifiable CPNI to non-affiliated third parties for —whether the carrier's own non- services or others' offerings—requires affirmative opt-in approval from the customer, such as explicit written or electronic consent. This stricter standard, rooted in Section 222(d) of the Communications Act, aims to prevent unauthorized external commercialization of sensitive network usage data. Consent mechanisms must be separate from billing statements or service terms to avoid bundling, ensuring customers can easily grant or revoke approval without affecting service provision. Revocation of opt-out consent remains available at any time, with carriers required to implement reasonable procedures to honor such requests promptly. These rules, implemented via 47 CFR § 64.2000 et seq., balance carriers' commercial interests in targeted marketing against privacy protections, though enforcement has highlighted inconsistencies in notice clarity and consent tracking.

Protections and Compliance Obligations

Carrier Responsibilities for Safeguarding CPNI

Under Section 222(a) of the , as amended, every telecommunications carrier bears a statutory duty to protect the of proprietary relating to its customers, including customer proprietary network (CPNI), which encompasses details such as the quantity, technical configuration, type, destination, location, and amount of use of a communications subscribed to by the customer. This duty requires carriers to implement safeguards against unauthorized use, disclosure, or access, except as expressly permitted under Section 222(c), such as for providing the customer's own or with customer approval. The Federal Communications Commission's rules in 47 CFR Part 64, Subpart U, operationalize this duty through specific safeguarding requirements. Carriers must take reasonable measures to detect and prevent unauthorized access to CPNI, including by monitoring for suspicious activity and employing security protocols comparable to those used for their own proprietary information. These measures extend to contractors, agents, or affiliates granted access, whom carriers must obligate via to maintain equivalent protections and limit use to authorized purposes. Personnel handling CPNI receive mandatory training on obligations, procedures, and detection of unauthorized attempts, with carriers required to maintain records demonstrating . Before disclosing CPNI—even to the —carriers must authenticate the requestor's using methods such as knowledge-based questions derived from records, password prompts, or public information not readily available online, ensuring separation of CPNI from non-proprietary data to prevent inadvertent exposure. Non- risks enforcement actions, as evidenced by the FCC's annual certification mandate under 47 CFR § 64.2011, where carriers affirm adherence to these protections or detail remedial steps for any lapses. Telecommunications carriers must provide customers with clear and conspicuous notice regarding the use and disclosure of their customer proprietary network information (CPNI) at the inception of service and on an annual basis thereafter. This notification informs customers of their right to approve or disapprove the carrier's use of, disclosure of, or access to CPNI by the carrier or its affiliates for marketing purposes related to communications services. The notice must specify the types of entities that may access CPNI, the purposes for such access, and the precise steps a customer must take to grant or deny permission, emphasizing that the default position is denial unless explicitly approved. Consent mechanisms under 47 CFR Part 64 Subpart U distinguish between opt-out and opt-in approvals to balance carrier operational needs with . approval allows carriers to use, disclose, or permit to CPNI for the carrier's or its affiliates' communications-related services to the unless the customer affirmatively objects after receiving and a reasonable opportunity to respond, typically via electronic or written methods but not solely oral communication. In contrast, opt-in approval requires affirmative —such as through a specific request—for disclosures to third parties outside the carrier's affiliates or for non-communications-related , ensuring stricter controls on sensitive . Carriers must authenticate customer identity through reasonable means, such as verifying account details during or interactions, before acting on any or disclosure request involving CPNI. These mechanisms stem from Section 222(c) of the Communications Act, which permits CPNI use for service provision without consent but mandates approval for other purposes, with FCC rules operationalizing this through notification and approval processes to prevent unauthorized access. Carriers are required to maintain records of or opt-in statuses and any disclosures, facilitating verification during FCC audits or . Failure to implement effective notification can result in deemed lack of approval, prohibiting certain CPNI uses until proper consent is obtained.

Enforcement, Controversies, and Criticisms

FCC Enforcement Actions and Penalties

The (FCC) enforces CPNI protections primarily through Section 222 of the Communications Act, which authorizes civil forfeitures for violations, with base amounts adjusted for severity, history, and ability to pay, up to $234,107 per violation as of 2024. Enforcement actions have included notices of apparent (NALs), forfeiture orders, and decrees, often addressing unauthorized disclosure, inadequate safeguarding, or misuse of CPNI such as call records, usage , and location information. Early cases typically involved smaller penalties for compliance failures, while recent actions have targeted systemic lapses and location by major carriers, resulting in multimillion-dollar fines. Notable enforcement prior to 2020 included consent decrees for CPNI misuse and security shortcomings. In April 2015, agreed to a $25 million settlement for failing to protect CPNI from unauthorized access by third parties. Cox Communications settled for $595,000 in October 2015 over inadequate controls allowing employee access to CPNI without business justification. Verizon Wireless entered a $1.35 million consent decree in March 2016 for deploying "supercookies" that uniquely identified customers and facilitated CPNI tracking without consent. These actions emphasized carrier obligations to limit internal access and prevent unauthorized disclosures. In , the FCC issued NALs proposing substantial penalties for data breaches exposing CPNI, including location , which carriers failed to reasonably safeguard. AT&T faced a proposed $57.27 million forfeiture for breaches from 2015–2019 that compromised millions of customers' location information. Similar NALs targeted ($48.3 million proposed), ($91.63 million proposed), and Sprint ($12.24 million proposed) for comparable failures in protecting geolocation shared with aggregators. These stemmed from practices enabling third-party access to precise customer locations without opt-in consent, violating Section 222's privacy requirements. By April 2024, the FCC finalized these as forfeiture orders, with some reductions: at $57.27 million, at $46.9 million, at $80.08 million, and Sprint at $12.24 million, totaling nearly $200 million across the four largest carriers. The orders cited carriers' knowing sale or provision of location data to third parties, inadequate oversight of vendors, and failure to implement reasonable measures despite awareness of risks. Subsequent court challenges emerged; in April 2025, the Fifth Circuit vacated the forfeiture, ruling FCC in-house adjudication violated Seventh Amendment jury trial rights under , though the FCC sought rehearing . Other recent settlements addressed breach aftermaths and compliance gaps. TracFone Wireless agreed to a $16 million consent decree in July 2024 for three breaches from 2020–2021 exposing CPNI of over 50 million customers due to poor cybersecurity practices. settled for $13 million in September 2024 over a 2023 that leaked call records, committing to enhanced measures. These actions underscore escalating penalties for location tracking and breach prevention failures, with the FCC prioritizing carrier accountability amid rising misuse concerns.
Carrier/EntityDateAction TypePenalty AmountKey Violation
April 2015$25 millionUnauthorized third-party CPNI access
October 2015$595,000Inadequate employee access controls
WirelessMarch 2016$1.35 millionSupercookie tracking
April 2024Forfeiture Order$57.27 millionLocation data breaches and sharing
April 2024Forfeiture Order$46.9 millionLocation data protection failures
April 2024Forfeiture Order$80.08 millionLocation data breaches and vendor oversight lapses
SprintApril 2024Forfeiture Order$12.24 millionLocation data security shortcomings
July 2024$16 millionMultiple CPNI-exposed data breaches

Debates on Privacy vs. Commercial Utility

Privacy advocates have long contended that CPNI protections under Section 222 are inadequate to safeguard against intrusive surveillance and commercial exploitation, particularly given the granular nature of data such as call records, which can reveal sensitive personal habits and associations. Organizations like the Electronic Privacy Information Center (EPIC) have criticized carriers for interpreting rules permissively, arguing that opt-out mechanisms fail to secure meaningful consent and enable unchecked data aggregation for profiling. In 2024, the FCC imposed nearly $200 million in fines on major carriers including Verizon, AT&T, and T-Mobile for sharing precise location data—deemed CPNI—without required opt-in approval, highlighting empirical instances of misuse where third-party aggregators resold access to bounty hunters and others, underscoring causal risks of privacy erosion when commercial incentives override consent. Telecommunications industry representatives counter that broad CPNI access fosters commercial utility essential for service innovation, competitive pricing, and , asserting that stringent opt-in requirements impose compliance burdens that deter beneficial uses like detection and tailored offerings. The , representing wireless carriers, has advocated for frameworks as pro-consumer, enabling efficient marketing without presuming blanket consent, and warned that overly restrictive rules could disadvantage U.S. firms against less-regulated global competitors. In challenging FCC proposals for enhanced privacy rules in 2016, industry groups argued such measures violated First Amendment protections for commercial speech, potentially stifling data-driven enhancements like usage-based billing. The tension peaked with the 2017 congressional repeal of FCC's 2016 broadband order, which had mandated opt-in for non-usage ; critics from groups labeled this a capitulation to industry lobbying, eroding safeguards amid rising data breaches, while proponents cited evidence that lighter-touch oversight better balances utility without overregulating core operations. Empirical data on outcomes remains mixed: while violations like the 2024 scandals reveal gaps, industry reports claim CPNI-driven boosts metrics, though independent verification of net effects is limited by data silos. This debate underscores a core , where absolutism risks forgoing verifiable efficiencies in , yet lax utility prioritization has demonstrably enabled unauthorized disclosures.

Recent Developments in Data Breaches and Location Tracking

In December 2023, the (FCC) adopted updated data breach notification rules, expanding requirements for telecommunications carriers to report breaches involving customer proprietary network information (CPNI) or personally identifiable information (PII) affecting 500 or more customers within seven business days to the FCC, FBI, and , with customer notifications following within 30 days. These rules broadened prior obligations, which had focused primarily on CPNI, to include inadvertent disclosures of PII alongside CPNI, aiming to address escalating cyber threats amid rising telecom breaches. In August 2025, the U.S. Court of Appeals for the Sixth Circuit upheld these regulations, rejecting challenges from telecom associations that argued the FCC exceeded its authority under Section 222 of the Communications Act, affirming carriers' duties to notify affected parties of breaches exposing call records, location data, or usage patterns as CPNI. Major carriers faced significant enforcement for CPNI-related breaches in this period. T-Mobile agreed to a $15.75 million with the FCC in over multiple incidents from 2021 to 2023, where unauthorized access exposed CPNI—including call detail records and location —for millions of current, former, and prospective customers, violating safeguards under 47 CFR Part 64 Subpart U. settled a 2023 for $13 million, involving the exposure of CPNI such as phone numbers and account details for approximately 73 million customers, with hackers accessing via third-party . Separately, in August 2025, reached a $177 million class-action for leaks from 2019 and later, allowing affected customers claims up to $7,500 for compromised CPNI including names, emails, and passcodes, highlighting persistent vulnerabilities in carrier handling despite regulatory mandates. Developments in location tracking intensified scrutiny of CPNI protections. In April 2024, the FCC issued notices of apparent liability totaling nearly $200 million against , , and for sharing real-time and historical customer location information—deemed CPNI under Section 222—with data aggregators and bounty hunters without obtaining affirmative, opt-in consent, enabling unauthorized tracking via cell-site location data accurate to within hundreds of meters. These actions followed investigations revealing carriers' "location-based services" agreements bypassed strict CPNI rules by routing requests through third parties, prompting the FCC to emphasize that all precise geolocation data qualifies as protected CPNI regardless of consent mechanisms. Multiple federal courts in 2024 and 2025 affirmed this interpretation, ruling that carriers must treat phone location records as CPNI subject to heightened safeguards, rejecting industry arguments that such data falls outside Section 222's scope. This enforcement wave underscored tensions between commercial location-sharing practices and privacy obligations, with the FCC signaling further actions against non-compliance in ongoing proceedings.

References

  1. [1]
    47 U.S. Code § 222 - Privacy of customer information
    A telecommunications carrier shall disclose customer proprietary network information, upon affirmative written request by the customer, to any person designated ...
  2. [2]
    Telecommunications Act of 1996 - Congress.gov
    ``(c) Confidentiality of Customer Proprietary Network Information.-- ``(1 ... ``(3) Aggregate customer information.--A telecommunications carrier that ...
  3. [3]
    Implementation of the Telecommunications Act of 1996 ...
    Telecommunications Carriers' Use of Customer Proprietary Network Information and Other Customer Information IP-Enabled Services
  4. [4]
    47 CFR Part 64 Subpart U -- Privacy of Customer Information - eCFR
    Any information that pertains to the transmission of specific telephone calls, including, for outbound calls, the number called, and the time, location, or ...
  5. [5]
    47 CFR § 64.2005 - Use of customer proprietary network information ...
    Any telecommunications carrier may use, disclose, or permit access to CPNI for the purpose of providing or marketing service offerings among the categories of ...
  6. [6]
    Privacy/Data Security/Cybersecurity: Customer Proprietary Network ...
    Dec 20, 2022 · The Commission's rules require carriers and interconnected VoIP providers to take reasonable measures to safeguard certain sensitive data.
  7. [7]
    FCC CLARIFIES CUSTOMER PRIVACY PROVISIONS OF 1996 ACT
    The Telecommunications Act of 1996 refers to this as "customer proprietary network information," or CPNI. Section 222 of the 1996 Act establishes CPNI ...
  8. [8]
    Customer Proprietary Network Information (CPNI)
    Clarified the Status of our CPNI rules after the Tenth Circuit's opinion and explained how parties may obtain customer consent for use of their CPNI.
  9. [9]
    47 CFR 64.2003 -- Definitions. - eCFR
    (g) Customer proprietary network information (CPNI). The term “customer proprietary network information (CPNI)” has the same meaning given to such term in ...
  10. [10]
    FCC CLARIFIES RULES FOR USE OF CUSTOMER PROPRIETARY ...
    Aug 16, 1999 · CPNI is the information a telephone company has obtained about a customer that relates to the quantity, technical configuration, type, ...
  11. [11]
    [PDF] fcc-07-22a1.pdf
    Apr 2, 2007 · 7 (1998) (CPNI Order) (describing the Commission's privacy protections for confidential customer information in place prior to the 1996 Act).
  12. [12]
    [PDF] Protecting the Privacy of Customers of Broadband and Other ...
    Section 222(a) changed that by extending the general duty to protect proprietary information to all telecommunications carriers, while sections 222(b) and (c) ...
  13. [13]
  14. [14]
    Customer Proprietary Network Information (CPNI) - Bloomberg Law
    The basic paradigm is that the CPNI is to be kept confidential while subscriber list information is to be made publicly available, although a subscriber usually ...<|separator|>
  15. [15]
    Telecommunications Act of 1996 | Federal Communications ...
    Jun 20, 2013 · The Telecommunications Act of 1996 is the first major overhaul of telecommunications law in almost 62 years.Missing: CPNI | Show results with:CPNI
  16. [16]
    Implementation of the Telecommunications Act of 1996 ...
    Sep 20, 2002 · ... Telecommunications Act of 1996), which governs carriers' use and disclosure of customer proprietary network information (CPNI). This ...
  17. [17]
  18. [18]
    [PDF] TELECOMMUNICATIONS ACT OF 1996 - Congress.gov
    Mar 5, 1996 · The Telecommunications Act of 1996 aimed to promote competition, reduce regulation, secure lower prices, higher quality services, and encourage ...
  19. [19]
  20. [20]
  21. [21]
  22. [22]
  23. [23]
  24. [24]
  25. [25]
  26. [26]
    Protecting the Privacy of Customers of Broadband and Other ...
    Sep 21, 2017 · (1) A telecommunications carrier may use, disclose, or permit access to CPNI, without customer approval, in its provision of inside wiring ...
  27. [27]
    [PDF] Federal Communications Commission FCC 02-208
    Jul 24, 2002 · ... Rulemaking, 13 FCC. Rcd 8061 (1998) (CPNI Order), adopting Subpart U of Part 64 of the Commission's Rules, 47 C.F.R. §§ 64.2000, et seq. 10 ...
  28. [28]
    [PDF] Federal Communications Commission FCC 02-214
    FCC 02-214 concerns the implementation of the Telecommunications Act of 1996, specifically regarding telecommunications carriers' use of customer proprietary ...
  29. [29]
  30. [30]
    Customer Proprietary Network Information - Federal Register
    Jun 8, 2007 · In this Order, the Commission responds to the practice of “pretexting” by strengthening its rules to protect the privacy of customer proprietary ...
  31. [31]
    47 CFR 64.2005 -- Use of customer proprietary network information without customer approval.
    ### Summary of 47 CFR § 64.2005: Use of CPNI Without Customer Approval
  32. [32]
    47 CFR 64.2009 -- Safeguards required for use of customer ... - eCFR
    (a) Telecommunications carriers must implement a system by which the status of a customer's CPNI approval can be clearly established prior to the use of CPNI.
  33. [33]
    47 CFR § 64.2008 - Notice required for use of customer proprietary ...
    (1) Carriers must wait a 30-day minimum period of time after giving customers notice and an opportunity to opt-out before assuming customer approval to use, ...
  34. [34]
    [PDF] Small Entity Compliance Guide
    Jun 6, 2008 · This guide helps small entities comply with FCC rules, including rule, notification, recordkeeping, and filing requirements. It covers rule ...
  35. [35]
    47 CFR 64.2007 -- Approval required for use of customer ... - eCFR
    Telecommunications carriers need approval to use customer CPNI, which can be written, oral, or electronic. Approval remains until revoked, and opt-in is ...
  36. [36]
    47 CFR § 64.2009 - Safeguards required for use of customer ...
    All carriers shall maintain a record of all instances where CPNI was disclosed or provided to third parties, or where third parties were allowed access to CPNI.
  37. [37]
    47 CFR § 64.2010 - Safeguards on the disclosure of customer ...
    (a) Safeguarding CPNI. Telecommunications carriers must take reasonable measures to discover and protect against attempts to gain unauthorized access to ...
  38. [38]
    Protecting the Privacy of Customers of Broadband and Other ...
    Dec 2, 2016 · The privacy framework in these rules focuses on transparency, choice, and data security, and provides heightened protection for sensitive customer information.
  39. [39]
    47 CFR § 64.2009 Safeguards required for use of customer ...
    All carriers shall maintain a record of all instances where CPNI was disclosed or provided to third parties, or where third parties were allowed access to CPNI.
  40. [40]
    Enforcement Matters | Federal Communications Commission
    Sep 10, 2024 · $16 million settlement. with TracFone Wireless following the Enforcement Bureau's investigations into three data breaches involving application ...Missing: cases | Show results with:cases
  41. [41]
  42. [42]
  43. [43]
  44. [44]
    Telecommunications Consumers Division - Enforcement Actions
    03-21-2019, $2,320,000 Forfeiture against Long Distance Consolidated Billing Company for cramming, slamming, deceptive marketing, and truth-in-billing ...
  45. [45]
  46. [46]
  47. [47]
  48. [48]
  49. [49]
    FCC Fines AT&T $57M for Location Data Violations
    FCC fines AT&T, Inc. over $57M for failing to reasonably protect its customers' location information.
  50. [50]
    FCC Fines Verizon $46M for Location Data Violations
    - **Date**: Document released as part of FCC-24-41, no specific date provided.
  51. [51]
  52. [52]
    Fifth Circuit Strikes Down FCC Forfeiture Order, Holds That It ...
    Apr 24, 2025 · In that order, the Commission imposed civil penalties against a communications provider for allegedly violating Section 222 of the ...
  53. [53]
    FCC EB Settles With AT&T For Vendor Cloud Breach
    FCC Enforcement Bureau enters into a $13M settlement with AT&T for vendor cloud breach. AT&T agrees to implement expansive consumer privacy upgrades.Missing: cases | Show results with:cases
  54. [54]
  55. [55]
  56. [56]
    Verizon v. FCC and USA (CPNI Location Enforcement) - Epic.org
    Petitioner was Verizon, its arguments included that CSLI is not CPNI–and therefore not protected by the Communications Act–unless that CSLI is generated during ...
  57. [57]
    FCC Fines Major Mobile Carriers Almost $200 Million for Illegally ...
    Apr 30, 2024 · The FCC has issued a total of $196 million in fines against four of the largest US mobile carriers for selling customer location data to data aggregators ...
  58. [58]
    Industry takes pro-consumer stance on location privacy policy
    Oct 30, 2000 · The FCC has yet to rewrite CPNI rules. According to CTIA's interpretation of the law, it is legally permissible today for mobile-phone carriers ...
  59. [59]
    Telecom industry, consumer advocates face off over constitutionality ...
    Jul 12, 2016 · The telecommunications industry has attacked the Federal Communications Commission's proposed privacy regulations for internet service ...
  60. [60]
    What Individuals Should Do Now That Congress Has Obliterated the ...
    Apr 12, 2017 · Congress has voted to reverse new FCC privacy protections that would have required Internet service providers (ISPs) like Comcast, Verizon, ...Missing: controversy | Show results with:controversy
  61. [61]
    FCC Fines National Mobile Providers for Sharing Customer Location ...
    May 6, 2024 · With limited exceptions, telecommunications carriers need customer “opt-in” approval before disclosing that customer's CPNI.Missing: delivery | Show results with:delivery
  62. [62]
    FCC Adopts Updated Data Breach Notification Rules To Protect ...
    On December 13, 2023, the FCC adopts updated data breach notification rules to protect consumers. DA/FCC #: FCC-23-111. Docket No: 22-21.
  63. [63]
    Sixth Circuit Upholds FCC's 2024 Breach Notification Rules | Akin
    Aug 25, 2025 · Cyber threats continued to escalate, and in 2023 the FCC issued a Notice of Proposed Rulemaking to amend the Data Breach Notification Rule. In ...
  64. [64]
    FCC's data breach reporting rules for telecoms are upheld in ...
    Aug 14, 2025 · Under the regulations, telecom companies must report breaches involving 500 or more customers' PII within seven business days. The rules, ...
  65. [65]
    UPDATE: Sixth Circuit Upholds FCC Data Breach Order
    Aug 28, 2025 · The Sixth Circuit upheld the FCC's 2023 data breach order earlier this month. The court's decision in Ohio Telecom Ass'n v.
  66. [66]
    T-Mobile Settles with FCC for $15,750,000 Over CPNI Breaches and ...
    ... data breaches and privacy violations that occurred between 2021 and 2023. These incidents affected millions of current, former, and prospective T-Mobile ...<|separator|>
  67. [67]
    AT&T settles a 2023 data breach for $13M. Recent incidents are ...
    Sep 18, 2024 · AT&T settles a 2023 data breach for $13M. Recent incidents are much worse. Telecom cybersecurity remains a challenge with widespread impacts.
  68. [68]
    AT&T may pay customers up to $7,500 in $177 million data breach ...
    Aug 16, 2025 · Millions of AT&T customers can file claims worth up to $7,500 in cash payments as part of a $177 million settlement related to data breaches ...
  69. [69]
    FCC's Warning Shot to Mobile Network Operators on CPNI
    May 14, 2024 · Ultimately, the Commission found the Carriers violated the FCC CPNI rules, issuing $57.3 million, $46.9 million, $12.2 million, and $80.1 ...
  70. [70]
    Multiple Courts Confirm: Carriers Must Protect Your Phone Location ...
    Sep 23, 2025 · The Federal Communications Commission (FCC) has issued and updated regulations defining and scoping legal obligations of carriers regarding CPNI ...Missing: responsibilities | Show results with:responsibilities
  71. [71]
    EPIC Letter to FCC Enforcement Bureau and Privacy and Data ...
    Oct 17, 2024 · Location data: The Task Force and Bureau should investigate potential misuses of subscriber location data and bring enforcement actions as ...<|separator|>