> > > > I use Admob and understand that the advertising ID maybe depends on the required DGPR settings. What should I do?
> > >
> > > You do not need the GDPR requirements you are thinking of for Google Play's Designed for Families Programs, specifically the Advertising Id. Furthermore, if you are using the Mobile Advert object, it's automatically incompliant because the consent dialog is hardcoded.
> > >
> > > I'm not sure if you can get away using the Mobile Advert as long as you do not launch the consent dialog. Although, considering it is Google, I wouldn't risk it. In spite of that, you still need a plugin to remove those ids specified, like this plugin does: constructcollection.com/documentations/mobile/mobile-advert-families-programs
> >
> > Ohh, okay.. and what do you think about these actions? Perhaps they can help?
> >
> >
>
> Those are only for COPPA, which are one of the requisites.
Yes, but judging by this window we can treat all users as children. It also mentions the GDPR window, which is why there is a problem, because when it wasn’t there, everything was fine. The window requires mandatory data collection.
Can you understand this? Google has introduced a mandatory requirement to illuminate the window, but it is prohibited for children. Haha, sur.
They themselves cannot understand their decisions, it’s the same network, like Admob, like Google, they shouldn’t have problems. I can't remove the GDPR window because it's mandatory. Why should I bypass some strange methods and new plugins and write something in the manifest... Hide something.. Is it really not possible to just track whether it is a child or not, and show a window depending on the age.. Maybe there is an action "Tag for under age of consent" is exactly it.
I apologize for so much text, but I want to figure it out once and for all. I removed children from the app and lost most of my audience. I won't be able to continue to receive such a stable income, and develop an update... It's a nightmare.
It would also be a good idea for the Construct developers to look at this whole situation, because as you write, they “dialog is hardcoded”... I am surprised by the silence of many, because this is clearly a problem.
If you are trying to vent, I understand. But, if you are asking me what's the issue, then to elucidate what's happening based on your provided Google rejection response:
- It's not an issue with your event sheet.
- Rather, it's an issue with your SDK integration and Android Manifest.
- You shouldn't have anything in your project that identifies your users since it's targeted only for children.
- In your case, your project's build integration.
- Assuming you only have the Mobile Advert plugin, you need to remove those identifiers.
- No, you do not need a consent dialog. Quite the opposite actually, it's preferably removed, if not required.
- Strictly remove the AD_ID permission.
When writing for this compliance for my own projects and plugin collections (a quick solution). I used this as my guide: support.google.com/googleplay/android-developer/answer/9893335