> 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.md).

# U.S. State Privacy Sections

U.S. State Privacy sections are encoded into the GPP String (`gppString`) when the end-user's country/region/state is included in the region configuration for a particular U.S. State regulation for a Didomi consent notice integrated with the IAB Global Privacy Protocol (GPP).

> For example, if your organization wanted to encode the California privacy section in the `gppString` for end-users in California, your organization would need to ensure that **California** was enabled for the **California Privacy Rights Act** in the consent notice's country/region configuration.

<figure><img src="/files/aNCoVywO70KmuxylixJB" alt="" width="563"><figcaption></figcaption></figure>

### U.S. State privacy section identifiers

Each U.S. State privacy section in the `__gpp` function of the IAB Global Privacy Protocol (GPP) API is identified using two identifiers: section ID and API prefix. Refer to the table below to learn more about these identifiers:

<table><thead><tr><th width="121.58331298828125"></th><th width="118.8333740234375">Data Type</th><th width="393.6666259765625">Description</th><th width="142.24993896484375">Example</th></tr></thead><tbody><tr><td>Section ID</td><td>Integer</td><td>Canonical identifier assigned to each section in the GPP specification and used by header to encode which sections are present. </td><td><code>8</code></td></tr><tr><td>API Prefix</td><td>String</td><td>Human-readable identiffier assigned to each section in the GPP specification and used to retrieve and parse the section via API.</td><td><code>usca</code></td></tr></tbody></table>


---

# 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.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.