If your company has received a consumer data request from a Utah resident, you need to understand what the law requires, how quickly you must respond, and what information must be redacted before you send the response. This guide covers the Utah Consumer Privacy Act (UCPA) in practical terms — what it means for your business, not just what the statute says.
These requests are formally known as Data Subject Access Requests (DSARs) under European law, or consumer privacy requests under U.S. state law. Regardless of the terminology, the obligation is the same: locate the consumer's personal data, review it, redact third-party personal information, and respond within the statutory deadline.
For a comparison of all US state privacy laws, see our comprehensive comparison page. For state-specific guidance, see our guides for California, Virginia, Colorado.
The Utah Consumer Privacy Act (UCPA) (Utah Code §§ 13-61-101 through 13-61-404) took effect on December 31, 2023.
Applicability thresholds: Conducts business in Utah or produces products or services targeted to Utah consumers, has annual revenue of $25 million or more, AND either: (a) controls or processes personal data of 100,000 or more Utah consumers per year, OR (b) derives over 50% of gross revenue from the sale of personal data and controls or processes data of 25,000 or more consumers.
Exemptions: State and local government, HIPAA-covered entities, GLBA-covered entities, nonprofits, institutions of higher education, tribes, air carriers.
Physical presence: No physical presence required.
Practical note: If you are unsure whether your business meets the thresholds, consult with your legal team. The penalties for non-compliance are significant, and "we didn't know the law applied to us" is not a recognized defense.
Under the UCPA, Utah consumers have the following rights regarding their personal data:
Utah's law is considered the most business-friendly US privacy law. There is no right to correct data. The right to delete is limited to data provided directly by the consumer. Sensitive data requires opt-in consent but the definition is narrower. No universal opt-out mechanism requirement.
You have 45 calendar days from receipt of the request to provide a substantive response.
Extensions: One additional 45-day extension with notice.
When the clock starts: Upon receipt.
Controllers may charge a reasonable fee for manifestly unfounded, excessive, or repetitive requests.
Critical point: The deadline runs from when you receive the request, not from when you finish verifying the consumer's identity. Do not wait to begin processing until verification is complete — start locating and reviewing the data immediately.
When you compile documents for a consumer data request response, you will inevitably find personal information belonging to other people — colleagues, clients, family members, business contacts. This third-party data must be redacted before you send the response to the requesting consumer.
Some categories of information require case-by-case assessment:
The entire point of a consumer data request is to give the individual access to their own data. Do not redact the requester's personal information. This includes their name, email, phone number, address, employment records, transaction history, and any other data that relates to them specifically.
This is what makes data request redaction different from standard document redaction. You are performing selective redaction: keeping one person's data while removing everyone else's. Automated tools that simply blank out all PII will over-redact and produce an unusable response.
Penalties: Up to $7,500 per violation.
Enforcement: Utah AG and Utah Division of Consumer Protection. No private right of action.
Cure period: 30-day cure period (does not expire — permanent).
No notable enforcement actions as of 2026. Utah's permanent cure period and higher thresholds make it the least aggressive of the comprehensive state privacy laws.
Risk note: Even where a cure period exists, it typically applies only to the first violation. A pattern of non-compliance or a failure to cure within the allowed period can result in full penalties. The cost of responding correctly the first time is significantly lower than the cost of enforcement.
SafeRedact automates the most time-consuming part of responding to consumer data requests: identifying and redacting third-party personal information across thousands of documents.
Need to respond to a data privacy request?
SafeRedact detects and removes third-party PII from documents automatically. Files never leave your browser.