A little-known federal database just got slapped down by a judge for doing exactly what many warned it would do: put lawful American voters on the chopping block.
Story Snapshot
- A federal judge blocked the revamped SAVE citizenship database from use in elections after finding it broke privacy law and risked purging eligible voters.
- Trump’s order tried to turn a benefits-eligibility tool into a near-national voter file by merging Social Security, immigration, and other records.
- Critics say the system is riddled with bad or stale data that mislabels citizens as noncitizens, while supporters sell it as “election integrity.”
- The real fight is whether centralized federal data should decide who gets to stay on your state’s voter rolls.
What the judge actually shut down
U.S. District Court Judge Sparkle L. Sooknanan ruled that the Trump administration’s revamped version of the Systematic Alien Verification for Entitlements program, known as SAVE, is unlawful and can no longer be used as an election tool.
She found that recent upgrades turned SAVE into a centralized federal database pulling in sensitive personal data in ways Congress had explicitly forbidden decades ago, and that the agencies behind it “knew” they were crossing those legal lines.[1]
The administration had already run at least 67 million voter registrations through this system after expanding its reach in 2025, with about 25 states using it to scan their rolls.[1] Supporters pitched it as a simple way to scrub noncitizens from voter lists.
The court saw something very different: a tool that merged vast pools of data, invited false matches, and set up lawful citizens—especially naturalized ones—to be tagged as suspects and potentially removed.
How SAVE was built, and how it got stretched
Congress created SAVE so the Department of Homeland Security could help agencies decide whether immigrants qualified for certain public benefits, not to run mass checks on every American voter.[1][5]
United States Citizenship and Immigration Services guidance underscores that SAVE can only verify what exists in immigration records and cannot definitively prove that someone is a noncitizen. It was never designed as a yes-or-no citizenship switch for a national voter file.[5][8]
Trump’s 2026 election executive order sought to change that by directing the Department of Homeland Security and the Social Security Administration to compile “State Citizenship Lists” drawn from federal citizenship and naturalization records, Social Security data, SAVE, and other systems.[2][7] The idea sounds neat on paper: send each state an updated list of people confirmed as citizens.
In practice, it meant building what voting-rights lawyers describe as “interagency databases” and even a United States Citizenship and Immigration Services “data lake,” combining tax records, medical data, biometric files, and voter information into a single, target-rich system.[10]
Where the errors come from, and who gets hit first
Centralized systems like this fail in a very predictable way. Many naturalized citizens still appear as noncitizens in older federal files, and those stale records feed directly into SAVE and the new data lake.[10][12]
When a state cross-checks its voter rolls against those databases, the system may flag a “possible noncitizen” even for a longtime citizen who did everything right.
A bipartisan research group found that sweeping claims about large numbers of noncitizen voters almost always collapse on closer review, with most “hits” turning out to be outdated, incomplete, or mismatched data.[13]
States that tried similar tactics in the past offer a preview. In Arizona, Georgia, and Tennessee, cross-checks against driver’s license and federal immigration data produced long lists of supposed noncitizen registrants, only for many to be cleared once they submitted proof.[11]
Analysts describe these citizenship checks as blunt instruments that impose extra hurdles on everyone while hitting Latino and Asian American voters hardest, because they are more likely to be naturalized citizens or have changed names and documents over time.[11]
What states like North Carolina and Arizona are doing with SAVE
North Carolina’s State Board of Elections announced a formal agreement with United States Citizenship and Immigration Services to use SAVE to flag “possible noncitizens” on its rolls, with rules for notice and a chance to respond before removal.[4] On paper, that sounds cautious.
But the same guidance North Carolina cites also warns that states cannot simply run SAVE checks on all registrants without specific immigration identifiers, and that SAVE cannot determine noncitizenship.[5][8] When you try to use a scalpel like a chainsaw, you get splinters.
Maricopa County, Arizona, signed its own agreement with Homeland Security to use the federal database for “voter list maintenance” and citizenship verification.[9]
Local critics, including a former county recorder, have pointed to “widespread errors” in similar efforts elsewhere and raised concerns about Social Security–based searches that bypass SAVE’s extra verification steps.[9][12]
Yet the Department of Homeland Security has not released basic accuracy metrics for these voter-related queries, leaving both sides arguing from fragments rather than full data.
The dilemma: secure elections without a federal super-database
Many care deeply about clean voter rolls, and they are right that only citizens should vote. They are also right to distrust sloppy state list maintenance.
But turning a benefits database into a de facto national voter file by merging Social Security, immigration, tax, and medical data runs counter to small-government and privacy instincts that used to define the right.
Congress barred centralized citizen databases for a reason, and Judge Sooknanan’s ruling leans heavily on those limits.[1][7]
“Under new rules governing several homeland security grant programs, states must take a number of steps, including phasing out certain electronic voting systems and moving to hand-marked paper ballots. They must also run their voter rolls through a controversial Department of…
— Jennifer Asper (@j3669) June 23, 2026
Election integrity has to mean more than “trust whatever Washington’s master file says.” A better path would demand transparent, audited list maintenance that stays close to the states, uses clear due process before any removal, and treats federal data as one imperfect clue, not the final verdict on anyone’s right to vote.
The judge’s message is blunt: if we are going to guard the ballot box, we have to guard Americans’ data and due process at the same time—or we are not conserving much of anything.
Sources:
[1] Web – Judge blocks use of federal database to check citizenship, saying it …
[2] YouTube – Judge blocks Trump admin’s federal voter-screening database
[4] Web – States Already Enacting Harmful SAVE Act Policies, Requiring Proof …
[5] Web – State Board to Check Voter Rolls to Identify, Remove … – NCSBE.gov
[7] Web – The “Proof of Citizenship” Trap – Rock the Vote
[8] Web – Proof of citizenship requirements for voter registration by state
[9] Web – Series Legislative Approaches to Ensuring Only Citizens Vote
[10] Web – Judge blocks use of federal database to check citizenship – Facebook
[11] Web – What Adding Motor Vehicle Data to USCIS’s SAVE System Means …
[12] Web – Using the Systematic Alien Verification for Entitlements (SAVE …
[13] Web – Issue Brief: Examining Changes to USCIS’s SAVE System
