Google says it will begin automatically disabling browser notifications from websites a user hasn’t interacted with in some time, extending the logic of its Safety Check tool (which already revokes unused camera or location permissions) to cut back on unwanted alerts. The change will roll out to Chrome on both Android and desktop, though it will not affect installed web apps. Google’s internal testing suggests this move leads to a large drop in notification “noise” without significantly reducing total click engagement, and in some cases low-volume sites even saw better interaction metrics. Users will be notified when a site’s notification access is removed, and they’ll retain control to re-enable permissions or disable the auto-revocation feature entirely.
Key Takeaways
– Chrome will now auto-revoke notification permissions for websites that send many alerts but see very low user engagement.
– Users receive alerts when permissions are removed and can re-enable them via Safety Check or by revisiting the site.
– The feature is optional: users may turn off the auto-revocation behavior entirely if they prefer full manual control.
In-Depth
In an effort to reduce the barrage of unwanted browser notifications, Google is expanding Chrome’s Safety Check tools to include automatic revocation of notification permissions for sites that users rarely engage with. The reasoning is straightforward: although users may receive dozens of alerts from sites, fewer than 1 percent of those notifications actually prompt any interaction. The new logic combines notification volume and user response metrics to decide which sites get stripped of permission. Importantly, Chrome won’t revoke alerts for web apps you’ve deliberately installed, so you won’t lose essential notifications you’ve opted into.
Under the hood, this approach aims to curtail “notification overload” — a common gripe among users — while preserving the core utility of alerts. According to Google’s internal tests, applying this filter significantly reduced noise without negatively affecting total notification click counts; in fact, some smaller sites sending fewer alerts saw relative gains in engagement. When the browser revokes permission for a site, it sends the user a message like “Chrome unsubscribed you from notifications,” letting people review which sites were affected. From there, they can restore permissions through Safety Check or by visiting the site itself and re-opting in.
That said, the feature isn’t imposed unilaterally: Chrome gives users the option to disable auto-revocation entirely if they prefer to handle all notification permissions manually. Early adopters will likely appreciate being freed from constant unsolicited pop-ups, while more hands-on users retain control over their notification landscape. By expanding Safety Check beyond cameras, location, and permissions for access, Google is signaling a shift toward more dynamic, engagement-based permission management — one where the browser takes more responsibility for trimming distractions, without fully dictating the user’s choices.