I prefer your approach. I’m just wondering how much this would affect our revenue if we always set consent=fase and show non-personalized ads?
I’m trying to get an answer about the revenue question. There may not be a precise answer since there are many factors in what goes into the eCPM calculation.
Rob
What is the default for hasUserConsent ?
The Consent SDK is not in the latest Admob plugin yet right? Just want to confirm this.
Dislam, regarding revenue: in AdMob you can filter a report by targetting type. For me it looks like revenue will drop by around 5% by converting all personalized ads to context-based.
What is the default for hasUserConsent ?
It has no default value on Admob’s side, so there’s no default value for Corona plugin, it’s an optional parameter. Like, you may distribute your app to countries, that don’t fall for GDPR restrictions, so there is no need in user consent.
The Consent SDK is not in the latest Admob plugin yet right?
That’s correct, due to some limitations, ConsentSDK implementations is planned to future plugin updates.
Without the Consent SDK in place, the app is considered non-compliance right? I think it is not possible to know if the users are from EU or not.
Without the Consent SDK in place, the app is considered non-compliance right?
We’ve implemented all needed APIs to be GDPR compliant, it’s just not Consent SDK, it serves a slightly different purpose.
Am I right to say without the Consent SDK, we can only default the value of hasUserConsent to false?
Am I right to say without the Consent SDK, we can only default the value of hasUserConsent to false?
Not sure that I’ve understood your question right.
When you have user consent for his data, you should set the parameter to true. If you don’t have this consent - set it to false to enable GDPR restrictions.
But to gain user consent for displaying personalised Admob ads, we will need the Consent SDK integrated so that we can present it to the users.
You can gain user consent for yourself, just like with basically every other ad plugin.
If the personal information we are collecting is for our own usage, then I think it is reasonable for us to present our own consent form. However, since the information is used by Admob, I don’t think we should be presenting our own custom consent form.
@falcon777 No. You can ask for consent yourself. Most apps I have seen so far are showing their own personal consent form. Most providers don’t even have a consent UI to display they expect you to have created one.
We published a checklist to our blog that guides you through what you need to do:
https://coronalabs.com/blog/2018/05/16/getting-your-corona-apps-ready-for-gdpr/
But to summarize here.
You, the developer present a dialog box of your own design that fits the style of your app that:
a. Tells the user that your app is going to be collecting data.
b. Provide a link to your privacy policy on your website.
c. In that privacy policy, provide more context that your ad providers are collecting data and link to their privacy policy.
d. Provide a UI that ask them to either consent to this, or decline it. It could be something as simple as a checkbox, on/off switch etc. using widget.newSwitch. This should be defaulted to no consent, since the EU’s intent is for the user to actively opt-in and not opt-out of consent.
e. Save that setting with your other app settings.
f. On your settings screen, provide the user an option to change their mind.
g. Decide how your app will behave if the user does not consent.
h. If your ad plugin will provide non-targeted/non-tracked ads, you can then pass the consent choice to the ad plugin according to the documentation for that plugin. If your plugin doesn’t have a consent API, then simply don’t initialize the plugin if there is no consent.
Rob
Thanks for the information. I have not exactly seen Admob consent interface yet so I cannot comment on that. I would have thought using the one provided by Admob would be the safest bet moving forward as they know best what data is being collected and how is it being used.
I think that would be fine if you only needed to get permission from Admob. But if you use any analytic provider then you would have to ask for that also or other ad networks.
For example, I use flurry. And their consent dialog box doesn’t look anything like Admob. So I would have to show Admob then Flurry. It would look awkward.
Some don’t have any. If I used Game Analytics I would have to roll my own consent dialog box because they don’t have one. So if you used Kiddoz they require consent but don’t have their own so you would still need to create one.
This is what the magic the gathering consent looks like. The ask for about 8 different consents all at once.
Sidenote: Kidoz have updated their SDK policy, it is is not necessary to gather consent for their sake.
@perflubron where did you see that? From their SDK policy:
ONSENT REQUIREMENTS & RIGHTS OF THE DATA SUBJECT
As between the parties, the Publisher undertakes accepts and agrees that the Data Subject do not have a direct relationship with Kidoz and that Kidoz relies on Publisher’slawful basis (as required under Data Protection Law). In the event consent is required under Data Protection Law, the Publisher shall:(i)ensure that it obtains consent from Data Subjectsand displays all necessary and applicable notices in accordance with the Data Protection Law as well as enable lawful transfer of the Personal Data to Kidoz;(ii)maintain a record of all consents obtained from Data Subject, including the time and data on which consent was obtained, the information presented to Data Subject; and(iii)record of the withdrawals of consent by Data Subject. The Publisher shall make these records available to Kidoz promptly upon request.
@agramonte: I am confused. You wrote you’re not planning to do any pop-ups for ads. This would be ideal. But according to Admob, we still have to ask for consent even if we are only showing non personalized ads**: https://support.google.com/admob/answer/7666366?hl=en&ref_topic=2745287**
"Although these ads don’t use cookies for ads personalization, they do use cookies to allow for frequency capping, aggregated ad reporting, and to combat fraud and abuse. Consent is therefore required to use cookies for those purposes from users in countries to which the ePrivacy Directive’s cookie provisions apply."
Or am I not understanding something correctly here?