A great example was given at the Chrome dev summit, which I think highlights the utility.<p>First, remember that you only need to click &#x27;Yes&#x27; when your browser asks you for Push permission. You have revealed nothing new to the website, but provided it a way to contact you later. Think of it as a frictionless temporary e-mail.<p>So you go to a ticket website, or maybe its even a restaurant website, and there&#x27;s some event coming up. Huh, yea, you want to know when tickets go on sale or whatever, but no way you want to give out your e-mail address <i>again</i> and get all that spam.<p>You instead opt for a push notification from the site when the tickets go on sale. Now you will be notified via your browser, and maybe once you see that notification, you&#x27;re happy, you&#x27;re done, so you unsubscribe (an option you can click on the notification itself to stop further push messages from that website).<p>If this privilege is abused, just as easy to cut-off that sole way to communicate that it has with you, right there on the notification. Unlike e-mail, when you kill the Push permission for a site, it has truly lost the ability to bug you ever again.<p>I&#x27;m sure there&#x27;s plenty of other cases where it might be useful to one-off contact a user when they want to know about something your website provides, and people are (properly) wary about giving out e-mail addresses.