The Utah Consumer Privacy Act in practice

This guide explains who the Utah Consumer Privacy Act (UCPA) covers, what it requires, and what changed in 2026, and lists the changes a privacy program needs for Utah residents.

The UCPA is the comprehensive Utah data privacy law for businesses that handle consumer data, codified at Utah Code Title 13, Chapter 61. The legislature enacted it as Chapter 462 of the 2022 General Session, and it took effect on December 31, 2023. This guide is not legal advice.

Where the UCPA stands in October 2026

Each change to the UCPA since it took effect is listed below, including two that start later.

DateChangeSource
December 31, 2023The UCPA takes effect.Laws of Utah 2022, Chapter 462
May 1, 2024Amendments to the definitions (13-61-101) and the exemptions (13-61-102). Synthetic data now counts as deidentified data.Laws of Utah 2024, Chapters 186 and 381
July 1, 2026Consumers get a right to correct inaccurate personal data.H.B. 418 (2025), Laws of Utah 2025, Chapter 468
January 1, 2027Motor vehicle manufacturers become subject to the UCPA, whatever their size.H.B. 357 (2026)
Model year 2030Covered vehicles must offer in-vehicle privacy controls.H.B. 357, new section 13-61-502

Who the UCPA applies to

Under section 13-61-102, a controller or processor is covered when it meets all three of these conditions:

  1. It conducts business in Utah, or it produces a product or service targeted to Utah residents.
  2. It has annual revenue of $25,000,000 or more.
  3. It meets at least one of two volume tests, listed below.

The two volume tests are:

  • it controls or processes the personal data of 100,000 or more Utah consumers in a calendar year
  • it controls or processes the personal data of 25,000 or more Utah consumers and gets over 50% of its gross revenue from selling personal data

The Utah statute does not say whether "annual revenue" means total revenue or revenue earned in Utah. Counting total revenue is the safer reading, because it makes more companies subject to the law. Virginia and Colorado have no revenue test at all.

A "consumer" is a Utah resident acting in an individual or household context, not anyone acting in an employment or commercial context. Data about employees, job applicants and business contacts therefore does not count toward the 100,000 threshold, and those people have no UCPA rights.

Exemptions

Section 13-61-102(2) exempts whole organizations and specific kinds of data. The exempt organizations are:

  • government entities, and contractors acting on behalf of a government entity
  • tribes
  • public and private institutions of higher education
  • nonprofit corporations
  • HIPAA covered entities and business associates
  • financial institutions and their affiliates governed by the Gramm-Leach-Bliley Act
  • air carriers

The exempt data includes HIPAA protected health information and several kinds of research and health-care quality data. It also includes FCRA-regulated consumer report activity and data handled under the Driver's Privacy Protection Act, FERPA and the Farm Credit Act. Data is also exempt when it is processed because a person applies to, works for, or contracts with a company, to the extent its use relates to that role. The same exemption covers that person's emergency contact details and data used to administer their benefits.

Worked examples

All five made-up examples below assume the company sells to Utah residents.

CompanyRevenueUtah dataCovered?
Online retailer$40 million120,000 Utah customersYes. It meets the revenue test and the 100,000 test.
Ad-tech firm$10 millionData on 500,000 Utah residents, mostly from data salesNo. It fails the revenue test. Virginia has no revenue test, so the same numbers for Virginia residents would bring the firm under Virginia's law.
B2B software company$200 million150,000 Utah users, all logging in with work accountsProbably not. Work users act in a commercial context, so they are not consumers.
Data broker$30 million, 60% from selling data30,000 Utah consumersYes, under the second volume test.
Car maker selling in UtahAnyAny connected-car dataYes from January 1, 2027, under H.B. 357.

Consumer rights

Section 13-61-201, as amended by H.B. 418, gives Utah consumers these rights:

  • Confirm and access. A consumer can confirm whether a controller processes their personal data and can access that data.
  • Delete. The right covers only personal data that the consumer provided to the controller. Data you bought, inferred or collected from other sources is outside the right.
  • Portability. A consumer can get a copy of data they previously provided, in a portable and readily usable format, where the processing is automated.
  • Correct inaccurate personal data, since July 1, 2026. The section on the correction right below gives the details.
  • Opt out of targeted advertising and of the sale of personal data.

