ironSource GDPR Compliance
GDPR compliance information for LevelPlay using ironSource.
Read time 1 minuteLast updated 3 hours ago
ironSource SDK implementations under the GDPR
Updated: January 8th, 2024When and Why Consent is Required
There are two EU legislations regulating when consent should be obtained from end-users:- GDPR: Requires a legal basis for processing personal data. ironSource’s ad network relies on legitimate interest for contextual ads, fraud prevention, and sharing device identifiers with attribution companies. Other ad networks and DSPs may rely on consent for interest-based ads. If you use LevelPlay, you can communicate consent values to supported ad networks.
- ePrivacy Directive: Requires consent for storing, accessing, or transmitting information from an end user’s device. You must obtain user consent before initializing any third-party SDK, including LevelPlay and ironSource ad network. If consent is not obtained, do not initialize the ironSource SDK.
Settings for Underaged Users
For underaged user settings, see the Child Directed Apps article.- For Android: Android settings
- For Unity: Unity settings
Consent Support
Non TCF users
ironSource SDK provides a client-side API to pass GDPR consent. Learn more: When you report setConsent, the information is shared with all mediated networks that support consent APIs. See tables below for supported networks and adapter versions.TCF users
Support for Google UMP and CMPs that support Google’s Additional Consent:- If using Google UMP, configure on the AdMob platform (details).
- If not using Google UMP, check your CMP’s documentation for Google’s Additional Consent support.
- Ensure the following networks are included in Google’s Additional Consent: ironSource, Unity, Vungle, Applovin, Chartboost.
- Starting with ironSource SDK 7.7.0, GDPR consent from Google UMP and CMPs is automatically passed to ironSource SDK and the listed networks. No further action needed. For older SDKs, see how to share consent.
- Set up non-registered TCF networks within your CMP per their guidelines.
- Pass info to LevelPlay using setConsent API (Android, iOS, Unity).
- All registered TCF vendors receive consent via the TCF protocol.
Mediated networks consent support
Network | Consent API Support | Registered TCF Vendor | Google CMP Custom Ad Partner | oRTB Support (Bidding only) |
|---|---|---|---|---|
| ironSource | v | v | v | |
| AppLovin | v | v | ||
| Amazon Publisher Services (APS) | v | |||
| BidMachine | v | v | v | |
| Chartboost | v | v | ||
| Digital Turbine (Fyber) | v | v | v | |
| Google AdMob & Ad Manager | v | v | v | |
| HyprMx | v | |||
| InMobi | v | v | v | |
| Liftoff Monetize (Vungle) | v | v | v | v |
| Maio | ||||
| Meta Audience Network | v | v | ||
| Mintegral | v | v | ||
| VK Ad Network | v | v | ||
| Pangle | v | v | ||
| Smaato | v | v | ||
| UnityAds | v | v | v |
Mediated networks adapter support for setConsent API
Network | Earliest consent support adapter version |
|---|---|
| iOS | |
| AppLovin | 4.1.4 (SDK 5.0.1) |
| BidMachine | All versions |
| Chartboost | 4.1.2 (SDK 7.2.0) |
| CSJ | All versions |
| Digital Turbine | 4.3.1 (SDK 7.4.0) |
| 4.1.4 (SDK 7.28) | |
| HyprMX | 4.1.2 (SDK 5.0) |
| InMobi | 4.1.3 (SDK 7.1.1) |
| Liftoff Monetize | 4.1.5 (SDK 6.2.0) |
| Maio | All versions |
| Meta Audience Network | All versions |
| Mintegral | All versions |
| VK Ad Network | All versions |
| Pangle | 4.3.6 (3.7.0.5) |
| UnityAds | 4.1.1 (SDK 2.1.1) |
- When sharing information with ironSource SDK through setConsent API, LevelPlay reports the setting to supported networks.
- AwesomeAds Marketplace does not participate in IAB TCF due to contextual targeting and minimal data collection.
- CSJ and Tencent: Supported only in China, GDPR not applied.
- See registered TCF Vendors and Google CMP partners.
For related resources, see: