I don’t have an ETA, but it should be soon.
Rob
Hey guys! I have some news. Good and bad.
Bad news is that 3286 have some issues on older devices (both android and iOS).
Good news - 3301 fixes that issues.
Sounds like all good news to me.
Can you please clarify what kind of issues? And what devices would be affected?
We rebuilt everyone of our apps for Apple, Google, and Amazon. Over 150+ builds and reviews on the stores, and now we may have to do it again!?
Very good point. Specially:
Android: 4.1 or lower
iOS: native builds only; arm7 devices, no matter OS version.
So if we don’t use Corona Native then all iOS builds are okay?
Build not with Corona Native (ex Enterprise). Not Corona Simulator
Sorry, that doesn’t make sense.
If we built with Corona SDK 3286, not Native or Enterprise, then are our apps okay?
If you built for iOS with the Corona simulator you are good to go. If you did native builds, arm7 devices (iPhone 4, 4s, 5) will not work. If you didn’t do native builds, you’re good here.
Then on Android, even with simulator builds, there are issues with really old Android devices on Android 4.1 and earlier.
Rob
Thanks Rob, that clears it up! We got scared for a second there, reliving the Apple review process for 26+ apps is not something I want to do again anytime soon. 
Hi Rob
With the whole commotion with GDPR, you have updated the community on your adherence to GDPR for Corona SDK and there has been a lot of focus on ad network plugins?
How about the other non-ad networkd plugins manage by Corona? Are they all compliant?
Ben
One vote to GameBit labs Qn.
Also i saw on Google Policy its written that we need to take consent for Cookies too, Do someone know about this and how to handle this.
Also i saw in Admob load call we have another Parameter now that need to be passed as false to enable GDPR for that user. I am not sure about that how it works, Does it mean it will show Non Personal Ads and if so how is it possible without cookies again and also how to remove data that is already collected at their end.
And so it begins…
Not entirely sure what to do about it though as I have no access to that user’s FB account?!
Is that because you have “Login with Facebook” or is there something else?
I don’t think we’ve addressed GameCenter, GPGS, In-App purchases. We don’t collect that data, so it would be your responsibility to link to the various privacy policies and it seems like an all or nothing opt-in for your users. That is if they decline consent for GPGS for example, simply don’t initialize it. My understanding was those services would offer their own consent. You can’t exactly use GameCenter, GPGS or IAP without some personally identifiable ID being collected.
Rob
Thanks Rob,
This is good. So does this mean we need to ask user to give consent on different items individually like for GPGS, IAP, ADS etc
It is the intent of the EU to be as granular as possible. You probably could get away with a global consent form that grants consent for everything to save you time, but the more permission you ask for in a big batch, the more likely a user will say no. If you ask for each item or at least group of items (permission for ads, permission for analytics, permission for IAP, etc.)
What you do is up to you. We are not lawyers and cannot provide anything that resembles legal advice. You might want to visit our blog at https://coronalabs.com and read our previous posts on GDPR where we link to resources that can answer many of these questions.
Rob
Hi Rob,
I am aware that these services are collecting data and we need to ensure consent is collected if we want to continue using these services. My question is, when Corona packages these plugins and make them available to everyone on the Marketplace (whether the plugin is free or paid), is there additional data that is collected by Corona when the plugin is used in our apps?
Ben
My biggest issue now is with analytics services. I read Yoger Game’s data policy (http://www.yogergames.com/data-policy/), and in the Analytics section it states, “…The analytics data collected is anonymous and is not personal data. At first startup of an app we generate a random unique identifier which does not contain any personal information, and cannot be used to uncover any such information.”
In reference to Yoger’s use of GA, the last two sentences contradict one another, because it is clearly stated that random unique identifiers are PII under GDPR and for games that target kids under whatever the legal age for that country, parental consent is required.
I am making kids apps too and if i really want to be compliant to GDPR-K and COPPA - based on my current reading and research, there isn’t any analytics service out there we can use without getting parental consent (which in itself is a dire quest)
Going down this path, it seems that the only analytics we can work on from now onwards will be what the app stores give us…
Ben.
Yoger and I go about it the same way. Per-app (not per-user), we generate a UUID. Then we use that UUID together with an anonymized IP address. IMHO, there is no way that can be used to identify anyone, or even build a profile of interests for that UUID (since it is only used for that one app)
Let’s say Google Analytics accidentally leaks their data. You won’t be able to map that random UUID to any other data set. You won’t be able to map the anonymized IP address to any other data set.