Cookies and Consent
Podcast · Cookies and Consent

Why Your Cookie Banner Is Illegal

by ZumiLabs · 22m
0:00 22m

Transcript

Made automatically from the audio, so it may contain mistakes. Click a line to play from there.

Host 1

Imagine this scenario, right? You are, well, days away from a massive product launch.

Host 2

Oh, the classic crunch time.

Host 1

Exactly. And suddenly your lead growth marketer is frantically messaging the front end engineering team. I mean, they are begging them to swap out traditional cookies for local storage and browser fingerprinting.

Host 2

Yeah. We're trying to hide the reject button.

Host 1

Right. They're pleading to take the reject all button on the cookie banner and just bury it behind a tiny invisible managed settings link. And they want to justify this whole maneuver by claiming, you know, it falls under legitimate interest.

Host 2

Which is always the excuse.

Host 1

Always. And why are they doing this? Because ad attribution rates are plummeting in Europe and absolute panic has just set in.

Host 2

Meaning that specific panic is playing out in product Slack channels all over the world today. And those clever technical workarounds being proposed, they are without a doubt, a complete legal minefield.

Host 1

Totally.

Host 2

Every single one of those desperate tactics to maintain visibility is actually a direct violation of regulatory law.

Host 1

Which is the exact reason we are unpacking this today. So welcome to the third part of our deep dive series into privacy, data, and AI law.

Host 2

Glad to be here for this one.

Host 1

Today our lens is focused sharply on cookies, device trackers, valid consent, dark patterns, and analytics. We are talking directly to you, the founders, product managers, engineers, and marketers who are in the trenches actually building these digital products.

Host 2

The people who actually have to write the code and design the banners.

Host 1

Right. Now let's get our mandatory disclaimers out of the way. This is general information, not legal advice. Everything we discuss is grounded in primary regulatory sources. Current as of today, November 16th, 2026.

Host 2

We have a very clear mission for this deep dive. We're going to dismantle some of the most persistent growth marketing myths that have really infected the tech industry.

Host 1

They really have.

Host 2

Yeah. We'll also be highlighting where specific national regulators like the French CNIL or the UK ICO actually diverge from the standard baseline rules. Because those subtle nuances well, they dictate how you build your technical architecture.

Host 1

Absolutely. Also, a quick reminder on assumed prerequisites for you all listening. We are jumping straight into the deep end, assuming you've already consumed part zero on the regulatory map, part one on GDPR roles, and part two.

Host 2

Right. No going back over the basics today.

Host 1

Exactly. Just to refresh your memory on our last deep dive, though, we mapped the precise borders of what counts as personal data under the GDPR, including the critical distinction between pseudonymization, which is still highly regulated, and true anonymization, which is not.

Host 2

A very crucial line to draw.

Host 1

So with that baseline established, okay, let's unpack this. I want to start with that desperate marketer trying to swap out cookies for local storage.

Host 2

Oh man. This is perhaps the most dangerous myth circulating in product teams right now.

Host 1

It really is everywhere.

Host 2

It is.

Host 1

Right. They think they found a loophole.

Host 2

Exactly. The logic is, well, if we use local storage or a tracking pixel or a mobile SDK, or if we just check the user's system fonts and battery level to create a browser fingerprint, we aren't using cookies, so we're safe.

Host 1

Spoiler alert, they are not safe.

Host 2

Not even a little. The black letter law from Europe's e-privacy rules shatters that assumption completely. The law isn't just about cookies, it protects the user's terminal equipment.

Host 1

You know, I always try to visualize a user's terminal equipment, so like their smartphone, their laptop, as their private home.

Host 2

That's a great way to look at it.

Host 1

Right. It doesn't matter if a burglar breaks in and only steals a generic paperclip, or even just like takes a photograph of your floor plan.

Host 2

Yeah, the paper clip isn't the point.

Host 1

Exactly. The crime is the act of breaking into the house in the first place. It's the unauthorized access that is heavily regulated.

Host 2

That analogy captures the legal reality perfectly. And this principle, it was cemented in the landmark Planet 49 case in the European courts.

