Oregon Privacy Section

If Oregon is included in the framework territories of a property's vendor list, Sourcepoint will set the Oregon privacy section.

	Value	Description
Section ID	15	The Oregon privacy section is registered as Section ID 15 under the GPP.
API prefix	usor	The Oregon privacy section is registered with API prefix usor.

Section encoding

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

Field	Data Type	Description
Version	Integer	The version of the Oregon privacy section used to encode the string.
ProcessingNotice	Integer	Notice of the Processing of Personal Data. 0 Not applicable. 1 Yes, notice was provided. 2 No, notice was not provided.
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 (11) 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 Condition or Diagnosis. 4. Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing Sexual Orientation. 5. Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing Status as Transgender or Nonbinary. 6. Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing Citizenship or Immigration Status. 7. Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing National Origin. 8. Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing Status as Victim of a Crime. 9. Consent to Process the Consumer’s Sensitive Data Consisting of Genetic Data. 10. Consent to Process the Consumer’s Sensitive Data Consisting of Biometric Data. 11. Consent to Process the Consumer’s Sensitive Data Consisting of Precise Geolocation Data.
KnownChildSensitiveDataConsents	Array	Consents 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.
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 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. 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