Chrome Quietly Removed Its Privacy Promise About On-Device AI—Here’s What It Means for You

Introduction

Google recently made a quiet change to Chrome’s privacy description that went largely unnoticed—until journalists and security researchers pointed it out. The company removed a previous promise that its “on-device AI” feature does not send data to Google servers. This matters because the feature, which is designed to run AI models directly on your computer, has been rolling out to more users in recent months, and many people assumed their data never leaves the machine.

If you use Chrome, here’s what actually changed, how to check whether the AI model has been installed on your device, and what steps you can take if you want to limit data sharing.

What Happened

The original privacy claim appeared in Chrome’s settings and documentation for on-device AI. It explicitly stated that the feature “does not send data to Google servers.” That wording has now been removed. As of early May 2026, the updated phrasing no longer offers that guarantee. Reports from Decrypt and GIGAZINE confirmed the deletion, and the change aligns with other developments: Chrome has been quietly downloading a roughly 4GB AI model onto some users’ systems, and some users have reported that deleting the model doesn’t seem to stick—Chrome will re-download it.

Importantly, this on-device AI feature is separate from other Chrome AI tools like “Help me write” or the built-in Gemini side panel. The specific feature in question seems to be related to an internal model that powers certain browser-level AI functions, such as smart text selection, summarization, or image understanding. Google hasn’t publicly explained why the privacy promise was removed, but the implication is clear: data may now leave your device under some circumstances.

Why It Matters

For many people, “on-device” processing is a key privacy advantage. It means sensitive data—like emails, browsing habits, or documents—doesn’t travel to a cloud server, reducing exposure to breaches, government requests, or third-party access. Removing that promise undermines trust. Even if Google claims the feature still runs locally in most cases, the removal suggests that the company wants the flexibility to send data to its servers, perhaps for model improvement, debugging, or future features.

The timing is also worth noting. As AI features become more embedded in browsers, the line between local and cloud processing is blurring. Chrome’s move highlights the need for users to take a more active role in managing these settings.

What Readers Can Do

1. Check if the AI model is installed on your computer

The model file is stored in Chrome’s user data directory. The exact path varies by operating system:

  • Windows: %LOCALAPPDATA%\Google\Chrome\User Data\OnDeviceAI
  • macOS: ~/Library/Application Support/Google/Chrome/OnDeviceAI
  • Linux: ~/.config/google-chrome/OnDeviceAI

Open that folder and look for subfolders containing model files. If the folder is empty or doesn’t exist, the model hasn’t been downloaded yet. If you see files, the model is already on your system.

Alternatively, you can check Chrome’s internal settings by typing chrome://settings/ai in the address bar. Some builds show an “On-device AI” toggle or status indicator here.

2. Disable or remove the on-device AI feature

Chrome’s AI settings have been changing rapidly, but as of now, you can try the following:

  • Go to chrome://settings/ai and look for any option related to “on-device AI” or “local AI model.” Turn it off if available.
  • If you want to remove the downloaded model, delete the entire OnDeviceAI folder mentioned above. Note: Chrome may re-download it later (reports suggest it does, especially after a restart). To prevent that, you can make the folder read-only or block Chrome’s write access using your operating system’s permissions.
  • For a more permanent solution, consider disabling Chrome’s automatic updates or using a flag. Type chrome://flags/#optimization-guide-on-device-model and set it to “Disabled.” Flags can change, so check that this flag still exists.

3. Consider alternative browsers

If you want a browser that is more transparent about local AI processing, a few options exist:

  • Firefox: Mozilla has been developing on-device AI features called “Firefox AI” but has stated it will not send user data to its servers. Mozilla’s privacy policy is generally more explicit about local-only processing.
  • Brave: This Chromium-based browser blocks many data collection features by default and offers a privacy-focused stance on AI.
  • Vivaldi: Another Chromium fork that gives users granular control over telemetry and experimental features.

Switching browsers is a hassle, but if you’re particularly worried about data leaving your device, it’s worth testing one of these alternatives.

Summary

Google’s removal of its “no data sent to servers” promise for Chrome’s on-device AI is a small but significant change. It doesn’t necessarily mean your data is being sent right now, but it means the company has reserved the right to do so in the future. If you value privacy, take a few minutes to check whether the AI model has landed on your machine and disable the feature if you want to be safe. And keep an eye on Chrome’s changing settings—this area is evolving, and what’s true today may not be true next week.

Sources: Decrypt (May 6 & 7, 2026), GIGAZINE (May 9, 2026).