What every agency has to tell the state — and no one else
Under the Government Data Privacy Act, the chief administrative officer of every governmental entity in Utah — that includes Weber County and the Sheriff's Office — must file this report every year, by December 31.
The privacy program report has to include, by statute:
- How the entity has initiated its privacy program
- A description of its privacy practices and high-risk processing activities
- A list of the types of personal data the entity currently shares, sells, or purchases
- The legal basis for sharing, selling, or purchasing that data
- The category of individuals or entities the data is shared with, sold to, or purchased from
- The percentage of employees who've completed required data-privacy training
- A description of any non-compliant processing activities and the entity's plan to fix them
That last one matters specifically for Weber County: any ALPR activity implemented before May 7, 2025 — which covers the county's 2021 Flock contract — is required to already appear in this report as a documented non-compliant activity, with a stated strategy for bringing it into compliance by July 1, 2027.
Public versus protected: the explorer
The same statute that requires the report also tells you exactly what happens to it once it's written.
| What the statute says | Status | What it means in practice |
|---|---|---|
| The report "shall be considered a protected record" | Protected | Protected records under GRAMA can be withheld from a public records request — the default is non-disclosure, not disclosure |
|
Statute text
§ 63A-19-401.3(2)(a): "The report described in Subsection (1) shall ... be considered a protected record under Section 63G-2-305." What this means for a records requestProtected records are one of GRAMA's non-public classifications — alongside private and controlled records. An agency can lawfully deny a request for this report on that basis alone, without weighing public interest against disclosure the way it must for some other categories. | ||
| The report must be shared with the Office of Data Privacy "on or before December 31 each year" | State only | The state itself sees every entity's full report annually. The public does not get the same access. |
|
Statute text
§ 63A-19-401.3(2)(b): the report shall be "shared with the office, in accordance with Section 63G-2-206, on or before December 31 each year." Why it's worth flaggingSection 63G-2-206 is GRAMA's inter-governmental sharing provision — it lets one government office see another's protected records for official use. So the flow of information runs entirely within government: entity to ODP. The statute never routes a copy, a summary, or an aggregate version to the public. | ||
| The entity must retain the report for "no less than five years" | Exists, not visible | The record exists and is preserved — it's simply not classified as something the public can inspect |
|
Statute text
§ 63A-19-401.3(2)(c): the report must be "retained by the governmental entity for no less than five years." The gap this createsFive years of retained reports for Weber County, the Sheriff's Office, and every other entity in the state — a running documentary record of what's shared, sold, or non-compliant — sits on file the entire time, protected the entire time. | ||
| The Privacy Commission "may study and recommend which information ... should be a public record" | Future, discretionary | There is a path to making parts of it public — but it runs through a 14-member commission's own discretion, not a public right |
|
Statute text
§ 63A-19-204(2)(g): the commission may "study and recommend which information contained in the privacy program report described in Section 63A-19-401.3 should be a public record." Why "may" mattersNothing requires the commission to take up this study, on any timeline. It's a standing option the commission can exercise — or not. See the membership chart below for who sits on that commission now. | ||
| A new technology-transparency study is due to the Government Operations Interim Committee by November 2027 | Deferred | This is the section that started as a real authorization requirement for ALPR, facial recognition, drones, and cell-site simulators — see below |
|
Statute text
§ 63A-19-407(3): "On or before the November 2027 interim meeting, the office shall report the findings and recommendations of the study ... to the Government Operations Interim Committee, including any recommended legislation." What this used to beThis section began life as "Truth in Surveillance" — a real pre-deployment authorization requirement. It didn't survive committee. The full story is below. | ||
Click any row for the statute text and what it actually means.
The bill briefly had teeth. Then it didn't.
H.B. 450's introduced version contained a section literally titled "Truth in Surveillance." It is gone from the law Utah actually passed.
What the introduced bill would have required
Before implementing a facial recognition system, a drone for persistent aerial surveillance, a license plate reader, or a cell-site simulator, a governmental entity that isn't a state agency would have had to get authorization from its own elected legislative body, in an open public meeting — with a description of the technology, the data it collects, its risks, and how it would be governed. Entities that already had one of these systems running — Weber County's Flock cameras included — would have had to report to their legislative body by November 30, 2026, and obtain that authorization retroactively by May 6, 2027.
What actually passed
All of it was deleted — the authorization requirement, the deadlines, the definitions built around it. In its place: a non-binding joint study by the Office of Data Privacy and the Privacy Commission, due to the Government Operations Interim Committee by the November 2027 interim meeting. No authorization requirement. No legislative-body vote. No deadline for any individual agency to justify what it already has running.
How it happened, hour by hour — March 4, 2026
Neither chamber's standing committee ever voted on the bill that became law. The version every committee actually reviewed and approved is not the version Gov. Cox signed.
Utah had a dedicated privacy auditor. It doesn't anymore.
Before this session, Utah law created a specific, Senate-confirmed position — the state privacy auditor — with a detailed, mandatory job. H.B. 450 removes the position and folds a version of the job into the state auditor's office generally.
What the old law required, in detail
- A dedicated state privacy auditor, appointed with the advice and consent of the Senate
- Compile privacy practices of every governmental entity
- Identify annually which entities' practices pose the greatest privacy risk
- Audit each year "in as timely a manner as possible" — the highest-risk practices
- Trigger a mandatory public hearing within 90 days for any entity that receives a reform recommendation
What H.B. 450 replaces it with
- No dedicated position. No Senate confirmation requirement.
- One new line: "the state auditor may audit the privacy practices of governmental entities"
- The detailed duties above — compile, identify highest-risk, audit each year, 90-day hearing — are technically still on the books, word for word, just reassigned from a named officer to "the state auditor" generally
- Result: a real tension between a new permissive top line and an untouched mandatory paragraph now assigned to no one in particular
Privacy Commission membership, before and after
H.B. 450 restructures the 12-to-14-member Utah Privacy Commission, which develops standards and reviews government privacy practices. New seats highlighted.
Commission staffing and support also moves in this bill — from the State Auditor's office to the Office of Data Privacy itself, the same office the commission is partly meant to review.
What Utah knows versus what residents can see
Even the internal reporting lines don't fully agree with each other after this bill.
One thing worth checking on Weber County specifically
Law enforcement itself opposed the bill's original version
At the February 18, 2026 hearing, the Utah Chiefs of Police, the Chair of the Law Enforcement Legislative Committee, and the Utah County Sheriff all testified in opposition to the bill as introduced. The bill was held that day. By the time it returned as Substitute #2 on February 24, that opposition had softened to neutral testimony. What changed between those two versions to bring law enforcement off opposition hasn't been checked against this piece yet — worth pulling before publication if it bears on the auditor or surveillance-study sections above.
Utah built a detailed, mandatory report on exactly the questions this whole series has been asking — who agencies share data with, what's non-compliant, what the risks are. Then it classified that report as protected, deleted the one section that would have required public authorization before deploying surveillance technology, and replaced a Senate-confirmed auditor with a permissive line no one is required to act on.

