The Hive bee sealUtah Hive Politicsfrom the publisher of The Weber County HiveThe people's publication. We investigate what's best for the public as a whole, not any party or special interest.
Transparency · TR 300.14← Transparency home · ← Hive library (every repo)
Office of Data Privacy · Enforcement Record

What the Privacy Office Can and Can't Do

Part 1 of 2: The office, and how a complaint moves

Utah's Chief Privacy Officer, in his own words — plus the finding underneath all of it: the one report that would show who's sharing or selling personal data is shielded from public records requests.

CASE 2026-ODP-01 · Posted Aug. 31, 2026 · Updated Oct. 17, 2026 · Page look updated Nov. 2, 2026

New to this? Read it in plain words One short page covering both parts.
Transparency pages (33) · tap to open
  1. Transparency docketEvery case file, searchable
  2. Who Gets a Say · plain wordsUtah's primary and map rules, 2018–2026
  3. Holding Power · plain wordsHow the rules kept one party in charge
  4. Selling the Vote · plain wordsThe business of political marketing in Utah
  5. Lost Ideals · plain wordsWhat Utah promised its voters
  6. The Fracture · plain wordsWhy Utahns say no party represents them
  7. It Happened Before · plain wordsUtah controversies and how they ended
  8. The 2026 Amendments · plain wordsAmendments A and B on your ballot
  9. Amendment B: Myth vs. Fact · plain wordsClaims checked against the record
  10. Amendment B QuizTest what you know
  11. Who Sits at the Taxpayers Association's Table · plain wordsIts leaders, lobbyists, sponsors and their money
  12. Weber Housing Authority · plain wordsA commissioner, his wife and the authority that pays their company
  13. What the Privacy Office Can and Can't Do · plain wordsUtah's Chief Privacy Officer
  14. Counting the Jobs · plain wordsJob promises and what was reported
  15. Matt Brower · plain wordsThe board seat that never came up
  16. Ten Days · plain wordsThe Nilson Foundation's 501(c)(3) claim
  17. One Vote, Four Checks · plain wordsS.B. 258 and preliminary municipalities
  18. The Land Counties Can't Zone · plain wordsTrust land and county zoning
  19. SITLA: The Land Nobody Zones · plain wordsWho answers for trust land
  20. Tyson Leaves Eagle Mountain · plain wordsFive years after opening
  21. Behind the Bench · plain wordsJudge and lawyer complaints in Utah
  22. Wrong Room, Right Message · plain wordsA housing adviser in Heber City
  23. Every Weber County Property Tax Increase Since 2019 · plain wordsThe full list
  24. A New Line on the Bill · plain wordsRoy and Riverdale fire annexation
  25. Paying for the Next Station · plain wordsHow Weber Fire District funds growth
  26. Weber County's New Sales Tax · plain wordsA public vote, but no vote by the public
  27. Bills That Did the Opposite · plain wordsBait and switch, 2018 to 2026
  28. The Blank Box · plain wordsThree disclosure forms, one pattern
  29. Utah's Campaign-Finance Enforcement Gap · plain wordsComplaints filed, few penalties
  30. One Lake, Two Money Pots · plain wordsThe Great Salt Lake Trust Council
  31. Wells at the Top · plain wordsPowder Mountain's water
  32. Then vs. Now · plain wordsEarlier plans and later approvals in Ogden Valley
  33. West Haven's 6% Energy Tax · plain wordsA new line on the power bill

Start here

What is this? Utah has an office whose entire job is to protect your personal data when the government collects it — your address, your driver's license info, your kids' school records, whatever an agency has on file. This piece is a record of the man who runs that office, Christopher Bramwell, answering direct questions in his own words about what that office can actually do when something goes wrong.

What's the goal? Not to accuse anyone of wrongdoing. It's to lay out, plainly and in his own words, what protections exist, what gaps he's acknowledged himself, and one thing the law itself sets up: the one report that would show which agencies are sharing or selling your data is filed with the state but off-limits to the public. You can read the record and decide for yourself what it means.

Short version
  • Christopher Bramwell has been Utah's Chief Privacy Officer since August 2021 and directs the Office of Data Privacy (ODP).
  • ODP's own list of duties covers a framework, training, monitoring and complaint intake. Enforcement or audit authority isn't listed among them.
  • A complaint goes first to the agency's Chief Administrative Officer, then to the Data Privacy Ombuds for mediation. The Government Data Privacy Act names the State Auditor and Attorney General as the enforcement mechanism.
  • Marvin Dodge heads the department ODP sits in, and he also chairs the Privacy Governing Board that evaluates ODP's structure and authority.
  • Each agency's annual Privacy Program Report, which lists the personal data it shares, sells or buys, is a protected record. ODP can request it; the public cannot.