Host 1

Oh, that was a huge case.

Host 2

Massive. The ruling made it undeniably clear that the law protects the terminal equipment, regardless of whether the data you're processing is considered personal data under the GDPR.

Host 1

Wait, that is a massive point. That completely blows up the common engineering argument of, but we aren't storing PII.

Host 2

It absolutely does. The courts basically said the private sphere is protected, period.

Host 1

Wow.

Host 2

Yeah. So if your script writes a unique identifier to track a user across the web, like in local storage, or if you simply passively scan their device to check their exact screen resolution and operating system to create a fingerprint.

Host 1

Which happens all the time.

Host 2

All the time. But you are interacting with their private device. Under e-privacy rules, getting access to information already stored on that device or storing new information on it requires prior informed consent.

Host 1

So it's a blanket rule.

Host 2

It blankets everything. Local storage, social media pixels, mobile SDKs, all of it.

Host 1

Okay, so that brings us to the next massive point of friction. And honestly, a loophole I hear growth teams pitch constantly.

Host 2

Let me guess. Legitimate interest.

Host 1

You guessed it. They say fine, we admit we're accessing the device, but what if we just categorize our meta-tracking pixels under the lawful basis of legitimate interest instead of actually asking the user for explicit consent?

Host 2

Yes.

Host 1

It's treated like the ultimate get out of jail free card by marketing teams.

Host 2

Well, regulators have thoroughly investigated that card and completely revoked it.

Host 1

It's totally dead.

Host 2

It is dead. The idea of using legitimate interest as a workaround for tracking pixels and personalized advertising is just over.

Host 1

Good to know.

Host 2

Yep. If we look at the meta ruling in the European courts and the subsequent guidelines from the European Data Protection Board, they outline a very specific mechanism.

Host 1

Which is what exactly?

Host 2

Well, when you place a social pixel on your website, you aren't just a passive bystander observing traffic. You are actively forcing your user's browser to send their data directly to a massive third-party advertising network.

Host 1

Which means legally you and that social network are basically partners in crime.

Host 2

In legal terms, it creates a joint controllership.

Host 1

Joint controllership. Yeah. Got it.

Host 2

You, the website publisher, are equally on the hook for how that data is collected and transmitted. And when you try to claim legitimate interest, you have to pass a balancing test.

Host 1

Right, weighing the pros and cons.

Host 2

Exactly. You're weighing the marketer's commercial interest in selling ads against the user's fundamental right to privacy.

Host 1

And I'm guessing the user wins that one?

Host 2

Every time. When you are tracking a user across the internet to build a highly intimate, invisible psychological profile of their habits, the user's fundamental rights almost always win.

Host 1

So you cannot bypass the consent banner. You actually have to ask permission.

Host 2

You have to ask. And the consent must be a freely given, specific informed, and unambiguous prior opt-in.

Host 1

That's a lot of adjectives.

Host 2

It is, but they all matter. Furthermore, regulators mandate that it must be just as easy for the user to withdraw that consent later as it was to give it in the first place.

Host 1

Okay, let's really dig into the mechanics of that phrasing. Freely given an unambiguous prior optum, because this drags us kicking and screaming into the world of user experience and banner design.

Host 2

Oh, the wild west of UX.

Host 1

Truly. I mean, we both know how much the industry loves a giant, bright green, flashing accept all button sitting right next to a tiny gray, practically camouflaged text link that says manage settings.

Host 2

Yes, the classic dark pattern.

Host 1

The entire psychological goal there is to just exhaust the user into clicking accept just so they can read the article.

Host 2

The industry has essentially been relying on cognitive friction to manufacture consent. But the regulatory task force on cookie banners specifically analyze these design tricks and categorize them as direct infringements.

Host 1

So they are explicitly illegal now.

Host 2

Yes. Designing a banner with no reject button on the first layer, meaning you force the user to click into a second menu just to say no is a blatant violation.

Host 1

Wow. And what about those check boxes that are already checked for you?

Host 2

