Chrome quietly removed documentation stating its on-device AI features do not send data to Google servers.
Key Takeaways
Chrome had publicly claimed its on-device AI processed data locally without sending it to Google servers.
That claim has been removed, signaling the privacy guarantee was either inaccurate or no longer applies.
The change affects users who chose Chrome’s on-device AI specifically to avoid server-side data exposure.
A weights.bin file controversy is connected, suggesting model inference details were under scrutiny before the claim removal.
Hacker News Comment Review
Commenters treat this as confirmation of a long-standing pattern, not a surprise, framing it as consistent with Google’s broader data practices.
The Apple Pay vs Google Pay contrast is raised as a concrete counterexample: Apple Pay runs payment logic fully on-device and works offline; Google Pay phones home on every transaction.
Speculation exists that Chrome may be offloading compute to user devices while still transmitting data, referencing parasitic computing concepts.
Notable Comments
@ChrisArchitect: Links Android Authority coverage of the weights.bin controversy as direct prior reporting on this issue.
@askonomm: Contrasts Google Pay server dependency with Apple Pay’s fully on-device, offline-capable model as evidence of Google’s structural data appetite.
