> 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/regulations-manager/frameworks/global-privacy-protocol-gpp/gpp-string/u.s.-state-privacy-sections/indiana-incdpa.md).

# Indiana (INCDPA)

The Indiana 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 **Indiana Consumer Data Protection Act** in the GPP consent notice.

{% hint style="info" %}
[Click here](https://www.didomi.io/blog/indiana-consumer-data-protection-act-incdpa) to learn more about the Indiana Consumer Data Protection Act on the Didomi blog.
{% endhint %}

<table><thead><tr><th width="120.199951171875"></th><th width="87.13336181640625">Value</th><th>Description</th></tr></thead><tbody><tr><td>Section ID</td><td>25</td><td>The Indiana privacy section is registered as Section ID 25 under the GPP.</td></tr><tr><td>API prefix</td><td><code>usin</code></td><td>The Indiana privacy section is registered with API prefix <code>usin</code>.</td></tr></tbody></table>

### Section encoding

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

<table data-header-hidden><thead><tr><th width="177.13323974609375">Field</th><th width="123">Data Type</th><th>Description</th></tr></thead><tbody><tr><td><code>Version</code></td><td>Integer</td><td>The version of the Indiana privacy section used to encode the string.</td></tr><tr><td><code>ProcessingNotice</code></td><td>Int(2)</td><td><p>Notice Describing Processing of Personal Data.</p><p><code>0</code> = Not Applicable, The Controller does not Process Personal Data</p><p><code>1</code> = Yes, notice was provided</p><p><code>2</code> = No, notice was not provided</p></td></tr><tr><td><code>SaleOptOutNotice</code></td><td>Int(2)</td><td><p>Notice of the Opportunity to Opt Out of the Sale of the Consumer’s Personal Data</p><p><code>0</code> = Not Applicable, The Controller does not Sell Personal Data</p><p><code>1</code> = Yes, notice was provided</p><p><code>2</code> = No, notice was not provided</p></td></tr><tr><td><code>TargetedAdvertisingOptOutNotice</code></td><td>Int(2)</td><td><p>Notice of the Opportunity to Opt Out of Processing of the Consumer’s Personal Data for Targeted Advertising</p><p><code>0</code> = Not Applicable, the Controller does not Process Personal Data for Targeted Advertising</p><p><code>1</code> = Yes, notice was provided</p><p><code>2</code> = No, notice was not provided</p></td></tr><tr><td><code>SaleOptOut</code></td><td>Int(2)</td><td><p>Opt-Out of the Sale of the Consumer’s Personal Data</p><p><code>0</code> = Not Applicable, SaleOptOutNotice value was not applicable or no notice was provided</p><p><code>1</code> = Opted Out</p><p><code>2</code> = Did Not Opt Out</p></td></tr><tr><td><code>TargetedAdvertisingOptOut</code></td><td>Int(2)</td><td><p>Opt-Out of Processing the Consumer’s Personal Data for Targeted Advertising</p><p><code>0</code> = Not Applicable, TargetedAdvertisingOptOutNotice value was not applicable or no notice was provided</p><p><code>1</code> = Opted Out</p><p><code>2</code> = Did Not Opt Out</p></td></tr><tr><td><code>KnownChildSensitiveDataConsents</code></td><td>Int(2)</td><td><p>Consent to Process Personal Data concerning a known Child in accordance with COPPA as required by Ind. Code Ann. § 24-15-4-1(5)</p><p><code>0</code> = Not Applicable, the Controller does not Process Sensitive Data of a known Child</p><p><code>1</code> = No Consent</p><p><code>2</code> = Consent</p></td></tr><tr><td><code>AdditionalDataProcessingConsent</code></td><td>Int(2)</td><td><p>Consent to Processing of the Consumer’s Personal Data that Is Not Reasonably Necessary for nor Compatible with the Disclosed Purpose(s) for which the Consumer’s Personal Data Was Processed</p><p><code>0</code> = Not Applicable, the Controller does not Process Personal Data that is Not Reasonably Necessary for nor Compatible with the Disclosed Purpose(s)</p><p><code>1</code> = No Consent</p><p><code>2</code> = Consent</p></td></tr><tr><td>MspaVersion</td><td>Int(6)</td><td>Version of the MSPA</td></tr><tr><td>MspaCoveredTransaction</td><td>Int(2)</td><td><p>Publisher or Advertiser, as applicable, is a signatory to the IAB Multi-State Privacy Agreement (MSPA), as may be amended from time to time, and declares that the transaction is a “Covered Transaction” as defined in the MSPA.</p><p><code>1</code> = Yes</p><p><code>2</code> = No</p></td></tr><tr><td>MspaMode</td><td>Int(2)</td><td><p>Publisher or Advertiser, as applicable, has enabled “Opt-Out Option Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.</p><p>Publisher or Advertiser, as applicable, has enabled “Service Provider Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.</p><p><code>0</code> = Not Applicable</p><p><code>1</code> = Opt-Out Option Mode</p><p><code>2</code> = Service Provider Mode</p></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didomi.io/regulations-manager/frameworks/global-privacy-protocol-gpp/gpp-string/u.s.-state-privacy-sections/indiana-incdpa.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.