Regulation Advanced Settings

GDPR – Managing Consent

LevelPlay’s mediation platform supports publisher communication of a user’s consent choice to mediated networks (for supported networks).

Starting from ironSource SDK 7.7.0, GDPR consent from the Google UMP (Google’s CMP solution) and CMPs that support Google Additional Consent, is automatically passed to the ironSource SDK. Learn more here. 

To use ironSource’s API to update a user’s consent status, use this function:

If the user provided consent, please set the following flag to true:

 [IronSource setConsent:YES];

If the user did not consent, please set the following flag to false:

 [IronSource setConsent:NO];

A detailed article regarding ironSource’s approach to GDPR and user consent can be found here.

US Privacy compliance

LevelPlay’s mediation platform (SDK Version 6.14.0 and above) supports publishers to restrict the sale or sharing of end users personal information under U.S. state privacy laws, such as the California Privacy Rights Act (CPRA).

The notification about personal information of specific users located in California, Virginia, Connecticut, Colorado or Utah, should be handled based on a “do not sell” setting by setting its value to “true” or “false”.

The API should be set before initializing the SDK.

If the user has opted out of “sale” or “sharing” of personal information:

 [IronSource setMetaDataWithKey:@"do_not_sell" value:@"YES"];

If “sale” of personal information is permitted:

 [IronSource setMetaDataWithKey:@"do_not_sell" value:@"NO"];

A detailed article regarding ironSource’s approach to U.S state privacy laws can be found here.

User-Level Settings for Child-Directed Apps with Age Gates

LevelPlay’s mediation platform (SDK Version 7.1.0+) enables publishers of child-directed apps to flag specific end-users as children, as may be permitted or required by applicable law (e.g. COPPA). Publishers of child-directed apps are responsible for determining whether an app is permitted to flag at the end-user level or must treat all end-users as children. Publishers should consult with their legal counsel accordingly.

The indication of whether a specific end-user is a child should be done using a “is_child_directed” flag, by setting its value to “true” or “false”.

The API should be set before initializing the SDK.

If the end-user is a child (as defined by applicable regulations):

[IronSource setMetaDataWithKey:@"is_child_directed" value:@"YES"];

If the end-user is not a child:

[IronSource setMetaDataWithKey:@"is_child_directed" value:@"NO"];

A detailed article regarding ironSource’s approach to child-directed apps can be found here.