Minnesota (MNCDPA)
The Minnesota 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 Minnesota Consumer Data Privacy Act in the GPP consent notice.
Click here to learn more about the Minnesota Consumer Data Privacy Act on the Didomi blog.
Section ID
23
The Minnesota privacy section is registered as Section ID 23 under the GPP.
API prefix
usmn
The Minnesota privacy section is registered with API prefix usmn.
Section encoding
The table below details the various fields of the Minnesota privacy section.
Note: Be advised that Didomi currently does not provide support for the KnownChildSensitiveDataConsents field.
Version
Integer
The version of the Minnesota privacy section used to encode the string.
SaleOptOutNotice
Integer
Notice of the Opportunity to Opt Out of the Sale of the Consumer's Personal Data
0 Not applicable.
1 Yes, notice was provided.
2 No, notice was not provided.
TargetedAdvertisingOptOutNotice
Integer
Notice of the Opportunity to Opt Out of Processing of the Consumer's Personal Data for Targeted Advertising
0 Not applicable.
1 Yes, notice was provided.
2 No, notice was not provided.
SaleOptOut
Integer
Opt-Out of the Sale of the Consumer’s Personal Data.
0 Not applicable.
1 Opted Out
2 Did Not Opt Out
TargetedAdvertisingOptOut
Integer
Opt-Out of Processing the Consumer’s Personal Data for Targeted Advertising.
0 Not applicable.
1 Opted Out
2 Did Not Opt Out
SensitiveDataProcessing
Array
Consents for each data activity (8) in the sensitive data category.
0 Not applicable.
1 No Consent
2 Consent
1. Consent to Process the Consumer's Sensitive Data Consisting of Personal Data Indicating Racial or Ethnic Origin.
2. Consent to Process the Consumer's Sensitive Data Consisting of Personal Data Indicating Religious Beliefs.
3. Consent to Process the Consumer's Sensitive Data Consisting of Personal Data Indicating a Mental or Physical Health Condition or Diagnosis.
4. Consent to Process the Consumer's Sensitive Data Consisting of Personal Data Indicating Sexual Orientation.
5. Consent to Process the Consumer's Sensitive Data Consisting of Personal Data Indicating Citizenship or Immigration Status.
6. Consent to Process the Consumer's Sensitive Data Consisting of Genetic Data for the Purpose of Uniquely Identifying an Individual.
7. Consent to Process the Consumer's Sensitive Data Consisting of Biometric Data for the Purpose of Uniquely Identifying an Individual.
8. Consent to Process the Consumer's Sensitive Data Consisting of Specific Geolocation Data.
KnownChildSensitiveDataConsents
Integer
Consent to process Personal Data from a known Child in accordance with COPPA:
0 Not applicable.
1 No Consent
2 Consent
AdditionalDataProcessingConsent
Integer
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.
0 Not applicable.
1 No Consent
2 Consent
MspaCoveredTransaction
Integer
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.
1 Yes
2 No
MspaOptOutOptionMode
Integer
Publisher or Advertiser, as applicable, has enabled “Opt-Out Option Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.
0 Not applicable.
1 Yes
2 No
MspaServiceProviderMode
Integer
Publisher or Advertiser, as applicable, has enabled “Service Provider Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.
0 Not applicable.
1 Yes
2 No
Gpc
Boolean
Is Global Privacy Control enabled for the vendor list and detected on the end-user's browser?
GpcSegmentType
Integer
Possible values: 0 = Core | 1 = GPC
Last updated