More difficult to remove than install. Adding the file took zero clicks. Removing it requires (a) discovering the file exists, (b) understanding what it is, © navigating into a hidden user profile path, (d) deleting it (and on Windows, also clearing the read-only attribute first), and (e) accepting that Chrome will silently re-download it on next eligible window unless the user also navigates chrome://flags, enterprise policy, or platform-specific configuration tooling to disable the underlying Chrome AI feature [5]. None of those steps is documented in the place a normal user looks - none of them is even hinted at in default Chrome.

This is 5: https://pureinfotech.com/stop-chrome-gemini-nano-download-windows-11/

Obviously only windows focused, so how other platforms stop would require more searching.

So we now have a four-way evidence chain - macOS kernel filesystem events, Chrome’s own per-profile state, Chrome’s runtime feature flags, and Google’s component-updater logs - all four agreeing on the same conduct, and the conduct is: a 4 GB AI model arrived on this user’s disk without consent, without notice, on a profile that received zero human input, in a window of 14 minutes and 28 seconds, on a Tuesday afternoon.