Cookie consent notice compliance in ALL EU SERVED apps before 30th September

Solar2D General Questions/Discussion
#1

Hi,

I had an email several weeks ago stating that if your app contains anything that uses cookies or data collection and is served to the EU,you must put up a notice that tells the end user BEFORE any ads or cookies are called.

So, this means if you have an app on any IOS/ Android store etc and it is downloadable in the EU you have to comply by the stated date otherwise risk the app being taken down.

Ok, so if you use any google services, admob, analytics etc  it means you have to comply.

Google have kindly given us some code here:

http://www.cookiechoices.org/

Basically, they are saying serve a system dialogue before the app starts to collect data or store cookies.

I got to thinking how intrusive this is to the user.

I have a blueprint in several forms; a screen that pops up telling the user about the cookies and a system dialogue box that does the same, both link to googles own cookie policy. I then store a boolean so next time the user starts the app it dosnt display as its already accepted.

Nice and simple.

My question is that I cannot see it implemented anywhere yet in either the play store or IOS, so does anybody have any ideas as to a better more non intrusive way to implement it ?

Of course we could not collect analytics or use ads but hey its how I make my money.

Thanks

#2

Has this affected no body here then ?

#3

I haven’t received any emails to this effect from either Apple or Google. Are you sure it’s legit? From whom did the email originate? When a user downloads an app from Google Play, they do have the permissions statement to review before they can even install it. IMO this is the disclosure. Also, you say you have a link to Google’s cookie disclosure. Does this document state that you need to inform the end user of data collection?

Normally if Google gives a url, it follows the template of http://<name of service>.google.com, or some variant. I’ve rarely encountered a situation where they provided a non-Google domain to serve as reference information. This, of course, is more anecdotal than anything else.

#4

Hi Alex,

yes absolutley legit here is the initial email from google. Disclosure has to be made clear using some kind of popup /notice etc as with websites.

Dear Publisher,

We want to let you know about a new policy about obtaining EU end-users’ consent that reflects regulatory and best practice guidance. It clarifies your duty to obtain end-user consent when you use products like Google AdSense, DoubleClick for Publishers and DoubleClick Ad Exchange.

Please review our new EU user consent policy as soon as possible. This requires that you obtain EU end users’ consent to the storing and accessing of cookies and other information, and to the data collection, sharing and usage that takes place when you use Google products. It does not affect any provisions on data ownership in your contract.

Please ensure that you comply with this policy as soon as possible, and not later than 30 September 2015.

If your site or app does not have a compliant consent mechanism, you should implement one now. To make this process easier for you, we have compiled some helpful resources at cookiechoices.org.

This policy change is being made in response to best practice and regulatory requirements issued by the European data protection authorities. These requirements are reflected in changes that have been recently made on Google’s own websites.

Thank you in advance for your understanding and cooperation.

Regards,
The Google Policy Team

*edited to add the originators URL : Google Ads Policy [publisher-policy-no-reply@google.com]

#5

Google AdSense and Admob are mutually exclusive, so I’m not sure that “products like Google AdSense” would apply to Admob. Admob is like AdSense in that they are both created by Google, and they both potentially serve ads. 

My above comment doesn’t even really address your main question, which I believe, is how would other developers include this disclosure in their apps. If I were to implement one, I would place my consent screen after my splash screen. They accept, they progress. If they don’t, it reminds them that they can’t use the app unless they consent, and if they do not on the second attempt, I would most likely inform them that the app needs to quit due to their non-consent.

#6

I received this mail too.

Any suggestions??

#7

Ok, seems admob is affected.

There is a running post here:

http://www.howtomakemobilegames.com/post/on-noes-google-has-a-new-policy-about-user-conscent-notifications-7520922?&trail=100

There is also a link to zeptolabs "om nom " or something, it displays something along these lines in the game.

#8

Has this affected no body here then ?

#9

I haven’t received any emails to this effect from either Apple or Google. Are you sure it’s legit? From whom did the email originate? When a user downloads an app from Google Play, they do have the permissions statement to review before they can even install it. IMO this is the disclosure. Also, you say you have a link to Google’s cookie disclosure. Does this document state that you need to inform the end user of data collection?

Normally if Google gives a url, it follows the template of http://<name of service>.google.com, or some variant. I’ve rarely encountered a situation where they provided a non-Google domain to serve as reference information. This, of course, is more anecdotal than anything else.

#10

Hi Alex,

yes absolutley legit here is the initial email from google. Disclosure has to be made clear using some kind of popup /notice etc as with websites.

Dear Publisher,

We want to let you know about a new policy about obtaining EU end-users’ consent that reflects regulatory and best practice guidance. It clarifies your duty to obtain end-user consent when you use products like Google AdSense, DoubleClick for Publishers and DoubleClick Ad Exchange.

Please review our new EU user consent policy as soon as possible. This requires that you obtain EU end users’ consent to the storing and accessing of cookies and other information, and to the data collection, sharing and usage that takes place when you use Google products. It does not affect any provisions on data ownership in your contract.

Please ensure that you comply with this policy as soon as possible, and not later than 30 September 2015.

If your site or app does not have a compliant consent mechanism, you should implement one now. To make this process easier for you, we have compiled some helpful resources at cookiechoices.org.

This policy change is being made in response to best practice and regulatory requirements issued by the European data protection authorities. These requirements are reflected in changes that have been recently made on Google’s own websites.

Thank you in advance for your understanding and cooperation.

Regards,
The Google Policy Team

*edited to add the originators URL : Google Ads Policy [publisher-policy-no-reply@google.com]

#11

Google AdSense and Admob are mutually exclusive, so I’m not sure that “products like Google AdSense” would apply to Admob. Admob is like AdSense in that they are both created by Google, and they both potentially serve ads. 

My above comment doesn’t even really address your main question, which I believe, is how would other developers include this disclosure in their apps. If I were to implement one, I would place my consent screen after my splash screen. They accept, they progress. If they don’t, it reminds them that they can’t use the app unless they consent, and if they do not on the second attempt, I would most likely inform them that the app needs to quit due to their non-consent.

#12

I received this mail too.

Any suggestions??

#13

Ok, seems admob is affected.

There is a running post here:

http://www.howtomakemobilegames.com/post/on-noes-google-has-a-new-policy-about-user-conscent-notifications-7520922?&trail=100

There is also a link to zeptolabs "om nom " or something, it displays something along these lines in the game.