Utah does not give a right to opt out of profiling or a right to appeal a refused request. Sensitive data gets a notice and an opt-out, not opt-in consent.

Two definitions in section 13-61-101 make the opt-outs narrower than in other states:

  • Sale means exchanging personal data for money. Colorado also counts other valuable consideration, not only money, so a data swap can be a sale in Colorado and not in Utah. Utah's definition also leaves out some disclosures to third parties. A disclosure is not a sale when its purpose matches what the consumer would reasonably expect, given the context in which they provided the data.
  • Targeted advertising means ads selected from a consumer's activity across nonaffiliated websites or apps over time. Ads based on activity on your own sites, ads based on the current search or page, and processing used only to measure ad performance, reach or frequency are excluded.

The correction right

As enacted in 2022, the UCPA had no right to correct inaccurate data. H.B. 418, "Data Sharing Amendments," added that right in the 2025 General Session. The new subsection says a consumer may request that a controller correct inaccuracies in their personal data, "taking into account the nature of the personal data and the purposes of the processing." The amendment took effect on July 1, 2026.

Correction requests have the same 45-day deadline as the other rights (13-61-203).

The Utah Digital Choice Act

H.B. 418 also created the Utah Digital Choice Act, which requires social media companies to support data portability and interoperability, including a user's "social graph." In 2026, H.B. 408 amended the Utah Digital Choice Act, which is now Title 13, Chapter 81. H.B. 408 takes effect on July 1, 2027.

Handling requests: deadlines, fees and authentication

A consumer submits a request by the means the controller sets, and the request must name the right (13-61-202). A parent or legal guardian exercises the rights of a known child under 13. Section 13-61-203 sets the response rules:

  • You must act on a request and tell the consumer what you did within 45 days of receiving it.
  • You may extend the period once by another 45 days if the complexity of the request or the number of requests makes the extension reasonably necessary. Before the first 45 days end, you must tell the consumer about the extension, its length and the reason.
  • If you decline a request, you must give the reasons within 45 days.
  • The first request in a 12-month period is free. You may charge a reasonable fee for a request, or refuse it, if the request is excessive, repetitive, technically infeasible or manifestly unfounded. You may also charge a fee or refuse if the request has a main purpose other than exercising a right, or if it is part of an effort to harass you. If you charge or refuse, you must show which of these grounds applied.
  • The 45-day deadline does not apply if you reasonably suspect a request is fraudulent and cannot authenticate it before the 45 days end. The statute sets no other deadline for that case.
  • If you cannot authenticate a request with commercially reasonable efforts, you do not have to comply, but you may ask the consumer for more information.

Section 13-61-303 adds two limits. You do not have to re-identify deidentified or pseudonymous data to answer a request. The access, deletion and portability rights do not apply to pseudonymous data if the information needed to identify the consumer is kept separate from the pseudonymous data, under technical and organizational controls.

If you already run a request workflow for Virginia or Colorado, Utah adds no new deadline. DSAR automation: building the data subject request workflow covers the request workflow, and Data subject access requests: how to respond, step by step covers intake and identity checks. The UCPA has no rule on authorized agents. Requests from Mine, Privacy Bee and other agent services covers requests that agent services send.

Controller and processor duties

Privacy notice. Under section 13-61-302, a controller must publish a clear, reasonably accessible privacy notice. The notice lists the categories of personal data you process, the purposes, how consumers exercise their rights, the categories of data you share with third parties, and the categories of those third parties. If you sell personal data or run targeted advertising, you must disclose clearly and conspicuously how consumers can opt out.

Sensitive data. Sensitive data covers data revealing racial or ethnic origin, religious beliefs, sexual orientation, citizenship or immigration status, or medical history and health conditions. It also covers genetic and biometric data processed to identify a person, and specific geolocation accurate within 1,750 feet. Before processing sensitive data collected from a consumer, you must give clear notice and an opportunity to opt out. For data about a known child under 13, you must follow the federal Children's Online Privacy Protection Act (COPPA). Virginia and Colorado require opt-in consent for sensitive data instead.

Security. A controller must keep reasonable administrative, technical and physical safeguards that fit the size, scope and type of the business and the volume and nature of the data.

