S. 1038 (119th)Bill Overview

TRACE Act

Crime and Law Enforcement|Computers and information technologyCongressional oversight
Cosponsors
Support
Lean Democratic
Introduced
Mar 13, 2025
Discussions
Bill Text
Current stageIntroduced

Held at the desk.

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

The TRACE Act requires the Attorney General (through the NIJ Director) to add a data field to the National Missing and Unidentified Persons System indicating whether a missing person’s last known location was confirmed or suspected to be on Federal land or in U.S. territorial waters, including specific unit or area details. It also mandates an annual report to the House and Senate Judiciary Committees counting cases involving Federal land or territorial waters, beginning the second calendar year after enactment.

Why people may split

Privacy and data-security concerns versus public-safety benefits

Watch point

Relative to its intended legislative type, this bill clearly prescribes a reporting/data-collection change and identifies responsible authorities and recipients for the reports.

The TRACE Act requires the Attorney General (through the NIJ Director) to add a data field to the National Missing and Unidentified Persons System indicating whether a missing person’s last known location was confirmed or suspected to be on Federal land or in U.S. territorial waters, including specific unit or area details.

It also mandates an annual report to the House and Senate Judiciary Committees counting cases involving Federal land or territorial waters, beginning the second calendar year after enactment.

Passage75/100

Targeted, low-cost administrative mandate with modest implementation burden; historically such technical reporting bills have high enactment rates.

CredibilityPartially aligned

Relative to its intended legislative type, this bill clearly prescribes a reporting/data-collection change and identifies responsible authorities and recipients for the reports. It provides useful definitional boundaries and a reporting cadence but omits funding and detailed implementation instructions.

Contention18/100

Privacy and data-security concerns versus public-safety benefits

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
Federal agenciesLikely burdened

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

Likely helped
  • Potential benefitProvides clearer national data to identify geographic patterns in missing person cases.
  • Federal agenciesHelps prioritize search and rescue resource allocation on Federal lands and waters.
  • Federal agenciesSupports interagency coordination by standardizing a Federal-land location data field.
Likely burdened
  • Potential burdenCreates additional administrative and IT costs for DOJ/NIJ and reporting agencies.
  • Potential burdenRaises privacy and data-security concerns about storing specific last-known location details.
  • Potential burdenThe "suspected" designation could generate inconsistent classifications and investigative confusion.
03 · Why people split

Why the argument around this bill splits.

Privacy and data-security concerns versus public-safety benefits
Progressive80%

Likely supportive because the bill improves data collection for missing persons on federal lands, aiding vulnerable populations and public safety.

Would want safeguards for privacy, data security, and consultation with Tribal governments because the bill excludes trust lands.

Leans supportive
Centrist85%

Generally favorable as a targeted, administrative measure to improve missing-person data and clarify jurisdiction.

Will focus on implementation details: costs, data quality, and proportionality of reporting requirements.

Leans supportive
Conservative70%

Likely supportive in principle because it is a narrow public-safety and data-collection measure, but cautious about centralizing personal-location data and unfunded federal responsibilities.

Would favor limits on scope and strong privacy protections.

Leans supportive
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Still ahead

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood75/100

Targeted, low-cost administrative mandate with modest implementation burden; historically such technical reporting bills have high enactment rates.

Scope and complexity
24%
Scopenarrow
24%
Complexitylow
Why this could stall
  • No cost estimate or funding authorization included
  • Data-privacy or victim-family sensitivity concerns not addressed
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 and data-security concerns versus public-safety benefits

Targeted, low-cost administrative mandate with modest implementation burden; historically such technical reporting bills have high enactmen…

Unlocked analysis

Relative to its intended legislative type, this bill clearly prescribes a reporting/data-collection change and identifies responsible authorities and recipients for the reports. It provides useful definitional boundarie…

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