Earlier quoted context omitted.
This is what I was just thinking. It asks for permission just like microphone or location. Both of which you could argue 'allow for surveillance'
Those permissions have pretty clear use-cases which benefits the user itself and enables things which otherwise wouldn’t be possible. What user-oriented use-cases does this enable which couldn’t have been done otherwise? I really thinks this is apples vs oranges.
In this case:
> Making these distinctions is important for applications which have the option of delivering notifications across multiple devices, such as a desktop and smartphone. Users may find it frustrating when notifications are delivered to the wrong device or are disruptive. For example, if they switch from a tab containing a messaging application to one for a document they are editing, the messaging application, not being able to observe that the user is still interacting with their device, may assume that they have left to grab a coffee and start delivering notifications to their phone, causing it to buzz distractingly, instead of displaying notifications on their desktop or incrementing a badge count.