{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreideg3uycnq24jxkgx2hggru23ltdv3k4xwiuele74pqq46omxu4li",
    "uri": "at://did:plc:awj2q63kg2v3k5xwsjh2uoe3/app.bsky.feed.post/3mlcczwvviqa2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiesdwwels4tg5zjrbbpyc3at4dndu53bm27n7czuvbrzwqvnzhlgi"
    },
    "mimeType": "image/jpeg",
    "size": 238740
  },
  "description": "Google announced that “you can now choose to share your approximate location with websites, instead of sharing precise location” on Chrome for Android.",
  "path": "/news/2026/05/07/chrome-for-android-now-supports-approximate-location/",
  "publishedAt": "2026-05-07T23:00:15.000Z",
  "site": "https://www.privacyguides.org",
  "tags": [
    "announced",
    "iOS",
    "Android",
    "Approximate Geolocation API",
    "Battery Status API",
    "Device Memory API",
    "undecided",
    "supporting",
    "found"
  ],
  "textContent": "Google announced that “you can now choose to share your approximate location with websites, instead of sharing precise location” on Chrome for Android.\n\nWebsites can ask for your location for a variety of purposes whether it‘s to make a delivery or to give you real-time directions.\n\nSome uses don’t require your exact location though, like checking your local weather. For those times, you can now provide a general location instead.\n\nBoth iOS and Android have supported approximate location at the OS level for a while. However, browsers strangely lack this feature.\n\nGoogle says the feature will come to desktop “in the coming months.”\n\n> We’re also planning to release new APIs for web developers that will let them request approximate location or specify if they need precise location. We encourage developers to review their location needs and only ask for precise location when it’s required for the site functionality.\n\nGoogle had a proposal for an Approximate Geolocation API as a standard browser feature for a while.\n\nGoogle has several APIs that only work in Chromium-based browsers for now, such as the Battery Status API that let websites see how much battery you have and the Device Memory API that lets sites see approximately how much memory you have.\n\nAs you can imagine, these can be privacy concerns, especially in regards to fingerprinting. It’s no surprise that other browser vendors haven’t adopted them.\n\nIt seems that Mozilla is undecided on whether they support the standard or now, but WebKit has now come out as publicly supporting it. This is good news for support for this feature in more browsers in the future.\n\nIt only makes sense to support approximate location in browsers given it already exists for apps on iOS and Android. Websites are much less trusted than installed apps and as such they should have the least possible data on you in order to function.\n\nApps have been found, even unintentionally, to leak your location data to analytics companies and allow cross-app location tracking. For websites, there are even more untrusted parties involved.\n\nThink of every site you visit, and how many of them randomly ask for your location. It can be very easy to unintentionally reveal your precise movements to a lot of parties.\n\nThis permission is a huge privacy win and I hope we can see widespread adoption soon. I’m not sure what Mozilla’s holdout is, but they should take another look and make a decision.\n\n\n",
  "title": "Chrome for Android Now Supports Approximate Location",
  "updatedAt": "2026-05-07T23:00:15.136Z"
}