API Reference

Connecticut Privacy Section

If Connecticut is included in the framework territories of a property's U.S. Multi-State Privacy (National) vendor list, Sourcepoint will set the Connecticut privacy section.

🚧

A legacy feature in Sourcepoint's U.S. Multi-State Privacy (National) vendor list builder is that we will set the Connecticut privacy section instead of the U.S. National privacy section if Connecticut is added to a U.S. Multi-State Privacy (National) vendor list.

ValueDescription
Section ID12The Connecticut privacy section is registered as Section ID 12 under the GPP.
API prefixusctThe Connecticut privacy section is registered with API prefix usct.

Section encoding

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

FieldData TypeDescription
VersionIntegerThe version of the Connecticut privacy section used to encode the string.
SharingNoticeIntegerNotice of the Sharing of the Consumer's Personal Data with Third Parties.

0 Not applicable.
1 Yes, notice was provided.
2 No, notice was not provided.
SaleOptOutNoticeIntegerNotice of the Opportunity to Opt Out of the Sales of the Consumer's Personal Data.

0 Not applicable.
1 Yes, notice was provided.
2 No, notice was not provided.
TargetedAdvertisingOptOutNoticeIntegerNotice 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.
SaleOptOutIntegerOpt-Out of the Sale of the Consumer’s Personal Data

0 Not applicable.
1 Opted Out
2 Did Not Opt Out
TargetedAdvertisingOptOutIntegerOpt-Out of Processing the Consumer’s Personal Data for Targeted Advertising.

0 Not applicable.
1 Opted Out
2 Did Not Opt Out
SensitiveDataProcessingArrayConsents 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 Revealing Racial or Ethnic Origin.

2. Consent to Process the Consumer's Sensitive Data Consisting of Personal Data Revealing Religious Beliefs.

3. Consent to Process the Consumer's Sensitive Data Consisting of Personal Data Revealing a Mental or Physical Health Condition or Diagnosis.

4. Consent to Process the Consumer's Sensitive Data Consisting of Personal Data Revealing Sex Life or Sexual Orientation.

5. Consent to Process the Consumer's Sensitive Data Consisting of Personal Data Revealing Citizenship or Immigration Status.

6. Consent to Process the Consumer's Sensitive Data Consisting of Genetic Data that May Be Processed for the Purpose of Uniquely Identifying an Individual.

7. Consent to Process the Consumer's Sensitive Data Consisting of Biometric Data that May Be Processed for the Purpose of Uniquely Identifying an Individual.

8. Consent to Process the Consumer's Sensitive Data Consisting of Precise Geolocation Data.
KnownChildSensitiveDataConsentsArrayConsents for each data activity (3) in the processing of personal or sensitive data of consumer who is a known child category.

0 Not applicable.
1 No Consent
2 Consent

1. Consent to Process Sensitive Data from a Known Child.

2. Consent to Sell the Personal Data of Consumers At Least 13 Years of Age but Younger Than 16 Years of Age.

3. Consent to Process the Personal Data of Consumers At Least 13 Years of Age but Younger Than 16 Years of Age for Purposes of Targeted Advertising.
MspaCoveredTransactionIntegerPublisher 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
MspaOptOutOptionModeIntegerPublisher 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
MspaServiceProviderModeIntegerPublisher 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
GpcBooleanIs Global Privacy Control enabled for the vendor list and detected on the end-user's browser?
GpcSegmentTypeIntegerPossible values: 0 = Core | 1 = GPC
{
  "Gpc": false,
  "GpcSegmentType": 1,
  "KnownChildSensitiveDataConsents": [
    0,
    0
  ],
  "MspaCoveredTransactions": 2,
  "MspaOptOutOptionMode": 0,
  "MspaServiceProviderMode": 0,
  "SaleOptOut": 2,
  "SaleOptOutNotice": 1,
  "SensitiveDataProcessing": [
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0
  ],
  "SharingNotice": 1,
  "TargetedAdvertisingOptOut": 2,
  "TargetedAdvertisingOptOutNotice": 1,
  "Version": 1
}