Explainer
Geolocation API implementations provide position estimates that are typically very accurate, but in many cases a high level of accuracy is not required. For instance, a store locator app can use precise location to draw a map of nearby store locations, but also works with a postal code.
Sharing precise location data puts the user's privacy at risk. To mitigate this risk, Geolocation API implementations should provide user controls that enable the user to limit the accuracy of location data delivered to sites. Mobile operating systems (iOS, Android) already expose similar controls as app-level permissions.
Additionally, the API should make it possible for sites to request safer defaults when precise location is not needed.
Related: #49
Explainer
Geolocation API implementations provide position estimates that are typically very accurate, but in many cases a high level of accuracy is not required. For instance, a store locator app can use precise location to draw a map of nearby store locations, but also works with a postal code.
Sharing precise location data puts the user's privacy at risk. To mitigate this risk, Geolocation API implementations should provide user controls that enable the user to limit the accuracy of location data delivered to sites. Mobile operating systems (iOS, Android) already expose similar controls as app-level permissions.
Additionally, the API should make it possible for sites to request safer defaults when precise location is not needed.
Related: #49