ID.me terms required for IRS sign-in
- ID
- 47732
- Status
- summarized
- Published
- 18 Nov 2026, 8:51 AM
- Fetched
- 18 Nov 2026, 4:31 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://consumerrights.wiki/w/ID.me_terms_required_for_IRS_sign-in
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.0
- Created
- 18 Nov 2026, 4:31 PM
- Tags
- Audience
- developerssaas_founders
What happened
A Consumer Rights Wiki entry documents that US taxpayers signing into IRS online services via ID.me are bound by ID.me's own Terms of Service, which push disputes to a neutral arbitrator instead of a judge or jury unless the user opts out within 30 days of accepting. The entry also notes ID.me's privacy policy says it may use information for marketing and may transfer it in a sale or merger, and that ID.me replaced the traditional login on Treasury's TreasuryDirect savings-bond site on October 28, 2026 — the day before senators Ron Wyden and Elizabeth Warren asked Treasury and the IRS to explain why they keep using ID.me instead of the government-run Login.gov, which also works for IRS sign-in.
Why it matters
Two decisions worth stealing for your own product: (1) if you integrate a third-party identity/eKYC vendor, that vendor's arbitration clause and data-transfer-on-acquisition terms become terms your users are stuck with — read them before you wire the SDK into a signup flow; (2) the 30-day opt-out window is a real UX obligation, and burying it is what got this written up on a consumer-rights wiki with a Senate letter attached. If you have US tax or savings-bond obligations, note that Login.gov remains an alternative for IRS sign-in and IRS Direct Pay needs no sign-in at all.
Discussion angle
If you ship signup through a third-party identity provider, whose terms does your user actually agree to — and would you surface a 30-day arbitration opt-out to them, or does your flow silently forfeit it?