FCC Proposal Would Require ID for Every New Phone Number – What’s Really at Stake?

The FCC’s claim: ID checks will curb illegal robocalls

On April 30, the Federal Communications Commission voted unanimously to require telecom providers to verify a customer’s government‑issued ID, legal name, physical address and, in many cases, an existing phone number before activating service. The agency says the move mirrors banking’s anti‑money‑laundering (AML) rules and will make it harder for “bad actors” to obtain a line and launch illegal robocalls. Fines would be levied per illegal call – $1,000 to $15,000 – shifting the financial risk onto carriers that fail to vet users adequately.

What’s actually new?

Aspect	Current practice	Proposed change
Verification	Most post‑paid contracts already require ID; prepaid phones can be bought with cash and no paperwork.	All voice services – including prepaid, pay‑as‑you‑go, and VoIP – must collect the same ID set.
Data retention	Carriers keep limited subscriber info for a few months.	Required to retain copies of ID documents for four years after a customer disconnects.
Watch‑list screening	Not standard for consumer activation.	Optional requirement to check new customers against law‑enforcement watchlists.
Penalty structure	Fines target carriers for failing to implement call‑blocking technology.	Per‑call fines for each illegal call placed by a poorly vetted subscriber.

The rule does not introduce new technical solutions for call‑blocking; instead it adds a bureaucratic layer that mirrors the KYC (Know‑Your‑Customer) regime used by banks.

Why the privacy backlash is justified

1. Loss of a rare anonymous channel

Prepaid phones bought with cash have long been a lifeline for:

• Journalists protecting sources from surveillance;
• Domestic‑violence survivors needing a quick, untraceable line;
• Whistleblowers and activists operating under repressive regimes. Requiring a government ID effectively ties every voice call to a legal identity, erasing the practical anonymity that still exists in the U.S. telecom ecosystem.

2. Data‑security risk

Storing scanned IDs for four years creates a high‑value target for data breaches. A 2024 breach of a major carrier’s subscriber database exposed millions of driver‑license numbers and addresses, leading to identity‑theft spikes. The FCC’s proposal does not specify encryption standards or audit regimes, leaving carriers to interpret “reasonable security” on their own.

3. Potential for mission‑creep

The rule invites future expansions, such as mandatory checks against broader government watchlists or integration with other surveillance programs. Once the infrastructure exists, adding new filters is a policy decision, not a technical hurdle.

Practical implications for different user groups

• Average consumer: May notice a longer activation process and a request for a photo of their driver’s license when buying a prepaid SIM online or in a store.
• Small‑business owners: Could face higher onboarding costs if they need to verify multiple employees or contractors for each line.
• Tech‑savvy privacy users: Might turn to encrypted messaging apps that rely on data‑only connections (e.g., Signal) or to satellite phones that operate outside the FCC’s jurisdiction.

How the proposal compares to existing AML rules

Banking AML regulations require identity verification for opening an account, but they also provide exemptions for low‑risk, low‑value accounts (e.g., a $100 cash deposit). The FCC draft does not include a similar risk‑based exemption for low‑cost prepaid plans, treating a $5‑a‑month phone line the same as a $2,000 post‑paid contract.

What’s missing from the FCC’s paperwork

1. Impact analysis – No quantitative estimate of how many robocalls would actually be prevented versus how many legitimate users would be deterred.
2. Technical alternatives – The agency could have funded advanced call‑authentication standards like STIR/SHAKEN, which are already being deployed, instead of defaulting to a KYC‑style approach.
3. Privacy safeguards – No clear guidelines on limiting secondary use of the collected ID data, nor on how carriers must respond to law‑enforcement data requests.

Possible workarounds and mitigations

• Use of virtual numbers: Services that provide VoIP numbers tied to existing, verified accounts could sidestep the ID requirement for new lines, though they may be subject to the same verification if the underlying carrier is covered.
• Adoption of end‑to‑end encrypted platforms: Moving critical communications to apps that do not rely on the public switched telephone network (PSTN) reduces exposure to the rule.
• Advocacy for a “low‑risk” exemption: Stakeholders could lobby for a carve‑out for prepaid plans under a certain price point, similar to the $100 cash‑deposit exemption in banking.

Bottom line

The FCC’s proposal is less a technical fix for robocalls than a policy decision to extend KYC‑style identity checks to the nation’s phone system. While the intent—to make it harder for scammers to obtain a line—is understandable, the trade‑off is the loss of one of the few remaining avenues for anonymous voice communication in the United States. Until the FCC provides a clear impact assessment and robust privacy safeguards, the rule poses significant risks to vulnerable populations and creates a new attack surface for data breaches.

---

For the full text of the FCC’s notice and the public‑comment portal, see the FCC website.