Privacy Compliance
This page explains how privacy and regulatory compliance works when using the Bidease Bidding SDK, including GDPR, CCPA, and IAB Global Privacy Platform (GPP).
Bidease follows industry-standard privacy frameworks and applies user consent signals automatically to all bid requests.
Responsibilities
Publisher
- Collect user consent using a compliant Consent Management Platform (CMP)
- Store consent signals according to IAB standards
- Ensure consent is obtained before initializing the Bidease SDK and requesting ads
Bidease
- Read standard IAB privacy signals from the device
- Apply consent and regulatory restrictions to all bidding activity
- Prevent use of personal data when valid consent is not available
note
The Bidease SDK does not collect consent itself.
Supported Regulations
The Bidease Bidding SDK supports the following privacy frameworks:
- GDPR (via IAB Transparency & Consent Framework v2)
- CCPA / CPRA (via IAB US Privacy String)
- GPP (Global Privacy Platform for multi-region regulatory coverage)
note
Consent is enforced based on the signals provided by the publisher's CMP.
How Consent Affects Bidding
User consent directly determines how bidding is performed:
- When valid consent is available, bidding may include personal or interest-based signals
- When consent is declined or missing, bidding is restricted to non-personalized or contextual demand
- When regulations apply and no valid consent is present, bidding behavior is automatically limited to ensure compliance
note
No additional configuration is required beyond proper CMP integration.
Supported Privacy Signals
| Key | Description |
|---|---|
IABGPP_HDR_GppString | Global Privacy Platform string |
IABGPP_GppSID | GPP active Section IDs |
IABTCF_gdprApplies | Whether GDPR applies (1 = yes, 0 = no) |
IABTCF_TCString | GDPR TC String |
IABUSPrivacy_String | CCPA privacy string |
warning
Publishers should not modify these values manually. They must be written and managed by the CMP.