ID.me terms required for IRS sign-in

US taxpayers and savings bond holders are increasingly being pushed to verify their identities through ID.me, a private company that collects sensitive personal and biometric data, in order to access IRS and TreasuryDirect services. Commenters question why the government relies on a commercial, .me-based provider when it already operates login.gov, raising concerns about privacy, exclusion of people without smartphones or certain phone plans, potential grift, and the difficulty of accessing or redeeming bonds. Some note that a recent federal mandate is supposed to expand login.gov across agencies, but point out that existing contracts and high fraud-prevention requirements have entrenched ID.me in the meantime.

Use of ID.me vs Login.gov for IRS and TreasuryDirect

  • IRS recently added Login.gov as a sign-in option; support appears very new (weeks old).
  • Historically IRS used ID.me, including selfie/biometric verification; some say IRS/Treasury moved to ID.me in 2021–2022.
  • TreasuryDirect and VA.gov also now require or strongly push ID.me; Treasury has already paid tens of millions and could pay up to $1B under contracts.
  • White House guidance now mandates agencies adopt Login.gov for public-facing sites within ~2 years; why ID.me was expanded shortly before this is debated.

Privacy, Surveillance, and Civil Liberties Concerns

  • Many object to giving extensive personal and biometric data to a for‑profit company for access to core government services.
  • Fears about government and contractors building centralized identity+face databases, enabling pervasive tracking and abuse.
  • Some refuse REAL ID or biometric-based verification on principle; see this as step toward ubiquitous national ID and increased surveillance.

Access, Equity, and Usability Issues

  • ID.me often demands smartphones, specific phone plan types, or high-quality cameras; this excludes retirees, low-income users, VOIP users, and ex‑pats.
  • Login.gov and ID.me both sometimes reject VOIP or prepaid numbers based on fraud‑risk scoring sourced from carriers.
  • Some users cannot complete ID.me due to minor data mismatches (e.g., address off by one digit).
  • Paper or mail-based processes still exist for IRS and TreasuryDirect, but are slow (months+) and increasingly de‑emphasized.

Security and Fraud Justifications

  • Supporters argue ID.me met stricter NIST digital identity (IAL2) standards and remote proofing requirements that Login.gov did not at the time.
  • Others counter that paper tax returns and refunds still work without comparable ID checks, so NIST requirements are a “fig leaf” and alternatives like mail-based account activation were possible.
  • Scale of tax refund fraud is cited as justification; critics say login vendors do little to stop other forms of fraud and mostly add friction for honest users.

Political and Governance Themes

  • Many see this as classic government contracting and “privatization” of core state functions, benefiting well‑connected vendors.
  • Some call it corruption or “grift,” arguing the government already operates Login.gov and should not outsource identity to a marketing-oriented company.
  • Others note Login.gov itself had serious compliance and oversight failures, undermining trust in the in‑house alternative.