Build 2019.3512 collects personal information!

Beta Testing Android 64-bit testing
#41

Yes, after Google rejected the apk compiled with version 3512, I compiled again with 3469 and it was accepted.

That’s why my doubt, that 3512 is doing personal data collection through some API or plugin

#42

Just now, I just received an answer to my third query to the Google team.

It is:

Hi Pablo,

Thank you for contacting the Google Play Team in regards to your app’s eligibility for Designed for Families.

Upon further review, we found that the app is not eligible for the following reasons:

We have detected that your app collects personal information, however it was not disclosed in your Play Console.

Apps that include children in the target audience must comply with all Families Policy Requirements, which requires that you disclose the collection of any personal information from children in your app, including through APIs and SDKs called or used in your app. 

Once these issues have been addressed, you may resubmit the app for review.

On all three occasions, the answers they have given me have been of this type. They do not give more detailed information.

But they insist that the app collects personal information, (this is with build 3512)

#43

have you set the childSafe and designedForFamilies tags in your code for admob?

#44

Yes, I have them set, anyway the influencing parameter is HasUserconsent, and I have it set to false.

#45

Besides, I insist, I have the problem with build 3512, with 3469 not, and it’s the same source code.

#46

But it’s not the same. There are significant changes in the underlying Android subsystems.  Any ad plugin you’re using may have a different behavior. We are not collecting any information, so just like you, we feel we didn’t change anything either. What changed was things we have to use.

Rob

#47

Please. Try submitting build without AdMob, see if same error rises. You don’t have to push it to live.

#48

Vlads, I was thinking just doing that.

I will do the test and tell you the result

#49

I have managed to upload using the latest 64bit 3512 & 3516 builds and they are live on playstore without any problems, and my apps is in “designed for families”

it uses exactly the same plugins as you mentioned above also, popup.social, IAP v3 and Admob. 

Not sure where your problem is as the same plugins are working fine for me.

I would still check your code as above on your code you showed to load the banners you load the banner and interstial without the childSafe and designedForFamilies,

this could be a factor especially if your in designed for families?

#50

Also does you apps page have a valid privacy policy? just a shot in the dark

#51

It seems to me if all they are asking is to have a privacy policy, that is the easiest of fixes anyone can do. Simply say you are not collecting any private information, but one of your third-party providers might and link to those third-party privacy policies.

There are tons of places you can find sample privacy policies from and plenty of places where you can have a free web page with a web page builder where you don’t even need to know HTML.

Having a website for your app is almost be a requisite for marketing your app and it’s easy enough to set up a page for your business that shows your apps and then just have a /privacy/index.html page with your policy.

Rob

#52

Hi chris raz, 

If you were kind, can you show me your admob.load() function call?

In Google Play I always had the link to privacy policies configured.

http://www.orangestudios.wirez.com.ar/privacy_policy.html

I don’t know what they think, but I think it would be fine.

#53

Hi @pbozzone0, as per your “load admob code” above you would need to add { childSafe = true, designedForFamilies = true} see below for eg.

if padType == "banner" then -- Banner -- ads.load("banner", {adUnitId=padmobID, hasUserConsent = false, childSafe = true, designedForFamilies = true}) else -- Intersticial -- if ads.isLoaded("interstitial") then ads.show("interstitial") else ads.load("interstitial", {adUnitId=padmobID, hasUserConsent = false, childSafe = true, designedForFamilies = true}) end end 

see the admob load docs for more info

http://docs.coronalabs.com/plugin/admob/load.html#childsafe-optional

I dont know if tat will solve your issue but you should not be putting up and app into designed for families without these tags set to true.

#54

Hi, I recompiled the apk with version 3517, uploaded them to Google Play, without changing absolutely nothing of the source code, and now they approved the apk.

In this version of the SDK have you changed anything about it?

#55

Glad to hear good news. No, we did t touch this.