Quick reference

This piece uses several acronyms. Tap or click a card to see what it stands for.

Who he is

Christopher Bramwell was appointed by Gov. Spencer Cox in August 2021 as Utah's inaugural Chief Privacy Officer and serves as Director of the Utah Office of Data Privacy (ODP), leading privacy-program efforts for governmental entities statewide. He worked with the Legislature on the Government Data Privacy Act (HB 491, 2024 General Session) and led the Strategic Privacy Program Plan required under Executive Order 2023-06. Before this role, he spent seven years (2014-2021) as Director of Information Privacy and Security at the Utah Department of Human Services, following earlier information-security work at the U.S. Department of Homeland Security and Idaho State University's National Information Assurance Training and Education Center. He holds an MBA from Idaho State University, completed through the National Science Foundation's CyberCorps program, and a political science degree from Brigham Young University.

The office

Per ODP's own staff page (privacy.utah.gov), Bramwell's team consists of Micah Vorwaller (Deputy Chief Privacy Officer), George McEwan (Privacy Architect), Brian Nelson (Privacy Analyst), Shane Paul (Training Director), Lana Taylor (Data Privacy Ombuds), and Kaleena Sedghi (Communication Specialist). The office is based at 4315 South 2700 West, Taylorsville, UT 84129; general contact is officeofdataprivacy@utah.gov, (801) 657-0507.

ODP's own site lists its statutory duties as: building a privacy framework for governmental entities to use; reviewing privacy legislation for gaps and conflicts; providing privacy training to government employees; monitoring high-risk data-processing activities; coordinating incident response with the state's Cyber Center; coordinating with the State Archivist on records management; taking public complaints through the Privacy Ombudsperson; and offering expert assistance to entities on high-risk data processing "as resources permit." Enforcement or audit authority isn't listed among them.

How a complaint actually moves

Per ODP's own "Privacy for Individuals" page, an individual with a data-privacy complaint submits it first to the Chief Administrative Officer (CAO) of the governmental entity involved. If the CAO can't resolve it, the individual or the entity can then ask the Data Privacy Ombuds to mediate. Mediation is the described outcome — the page doesn't describe an enforcement or penalty step at that stage.

Show diagram: complaint routing How a data privacy complaint is routed A complaint goes first to the entity's Chief Administrative Officer. If unresolved, it goes to the Data Privacy Ombuds for mediation. Enforcement, when it happens at all, sits with the State Auditor or Attorney General, both independently elected offices — not with ODP. STEP 1 Entity's CAO if unresolved STEP 2 Data Privacy Ombuds mediation only ENFORCEMENT, IF ANY State Auditor or Attorney General ODP itself does not sit anywhere in this enforcement chain — it builds the framework and templates that precede it. SOURCE: PRIVACY.UTAH.GOV, "PRIVACY FOR INDIVIDUALS"; BRAMWELL'S OWN DIRECT QUOTE, ABOVE

Large-print version: where a complaint goes

Same steps as the diagram above, from ODP's "Privacy for Individuals" page.