Another widespread violation they flagged. Presenting users with pre-ticked boxes is out. The courts have explicitly ruled that a pre-ticked box does not constitute active consent.

Host 1

Right.

Host 2

Silence or just giving up and closing the banner is not consent.

Host 1

It is genuinely amazing how long the internet operated that way. I mean, you'd visit a site and every single intrusive tracking option was already toggled to on by default.

Host 2

And you had to manually untoggle 50 different vendors while the banner lagged?

Host 1

Exactly. It was infuriating.

Host 2

Well, the tolerance for those tactics has completely evaporated. And we are seeing a unified transatlantic crackdown on this.

Host 1

Even in the U.S., yes.

Host 2

The California Privacy Protection Agency recently issued an advisory demanding symmetric choices and clear language.

Host 1

Symmetric meaning equal buttons.

Host 2

Exactly. If you present an accept all button, you must have a visually equal, identically prominent reject all button right next to it.

Host 1

So the era of manipulative UX is actually closing, which makes sense when you look at broader legislation too, like the Digital Services Act in Europe, which actually bans these deceptive designs outright for online platforms.

Host 2

Right. The DSA explicitly targets what we call dark patterns, manipulative UX designs created solely to subvert user autonomy.

Host 1

It's all about autonomy.

Host 2

It is.

Host 1

Okay, so the baseline rules are crystal clear. You need a symmetric accept all and reject all button on the very first layer. You need affirmative opt-in, no pre-ticked boxes, no fake legitimate interests for tracking pixels.

Host 2

That's the baseline, yes.

Host 1

But here is where it gets really interesting, because we have to bridge the gap between regulatory theory and actual product development.

Host 2

Right. Where the rubber meets the road. Exactly. Yeah. If a product manager can't track behavior without consent, how do they even know if their website is functioning? This brings up the massive gray area of basic analytics. It's probably the most common dilemma teams face. The strict rule says any non essential access to the terminal equipment requires consent.

Host 1

But what about simply counting page views?

Host 2

Right, is knowing how many people visited your checkout page strictly essential to providing the service?

Host 1

Most product managers would scream, yes. I mean, it's the lifeblood of running the business. But historically, legally, even basic analytics have required the user to opt in.

Host 2

They have. However, you mentioned earlier that we'd highlight where national regulators diverge.

Host 1

Yes, the exceptions.

Host 2

Right. And France's data protection authority, the CNIL, has carved out a very specific, very narrow exemption here.

Host 1

Oh, this is a vital nuance for anyone deploying products in Europe.

Host 2

It really is. The CNIL allows for first-party audience measurement without prior consent.

Host 1

Meaning you can actually count your visitors without waiting for them to click accept on a banner.

Host 2

Yes.

Host 1

But let me stop you right there because I want to make sure everyone listening gets this right. You can't just plug in standard Google Analytics out of the box and claim this French exemption, right?

Host 2

Absolutely not. Do not do that.

Host 1

Yeah, I figured.

Host 2

The technical caps on this exemption are incredibly rigid. The analytics must be strictly for your own first-party measurement.

Host 1

Okay, so no sharing.

Host 2

Right. You cannot use cross-site tracking IDs that follow the user to other websites. You also must implement mandatory IP truncation. Which means meaning you intentionally delete the last few digits of the user's IP address so it cannot be traced back to a specific household.

Host 1

Got it.

Host 2

But the biggest hurdle, the one that catches most teams, is that there must be absolutely zero vendor reuse of the data.

Host 1

Okay, let's explain why that matters. Why do regulators care if the vendor reuses the data? As long as I get my page view metrics.

Host 2

Because of the hidden mechanics of third-party tools.

Host 1

Right.

Host 2

When you plug in a standard free analytics tool, that vendor isn't providing that service out of the goodness of their heart.

Host 1

Definitely not.

Host 2

No. They are pooling the data from your website with data from millions of other websites across the internet. They're building massive shadow profiles of users behind the scenes to train their own algorithms and fuel their own advertising networks.

Host 1

So you're feeding their machine.

Host 2

