Summary of The case for banning cookie banners

Overview of The VergeCast episode: The case for banning cookie banners

Host David Pierce opens with a quick phone tangent (a modular “side phone”) and then dives into two main interviews. First, Kate Klonick (professor/author) makes a forceful case for eliminating cookie banners. Second, Allison Johnson (The Verge) describes her hands‑on experience with Ask Maps — Google Maps’ Gemini‑powered planning assistant. The hosts also field a listener hotline about e‑ink phones and discuss the practical and privacy tradeoffs of AI in location services.

Key topics & structure

• Introduction: host’s new “side phone” hardware concept (modular attachments).
• Main segment 1: cookie banners — history, problems, and why Kate Klonick argues they should be removed.
• Main segment 2: Ask Maps (Gemini in Google Maps) — how it works, real‑world use, benefits and risks.
• Hotline: listener question about e‑ink phones as a way to “slow down” smartphone use.
• Housekeeping: call for listener questions/screenshots; upcoming episode about The Verge.

Kate Klonick on cookie banners — history, problems, and proposal

How cookie banners got here

• Cookies are a neutral web mechanism (session state, “breadcrumbs”) that became central to ad tracking.
• Europe reacted earlier and more aggressively than the U.S. (e‑privacy directive → GDPR-era developments), producing rules that required user control over processing.
• Industry, lawyers, and compliance teams shaped how regulations were implemented; pop‑up banners became the de facto compliance mechanism even though the original rules didn’t mandate a banner.

Why banners are worse than “neutral”

• They offer “manufactured consent”: the illusion of meaningful choice while accomplishing little.
• Banners have calcified into an industry standard that eases regulatory pressure and preserves tracking practices.
• They impose real costs: time/attention, user friction, energy and network overhead, and they crowd out discussion of better solutions.

What Klonick recommends

• Remove cookie banners entirely to force a policy and product rethink; a temporary “nothing” might be preferable to a broken system that stifles better options.
• Consider alternatives: browser‑level or middleware solutions, clearer technological/legislative approaches, possibly economic models (e.g., compensated data sharing) — though she admits no perfect replacement exists yet.
• Regulators (EU is re‑examining rules) and industry should pursue new conversations, not rely on the banner compromise.

Notable quotes / framing

• “Manufactured consent” — the term Klonick uses to describe the illusion of meaningful user agreement.
• “You don't have to have bruised shins” — a metaphor for fixing a broken UX rather than tolerating ongoing friction.
• “Brussels effect” — EU rules often become de‑facto global solutions because big platforms standardize worldwide.

Allison Johnson on Ask Maps (Gemini + Google Maps)

What Ask Maps is

• A Gemini chat interface embedded in Google Maps that can:
  • Answer natural‑language, contextual queries (e.g., plan a date, find kid‑friendly coffee shops).
  • Pull from Google Maps data: reviews, place info, transit, weather.
  • Consolidate itinerary details (stops, transit links, suggested timing).

How Allison used it (day‑trip experiment)

• Gave Gemini constraints (public transit, lunch, walk, laptop‑friendly coffee shop, home by 4:30).
• Ask Maps produced an itinerary: suggested restaurants/parks, transit timing, weather checks.
• Benefits:
  • Saves time and cognitive effort stitching multiple Map searches into a single plan.
  • Helpful for exploratory/recreational use — finds neighborhood spots, transit routes, practical timings.
  • Particularly useful for non‑standard queries (e.g., kid‑friendly stops, “places with train views”).

Limitations and UX issues

• Personalization sometimes repeats places the user has already visited; Ask Maps doesn’t always respect or fully leverage past history/local knowledge.
• Exporting itineraries and integration with other tools (e.g., Google Docs or a multi‑stop navigation workflow) felt clumsy or incomplete.
• Interface choices around how much of your data/history it surfaces are still being worked out.

Privacy and broader concerns

• Ask Maps intensifies the location‑data tradeoff: more useful recommendations come from deeper knowledge of users’ movements and preferences.
• Users feel tension: the utility of Maps vs. unease about how much Google knows (location history, tagged photos, kids’ names via Google Photos).
• Allison’s take: she finds Ask Maps genuinely useful for certain use cases and is comfortable using it for exploratory plans, despite the privacy unease.

Hotline: e‑ink phones — practical verdict

• Idea: an e‑ink phone could slow down attention and cut social video consumption.
• Practical experiences and issues:
  • Secondary e‑ink devices (or an “e‑ink mode” on a conventional phone) can be great for reading and battery life, but are hampered by:
    • Slow refresh / visual artifacts; poor multimedia/camera experiences.
    • App compatibility and general usability for day‑to‑day tasks (maps, websites, photos).
  • The “mode switch” approach (make it intentionally harder to access distracting apps) may be more effective than a full e‑ink UI. Physical friction (a “brick” you must walk to, a hardware switch) often succeeds where software toggles fail.
• Conclusion: e‑ink phones are promising for a niche/secondary device role, but not yet a practical single‑phone replacement for most users.

Key takeaways

• Cookie banners have become a counterproductive permanent solution: they create superficial compliance and prevent real privacy innovation. Klonick argues removal would open space for better regulation and product designs.
• Ask Maps demonstrates a compelling, practical application of generative AI in location services — it saves planning time and surfaces experiences — but raises sharper privacy and personalization questions because it’s grounded in rich location and review data.
• E‑ink phones can help limit distractions as a secondary device or via increased friction, but hardware and UX limitations keep them from replacing mainstream smartphones today.

Actions & recommendations (for listeners)

• If you experience especially bad cookie banners, screenshot them and send them to the show (VergeCast hotline: 866‑VERGE‑11; email: vergecast@theverge.com) — the hosts want examples to “name and shame.”
• Try Ask Maps if you use Google Maps and want help planning multi‑stop or exploratory outings — it’s most useful for recreational planning and rapid itineraries.
• If you want to cut phone distractions, consider friction solutions (hardware or behavioral) in addition to software limits — full e‑ink replacements still have major tradeoffs.

Further context / follow ups in the episode

• The EU is actively rethinking parts of its data‑protection rules; cookie banners are on the table for simplification or removal.
• The episode ends with a call for listener questions about The Verge for an upcoming episode and thanks to guests and producers.