Yes, Chrome can now take away the notification permission a shopper once gave your store, without the shopper doing anything. It happens only when engagement is very low, for a site the person has not interacted with recently, and the site also sends a high volume of notifications, so stores that send fewer, more useful messages to engaged shoppers are in the best position to keep their subscribers.

This post explains what Google announced, which sites are affected, what is not affected, and the practical steps a Shopify store can take so its web push list keeps working.

Bring shoppers back with web push notifications from Firepush

Try Firepush for free

What Chrome Changed

On 10 October 2025, Google announced that Chrome will automatically remove notification permission from sites you have not interacted with recently. The feature is part of Chrome on Android and on desktop.

It is built into Safety Check, the part of Chrome that already looks after other permissions. In the same announcement, Google points out that Safety Check already does this for permissions such as camera and location. Notifications are now handled the same way.

Safety Check is not something a shopper has to open and run by hand. Since its revamp in September 2024, Safety Check runs automatically in the background on Chrome and tells the person when it has acted, for example when it revokes permissions from sites they no longer visit.

For a store owner, the important part is simple: a subscriber who once clicked "Allow" can lose that permission later, quietly, if they stop engaging with your store while your notifications keep arriving.

Safety Check
Notification permission was removed from a site you have not visited recently.
Allow againGot it
Illustration: roughly what a Chrome notice can look like when Safety Check removes a notification permission. The wording is ours, not Chrome's exact text. Google says Chrome informs the person when it happens.

Which Sites Lose Permission

Chrome does not remove permission from every site that sends notifications. Google is clear that the feature only revokes permission when there is very low user engagement and a high volume of notifications being sent. Both conditions matter together:

  • Low engagement. The person has not interacted with the site recently. Google speaks of engagement in general and does not say that notification clicks alone count.
  • High volume. The site sends a lot of notifications.

Both conditions together

Low engagement
High volume
Permission can be removed
High engagement
High volume
Not what this feature targets
Low engagement
Low volume
Not what this feature targets
High engagement
Low volume
Not what this feature targets
Based on Google's announcement. Google does not publish an exact number for either condition.

Google's announcement does not publish an exact number for either condition, so there is no official count of messages or level of engagement to aim for. What it does make clear is the direction: many notifications sent to people who no longer interact with the site is the pattern Chrome is looking for.

This is separate from an older rule. Since 2024, Safety Check has also been revoking notification permission from sites that Google Safe Browsing finds to be deceiving users into granting the permission. An honest Shopify store asking for permission in a normal way is not the target of that rule, but it is a good reminder that how you ask matters as much as what you send. In August 2026 Google added that Chrome also removes notification permission from sites that have repeatedly received suspicious notification warnings, and that people can review and grant removed permissions again in Safety Hub.

What Stays the Same

A few things do not change, and they are worth knowing before you worry about your list:

So a removed permission is not always gone for good. A shopper who comes back to your store and still wants to hear from you can subscribe again. That gives you a second chance, but only if your store gives them a reason to come back and a clear, friendly way to opt in again.

A removed permission can come back

1
Chrome removes the permission and tells the shopper
2
The shopper comes back to your store
3
They turn notifications back on through your clear, friendly opt in
Source: Google says a person can grant the permission again through Safety Check, or by visiting the site and turning notifications back on.

New to web push? Start with our complete guide to web push notification marketing, which covers how web push works and how to add it to a Shopify store.

Why Google Made This Change

Google's reason is notification overload. According to the announcement, less than 1% of all notifications receive any interaction from users. In other words, most notifications sent through Chrome are ignored.

The more useful finding for marketers is what happened in Google's tests. Google reports that the feature brought a significant reduction in notification overload with only a minimal change in total notification clicks. Its experiments also showed that websites that send a lower volume of notifications are actually seeing an increase in clicks.

That is the heart of the change. Sending more messages does not mean getting more clicks. The clicks were coming from a small share of notifications all along, and the sites that send less are being rewarded with more attention.

This is part of a wider move by Chrome to give people more control. In 2024 Google also added a one tap "Unsubscribe" button in the Android notification drawer, first on Pixel phones, and reported that this led to a 30 percent reduction in notification volume on supported Pixel devices. Shoppers now have more ways than ever to stop hearing from a store that annoys them.

Two numbers from Google

Less than 1%
of all notifications receive any interaction
30%
less notification volume on supported Pixel devices after the one tap Unsubscribe button
Sources: Google, October 2025 and Google, September 2024.

What This Means for a Shopify Store

For most stores, this is good news dressed up as a threat. If you send a modest number of relevant notifications to shoppers who still come back to your store, you are far from the pattern Google describes. The stores at risk are the ones that send frequent broadcasts to everyone, whether or not the message fits the person.

Think about it from the shopper's side. Someone allowed notifications because they liked your products. If they then get a general sale message every day, they stop reading them. Chrome sees many messages and a person who no longer interacts with the site, and that subscriber may be removed from your list without ever pressing a button.

The fix is not a trick. It is sending messages that people actually want to open. A few kinds of web push messages are naturally more relevant than a general broadcast:

  • Cart reminders, sent to a shopper who left items in their cart. The message is about something they chose themselves.
  • Welcome messages, sent right after someone subscribes, when their interest in your store is highest.
  • Messages to a segment, such as shoppers who viewed a certain collection, instead of the whole list.

Firepush supports all three: cart reminders, welcome messages and segments, so you can send to the shoppers a message is meant for rather than to everyone at once.

What to Do in Your Store

Here are practical steps you can take this week to keep your web push subscribers:

  1. Send fewer broadcasts. Look at how many campaigns your whole list received last month. If it is several a week, cut back and keep only the ones with a real reason, such as a genuine sale or a new product launch.
  2. Lead with automated, personal messages. Let cart reminders and welcome messages do most of the work. They go to one shopper at a time, at a moment that makes sense for that shopper.
  3. Use segments for campaigns. Before you send a campaign, ask who it is really for. Send a new arrivals message to people who browsed that category, not to every subscriber.
  4. Watch how shoppers respond, not just your sends. Google does not say that notification clicks alone keep the permission; it looks at engagement together with how many notifications a site sends. A falling click rate is still an early sign that shoppers are losing interest, so treat it as a warning and change what you send.
  5. Write messages worth clicking. Keep the title clear and the text short, and say exactly what the shopper gets. Our guide to push notification character limits shows how much text fits on each platform.
  6. Ask for permission at the right moment. A shopper who opts in because they want your updates is more likely to engage later. Since Chrome 155, Chrome on Android uses a lighter prompt that closes by itself if the shopper does not answer, and adds a way to subscribe later from the site controls, so asking at a relevant moment matters even more. Our post on quieter web push opt-ins explains how browsers treat permission requests and how to ask well.
  7. Give returning shoppers a way back. Because a person can turn notifications on again when they visit your site, keep a clear and polite opt in on your store for shoppers who lost permission and come back.

The Short Version

Chrome on Android and desktop now removes notification permission from sites that send a high volume of notifications to people who have not interacted with them recently. Installed web apps are not affected, shoppers are told when it happens, and they can turn notifications back on.

Google's own tests point to the same lesson every store owner can use: sites that send fewer notifications get more clicks. Send fewer, more relevant messages, lean on cart reminders and welcome messages, use segments for campaigns, and your subscribers have every reason to stay.