> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-global-privacy-protocol-gpp/gpp-string/u.s.-state-privacy-sections/utah-ucpa.md).

# Utah (UCPA)

The Utah privacy section will be set in the `gppString` for the end-user if the end-user's country/region/state is included in the region configuration for **Utah Consumer Privacy Act** in the GPP consent notice.

{% hint style="info" %}
[Click here](https://www.didomi.io/blog/utah-consumer-privacy-act) to learn more about the Utah Consumer Privacy Act on the Didomi blog.
{% endhint %}

<table><thead><tr><th width="107.13336181640625"></th><th width="88.5333251953125">Value</th><th>Description</th></tr></thead><tbody><tr><td>Section ID</td><td>11</td><td>The Utah privacy section is registered as Section ID 11 under the GPP.</td></tr><tr><td>API prefix</td><td><code>usut</code></td><td>The Utah privacy section is registered with API prefix <code>usut</code>.</td></tr></tbody></table>

### Section encoding

The table below details the various fields of the Utah privacy section.

{% hint style="warning" %}
**Note**: Be advised that Didomi currently does not provide support for the `KnownChildSensitiveDataConsents` field.
{% endhint %}

<table><thead><tr><th width="175.26666259765625">Field</th><th width="115.2000732421875">Data Type</th><th>Description</th></tr></thead><tbody><tr><td><code>Version</code></td><td>Integer</td><td>The version of the Utah privacy section used to encode the string.</td></tr><tr><td><code>SharingNotice</code></td><td>Integer</td><td>Notice of the Sharing of the Consumer's Personal Data with Third Parties.<br><br><code>0</code> Not applicable.<br><code>1</code> Yes, notice was provided.<br><code>2</code> No, notice was not provided.</td></tr><tr><td><code>SaleOptOutNotice</code></td><td>Integer</td><td>Notice of the Opportunity to Opt Out of the Sales of the Consumer's Personal Data.<br><br><code>0</code> Not applicable.<br><code>1</code> Yes, notice was provided.<br><code>2</code> No, notice was not provided.</td></tr><tr><td><code>TargetedAdvertisingOptOutNotice</code></td><td>Integer</td><td>Notice of the Opportunity to Opt Out of Processing of the Consumer’s Personal Data for Targeted Advertising.<br><br><code>0</code> Not applicable.<br><code>1</code> Yes, notice was provided.<br><code>2</code> No, notice was not provided.</td></tr><tr><td><code>SensitiveDataProcessingOptOutNotice</code></td><td>Integer</td><td>Notice of the Opportunity to Opt Out of the Processing of the Consumer’s Sensitive Data.<br><br><code>0</code> Not applicable.<br><code>1</code> Yes, notice was provided.<br><code>2</code> No, notice was not provided.</td></tr><tr><td><code>SaleOptOut</code></td><td>Integer</td><td>Opt-Out of the Sale of the Consumer’s Personal Data.<br><br><code>0</code> Not applicable.<br><code>1</code> Opted Out<br><code>2</code> Did Not Opt Out</td></tr><tr><td><code>TargetedAdvertisingOptOut</code></td><td>Integer</td><td>Opt-Out of Processing the Consumer’s Personal Data for Targeted Advertising.<br><br><code>0</code> Not applicable.<br><code>1</code> Opted Out<br><code>2</code> Did Not Opt Out</td></tr><tr><td><code>SensitiveDataProcessing</code></td><td>Array</td><td>Consents for each data activity (8) in the sensitive data category.<br><br><code>0</code> Not applicable.<br><code>1</code> No Consent<br><code>2</code> Consent<br><br><strong>1.</strong> Opt-Out of the Processing of the Consumer's Sensitive Data Consisting of Personal Data Revealing Racial or Ethnic Origin.<br><br><strong>2.</strong> Opt-Out of the Processing of the Consumer's Sensitive Data Consisting of Personal Data Revealing Religious Beliefs.<br><br><strong>3.</strong> Opt-Out of the Processing of the Consumer's Sensitive Data Consisting of Personal Data Revealing Sexual Orientation.<br><br><strong>4.</strong> Opt-Out of the Processing of the Consumer's Sensitive Data Consisting of Personal Data Revealing Citizenship or Immigration Status.<br><br><strong>5.</strong> Opt-Out of the Processing of the Consumer's Sensitive Data Consisting of Personal Data Revealing Medical History, Mental or Physical Health Condition, or Medical Treatment or Diagnosis by a Health Care Professional.<br><br><strong>6.</strong> Opt-Out of the Processing of the Consumer's Sensitive Data Consisting of Genetic Data for the Purpose of Identifying a Specific Individual.<br><br><strong>7.</strong> Opt-Out of the Processing of the Consumer's Sensitive Data Consisting of Biometric Data for the Purpose of Identifying a Specific Individual.<br><br><strong>8.</strong> Opt-Out of the Processing of the Consumer's Sensitive Data Consisting of Specific Geolocation Data.</td></tr><tr><td><code>KnownChildSensitiveDataConsents</code></td><td>Integer</td><td>Consent to Process Sensitive Data from a Known Child.<br><br><code>0</code> Not applicable.<br><code>1</code> No Consent<br><code>2</code> Consent</td></tr><tr><td><code>MspaCoveredTransaction</code></td><td>Integer</td><td>Publisher or Advertiser, as applicable, is a signatory to the IAB Multi-state Service Provider Agreement (MSPA), as may be amended from time to time, and declares that the transaction is a “Covered Transaction” as defined in the MSPA.<br><br><code>1</code> Yes<br><code>2</code> No</td></tr><tr><td><code>MspaOptOutOptionMode</code></td><td>Integer</td><td>Publisher or Advertiser, as applicable, has enabled “Opt-Out Option Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.<br><br><code>0</code> Not applicable.<br><code>1</code> Yes<br><code>2</code> No</td></tr><tr><td><code>MspaServiceProviderMode</code></td><td>Integer</td><td>Publisher or Advertiser, as applicable, has enabled “Service Provider Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.<br><br><code>0</code> Not applicable.<br><code>1</code> Yes<br><code>2</code> No</td></tr></tbody></table>

{% tabs %}
{% tab title="Example" %}

```json
{
  "Version": 1,
  "SharingNotice": 1,
  "SaleOptOutNotice": 1,
  "TargetedAdvertisingOptOutNotice": 1,
  "SensitiveDataProcessingOptOutNotice": 1,
  "SaleOptOut": 2,
  "TargetedAdvertisingOptOut": 2,
  "SensitiveDataProcessing": [0, 0, 0, 0, 0, 0, 0, 0],
  "KnownChildSensitiveDataConsents": 0,
  "MspaCoveredTransaction": 1,
  "MspaOptOutOptionMode": 1,
  "MspaServiceProviderMode": 2
}
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-global-privacy-protocol-gpp/gpp-string/u.s.-state-privacy-sections/utah-ucpa.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.