Utah Wants a Cleaner Voter File Without Leaving the Personal Data Wide Open.

What should the state be able to prove before removing a name from the voter roll?

Senate Bill 153 strengthens the procedures and record access used to identify registrations tied to people who died, moved, registered twice, or became otherwise ineligible.

Picture an election clerk receiving a possible match between a voter and a death record. The names agree, but the middle name or birth date does not. A second source may show that the registered voter is alive. SB153's value depends on whether the clerk treats the first match as a lead to verify or as an automatic command to remove.

The same problem appears with moves and duplicates. A college student may use a family address, a military voter may be away for years, and two people may share common identifying details. List maintenance needs matching standards strong enough to distinguish an ineligible record from an unusual but lawful life.

Accurate removal protects every lawful vote. A weak match can also target the wrong person. Two voters may share a name and birth year. A change of address may be temporary. A citizen may choose not to vote for several elections and remain fully eligible.

The safeguard lives in the next steps: reliable source matching, notice, time to respond, a correction process, and a record showing why the registration changed.

Notice should identify the proposed change and give the voter a usable response route online, by mail, and in person. If the state removes or inactivates the record, it should retain the evidence and decision long enough for an audit, election contest, or wrongful-removal claim.

House Bill 361 consolidates election-administration functions and revises access to voter information. Some fields must remain available for election verification, public oversight, and lawful political activity. Sensitive identifiers can expose a voter to fraud, harassment, or bulk misuse.

Picture a campaign requesting a voter list for door-to-door outreach, a journalist testing whether registrations were handled consistently, and a data broker seeking the same file for resale. The first two uses can support political participation and public oversight. The third can turn a civic record into a commercial profile. Access rules should distinguish the requester, fields, purpose, and downstream use.

Consolidation can make statewide administration more consistent, but it also places more valuable data behind fewer doors. Role-based permissions, multifactor access, download limits, audit logs, breach notice, and penalties for misuse should follow the centralized file.

The public needs a field-by-field rule showing what is open, what is restricted, who may request it, how long it is kept, and who accessed it. “Voter data” is too broad a label for records that range from public registration information to sensitive personal identifiers.

The state should publish a data dictionary that answers those questions in plain language. A voter should be able to learn which information is public, request correction, and see the safeguards around restricted identifiers without becoming an election-law specialist.

Utah is cleaning the voter file and redrawing the privacy lines around it. Both tasks depend on a record someone can audit.

Utah should be able to explain why a voter's registration changed and show who accessed that voter's personal data, when they accessed it, and why.

This is our read of the laws. We encourage you to read them yourself and reach your own conclusions.