Chrome Quietly Deleted Its On-Device AI Privacy Promise

Every browser update now ships with another AI feature you didn’t ask for. What’s getting harder to find is a clear answer to where your data actually goes. Google just deleted a single sentence from Chrome’s official documentation — the one that promised on-device AI never sends data to Google servers — and the silence around the change is louder than the change itself.

What “On-Device” Was Supposed to Mean

The term carried weight for a reason. On-device AI means the model runs inference locally, on your machine. Inputs and outputs stay put. No round trip to a cloud GPU farm.

When Google rolled Gemini Nano into Chrome last year, this was the entire pitch. Your prompts don’t leave your laptop, so type away. For anyone who’d watched a decade of “anonymized telemetry” turn into ad targeting, that promise wasn’t marketing fluff — it was the reason to opt in.

The Sentence That Vanished

The problem is how the promise disappeared. No changelog. No blog post. No footnote. A developer comparing documentation revisions noticed the line was gone, and that’s how the broader community found out.

The replacement language is the kind of phrasing lawyers love and users should hate — something to the effect of “data may be processed.” “Does not send” became “may send.” One word. Opposite meaning.

Three Plausible Reasons for the Edit

Google hasn’t commented, so we’re left with theories. Three stand out.

The first is a shift to hybrid processing: light tasks run locally, heavier ones get punted to the cloud. If that’s what’s happening, the old sentence wasn’t just outdated — it was wrong.

The second is telemetry and model-improvement data. Even if inference itself stays on-device, usage patterns, error logs, and prompt metadata can still ship out in “anonymized” form. Strictly speaking, that’s data leaving the device.

The third is the most boring and probably the most accurate: legal risk management. Absolute claims age badly. Removing the sentence preemptively keeps options open for whatever the product team ships next quarter.

What This Changes for You

You don’t need to uninstall Chrome over this. But you should drop the assumption that on-device equals airtight privacy. That equation doesn’t hold anymore — at least not as a guarantee Google is willing to put in writing.

If you’ve been using Chrome’s AI to summarize internal docs, polish sensitive emails, or draft anything covered by an NDA, this is worth a pause. You no longer have a clear answer about where the input is processed or what leaves the machine. Linus Tech Tips kicked off their “de-Googling” series last year by going after Chrome first, and that video pulled close to 3 million views. The thesis just got fresher.

The Real Issue Is Transparency

The worst part of this story isn’t where the data goes. It’s that Google changed a privacy commitment without telling anyone.

Documentation should follow architecture — fine, that’s how engineering works. But quietly editing the privacy posture of a browser used by billions, with no changelog and no notice, undermines every other guarantee in the document. If the promises can change overnight, the promises were never the point. How often do you actually check what your browser is promising you this week versus last?