# Tennessee (TIPA)

The Tennessee 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 **Tennessee Information Protection Act** in the GPP consent notice.

{% hint style="info" %}
[Click here](https://www.didomi.io/blog/tennessee-data-privacy-law) to learn more about the Tennessee Information Protection Act on the Didomi blog.
{% endhint %}

<table><thead><tr><th width="106.20001220703125"></th><th width="85.7332763671875">Value</th><th>Description</th></tr></thead><tbody><tr><td>Section ID</td><td>22</td><td>The Tennessee privacy section is registered as Section ID 22 under the GPP.</td></tr><tr><td>API prefix</td><td><code>ustn</code></td><td>The Tennessee privacy section is registered with API prefix <code>ustn</code>.</td></tr></tbody></table>

### Section encoding

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

<table><thead><tr><th width="167.800048828125">Field</th><th width="116.4000244140625">Data Type</th><th>Description</th></tr></thead><tbody><tr><td><code>Version</code></td><td>Integer</td><td>The version of the Tennessee privacy section used to encode the string.</td></tr><tr><td><code>ProcessingNotice</code></td><td>Integer</td><td>Notice of the Processing of Personal Information.<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 Sale of the Consumer’s Personal Information.<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 Information 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>SaleOptOut</code></td><td>Integer</td><td>Opt-Out of the Sale of the Consumer’s Personal Information.<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 Information 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> Consent to Process the Consumer’s Sensitive Data Consisting of Personal Information Revealing Racial or Ethnic Origin.<br><br><strong>2.</strong> Consent to Process the Consumer’s Sensitive Data Consisting of Personal Information Revealing Religious Beliefs.<br><br><strong>3.</strong> Consent to Process the Consumer’s Sensitive Data Consisting of Personal Information Revealing a Mental or Physical Health Diagnosis.<br><br><strong>4.</strong> Consent to Process the Consumer’s Sensitive Data Consisting of Personal Information Revealing Sexual Orientation.<br><br><strong>5.</strong> Consent to Process the Consumer’s Sensitive Data Consisting of Personal Information Revealing Citizenship or Immigration Status.<br><br><strong>6.</strong> Consent to Process the Consumer’s Sensitive Data Consisting of Genetic Data that May Be Processed for the Purpose of Uniquely Identifying an Individual.<br><br><strong>7.</strong> Consent to Process the Consumer’s Sensitive Data Consisting of Biometric Data that May Be Processed for the Purpose of Uniquely Identifying an Individual.<br><br><strong>8.</strong> Consent to Process the Consumer’s Sensitive Data Consisting of Precise Geolocation Data.</td></tr><tr><td><code>KnownChildSensitiveDataConsent</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>AdditionalDataProcessingConsent</code></td><td>Integer</td><td>Consent to Processing of the Consumer’s Personal Information that Is Not Reasonably Necessary for nor Compatible with the Disclosed Purpose(s) for which the Consumer’s Personal Information Was Processed.<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><tr><td><code>Gpc</code></td><td>Boolean</td><td>Is Global Privacy Control enabled for the vendor list and detected on the end-user's browser?</td></tr><tr><td><code>GpcSegmentType</code></td><td>Integer</td><td>Possible values: <code>0</code> = Core | <code>1</code> = GPC</td></tr></tbody></table>

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

```json
{
  "Version": 1,
  "ProcessingNotice": 1,
  "SaleOptOutNotice": 1,
  "TargetedAdvertisingOptOutNotice": 1,
  "SaleOptOut": 2,
  "TargetedAdvertisingOptOut": 2,
  "SensitiveDataProcessing": [0, 0, 0, 0, 0, 0, 0, 0],
  "KnownChildSensitiveDataConsent": 0,
  "AdditionalDataProcessingConsent": 0,
  "MspaCoveredTransaction": 1,
  "MspaOptOutOptionMode": 1,
  "MspaServiceProviderMode": 2,
  "Gpc": false,
  "GpcSegmentType": 0
}
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.