Confusing and incorrect wording in GDPR message

74 views
Skip to first unread message

bellissimo

unread,
Sep 18, 2023, 5:50:54 AM9/18/23
to Google Mobile Ads SDK Developers
Hi. When creating a GDPR message in AdMob, it contains the following text which cannot be changed:

'Look for a link at the bottom of this page or in our privacy policy where you can withdraw consent.'

I assume this has been copied and pasted from the web notice, where a website would typically have a link to the Cookie Settings or the Privacy Policy in the footer. However this is not generally applicable for an app, which does not typically have a footer. In an app consent would usually be managed in the Settings somewhere (maybe in a Privacy section, but not usually in the Privacy Policy itself), but it would vary per app.

The GDPR regulations state that it must be made clear how a user can manage their consent settings, so the standard text is potentially in breach of the GDPR for a lot of apps and at the very least incorrect and confusing.

Can you please adjust this part of the text so it is more suitable for mobile apps, or even better make it adjustable so each app can inform the user as to exactly how the consent can be managed.

Mobile Ads SDK Forum Advisor

unread,
Sep 18, 2023, 12:25:50 PM9/18/23
to doogl...@gmail.com, google-adm...@googlegroups.com

Hello,

Thank you for reaching out to us.

Would you kindly send us screenshots of this? This is so we could investigate further and provide appropriate guidance.

This message is in relation to case "ref:_00D1U1174p._5004Q2omWCJ:ref"

Thanks,
 
Google Logo Mobile Ads SDK Team


bellissimo

unread,
Sep 19, 2023, 3:53:16 AM9/19/23
to Google Mobile Ads SDK Developers
Screenshot 2023-09-19 at 08.43.08.png

Mobile Ads SDK Forum Advisor

unread,
Sep 19, 2023, 11:07:23 AM9/19/23
to doogl...@gmail.com, google-adm...@googlegroups.com

Hi,
Thank you for contacting the Mobile Ads SDK support team.

By reviewing your concern, I understand that you want to change the GDPR message in AdMob UI. Your concern is more related to the product rather than Mobile Ads SDK implementation. I would recommend reaching out to the Product Support Team as they are better equipped to address your concern.
Reply all
Reply to author
Forward
0 new messages