Veteran DATA Act

What happened: On April 15, 2026, the House Veterans' Affairs Subcommittee on Oversight and Investigations marked up and forwarded HR7280, the Veteran DATA Act, to the full committee by voice vote. The bill, introduced by Rep. Budzinski (D-IL-13) with two cosponsors, prohibits the VA Secretary from entering into contracts that would allow contractors to sell or otherwise disclose sensitive personal information for consideration. It also requires the VA to insert standard clauses in all 'covered contracts' barring monetization, sale, or misuse of veteran data and to issue guidance on enforcement. This is an authorization-only bill — it authorizes zero new funding. The mechanism is a procurement restriction and compliance mandate on existing and future VA contracts.

The money trail: There is no direct appropriation. The cost to the government is administrative (developing model contract clauses, training personnel). For contractors, the bill imposes a compliance cost — companies currently monetizing veteran data would need to stop, and all contractors must update their data-handling practices. No federal spending is authorized or directed toward any private entity.

Convergence: The related bill HR7241 (Protect Veterans from the THIEF Act) was referred to the same subcommittee. Both bills target the same objective: preventing VA contractors from profiting from veteran data. This convergence confirms a legislative theme — Congress is actively building a regulatory framework around veteran data privacy. However, neither bill creates a procurement opportunity or revenue stream for any public company. The connection is a shared policy goal, not a shared funding stream or technology class.

Structural winners and losers: The primary affected parties are VA contractors — IT services firms, healthcare data processors, and claims administrators. However, no specific public company is identified in the bill text, and the prohibition is on selling data, not on performing contract services. For large IT contractors ($GDIT, $LDOS, $SAIC, $CACI), veteran data-related revenue is a small fraction of total VA contracting. The compliance burden is likely manageable and could actually favor incumbents with established compliance infrastructure (Rule 23: regulatory moat). Competitive effects are too diffuse to warrant inclusion of any ticker at the 0.65 confidence gate.

Timeline: The bill has passed subcommittee. Next steps: full committee markup, House floor vote, Senate introduction/referral, and final passage. No Senate companion bill exists yet. The 119th Congress runs through January 2027, so there is legislative time remaining.