<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Browser on The Coders Blog</title><link>https://thecodersblog.com/tag/browser/</link><description>Recent content in Browser on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 16:55:48 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/browser/index.xml" rel="self" type="application/rss+xml"/><item><title>Chrome's On-Device AI: Data Privacy Under Scrutiny</title><link>https://thecodersblog.com/chrome-s-on-device-ai-data-handling-2026/</link><pubDate>Thu, 07 May 2026 16:55:48 +0000</pubDate><guid>https://thecodersblog.com/chrome-s-on-device-ai-data-handling-2026/</guid><description>&lt;p&gt;The silent, four-gigabyte download of a large language model into your user profile isn&amp;rsquo;t exactly a quiet whisper; it&amp;rsquo;s a digital bullhorn that many Chrome users are only now noticing. Google&amp;rsquo;s push for on-device AI, primarily through its Gemini Nano model, has landed squarely in the crosshairs of privacy advocates and tech-savvy users, not for what it &lt;em&gt;does&lt;/em&gt;, but for how it &lt;em&gt;arrives&lt;/em&gt;. The fundamental issue isn&amp;rsquo;t the AI itself, but the insidious lack of consent and transparency surrounding its deployment.&lt;/p&gt;</description></item></channel></rss>