Exactly. The second your user's data enters that global pooling machine, you are no longer doing first party measurement. You are feeding a global tracker. That is why the exemption immediately breaks.

Host 1

So if you are using out of the box tools where the vendor pools the data, you unequivocally need prior opt-in consent across the EU and the UK.

Host 2

You do.

Host 1

So the CNIL exemption is a highly technical precision instrument. It requires deliberate engineering, not just installing a plugin.

Host 2

It requires you to technically guarantee that the data stays siloed for your eyes only.

Host 1

That makes total sense. Okay, let's pivot to another massive gray area, one that is really dominating tech headlines right now. Consent or pay. Yeah, we are seeing dominant platforms give users an ultimatum. Either give us your consent to track you for personalized ads or pay a monthly subscription fee to use our service.

Host 2

The infamous pay or okay model.

Host 1

That's the one.

Host 2

It's highly controversial. And the European regulators recently issued a stark warning regarding the risks that large online platforms face when they force these models on their users.

Host 1

Because it messes with the idea of freely given consent.

Host 2

Exactly. The entire debate hinges on that phrase we discussed earlier. Consent must be freely given.

Host 1

Well, let me play devil's advocate for the product builders listening. Go for it. Running a massive platform with millions of users costs an absolute fortune in server fees and engineering salaries. If a user flat out refuses to view personalized ads, which is how the business actually survives, why shouldn't the business be allowed to charge them a subscription to cover those costs?

Host 2

It's a fair question.

Host 1

Right. Why do regulators view that as coercive rather than just a basic economic transaction?

Host 2

It really comes down to the imbalance of power.

Host 1

How so?

Host 2

Well, if the service is a minor entertainment app, maybe it is a fair transaction. You don't need it to survive. But what if the service is a dominant social network that you absolutely rely on for your business or to communicate with your family?

Host 1

So it's about dependency.

Host 2

Right. If a user faces a significant negative consequence, like being locked out of a vital service or facing an unreasonably high punitive fee simply because they want to protect their fundamental right to privacy. Well, regulators question whether the choice to click accept was truly free.

Host 1

Yeah, it feels less like a choice and more like being held for ransom at that point.

Host 2

Exactly. The concern is that privacy becomes a luxury good, only available to those who can afford the monthly fee.

Host 1

Which goes against the whole concept of privacy as a fundamental human right.

Host 2

Now, while regulators haven't banned consent or pay in every single scenario across the board, they strongly advise that dominant platforms need to offer an equivalent free alternative that does not involve behavioral advertising.

Host 1

So relying on a strict ultimatum is legally perilous.

Host 2

Very perilous.

Host 1

Now I want to move from the philosophical debates to the actual code base.

Host 2

You're talking about the race condition, aren't you?

Host 1

I am.

Host 2

The notorious tag manager race condition.

Host 1

The race condition.

Host 2

The absolute bane of the front end developer.

Host 1

Exactly. You spend weeks designing a beautiful, compliant, perfectly symmetrical cookie banner through a consent management platform.

Host 2

It looks great on screen.

Host 1

Right. But because of how modern websites are loaded asynchronously, your third-party tracking scripts in your tag manager actually fire milliseconds before your consent banner fully loads and registers what the user actually wants.

Host 2

And this is where your house and burglar analogy comes right back into play.

Host 1

It is. It's like letting a vampire into your house while you are still standing on the front porch asking if they want to come in.

Host 2

It's a great image.

Host 1

By the time the user sees the banner, the tracker is already inside the terminal equipment executing code.

Host 2

And legally speaking, that vampire represents a direct breach of the GDPR rules that mandate data protection by design and by default.

Host 1

Because it defaulted to on.

Host 2

Exactly. It's not enough for your legal team to approve the visual design of a banner. Your engineering architecture must strictly enforce it.

Host 1

Right.

Host 2

If marketing scripts are firing and accessing the terminal equipment before the consent signal is actively registered as true, you are operating illegally. The default state at the network level must be off.

Host 1

Which means your QA teams cannot just be clicking buttons on the user interface and assuming it works.