Nondiscrimination. You cannot deny goods or services, charge a different price, or give a different quality because a consumer exercised a right. You may offer a different price or a discount to a consumer who opted out of targeted advertising, or as part of a bona fide loyalty, rewards or club card program. A contract term that waives or limits a consumer's rights is void.

Processor contracts. Under section 13-61-301, a controller and processor must sign a contract before the processor starts work. The contract sets the processing instructions, the nature and purpose of the processing, the type of data, the duration, and each party's rights and obligations. It binds each person who processes the data to confidentiality. The contract also requires the processor to sign a written contract with each subcontractor, and that contract must include the processor's obligations. A data processing agreement written for GDPR Article 28 already covers instructions, confidentiality and subcontractor terms. See Data processing agreement (DPA): what it must contain and Subprocessor lists and change notices.

Permitted processing. Section 13-61-304 lists processing the chapter does not restrict, such as legal compliance, fraud and security work, product repair and recalls, and internal analytics to improve a product. If you rely on one of these exceptions, you must show that the processing qualifies.

What Utah does not require. Utah has no data protection assessment duty, no universal opt-out signal mandate, and no appeal process.

Motor vehicle manufacturers from January 2027

H.B. 357 adds a second way to become subject to the UCPA. From January 1, 2027, the UCPA applies to any motor vehicle manufacturer whose vehicles are sold or leased in Utah and that collects, transmits or stores personal data through a vehicle data collection system. The revenue and volume tests do not apply to these manufacturers.

For model year 2030 and later, the bill requires in-vehicle privacy controls. Through the vehicle's own screen or controls, a consumer must be able to:

  • view the categories of personal data the vehicle collects
  • view the categories of third parties that receive the data
  • opt out of sales and targeted advertising
  • delete data the consumer entered into the vehicle or loaded from a connected phone

A manufacturer can offer the same controls in a website or app, but cannot require the consumer to use one. A manufacturer that receives a court order or a protective order must delete all personal data within five business days. Section 13-61-302 contains the notice, sensitive-data and security duties. H.B. 357 adds three exceptions to that section, and they apply only to motor vehicle manufacturers and data from their vehicles:

  • None of section 13-61-302 applies to data a vehicle collects only for safety, vehicle operation or legal compliance.
  • The whole section is also lifted for data the vehicle processes temporarily, keeps inside the vehicle, and stores no longer than necessary.
  • Only the consent requirements of section 13-61-302 are lifted for data collected for internal product improvement. The manufacturer must collect only the minimum data needed and use it only for that purpose.

Enforcement and the 30-day cure period

Two state agencies share enforcement:

  1. The Division of Consumer Protection runs the complaint system and may investigate (13-61-401). If the director finds reasonable cause to believe there is substantial evidence of a violation, the director must refer the matter to the Attorney General.
  2. The Utah Attorney General has exclusive authority to enforce the chapter (13-61-402). At least 30 days before suing, the Attorney General must send written notice of each alleged violation and the basis for it.

After the notice, a company can prevent the lawsuit in two steps:

  • cure the violation within 30 days
  • send the Attorney General an express written statement that the violation is cured and will not happen again

The Attorney General can sue a company that does not cure, or one that cures but then keeps violating the chapter. In either suit, the state can recover actual damages to consumers and up to $7,500 per violation. The money goes into the state's Consumer Privacy Account. When several companies share the same unlawful processing, liability is split by comparative fault. Under section 13-61-305, consumers cannot sue under the UCPA. Utah's right to cure does not expire, while Colorado's cure period ended on January 1, 2025.

The first enforcement case

On June 30, 2025, the Division and the Attorney General sued Snap Inc. in Utah state court. According to the Department of Commerce announcement, one of the three counts claims a UCPA violation. The state says Snap did not inform consumers about its data collection and processing. It also says Snap gave users and parents no opportunity to opt out of the processing of sensitive data such as biometric and geolocation data. We found no ruling on the privacy count as of October 2026.

How Utah privacy law compares with Virginia and Colorado

The table compares Utah with Virginia and Colorado. The Virginia column comes from the Consumer Data Protection Act, and the Colorado column from the Colorado Attorney General's guidance on the Colorado Privacy Act.

