GDPR - current State of monetization plugins.

Solar2D Monetization (in-app purchases, ads, etc.)
#21

Hi agramonte,

Been doing some extra reading today on Appodeal’s site. According to this article:

"The updated 2.4.1 version of the Parallel Bidding SDK can be initialized whether or not an end-user provides their consent. Publishers will still be responsible for collecting this consent and passing it to our SDK.

 

In case an end-user doesn’t agree on processing their personal data, Appodeal SDK 2.4.1 will notify all ad demand partners so they won’t collect any information from this user and our ad demand partners will just show non-targeted and less relevant ads to such users. If consent is given, they will personalize an end-user ad experience in accordance with shared information."

 

My initial thought is supported, you can still serve ads without the need to ask for consent, however you’re looking at lower eCPM returns.

 

Ben.

#22

Yes and that is sufficient for GDPR. The GDPR-K has a “no data policy” for anybody under the age of 16 (in Germany) and with consent required from the parent if you are not doing that. COPPA requirements are slightly different. Your original question was if you send the flag for GDPR and the old flag for childdirectedtreatment would you be compliant for GDPR kids. I am not sure that text from appodeal answers that question.

#23

The whole issue is about collection, disclosing, storing and manipulating of personal information that are used for analytics, targeting personalized ads, building profile models without consent, which undermines people’s basic rights to privacy.

The issue is not advertising to app users and kids. Consent is not required to serve Superawesome ads (I have emailed them to confirm this) because they serve ONLY contextual ads.

Which directly means we can serve contextual ads from any networks to our users if no PII is collected and used to serve said ads.

Why most ad networks are so persistent with getting consent from users? I believe it is because their competitiveness in the ad market depend on serving the best personalized ad, which in terms drives eCPM rates and their bottom-line - and right now consent is a boulder they need to overcome.

I believe my research has led me to the conclusion that hasUserConsent and childDirectedTreatment , when used properly will allow me to serve safe contextual ads in my kids app, still we need a lawyer to confirm this.

Ben

#24

I agree mostly with your statement. I believe some ad networks capture what is considered personal information as a matter of fact while serving ads (regardless if those ads are personalized or not).

For example, Admob captures information regardless of the flag and therefore they require consent even if the flag is sent. Kidoz records the ip and the idfa (from Apple). They need consent because those ids break the GDPR-K requirements. Superawesome does neither.

I think your assumption that hasUserConsent and childDirectedTreatment cover you is incorrect. Again I am not a lawyer but just looking at whether they use personalized ads is not enough for GDPR-K. You have to look at what data the capture and record as a matter of fact even if they don’t send personalized ads.

#25

Got replies from Superawesome and Appodeal.

  1. Superawesome, you don’t need consent to serve ads. They are end-to-end 100% compliant to GDPR-K and COPPA.

  2. Appodeal, you need to do two things:

  • properly set hasUserConsent and childDirectedTreatment in your app

  • in the web dashboard select filter mature content & COPPA.

You won’t need to deselect ad networks that are not compliant, with the settings above, it is passed down in their backend.