Artificial Intelligence Policy Tracker
Search
Menu

AI policies in Utah (United States)

Search and filter source-backed AI laws, regulations, standards, guidance and consultations. Each record shows its status, key dates, verification state and official source.

Results

1 of 244 instruments match

Utah (United States) Act / statute In force Binding

Utah Artificial Intelligence Policy Act (SB 149)

Utah Artificial Intelligence Policy Act (SB 149, 2024, as amended by SB 226 and SB 332 in 2025)

Effective 1 May 2024, the Act requires a person using generative AI to interact with a consumer in a consumer transaction to disclose clearly that the consumer is interacting with AI when asked (as amended in 2025, when the interaction is high-risk or on request), and requires providers of regulated occupations (for example health and legal services) to disclose generative-AI use proactively. It states that using AI is no defence to consumer-protection violations, created the Office of Artificial Intelligence Policy and an AI learning laboratory allowing regulatory mitigation agreements, and originally sunset in 2025, extended to 2027.

Applies from 1 May 2024 Verified (reviewed by Bhaskar Bhatt; a factual check against the official source, not a legal review) Official source

Frequently asked questions

What counts as an AI policy instrument here?

Anything a government or standards body has actually issued: acts, regulations, executive orders, rules, national strategies, frameworks, guidance, codes of practice, voluntary standards and open consultations. Each record states which of those it is, whether it binds anyone, and links the official source it was read from.

Are these records legally verified?

A record is marked verified only after a named reviewer has opened its official source and confirmed each field. Anything that has not been through that carries "pending review" on the record itself, and the data-health document reports the current totals. Nothing here is legal advice.

How current is the information?

Every record carries the date its source document was published and the date it was last checked. A record not re-checked within the freshness window set by the verification policy is flagged as stale rather than quietly presented as current.

Can I reuse this data?

Yes. The records are published under CC BY 4.0 with attribution, and are available as CSV, newline-delimited JSON and a read-only REST API that needs no key. Cite the record URL, the date accessed and the official source alongside it.