H.R. 1602 (119th)Bill Overview

Financial Privacy Act of 2025

Finance and Financial Sector|Congressional oversightCorporate finance and management
Cosponsors
Support
Bipartisan
Introduced
Feb 26, 2025
Discussions
Bill Text
Current stageCommittee

Placed on the Union Calendar, Calendar No. 14.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief
Plain-English summaryWhat this bill actually does

The Financial Privacy Act of 2025 requires the Treasury Secretary to report annually to key congressional committees about the number and retention of Bank Secrecy Act (BSA) reports and related FinCEN holdings. It mandates disclosure of written protocols governing agency access to FinCEN data, requires annual review and possible revision of those protocols in consultation with the DNI and Attorney General, and obliges the Secretary to provide protocols on request and notify committees of revisions within 30 days.

Why people may split

Privacy vs enforcement efficacy: protections versus operational secrecy

Watch point

Narrow oversight bill with modest burdens and a sunset; likely to attract bipartisan support but may face some law-enforcement pushback.

The Financial Privacy Act of 2025 requires the Treasury Secretary to report annually to key congressional committees about the number and retention of Bank Secrecy Act (BSA) reports and related FinCEN holdings.

It mandates disclosure of written protocols governing agency access to FinCEN data, requires annual review and possible revision of those protocols in consultation with the DNI and Attorney General, and obliges the Secretary to provide protocols on request and notify committees of revisions within 30 days.

The new section sunsets after seven years and the Act includes findings about the scale and sensitivity of BSA, SAR, CTR, Form 8300, and beneficial ownership reporting.

Passage40/100

Modest, administrative transparency measure with limited cost and a sunset increases chances, but national-security sensitivities and Senate hurdles reduce likelihood.

CredibilityPartial

How solid the drafting looks.

Contention60/100

Privacy vs enforcement efficacy: protections versus operational secrecy

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
Federal agenciesFederal agencies

These are examples from the analysis, not a ranked list of the most-affected groups.

Likely helped
  • Federal agenciesIncreases transparency on FinCEN holdings and agency access by providing annual report metrics and protocol disclosures…
  • Potential benefitStrengthens privacy safeguards by requiring annual protocol reviews to limit collection, retention, and dissemination o…
  • Potential benefitEnhances congressional oversight by mandating committee access to protocols and timely notice of revisions.
Likely burdened
  • Potential burdenImposes administrative and compliance costs on Treasury and FinCEN to compile detailed historical and annual reports.
  • Potential burdenDisclosure of protocols and query counts to committees risks exposing sensitive operational or investigative procedures.
  • Federal agenciesAdditional procedural requirements might slow interagency access, potentially delaying time-sensitive investigations.
03 · Why people split

Why the argument around this bill splits.

Privacy vs enforcement efficacy: protections versus operational secrecy
Progressive75%

Likely supportive as a transparency and privacy-strengthening step that increases congressional oversight of FinCEN data access.

Views the bill as a modest reform but insufficient without stronger limits on collection, retention, and public accountability.

May see the seven-year sunset as too temporary.

Leans supportive
Centrist70%

Views the bill as a pragmatic accountability measure that balances oversight and operational needs by involving DNI and AG in reviews.

Sees value in periodic reporting and clearer protocols, while worrying about administrative burden and potential harm to active investigations.

Would favor technical fixes to protect classified material and quantify costs.

Leans supportive
Conservative25%

Skeptical of new reporting obligations that could micromanage law enforcement and expose operational protocols.

While supporting congressional oversight in principle, likely opposes disclosures that might aid criminals or hinder investigations.

Prefers stronger exemptions for national security and operational secrecy.

Likely resistant
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood40/100

Modest, administrative transparency measure with limited cost and a sunset increases chances, but national-security sensitivities and Senate hurdles reduce likelihood.

Scope and complexity
24%
Scopenarrow
24%
Complexitylow
Why this could stall
  • Possible classified-information limits on sharing protocols with Congress
  • Intensity of law-enforcement or intelligence community opposition
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Privacy vs enforcement efficacy: protections versus operational secrecy

Modest, administrative transparency measure with limited cost and a sunset increases chances, but national-security sensitivities and Senat…

Unlocked analysis

Pro readers get the full perspective split, passage barriers, legislative design review, stakeholder impact map, and lens-based policy tradeoff analysis for Financial Privacy Act of 2025.

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis