> 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/united-states-u.s.-privacy-regulations.md).

# United States (U.S.) privacy regulations

Expand the accordions below for support information and recommendations for each U.S. state privacy regulation currently supported by Didomi.

{% hint style="info" %}
If your consent notice utilizes the IAB Global Privacy Protocol (GPP) to support U.S. privacy regulations, [click here](/consent-management-platform-cmp/frameworks-regulations/iab-global-privacy-protocol-gpp.md) for more information.
{% endhint %}

<details>

<summary><strong>California</strong>: California Privacy Rights Act (CPRA)</summary>

Refer to the table below regarding default and recommended settings when configuring the California Privacy Rights Act (CPRA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for California, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Share my personal information</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my data for social security, driver's license, state identification card, or passport number</li><li>Use information that reveal account log-in, financial account, debit card, or credit card number in combination with any required security or access code, password, or credentials allowing access to an account</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal precise geolocation</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal racial or ethnic origin, religious or philosophical beliefs, or union membership</li><li>Use information that reveal mail, email, and text messages unless I am the intended recipient of the communication</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the California Privacy Rights Act (CPRA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/cn7rpGZ0qav4hln2IN8u">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your CPRA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the California Privacy Rights Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/ZpfcjpmbpvaLqJSLbKTU" alt="" width="516"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Colorado</strong>: Colorado Privacy Act (CPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Colorado Privacy Act (CPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Colorado, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal sex lift or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Colorado Privacy Act (CPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/Y32FJA2kte5objaxBdab">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your CPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Colorado Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/cVKWaDJ2PquOIHcbFHJz" alt="" width="516"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Connecticut</strong>: Connecticut Data Privacy Act (CTDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Connecticut Data Privacy Act (CTDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Connecticut, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal precise geolocation</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Connecticut Data Privacy Act (CTDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/1JC31zoVgfD60rKqZfsM">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your CTDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Connecticut Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/MDV5t3U11q4Pi2gz8mfr" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Delaware</strong>: Delaware Personal Data Privacy Act (DPDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Delaware Personal Data Privacy Act (DPDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Delaware, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis </li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal precise geolocation</li><li>Use information that reveal my status as transgender or nonbinary</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Delaware Personal Data Privacy Act (DPDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/8opAJTMOlh4pPHJcH3Lt">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your DPDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Delaware Personal Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/MzrbSRdV30tY5CESyBUJ" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Florida</strong>: Florida Digital Bill of Rights (FDBR)</summary>

Refer to the table below regarding default and recommended settings when configuring the Florida Digital Bill of Rights (FDBR) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Florida, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal precise geolocation</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Florida Digital Bill of Rights (FDBR):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/PjImDsLrG1VWvCls5Fso">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your FDBR configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Florida Digital Bill of Rights will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/FQdLJkuQ7SXOcovVdbv0" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Indiana</strong>: Indiana Consumer Data Protection Act (INCDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Indiana Consumer Data Protection Act (INCDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Indiana, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis </li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal precise geolocation</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Indiana Consumer Data Protection Act (INCDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your INCDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Indiana Consumer Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Iowa</strong>: Iowa Consumer Data Protection Act (ICDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Iowa Consumer Data Protection Act (ICDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Iowa, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis </li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal precise geolocation</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Iowa Consumer Data Protection Act (ICDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/BW1kH7lfH45VsiHVQci1">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your INCDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Iowa Consumer Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/jeQouHsdjKBZyDtncvqW" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Kentucky:</strong> Kentucky Consumer Data Protection Act (KCDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Kentucky Consumer Data Protection Act (KCDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Kentucky, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis </li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal precise geolocation</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Kentucky Consumer Data Protection Act (KCDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your KCDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Kentucky Consumer Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Maryland</strong>: Maryland Online Data Privacy Act (MODPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Maryland Online Data Privacy Act (MODPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Maryland, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Maryland Online Data Privacy Act (MODPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your MODPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Maryland Online Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Minnesota</strong>: Minnesota Consumer Data Privacy Act (MNCDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Minnesota Consumer Data Privacy Act (MNCDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Minnesota, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis </li><li>Use information that reveal precise geolocation</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Minnesota Consumer Data Privacy Act (MNCDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/o6bYr6Xkh7WgKqz4ExT3">state-specific</a> section of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your MNCDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Minnesota Consumer Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Montana</strong>: Montana Consumer Data Privacy Act (MCDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Montana Consumer Data Privacy Act (MCDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Montana, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal precise geolocation</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Montana Consumer Data Privacy Act (MCDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/ArjlnqKbMWd9BfDBBNrC">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your MCDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Montana Consumer Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Nebraska</strong>: Nebraska Data Privacy Act (NDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Nebraska Data Privacy Act (NDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Nebraska, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal precise geolocation</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Nebraska Data Privacy Act (NDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/3xAirZZY2qwH5tTsiCzO">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your NDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Nebraska Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>New Hampshire</strong>: New Hampshire Privacy Act (NHPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the New Hampshire Privacy Act (NHPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for New Hampshire, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal precise geolocation</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the New Hampshire Privacy Act (NHPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or s<a href="/pages/kwiMDRKUzDjm24OHry0m">tate-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your NHPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the New Hampshire Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>New Jersey</strong>: New Jersey Data Privacy Act (NJDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the New Jersey Data Privacy Act (NJDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for New Jersey, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal precise geolocation</li><li>Use information that reveal my status as transgender or nonbinary</li><li>Use information that reveal account log-in, financial account, debit card, or credit card number in combination with any required security or access code, password, or credentials allowing access to an account</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the New Jersey Data Privacy Act (NJDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/coixRB4alsrebAL3lvdF">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your NJDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the New Jersey Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Oregon</strong>: Oregon Consumer Privacy Act (OCPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Oregon Consumer Privacy Act (OCPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Oregon, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal precise geolocation</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal my status as transgender or nonbinary</li><li>Use information that reveal national origin</li><li>Use information that reveal my status as a victim of a crime</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Oregon Consumer Privacy Act (OCPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/9tOLkXVRggbxzDe7nAV6">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your OCPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Oregon Consumer Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Rhode Island</strong>: Rhode Island Data Transparency and Privacy Protection Act (RIDTPPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Rhode Island Data Transparency and Privacy Protection Act (RIDTPPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Rhode Island, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal precise geolocation</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Rhode Island Data Transparency and Privacy Protection Act (RIDTPPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> of the GPP String.</td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Tennessee:</strong> Tennessee Information Protection Act (TIPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Tennessee Information Privacy Act (TIPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Tennessee, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li><li>Use information that reveal precise geolocation</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Tennessee Information Privacy Act (TIPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/gS7ev6mwXRFIM1Nw7sZk">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your TIPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Tennessee Information Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Texas</strong>: Texas Data Privacy and Security Act (TDPSA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Texas Data Privacy and Security Act (TDPSA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Texas, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal precise geolocation</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Texas Data Privacy and Security Act (TDPSA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/0olGSvHQZlcvnIh10BUb">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your TDPSA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Texas Data Privacy and Security Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Utah</strong>: Utah Consumer Privacy Act (UCPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Utah Consumer Privacy Act (UCPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Utah, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis </li><li>Use information that reveal precise geolocation</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Utah Consumer Privacy Act (UCPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/89nSYpn7bJ2TrLvUMBSD">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your UCPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Utah Consumer Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Virginia</strong>: Virginia Consumer Data Protection Act (VCDPA)</summary>

Refer to the table below regarding default and recommended settings when configuring the Virginia Consumer Data Privacy Act (VCDPA) on a consent notice:

<table><thead><tr><th width="223"></th><th>Description</th></tr></thead><tbody><tr><td>Default territories</td><td>Automatically set for Virginia, United States</td></tr><tr><td>Recommended purposes</td><td><ul><li>Sell my personal information</li><li>Use my personal information for targeted advertising</li></ul></td></tr><tr><td>Recommended sensitive personal information (SPI) purposes</td><td><ul><li>Use information that reveal my racial or ethnic origin,</li><li>Use information that reveal religious beliefs</li><li>Use information that reveal mental or physical health condition or diagnosis</li><li>Use information that reveal precise geolocation</li><li>Use information that reveal sex life or sexual orientation</li><li>Use information that reveal citizenship or immigration status</li><li>Use information that reveal my genetic data</li><li>Use information that reveal my biometric data for the purpose of uniquely identifying an individual</li></ul></td></tr></tbody></table>

Refer to the table below for information on popular integrations with the Virginia Consumer Data Privacy Act (VCDPA):

<table><thead><tr><th width="243">Integration</th><th>Availability</th></tr></thead><tbody><tr><td>IAB Transparency and Consent Framework (TCF)</td><td>No</td></tr><tr><td>Google Consent Mode v2</td><td>No</td></tr><tr><td>IAB Global Privacy Protocol (GPP)</td><td>Yes. Supported via the <a href="/pages/yFMv9DoGtPgkA7H6KgLm">National section</a> or <a href="/pages/XFWbsPVKAqp3Q3sZ4hww">state-specific section</a> of the GPP String.</td></tr><tr><td>Global Privacy Control (GPC)</td><td><p>GPC is a privacy signal supported by several browsers for end-users to specify at the browser level that they do not want their data to be processed. When a GPC signal is detected, your VCDPA configured consent notice is adjusted to respect the end-user choice via GPC:</p><ul><li>A "GPC signal detected" icon is displayed in the notice.</li><li>All personal information will be set to <strong>Do not sell</strong> / <strong>Do not share</strong>.</li><li>Instead of <strong>Agree and Close</strong> there will be a <strong>Close</strong> button.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Consent notices configured for the Virginia Consumer Data Privacy Act will support the GPC signal automatically. Currently, it is not possible to deactivate GPC support for the consent notice.</p></div></td></tr></tbody></table>

<figure><img src="/files/Ss0SqtXf1zP4cZTeboTw" alt="" width="455"><figcaption></figcaption></figure>

</details>


---

# 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/united-states-u.s.-privacy-regulations.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.