
Google Chrome silently installs 4 GB Gemini Nano AI model to user device without consent
As reported by That Privacy Guy, Google Chrome has begun silently deploying a 4 GB Gemini Nano AI model file, named weights.bin, onto user devices without requesting explicit consent. The file resides in the OptGuideOnDeviceModel directory and contains the on-device large language model used to power various AI-driven browser features.
When users delete the weights.bin file, Chrome automatically re-downloads it as long as browser AI features remain active. Following this behavior, features such as “Help me write” and on-device scam detection are enabled by default on any machine that meets specific hardware requirements. While these functions were introduced to enhance browsing, Chrome does not display a consent prompt or settings checkbox before installing the supporting AI model, leaving many users unaware of its presence.
To prevent Chrome from restoring the file, users must manually disable AI features via chrome://flags or implement enterprise policy tools, methods which are not generally accessible to home users. Alternatively, uninstalling Chrome removes the AI model. This approach has drawn criticism regarding both privacy practices and the environmental impact associated with unsolicited 4 GB downloads on millions of devices. Observers are now watching to see if future versions of Chrome will require explicit opt-in for such AI features in response to the growing backlash.




Comments
Some people like using AI tools in their browser and some people don't. But, damn Google, give us a choice. 4GB is a decent chunk of storage space!
Very good point from a consumer's point of view. From a corporation's point of view (besides tracking consumers and all other unpleasant things) every opt-out option is an additional fork and maintenance cost. Now Google would have to make sure that Chrome works well with AI and without. In reality, any corporation would like to maintain only one version of consumer software and on as few platforms as possible. It's way cheaper this way.
That's an interesting take. I wouldn't say there's an overhead with forking code, but potentially maintenance. You will already know this, but systems are built with feature flags or configurable options to enable/disable features to tailor our user experience. I'm a dev, too, and it's pretty much standard practice for us. Looking back at the Firefox and AI "debacle", Mozilla implemented a kill switch for those who don't want it. Consumers want the opt-in choice, but these tech orgs get too excited and just throw things in our face as if they chose it's something we need, which we probably don't and opt-out is an after thought. Screw that.
And this is why I don't use Chrome. I use Helium in a compact minimalistic mode. For the rare case of needing DRM I use a heavily debloated Edge since it's already installed.
the avg chrome user won't really care honestly, i mean their reasoning for using chrome is still "because its fastest" lmao
Google did a thing...it was bad...again..smh.