Host 2

No, visual testing is useless here.

Host 1

They have to actually audit the network traffic.

Host 2

They do. And this strict technical banner first opt-in approach we've been discussing, it's very specific to Europe.

Host 1

Yeah, let's contrast that a bit.

Host 2

To briefly set the stage for global products, we are seeing a drastically different architectural mindset emerging in the United States.

Host 1

Right. The US is trying to figure out how to move away from pop-up fatigue entirely, relying instead on browser level signals.

Host 2

The primary mechanism there is the global privacy control or GPC.

Host 1

How does that work in practice?

Host 2

Instead of forcing a user to manually click reject all on thousands of individual websites, the GPC allows users to set their privacy preference once in their browser settings.

Host 1

Oh, that sounds so much better.

Host 2

It is. A lot of ground covered today.

Host 1

For sure. But how do you actually operationalize this into your daily sprints? We have distilled this down into three mandatory habits for digital teams.

Host 2

Let's run through them. Habit number one, you must audit your incognito network traffic.

Host 1

Crucial step.

Host 2

Yeah. Before you interact with your own cookie banner, open your developer tools, navigate to the network tab, and watch the scripts load. If you see advertising tags, pixels, or non essential SDKs firing before you have actively clicked accept all, you have a race condition.

Host 1

And you have to fix it.

Host 2

You must reconfigure your tag manager so the default state is strictly off.

Host 1

Habit number two. Enforce symmetric layer one buttons. Go look at your live cookie banner right now.

Host 2

Seriously, go look at it.

Host 1

If accept all is bright blue and manage settings is hidden in tiny great text, you need to change it today. Put a clear, visually identical reject all button right next to the accept button.

Host 2

No more tricks.

Host 1

And while you're auditing that, ruthlessly eliminate any fake, legitimate interest toggles for tracking pixels. They are legally invalid, just get rid of them.

Host 2

And habit number three do not forget to audit your mobile applications alongside your web tags.

Host 1

Mobile, the forgotten frontier.

Host 2

Exactly. The French regulator recently published specific guidelines targeting over permissioning in mobile apps.

Host 1

What does that look like?

Host 2

Well, if your app requests access to the microphone location data or contact list, and then silently funnels that raw data to third-party SDKs for advertising without explicit layered consent, you are directly in the regulatory crosshairs.

Host 1

Mobile is not a lawless frontier.

Host 2

Not at all. The terminal equipment rules apply equally to the phone in your pocket.

Host 1

And as always, remember to engage your actual legal counsel when you are implementing these changes. Product nuances, specific tech stacks, and your exact business model require specific legal mapping that we simply cannot do on a general deep dive.

Host 2

Right. The engineering reality of how a specific data packet flows requires nuanced legal interpretation to ensure it actually matches the statutory requirements. You have to bridge the gap between the code and the law.

Host 1

Which tees up our next conversation perfectly. In part four of the series, we are going to pivot our focus entirely to the U.S. picture.

Host 2

That's gonna be a fun one.

Host 1

We will explore the California regulations, dive deep into the technical implementation of the global privacy control we just mentioned, and try to untangle the massive headache that is U.S. state level fragmentation.

Host 2

It requires a completely different architectural mindset. It is absolutely essential knowledge for anyone building for a global user base.

Host 1

But before we let you go, I want to leave you with a lingering question to ponder. We just talked about the global privacy control allowing our web browsers to automatically negotiate our privacy boundaries in the background without us ever having to lift a finger.

Host 2

A beautiful concept.

Host 1

It is. When that technology finally becomes ubiquitous and standardized, will we look back on this current era of manually clicking accept or reject on thousands of individual manipulative cookie banners as a primitive, wildly inefficient phase of the early internet?

Host 2

It's a fascinating thought to consider. Are we currently just slapping regulatory band-aids on a fundamentally broken system? Well, the actual long term solution lies in fixing the infrastructure itself.

Host 1

Definitely something to mull over before your next sprint planning meeting. Thanks for diving deep with us.

Save to playlist

Manage playlists →

Share