- From: James E. A. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Sep 2024 15:59:48 +0000
- To: public-device-apis-log@w3.org
If I start a location watch, then send the app to the background, I *expect* the app to keep watching my location until the `App Is Watching Your Location` notice disappears, at which point the consent is obviously revoked; this is the same model that *every* existing navigation app uses; it's an excellent model, and I've never seen any criticism against it. As long as the app isn't allowed to *start* collecting location data in the background — if the user has to affirmatively open the app for it to even have the opportunity to open a location-watch session — then what *exactly* is the supposed privacy risk? In particular, "geofencing" seems to be **infinitely** more risky, privacy-wise. If an app can get my consent *once* and then lurk in the background, unseen, with no notification, indefinitely waiting for Firefox/Google/Microsoft/systemd to notify it that I've left the city — which is a rather basic example of geofencing — that seems like \*way\* more of a concern than the natural use-case of "bike ride tracking app keeps running when I turn the screen off or check my texts". -- GitHub Notification of comment by James-E-A Please view or discuss this issue at https://github.com/w3c/geolocation-sensor/issues/22#issuecomment-2338501450 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 9 September 2024 15:59:49 UTC