People confuse GDPR with ePrivacy. GDPR is not about cookies and it’s not about mere informing of users, but about getting consent for data processing. Publish

People confuse GDPR with ePrivacy. GDPR is not about cookies and it’s not about mere informing of users, but about getting consent for data processing. Publishers and service providers are required to ask for consent, with clear language and the default is opt-out. Also from what I understand you can’t block users from using your service when they opt out of any data purpose that isn’t legitimate and the definition of legitimate data purposes is very narrow. For example it doesn’t really matter that ads profiling is how the company makes revenue, making more money is not a legitimate interest. Some companies, like Facebook, are of course trying to resist this. But I’m pretty sure they’ll end up with big fines. On popups, IAB’s specification uses the consensu.org domain for the cookie, so that consent can be shared between multiple domains. A publisher cannot share that consent with other publishers in case the list of partners used is custom of course, but you can still share it between your own domains. The purpose being to minimize the popups. Given that publishers have a legal obligation to get the user’s consent, I strongly believe that ad-blockers blocking GDPR popups is legal trouble for both publishers and ad-blockers. Blocking ads wasn’t deemed illegal thus far and it wasn’t for a lack of trying. Blocking GDPR pop-ups on the other hand will imo not have that same fate. Also some users will legitimately want to have their data used for personalization and you can’t regulate against that. This might be an unpopular opinion however given the choice between personalized ads and a paywall, I predict that most people will choose personalized ads.