flowchart TD
  A["You have a privacy complaint
about a government agency"] --> B["Step 1: that agency's
Chief Administrative Officer"] B -->|"if not resolved"| C["Step 2: Data Privacy Ombuds
mediation"] C -.->|"enforcement, if any"| D["State Auditor or
Attorney General"]
Note on the diagram above: the direct quote it points to is now in Part 2, The questions and his answers (first question).
Added Oct. 17, 2026: At the Privacy Governing Board's Dec. 15, 2025 meeting, Data Privacy Ombudsperson Lana Taylor "said that for FY2026 they have received 21 complaints, FY2025 had 19." The minutes say 11 of the 21 "were related to privacy practices of a governmental entity" and 10 to private entities. Source: board minutes, Dec. 15, 2025.
Added Oct. 17, 2026: ODP's own 2026 legislative update slides say H.B. 450 (2026), effective May 6, 2026, "Requires an individual to go directly to the chief administrative officer of a governmental entity to make a data privacy complaint instead of to the Ombuds." Source: ODP, 2026 Legislative Update.

How compliance is measured

Per ODP's own site, the Dec. 31, 2025 privacy-program deadline required each governmental entity to designate its own Chief Administrative Officer, complete its own privacy program report, and run its own self-assessment against ODP's maturity model to gauge how mature its privacy practices are. ODP's role in that process is to provide the framework, templates, and self-assessment tools — the assessment itself is done by the entity, not independently audited by ODP.

Separately, under Utah Code § 63A-19-301(5), ODP can grant an individual entity an extension or exemption from certain GDPA duties. When it does, the statute requires ODP to report which entity received it and why — but only to the Utah Privacy Governing Board, not to any enforcement body.

Added Oct. 17, 2026: At the Dec. 15, 2025 Privacy Governing Board meeting, Bramwell said, "Currently most entities are at level one," and "Currently this is about implementation, not compliance and will take time." Source: board minutes, Dec. 15, 2025.

Who oversees the office

The Utah Privacy Governing Board is a five-member advisory body that meets at least twice a year. Per its own description, its duties include recommending changes to state privacy policy, approving the Utah Privacy Commission's agenda, addressing issues the Ombudsperson raises, and evaluating the structure and authority of the Office of Data Privacy itself.

Its current members, per the board's own page: Marvin Dodge (Chair, Governor's designee), Tina M. Cannon (State Auditor), Rep. David Shallenberger (House Speaker's designee), Sen. Kirk Cullimore (listed as Senate Majority Whip, Senate President's designee — his current Senate title is Majority Leader as of Jan. 2025, so this listing may not be current), and John Dougall (Attorney General's designee).

Dodge, who chairs this board, is also the head of the Department of Government Operations — the department ODP sits inside (his title appears as "Commissioner" on the Governor's own cabinet page and as "Executive Director" on ODP's founding presentation; same office, inconsistent title). Per ODP's own founding presentation, Bramwell "reports directly to Marvin Dodge" in that role. The board that evaluates ODP's structure and authority is chaired by the same person Bramwell reports to.

Show diagram: the reporting loop The reporting loop between ODP, GovOps, and the Privacy Governing Board Christopher Bramwell reports to Marvin Dodge, head of the Department of Government Operations. Dodge also chairs the Utah Privacy Governing Board, the body whose job includes evaluating the structure and authority of Bramwell's own office. Christopher Bramwell Chief Privacy Officer, ODP reports to Marvin Dodge Head, Dept. of Government Ops also chairs Utah Privacy Governing Board evaluates ODP's structure and authority oversees SOURCE: UTAH PRIVACY GOVERNING BOARD MEMBERSHIP PAGE; ODP'S OWN FOUNDING PRESENTATION (PRIVACY.UTAH.GOV)

Large-print version: the reporting loop

From the board's membership page and ODP's founding presentation, as described above.

flowchart TD
  A["Christopher Bramwell
Chief Privacy Officer, ODP"] -->|"reports to"| B["Marvin Dodge
head of GovOps"] B -->|"also chairs"| C["Utah Privacy
Governing Board"] C -.->|"evaluates ODP's structure
and authority"| A C -->|"approves the agenda of"| D["Utah Privacy Commission"]
Checked Oct. 17, 2026: the board's page still lists Sen. Kirk Cullimore as "Senate Majority Whip (Senate President Designee)." Source: Utah Privacy Governing Board page.

The Privacy Commission

A separate body, the Utah Privacy Commission, sets data-privacy guidelines and best practices and reviews governmental technology use related to privacy and security. Its current membership (per privacy.utah.gov) includes David Sonnenreich (Chair), Brandon Greenwood, Don J. Wood, J. Tanner Jensen, Jason B. Shelton, Jeremy Baker, Jeremy Zabriskie, Kent Millington, Ryan Arbon, Sam Smith, Steven McCown, Tyler Reese — and Micah Vorwaller, ODP's own Deputy Chief Privacy Officer, who sits as a Commissioner on the same commission his office answers to.

Ryan Arbon is the Weber County Sheriff.

Three bodies, easy to conflate: ODP is the staffed office that does the day-to-day work. The Privacy Commission (this one) is a larger, ~13-member advisory body that sets guidelines and reviews government technology use — a mix of outside members and ODP staff. The five-member Privacy Governing Board (above) is a smaller, higher-level political body that approves the Commission's agenda and evaluates ODP's own structure and authority. None of the three is a subset of another; they're three separate bodies with different jobs.

Per the commission's own May 13, 2026 meeting minutes, the commission is in the process of administratively transitioning its website and communications from the Utah State Auditor's office to GovOps/ODP — moving its day-to-day home from an independently elected office to the department that houses ODP itself. HB 450 (2026 session) is the bill that authorizes this: it explicitly "transfers support of the Utah Privacy Commission from the state auditor's office to the Office of Data Privacy" and restructures the commission's membership. The same May 13 minutes show the Auditor's office maintains dedicated privacy-audit staff (an Assistant State Privacy Auditor and a Privacy Audit Outreach position), who presented on a data breach involving Instructure/Canvas and said a report would follow.

Added Oct. 17, 2026: The enrolled H.B. 450 (2026), "Data Privacy Amendments," lists Rep. David Shallenberger as House primary sponsor and Sen. Kirk Cullimore as Senate sponsor. Both are listed on this page as Privacy Governing Board members. ODP's 2026 legislative update says the bill also changed the commission so the Governor appoints "a member who is a private citizen representing the public" and the State Board of Education appoints a member for public education and "the privacy interests of students." Sources: H.B. 450 enrolled copy; ODP, 2026 Legislative Update.
Added Oct. 17, 2026: The May 13, 2026 minutes record the Instructure/Canvas item as "latest breach with Instructure / Canvas. They will publish their report." No State Auditor report on that breach was found in web searches on Oct. 17, 2026. Source: Privacy Commission minutes, May 13, 2026.

The report the public can't read

Every governmental entity is required to file an annual Privacy Program Report with ODP by December 31 each year, under Utah Code § 63A-19-401.3. The report has to include the types of personal data the entity shares, sells, or purchases; the legal justification for those activities; the categories of people or entities involved; any noncompliant data-processing activities found; and the plan to fix them.

Per ODP's own description of the report: "This report is considered a protected record under Utah Code § 63G-2-305 and may be requested by the Office." The report that would show which agencies are sharing or selling personal data — and to whom — is filed with the state but shielded from ordinary public records requests. ODP itself can request a copy. The public cannot.

It isn't the only example. Utah's 2024 breach-notification law (SB 98, amending the Protection of Personal Information Act) added similar language for a different document: when an entity reports a data breach to the Utah Attorney General or the Utah Cyber Center, that notification "may be deemed confidential and classified as a protected record" under certain conditions. So both the annual report on what data an entity shares or sells, and the notification an entity files after a breach, can end up shielded from the same public that was affected.

Checked Oct. 17, 2026: ODP's Privacy Program Report page reads, "The report must be shared with the Utah Office of Data Privacy on or before December 31 of each year," and "The report is a protected record under Utah Code § 63G-2-305." (Read as page text.) Bramwell's Aug. 19, 2026 slides to legislators say, "First reports will be submitted to the Office by Dec 31, 2026." Sources: ODP, Privacy Program Report page; Bramwell presentation, Aug. 19, 2026.

About this record

In spring 2025, Christopher Bramwell — Utah's Chief Privacy Officer and Director of the Office of Data Privacy (ODP) — responded publicly to a series of questions in a Utah County community Facebook group. He answered each question individually, in writing, on the public record. The exchange was screenshotted and timestamped at the time.

What follows is a record of what he said, in the order the questions were asked, with the statutory context needed to read each answer accurately. Where something has since changed, that's noted separately at the end.

His answers are in Part 2. Read the questions and his answers →

Updates since this was posted

News and records found online, with dates. Listed for information only.

More words to know

The Quick reference above explains the acronyms. Tap a card to see what these words mean.

Questions to ask, and whom to ask

Questions readers can ask public offices. The original "Questions worth asking" are in Part 2.

Office of Data PrivacyAfter the first Privacy Program Reports arrive by Dec. 31, 2026, will ODP publish any summary, such as how many entities report selling personal data?
Utah Privacy Governing Board (chair Marvin Dodge)What did the board recommend about ODP's "structure, placement within state government" and authority at its Sept. 23, 2026 meeting?
Your state senator and representativeShould the Government Data Privacy Act name a penalty, as the Consumer Privacy Act does for businesses?
Office of the State AuditorWhen will the report on the Instructure/Canvas breach, mentioned at the May 13, 2026 commission meeting, be posted?

Connected Hive work

Behind this piece

19
Sections in the original page
8
Answers from Bramwell, kept word for word
16
Records and articles opened for the Oct. 17 update
30
Searches run for the Oct. 17 update (estimate)
2
Parts in this series

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.

Sources

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.

Added Oct. 17, 2026

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 · Journalism

The 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