Data privacy
Comply with global regulations and support for user consent signals.
Read time 1 minuteLast updated 2 days ago
Privacy classes
The following object classes contain the requesting app's COPPA compliance flag, GDPR compliance flag, CCPA compliance flag, and user consent flag. Visit our legal site for more information on Unity's approach to privacy. To ingest and act on bid requests based on the user's GDPR, COPPA, CCPA, and user consent status, Unity's Exchange provides updated OpenRTB specs to reflect the related changes to the bid request fields.regs object and extensions
An object class that contains the requesting app's COPPA, GDPR, and CCPA compliance flags.Attribute | Type | Example | Description |
|---|---|---|---|
| int |
| Flag indicating if the bid request is subject to the COPPA regulations established by the USA FTC.
Note Unity always sends this attribute when the value is |
| int |
| Flag indicating if the request is subject to GDPR. Note Unity always sends this attribute when applicable to affected regions. |
| string |
| Flag indicating consent for requests subject to CCPA regulations. The string format must follow the IAB's U.S. privacy specifications. Note Unity always sends this attribute when applicable to affected regions. |
| string |
| Upon confirming opt-out from a LGPD-affected user, the request structure for that user's device sends a flag in the regs.ext.lgpd object with the integer value true. Unity also strips all personally identifiable information (for example: IDFA, AAID, and IP address) from the request. Note This attribute is always passed when applicable to affected regions. For more information on the spec, contact your Unity account manager. |
user object extension
An object class that contains the requesting app's user consent flag for data collection.Attribute | Type | Example | Description |
|---|---|---|---|
| string |
| Flag indicating if the end user has consented to data collection.
|