GPDR consent forms.

[JoePringles]

So basically every single plugin which uses user data are telling developers to give consent.

They say develop a UI that includes your privacy statement and whatever.

I don’t have any privacy statement or anything like that.

I use appodeal and the plugin automatically asks for consent.

But for other plugins, (specifically GameAnalytics), they say to:

“The consent they(developers) ask for from their players must include that their data will be used for analytics and marketing purposes. “

If Appodeal automatically asks for consent, do I have to ask consent for GameAnalytics?
If yes, is there any sample GPDR consent code out there?

Thanks a bunch bros.

[anaqim]

GDPR has some basic requirements.

A privacy statement is one. The content of this one you should read up on but you need to say what you store and collect, why and what it is used for, and how long it is stored (and why if unreasonably long).

Auto exclude by default is another, meaning user need to opt-in.

Noone can be asked to agree with large lawyer fingerprint textwalls anymore. Users need a short and simple description each time they are asked to agree (opt-in) to anything, for it to be GDPR compliant.

GDPR may seem huge but it makes sense once you get through it.

Still, I recommend reading up on it and try to find some abrivated explanations out there.

Everyone feels this is a big stopper but the overall point is very good for consumers.

For example, if a user agree that you store personal info, you also need to provide a way they can opt-out and delete all of it, should they choose. There is also a requirement on documenting how this data is stored, which security measures are in place, and how you detect and handle data theft, should that occur.

Main players out there (google, apple, microsoft, etc) have already and are still implementing solutions to makes this easier for developers, but I suspect it will stili take a little time before all is in place.

[anaqim]

Oh, and this is important.

GDPR is about improving data security and not about slapping developers with lawsuits should they not be perfect compliant with every paragraph.

As long as you can document that you have made and continue to make improvements to comply with this new ruleset, you’ll be fine 

[JoePringles]

thanks for the info

but is there any sample consent ui’s out there?

[anaqim]

not that i am aware of.

I’ve done a little on the subject in my day job and we had to read the law, figure out what we need, and create the documents and routines we needed.

That being said, I’m sure there are shortcuts out there but its all still fresh.

For your initial question, if appodeal automatically asks for consent, couldnt you use that as a template for the consent you need for gameanalytics? There is no copyright on such stuff.

[rob]

I would start by reading here:  https://coronalabs.com/blog/2018/05/16/getting-your-corona-apps-ready-for-gdpr/

and then by following the links to the Appodeal blog where they talk more about getting ready for GDPR. I did not know that Appodeal provided their own dialog. Their blog posts certainly say for you the developer to provide it. The only ad provider that I know asks for their own consent is Unity Ads. The Appodeal plugin uses a flag passed from the developer (i.e. you) to their .init() function if the user has provided consent or not. The only way you can know that is if you present the dialog box. What you may be seeing is a result that Appodeal is a mediation service (they use other ad providers) and one of their ad providers, such as Unity Ads may be asking independently.

The blog post I listed above shows a suggested screen for asking for Appodeal consent.

You really should have a website. On that website, you should set up a page with your privacy policy on it.  For instance, if you get the domain name https://mysuperawesomegames.com you would have a page https://mysuperawesomegames.com/privacy that would hold your privacy policy. We can’t tell you what to put there because it’s your policy. You collect or don’t collect information differently than I do. You can read other similar developer’s privacy policies and write yours in your own verbiage that covers what you do.  GDPR pushes people to express their privacy policies in plain language and not pages and pages of legalize so it favors a non-lawyer style of writing. Be honest, say what you collect or what services you use that may be collecting data and then provide links to those services privacy policies. This sounds harder than it really is.

When you submit an app to Google Play or Apple’s App Store, you will be asked to provide your privacy policy URL so it can be displayed on your app’s download page. This gives people the ability to know what’s being used before they ever download your app. This is why you really, really should do this step.

 Rob

[anaqim]

GDPR has some basic requirements.

A privacy statement is one. The content of this one you should read up on but you need to say what you store and collect, why and what it is used for, and how long it is stored (and why if unreasonably long).

Auto exclude by default is another, meaning user need to opt-in.

Noone can be asked to agree with large lawyer fingerprint textwalls anymore. Users need a short and simple description each time they are asked to agree (opt-in) to anything, for it to be GDPR compliant.

GDPR may seem huge but it makes sense once you get through it.

Still, I recommend reading up on it and try to find some abrivated explanations out there.

Everyone feels this is a big stopper but the overall point is very good for consumers.

For example, if a user agree that you store personal info, you also need to provide a way they can opt-out and delete all of it, should they choose. There is also a requirement on documenting how this data is stored, which security measures are in place, and how you detect and handle data theft, should that occur.

Main players out there (google, apple, microsoft, etc) have already and are still implementing solutions to makes this easier for developers, but I suspect it will stili take a little time before all is in place.

[anaqim]

Oh, and this is important.

GDPR is about improving data security and not about slapping developers with lawsuits should they not be perfect compliant with every paragraph.

As long as you can document that you have made and continue to make improvements to comply with this new ruleset, you’ll be fine 

[JoePringles]

thanks for the info

but is there any sample consent ui’s out there?

[anaqim]

not that i am aware of.

I’ve done a little on the subject in my day job and we had to read the law, figure out what we need, and create the documents and routines we needed.

That being said, I’m sure there are shortcuts out there but its all still fresh.

For your initial question, if appodeal automatically asks for consent, couldnt you use that as a template for the consent you need for gameanalytics? There is no copyright on such stuff.

[rob]

I would start by reading here:  https://coronalabs.com/blog/2018/05/16/getting-your-corona-apps-ready-for-gdpr/

and then by following the links to the Appodeal blog where they talk more about getting ready for GDPR. I did not know that Appodeal provided their own dialog. Their blog posts certainly say for you the developer to provide it. The only ad provider that I know asks for their own consent is Unity Ads. The Appodeal plugin uses a flag passed from the developer (i.e. you) to their .init() function if the user has provided consent or not. The only way you can know that is if you present the dialog box. What you may be seeing is a result that Appodeal is a mediation service (they use other ad providers) and one of their ad providers, such as Unity Ads may be asking independently.

The blog post I listed above shows a suggested screen for asking for Appodeal consent.

You really should have a website. On that website, you should set up a page with your privacy policy on it.  For instance, if you get the domain name https://mysuperawesomegames.com you would have a page https://mysuperawesomegames.com/privacy that would hold your privacy policy. We can’t tell you what to put there because it’s your policy. You collect or don’t collect information differently than I do. You can read other similar developer’s privacy policies and write yours in your own verbiage that covers what you do.  GDPR pushes people to express their privacy policies in plain language and not pages and pages of legalize so it favors a non-lawyer style of writing. Be honest, say what you collect or what services you use that may be collecting data and then provide links to those services privacy policies. This sounds harder than it really is.

When you submit an app to Google Play or Apple’s App Store, you will be asked to provide your privacy policy URL so it can be displayed on your app’s download page. This gives people the ability to know what’s being used before they ever download your app. This is why you really, really should do this step.

 Rob