Hot Take: Google Chrome, Gemini Nano, and the 4 GB Consent Problem Show Notes Google Chrome has been quietly downloading a roughly 4 GB AI model called Gemini Nano onto user devices in the background. No clear consent prompt. No notification. Just a file called weights.bin turning up in a folder called OptGuideOnDeviceModel like it pays the mortgage. In this Hot Take, Noel breaks down why this is not an "AI is evil" story. It is a consent story. A governance story. And a vendor entitlement story that every UK small business needs to take seriously. What Noel Covers Why a 4 GB background download is not a minor browser update What Google's own developer documentation confirms about model lifecycle management, background downloads, and full model updates Why "it was in the documentation" is not consent The governance mess this creates for managed business devices PECR and the ICO's guidance on storage and access technologies The environmental cost at Chrome scale (67.97% worldwide browser share) Why AI Mode in Chrome and on-device Gemini Nano are not the same thing, and why the confusion matters The embarrassingly simple fix Google has not implemented What UK small businesses should actually do about it right now Key Quote "We have somehow built frontier AI and still can't manage the radical engineering challenge of a bloody consent prompt." Read the Full Analysis The full article includes the complete source documentation, PECR regulatory detail, competitive advantage strategies, board-level talking points, and a step-by-step action list for UK small businesses. Read the full article on the blog Sources Referenced All 14 primary sources, including Google's own developer documentation, ICO PECR guidance, and StatCounter market share data, are cited in the full blog post. Full source table in the article

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related