Just wondering what the general thoughts on the new EU GDPR (General Data Protection Regulation) due to be implemented in mid May are?
For me there are 2 areas that will impact on my apps I think - advertising & analytics. From the emails I have received from Google (the latest being today), it looks like I will have to seek user consent to show targeted ads & if they decline that, then I'll have to still get their consent for non-targeted ads because AdMob uses cookies for frequency capping, etc...
If they decline that consent, I can offer them an option for an in-app purchase (that I would normally offer to stop ads) - but in reading the Guidelines On Consent (http://ec.europa.eu/newsroom/article29/item-detail.cfm?item_id=623051) it seems that you can't actually stop them using the app if they refuse to give consent & also refuse to pay the fee (apparently their consent isn't classified as being given "freely" because their refusal is to their detriment).
Apparently Google will offer a way of asking for consent via an AdMob SDK, but I don't think this is available as-yet & when it is it will no doubt take some time to be available for B4A, so in the meantime I think we will have to provide some kind of in-app consent form.
On top of that, you also have to provide a way for users to withdraw their consent at any time & a way for them to request that all their data is irretrievably deleted.
At this point the only thing I have done is create a Data Consent Policy on my Facebook page that I will link to from my apps. I'm not really sure what other steps to take at this stage.
All in all, it seems like a bit of a minefield & I suspect it will have a big negative impact on in-app advertising revenues from EU - especially if users only give consent for non-targeted ads.
Any thoughts / comments / insights?
- Colin.
For me there are 2 areas that will impact on my apps I think - advertising & analytics. From the emails I have received from Google (the latest being today), it looks like I will have to seek user consent to show targeted ads & if they decline that, then I'll have to still get their consent for non-targeted ads because AdMob uses cookies for frequency capping, etc...
If they decline that consent, I can offer them an option for an in-app purchase (that I would normally offer to stop ads) - but in reading the Guidelines On Consent (http://ec.europa.eu/newsroom/article29/item-detail.cfm?item_id=623051) it seems that you can't actually stop them using the app if they refuse to give consent & also refuse to pay the fee (apparently their consent isn't classified as being given "freely" because their refusal is to their detriment).
Apparently Google will offer a way of asking for consent via an AdMob SDK, but I don't think this is available as-yet & when it is it will no doubt take some time to be available for B4A, so in the meantime I think we will have to provide some kind of in-app consent form.
On top of that, you also have to provide a way for users to withdraw their consent at any time & a way for them to request that all their data is irretrievably deleted.
At this point the only thing I have done is create a Data Consent Policy on my Facebook page that I will link to from my apps. I'm not really sure what other steps to take at this stage.
All in all, it seems like a bit of a minefield & I suspect it will have a big negative impact on in-app advertising revenues from EU - especially if users only give consent for non-targeted ads.
Any thoughts / comments / insights?
- Colin.