Part 2 of 2: His answers, incidents and checks
CASE 2026-ODP-01 · Posted Aug. 31, 2026 · Updated Oct. 17, 2026 · Page look updated Nov. 2, 2026
Click a question to see his answer.
"There are summaries of data privacy complaints on the privacy.utah.gov website. Currently the government data privacy act has the state auditor and the attorney general as the enforcement mechanisms."
"We have been creating what we call data governance models, which can be adopted by governmental entities to transparently show how an entity balances privacy, transparency and use of data/records. This would allow the public to have a single place they can go and review to see how data/records are governed, and if there is something wrong with the models, then the public could help to adjust the models by engaging with either the Utah Office of Data Privacy, or the Utah Privacy Commission."
"Data minimization is being built into the below mentioned data governance model. Minimization occurs at the point of collection, whereas retention and archiving requirements is what then applies to data/records after is already collected or created. When it comes to personal data entities are still required to meet all applicable records management requirements."
"The privacy program framework is based off of generally applicable, legal requirements that most cities and counties are already supposed to be following. Many cities and counties have adopted the framework with quite a few counties actually doing so in ordinance. Any third-party contractor that is processing personal data and records on behalf of a governmental entity has the same legal obligations under the government data privacy act as the government entity itself. This applies to software vendors or any other third parties."
"Office is NOT an enforcement mechanism, however we are helping to scale the use of standardized contract terms and conditions that ensure third parties are required to meet GDP requirements and cannot use state data or personal data in ways that are against individual Utahns' best interest."
"The legislature has defined what constitutes selling in the definitions of GDPA. My office will be receiving its first reports of such activities in December 2026. My experience has been that most entities do not have any desire to sell personal data. However, there are multiple places in Utah law where entities are required to make personal data available for a fee or for sale. Keep in mind that there are many public records that also contain personal data so there is a lot of personal data that can be made available at no cost."
"We have had this discussion a few times in public meetings with the Utah Privacy Commission. My office is also coordinating research on this topic to inform legislative recommendations. Current leading academics have acknowledged that almost any de-identified or anonymized data sets can be re-identified with a small set of data points and artificial intelligence is just making it easier and trivial to do so. I am currently spending time evaluating synthetic data as a possible alternative to de-identified or anonymized data as a possible better option. Because anonymized or de-identified data is trivial to re-identify my personal opinion is that sharing of such data sets should be phased out. My personal opinion is that governments should not sell personal data... The state does not yet have official policy on this topic, the discussions are ongoing."
"In Utah's government data privacy act there are some foundational guidelines and requirements related to scoring, predictive analytics, and requirements for my office to make recommendations related to automated decision-making. My ODP has published an initial version of a privacy impact assessment and are currently drafting an AI specific tool and AI policy templates that entities can utilize. I hope that in the next legislative session we can establish more clear guardrails in the government data privacy [act] relating to artificial intelligence."
These answers were given in spring 2025. Several things referenced in them have since moved forward on their own timeline:
SEDI — Utah's State-Endorsed Digital Identity program (SB 275) passed unanimously and took effect May 6, 2026, on the schedule officials described at the time.
The AI compliance tool Bramwell referenced as being drafted was presented publicly the following month: a Utah Valley University student, working with the university's Herbert Institute, built and demonstrated an AI-assisted privacy-compliance tool at the state's May 2025 Data Governance Summit.
The December 2026 reporting deadline he cited for data-monetization activity has not yet arrived as of this writing.
A second annual Data Governance Summit was held at UVU on May 21, 2026, where state officials described the privacy program as having moved from writing policy to implementing it.
Worth noting for comparison: Utah's privacy law for private businesses, the Consumer Privacy Act, spells out a specific penalty — up to $7,500 per violation, enforced by the Attorney General after a 30-day cure period. The Government Data Privacy Act — the one covering the government entities ODP oversees — doesn't appear to specify any comparable penalty amount. It names the State Auditor and Attorney General as the enforcement mechanism, which is exactly what Bramwell told Shauna directly, but without a stated dollar figure or fine structure attached to a violation.
Health records aren't covered by the Government Data Privacy Act the way most other personal data is. Per Utah's own "Privacy for Individuals" guidance (publicsafety.utah.gov), an individual's data privacy rights depend on which entity holds the data and what kind it is — GDPA covers general personal data held by governmental entities, but health information specifically falls under the federal Health Insurance Portability and Accountability Act (HIPAA) instead, a separate framework with its own rules.
For the University of Utah specifically: University of Utah Health's own patient privacy page states that every patient is given a Notice of Privacy Practices at their first visit — this is the actual document that tells you how your health information is used and shared, including for treatment, billing, health oversight investigations, law enforcement requests, organ donation, approved research, and "specialized government functions such as intelligence and national security." That notice, not a GDPA filing, is where an individual's visibility into health-data sharing comes from.
Separately, per the university's own reporting, GDPA still applies to the university as a governmental entity for personal data outside the health-records context — student and administrative records, for instance. The university created a new Chief Information Privacy Officer position in response, held by Jamie Ross, to centralize privacy compliance campus-wide beyond the health system's existing HIPAA program.
The scenario you're describing — a hospital or clinic scanning your ID, that visit data flowing through insurance, and ending up in a shared repository that connects hospitals "for continuity of care" — is a real, specific system: the Clinical Health Information Exchange (cHIE), run by the Utah Health Information Network (UHIN).
UHIN is a private nonprofit, founded in 1993 — not a governmental entity. Its cHIE connects roughly 90% of Utah's hospitals, 1,300+ providers, and holds records on more than 8 million patients, sending admit/discharge/transfer notifications so a hospital or clinic you visit can see what happened at a different one. That's the "continuity of care" framing your doctor's office would use.
Because UHIN isn't a governmental entity, the GDPA and ODP don't oversee it — even though the Utah Department of Health and Human Services is a UHIN member and interacts with it directly for Medicaid enrollment. What actually governs your data inside the cHIE is HIPAA, plus UHIN's own participation rules.
On opting out: UHIN provides a "CHIE Patient Participation" form — you fill it out, get it notarized, and mail it in to stop your records from being shared through the exchange. That's the individual's actual control point, separate from anything GDPA or ODP administers. Worth noting a shift over time: when the cHIE launched around 2010, participation required patients to actively consent (opt in) before their records were shared; a 2012 state Medicaid rule (R414-8) instead automatically enrolled Medicaid recipients in the cHIE while requiring the Department to notify them of their right to opt out. Current UHIN materials describe the same opt-out framing for patients generally — you're presumed to participate unless you file the form to stop it, a different default than the system started with.
Whatever the policies promise, here's the actual track record at these same institutions, from public news reporting:
March 2020: University of Utah Health disclosed a phishing attack that compromised employee email accounts and infected a workstation with malware. Later reporting put the number of affected patients at roughly 10,000; exposed information included names, birthdates, and clinical information.
2023, a wave of separate vendor breaches tied to University of Utah Health Plans (UUHP): a nationwide vulnerability in the MOVEit file-transfer software used by multiple UUHP vendors led to three distinct incidents in the same year. TMG Health's server was accessed between May 30 and June 2, 2023, exposing roughly 3,900 UUHP member records — names plus, depending on the individual, mailing address, email, phone number, date of birth, Social Security number, medical claims information, banking information, billing information, and medical treatment information. Separately, Virgin Pulse (a UUHP vendor for its HealthyU program) and Delta Dental (administering UUHP's Medicare Advantage dental benefits) each reported their own MOVEit-linked breaches the same year, affecting different groups of UUHP members. The same nationwide MOVEit vulnerability separately exposed University of Utah Advancement records (through vendor TIAA Kaspick) and more than 13,800 current and former university employees' dates of birth and Social Security numbers (through TIAA's own vendor relationship) — four separate breaches at the university traced to the same underlying software flaw.
March 2024: UHIN — the nonprofit running the cHIE described above — was affected by the Change Healthcare cyberattack, a major nationwide incident that disrupted claims and remittance processing across the U.S. health system. UHIN has publicly documented its response efforts; this wasn't a breach of UHIN's own systems, but it illustrates how dependent the state's health-data infrastructure is on a small number of national vendors.
In each case reported here, the affected organization stated there was no confirmed evidence the exposed data had been misused, and offered identity-monitoring services to those affected.
Yes — just not through the individual entity reports described above. Separate from ODP entirely, the independently-elected State Auditor's office has its own State Privacy Auditor, a position held by Nora Kurzova since her Senate confirmation in February 2025. Her office audits how more than 1,800 government entities handle personal data — and per the Auditor's own site, its reports "are publicly available and no GRAMA request is required to obtain any of this information from the Office." Reports going back at least 10 years are posted directly online.
What those audits have actually found, on the record:
The State Privacy Officer's FY2023 annual report reviewed 1,617 governmental entities against a basic legal requirement — posting a privacy policy statement on their website — and found only 34% compliant; 66% were not. The same report found that of the entities reviewed in depth, none had an "optimized" or "well-managed" privacy program; every one fell into the lowest ("ad-hoc") maturity category, meaning privacy practices existed only inconsistently and mostly in reaction to complaints or breaches, not as a codified program.
More recently, in 2025, a State Auditor's office review — triggered by an internal whistleblower complaint, not a routine audit — found that the Utah Department of Health and Human Services had more than 1,000 users with access to a database covering roughly 6 million records on more than 2 million Utahns, without procedures in place to adequately detect or manage data breaches. State Auditor Tina Cannon presented those findings to the Legislature's Social Services Appropriations Subcommittee.
So the verification path exists — it just runs through the Auditor's independent audit function, which produces public findings, rather than through the individual Privacy Program Reports that stay protected under GDPA.
1,617 government entities reviewed. From the State Privacy Officer Annual Report FY2023, as described above.
Laid end to end, here's the documented sequence this piece covers:
Utah built a statewide privacy framework (GDPA, 2024) and a new office to run it, appointing Bramwell as the state's first Chief Privacy Officer. Two additional oversight bodies were created alongside it — the Utah Privacy Commission and the five-member Privacy Governing Board — with membership drawn from a mix of elected officials, agency heads, and appointees. The entity meant to independently monitor privacy compliance for a specific new venture, the Nucleus Institute, was itself written into a 2025 law exempting it from the state's open-meetings and public-records laws. The annual report that would show which government entities are sharing or selling personal data was classified as a protected record, retrievable by ODP itself but not by the public. A 2026 law then moved the Privacy Commission's own administrative support from the independently elected State Auditor's office into GovOps — the same department that houses ODP and is run by the person Bramwell reports to, who also chairs the Governing Board that evaluates ODP's own authority.
None of these changes happened in secret — each is documented in a public bill, a public meeting record, or the agency's own website. Taken together, they raise questions worth asking directly:
This record doesn't answer those questions. It documents the sequence that makes them worth asking.
The full list of updates is on Part 1.
Tap a card to see what it means. The acronym cards are in Part 1.
Questions readers can ask public offices. More are in Part 1.
Posted Aug. 31, 2026. Updated Oct. 17, 2026: split into two linked parts with one plain-words page; added a short version, on-this-page links, words to know, large-print diagrams, questions to ask, connected Hive work, updates since posting, dated notes with newer records, and links for sources. Colors changed to White & navy and text made larger. Bramwell's answers are unchanged, word for word. No earlier facts or wording changed.
Christopher Bramwell's public responses, Utah County community Facebook group, spring and December 2025 (screenshots timestamped and retained). Utah's Government Data Privacy Act (HB 491, 2024 General Session), including Utah Code §§ 63A-19-301(5) and 63A-19-401.3, and Utah Code § 63G-2-305. HB 450 (2026 General Session). SB 98 (2024 General Session), Online Data Security and Privacy Amendments, amending the Protection of Personal Information Act (§ 13-44-101 et seq.). Utah SB 275 (State-Endorsed Digital Identity), effective May 6, 2026. Utah Valley University Herbert Institute, 2025 and 2026 Data Governance Summit program materials. Utah Office of Data Privacy staff, "About ODP," "Privacy for Individuals," "Privacy for Governmental Entities," and "Privacy Program Report" pages, and the Utah Privacy Governing Board and Utah Privacy Commission membership pages (privacy.utah.gov). Utah Privacy Commission meeting minutes, May 13, 2026. Utah Department of Public Safety, "Privacy for Individuals" page. University of Utah Health, "Patient Privacy" page. @theU, "Protecting your privacy" and "University of Utah Statement: MOVEit Vendor Data Incidents." UHIN/CHIE, "For Patients" and provider pages, and news/cybersecurity updates (uhin.org). Utah Administrative Rule R414-8, Electronic Personal Medical Records for the Medicaid Program. KSL.com, KSLTV, KUTV, Fox13, Deseret News, SecurityWeek, and Mid-Utah Radio reporting on University of Utah Health data breaches, 2020 and 2023. Office of the Utah State Auditor: "Audit Reports" page, State Privacy Officer Annual Report FY2023, State Privacy Auditor biography page, and news release confirming Nora Kurzova as State Privacy Auditor (Feb. 27, 2025) (auditor.utah.gov). Reporting on the 2025 Utah Department of Health and Human Services data-security audit.
Links for sources listed above (each opened Oct. 17, 2026):
New records used in the Oct. 17 update:
Utah Hive Politicsfrom the publisher of The Weber County HiveIndependent · Accountability · JournalismThe Weber County Hive and Utah Hive Politics: the people's publication. We investigate what's best for the public as a whole, not for any party or special interest group. We report public records. You decide.
Send a tipTips we checkedSee a mistake? Tell us
Independent accountability journalism. Public records only. We report; you decide.
We never name tipsters. When we correct a page, the fix and its date are shown on the page.
Transparency home · Master Index (Hive library) · Read on Substack