We are working on updating our privacy policy as part of working towards GDPR compliance. The discrepancy between the existing privacy policy and turning off launchPad is likely an oversight. I also don’t remember if launchPad being disabled was intentional and the privacy policy just needs updated, or its the opposite, launchPad being disabled was broken along the way. I’ll see if I can find out which is which and make sure as we update the privacy policy this gets adapted.
Rob
Hi Rob,
Where can we find details about what data is being collected?
Is it possible to turn this off?
Is there any other under the hood stuff happening like this? (without directly mentioning)
Thank you
Here’s what I can tell you today. Our engineering team is working very hard to help us get to GDPR compliance. This will likely result in a change in what data we collect and how we do it. I need to respect their request to work on this and not have them go on research expeditions. Once we get these changes in, get the privacy policy updated and so on I think we can be a bit more specific on these questions.
I would request that you wait until we announce our GDPR information and then pursue these questions after that.
Rob
Starting with the daily build (and current public build) on May 25, 2018, we disabled any data collection that would be considered private data according to the GDPR rules put in place by the EU. We were still collecting usage data, like daily active users, anti-fraud information for ad plugins etc.
Starting with Daily build 2018.3454 which was released on December 27, we have disabled all stats collection. So if you’re using 2018.3454 or later it should not be making connections to stats.coronalabs.com
See: https://coronalabs.com/blog/2018/12/27/corona-is-now-100-analytics-free/
Rob
thank you!
Any update on that (5 months have passed)? Also - apart from GDPR compliance, is Corona going to enable switching analytics off? Even via a paid plugin? There are some of us users for whom mandatory analytics is a CRITICAL BLOCKER and inability to turn it off means instant ditching of Corona… 
If you’re using 3301 or later, the stats we collect do not include any private data. We have not been collecting any private data since May 16th, when GDPR kicked in if you’ve built with 3301 or later.
Corona is free to use. For this to happen, we have to be able to know how many sessions run, daily active users and so on. We can collect this without invading the app user’s privacy.
I’ll suggest offering a paid plugin to disable stat collection.
Rob
Thank you, Rob. Yes, I think a paid plugin would be fair - by the same token that one can pay to remove the default splash screen.
Rob,
any update on the subject? an estimate, perhaps?
Regards,
Piotr
We had a brief discussion. The general thought is that might be a good idea, but we don’t have any action items at this time to implement it. I’m sure we will discuss it more over the next few weeks.
Just out of curiosity, what would you be willing to pay to turn off our analytic collection? Note: we would probably not be able to turn off any ad analytics.
Rob
“we would probably not be able to turn off any ad analytics”
– by that do you mean then when ads are enabled then there would be some analytics connected to that and when they are disabled there would be no analytics at all?
If so then we’re on the same page, otherwise - could you explain?
I was thinking of it in terms similar to removing the splash screen. Basically I would like to be able to show to my consumers the product in the shape I want it to have - no “foreign” splash screen and no forced analytics… For that I would be willing to pay $99 for each element separately, so perhaps when bought together they could make some bundle, say: “Pure game, no bloating elements, for $159 -> no splash, no stats”?
When you use an ad plugin, we have to track ads delivered for contractual/fraud reasons. This is different information that Corona collects for all apps. For all apps, we track daily active users, sessions and other harmless, non-private stats. They are two different classes of stat collection. Since we have contractual requirements on ads, I seriously doubt we can turn those off. What we could potentially disable is the stats we collect on all apps.
Rob
Yes, so I understood you correctly. We are talking about non-ad stats which means that:
if I turned that new plugin on and turned ads on, there would still remain these ad-related analytics, but
when I turned the plugin on and not use ads, then there would be no stats at all.
Correct? 
If so, then my feeling would be: $99 for the non-stats plugin - just as it is for no-splash-screen; but when the two go together, I would offer some discount since one is a conceptual extension of the other (-> perhaps $159?).
Correct.
Great. I’m looking forward to learning more when your plans are crystalized.
Regards,
Piotr
Starting with the daily build (and current public build) on May 25, 2018, we disabled any data collection that would be considered private data according to the GDPR rules put in place by the EU. We were still collecting usage data, like daily active users, anti-fraud information for ad plugins etc.
Starting with Daily build 2018.3454 which was released on December 27, we have disabled all stats collection. So if you’re using 2018.3454 or later it should not be making connections to stats.coronalabs.com
See: https://coronalabs.com/blog/2018/12/27/corona-is-now-100-analytics-free/
Rob
thank you!