RuleUtahVirginiaColorado
Revenue test$25 million, plus a volume testNoneNone
Volume test100,000 consumers, or 25,000 consumers and over 50% of revenue from sales100,000 consumers, or 25,000 consumers and over 50% of revenue from sales100,000 consumers, or 25,000 consumers and any revenue or discount from sales
NonprofitsExemptExemptCovered
Employee and B2B dataExcludedExcludedExcluded
Correction rightYes, since July 1, 2026YesYes
Sensitive dataNotice and opt-outOpt-in consentOpt-in consent
Profiling opt-outNoYesYes
AppealsNoneYes, answered within 60 daysYes
AssessmentsNoneData protection assessmentsData protection assessments
Universal opt-out signalNot requiredNot requiredRequired since July 1, 2024
Response time45 days, plus one 45-day extension45 days, plus one 45-day extension45 days, plus one 45-day extension
Cure period30 days, no end date30 days60 days, ended January 1, 2025
EnforcerAttorney General, after a Division referralAttorney GeneralAttorney General and district attorneys
Civil penaltyUp to $7,500 per violation, plus actual damagesUp to $7,500 per violationSet by the Colorado Consumer Protection Act

A company that complies with Virginia or Colorado meets Utah's requirements once it adds two things: a Utah opt-out for sensitive data, and request tooling that recognizes Utah residents. California's law differs in two ways: it covers employee data, and its revenue test alone makes a company subject to the law. The CPRA and the 2026 CCPA regulations covers the California rules.

A preparation checklist

  1. Run the applicability test. Check total revenue first, then count unique Utah consumers from the last calendar year across product, marketing and support systems, leaving out business contacts and employees. Record the count and the method. The 100,000 test counts data you control or process, not only data you sell.
  2. Map where Utah data is stored. You need to know which systems hold the data before you can answer access or correction requests. Data mapping and discovery and Record of processing activities (ROPA): fields and template cover how to build the inventory.
  3. Mark the data the consumer provided. Utah's deletion and portability rights reach only data the consumer gave you. A source field in each system lets you limit those responses to that data. Without a source field, the only option is to delete all of a consumer's data, which also meets the rules of states with wider deletion rights.
  4. Turn on correction for Utah. If your request form hid the correction option for Utah residents before July 2026, remove that rule.
  5. Review sensitive data flows. List where you process health, precise location, biometric or demographic data. Give clear notice and an opt-out before processing. If you also operate in states that require opt-in consent, one opt-in consent flow also meets Utah's notice-and-opt-out rule.
  6. Update the privacy notice to cover every element in 13-61-302. Add a visible opt-out link if you sell data or run targeted ads.
  7. Check processor contracts. Confirm that each vendor that receives Utah consumer data has a contract with the 13-61-301 terms.
  8. Set deadlines. Configure 45-day deadlines, send any extension notice before day 45, and record the reason for every refusal.
  9. Prepare for a notice letter. Decide who receives Attorney General correspondence and who can sign the written cure statement. Keep evidence that each fix is in place, because the cure period is only 30 days.
  10. Add January 1, 2027 to your calendar if you build vehicles or connect to vehicle data.

FAQ

Do we need a cookie banner for Utah?

No consent banner is required, but you do need a clear way to opt out of targeted advertising and sales. Utah does not require you to honor Global Privacy Control, but many companies already honor it for California and Colorado.

Can a consumer sue us under the UCPA?

No. Section 13-61-305 gives consumers no right to sue. Only the Attorney General enforces the law, after a 30-day cure notice.

Is a nonprofit covered?

No. Section 13-61-102 exempts nonprofit corporations. Colorado's law covers nonprofits, so a nonprofit with Colorado supporters can still have state privacy duties.

Need this built?

We build request intake, data mapping and opt-out handling for state privacy laws. To discuss a Utah or multi-state setup, tell us about your project, and we will reply with questions or a rough plan.

For the other regulators you may deal with besides Utah's Attorney General, see Who regulates privacy where: powers, GDPR fines and penalties and the Data protection authority directory.

Privacy engineering notes by email

When we publish a new guide on data mapping, DSR automation or AI privacy, we send it to this list. Nothing else.