If you have a mobile app that shows ads or needs any sort of GDPR consent in any way you have to buy this the first day it’s out. Impossible it doesn’t save you thousands of dollars in dev time alone.
For the especially severe violations listed in Art. 83, para. 5 of the GDPR, the fine framework can be up to € 20 million, or in the case of a company, up to 4% of their total global turnover in the previous fiscal year, whichever is higher. But even the catalogue of less severe violations (Art. 83, para. 4) sets forth fines of up to € 10 million, or, in the case of a company, up to 2% of its entire global turnover of the previous fiscal year, whichever is higher.
Required by GDPR
Provided by Consent Monitor
|Collect explicit consent if your app uses an ad network to show personalized ads.|
|Request for consent is prominent and separate from the terms and conditions.|
|Requests for consent don't use pre-ticked checkboxes or any other type of default measures.|
|Requests for consent are made in clear, plain language that is easy for the user to understand.|
|Requests for consent contain an explanation of why the data is collected and how it will be used.|
|Users are given an option to consent separately to distinct purposes of use for each piece of data collected.|
|Users are informed about the organization and any third-party controllers who will be relying on the consent.|
|Users are informed about their right to withdraw their consent.|
|Users are given the ability to easily withdraw their consent.|
|A record is retained of when and how consent is collected from each user.|
|A record is retained of the exact wording of the request that the user gave consent to.|
|User is given the ability to submit a request to be forgotten and have their data purged.|
This looks like a really interesting solution for what could be an intractable problem for mobile developers, especially smaller ones with fewer resources.