Chrome’s extension purge: a security upgrade with real costs
Chrome’s extension purge is Google’s multi‑step effort to remove outdated Manifest V2 add‑ons, ban risky products like prediction markets, and strictly limit extension data collection, forcing both users and developers to clean up how browser add‑ons access and use personal information. This is not a minor policy tweak; it is a structural reset of what extensions can be, what data they can touch, and how accountable they must be for that access. Google has now pinned the final Web Store removal date for remaining Manifest V2 extensions to August 31, 2026, marking the last visible stage of a phase‑out that has been unfolding for years. At the same time, enforcement of new Chrome Web Store policy on extension data collection and prohibited products starts August 1, 2026, giving developers a narrow window to adapt or disappear.
Manifest V2 removal: the end of a long grace period
The Manifest V2 removal is the clearest sign that the grace period for legacy extensions is ending. Google will strip all remaining Manifest V2 extensions from the Chrome Web Store on August 31, 2026, a date recently added to its public timeline. Extensions already installed on Chrome 138 or earlier can stay, but they will be frozen: no new versions, no store listing, and no way to reinstall them once removed. Google’s timeline makes it clear that Manifest V2 support has already been disabled in Chrome and that Chrome 139 is the forward‑looking cut‑off for users. This is not about nostalgia; it is about risk. Old extensions often rely on broader, more powerful APIs, and they were built under looser privacy expectations. By shutting them out of the store, Google is trying to cap that risk, even if it strands users who depend on advanced ad blockers or niche tools that never made the jump to Manifest V3.
Chrome Web Store policy: data collection clamps down
The most consequential change for ordinary users is the clampdown on extension data collection. Google updated Chrome Web Store developer policies on July 1, with enforcement starting August 1. Under the new Limited Use Policy, extensions can only collect data strictly necessary for their disclosed single purpose—extra collection for analytics, advertising, or future features is off‑limits. The Disclosure Requirements Policy now demands that every instance of data collection be clearly explained, even when it is central to the extension’s function, and developers must inform users if those practices change after installation. To quote the update, “Extensions still collecting data outside their disclosed purpose after the deadline risk removal from the Chrome Web Store.” This explicitly targets the long‑standing gap between permissions requested and data actually used, where coupon finders and screenshot tools quietly behaved like data brokers while pretending to be simple utilities.
Prediction market ban and new prohibited products
Alongside privacy rules, Chrome Web Store policy now draws harder lines around what extensions can do with money and AI. Google has updated its Store policies to include an explicit prediction market ban: “Extensions that facilitate or enable real money transactions on predictive outcomes are not allowed.” Enforcement for this and related changes begins August 1, 2026. Predictive markets get their own category under regulated goods and services, meaning any extension that enables real‑money bets on outcomes directly in the browser will be barred. The same policy update also bans extensions built to bypass safety guardrails in AI‑powered services. These moves follow increased scrutiny of platforms like Polymarket and Kalshi, which regulators accuse of operating as illegal sports betting platforms. Together with Chrome 151’s patching of 382 vulnerabilities, the message is clear: Google wants fewer high‑risk behaviors embedded at the browser level, whether they involve speculative markets, unsafe AI, or quietly siphoned user data.
How users and developers should respond before extensions vanish
Ordinary users cannot afford to treat this as background noise. Manifest V2 removal means older extensions will disappear from the Chrome Web Store with no easy recovery option; once you uninstall a legacy add‑on after August 31, you will not be able to reinstall it from the store. New data rules mean extensions that over‑collect information or hide their practices face enforcement and potential removal after August 1. Nobody gets a personalized warning before either category disappears, which is why a local audit matters. The most useful step is to open chrome://extensions, check what each installed extension can access, and ask whether that access matches what the extension claims to do. Remove anything suspicious, replace unmaintained Manifest V2 tools with Manifest V3 alternatives where possible, and pay attention to updated privacy notices from extensions you rely on. Developers, meanwhile, need to narrow each extension to a single clear purpose, trim data collection to match, and publish transparent disclosures—or accept that their work may vanish from the Web Store entirely.
