Google this month added a new approximate location sharing option to Chrome on Android, allowing users to grant websites a neighborhood-level position instead of their precise coordinates. The announcement, published on May 5, 2026, by Archit Agarwal, product manager at Chrome, marks a structural change to how the browser mediates between user privacy and the location-based functionality that websites commonly request.

Until now, Chrome users faced a binary when a website asked for location data: grant precise access or refuse entirely. The new option introduces a third path. A user visiting a weather site, for example, can share a general area without disclosing a street-level position. The distinction matters because the two data categories carry very different privacy implications, and the change acknowledges that most location use cases do not actually require pinpoint accuracy.

How the new permission dialog works

According to Google's announcement, the Chrome permission prompt on Android now presents two explicit choices when a website requests location: "Precise" - labeled as exact location - and "Approximate" - labeled as neighborhood. The user selects one before also deciding whether to allow access while visiting the site, allow it just once, or never allow it. This layered structure mirrors patterns already familiar from Android's native app permission system, where the operating system itself has supported approximate location grants since Android 12, released in October 2021.

The dialog operates at the browser level, meaning the choice applies to the specific website in question rather than to Chrome as a whole. A user could therefore share precise location with a navigation site while granting only approximate access to a news portal - managing different sites differently based on what seems proportionate.

What approximate location actually means technically

Approximate location is not a vague concept. On Android, the platform-level approximate location permission - ACCESS_COARSE_LOCATION - delivers coordinates accurate to roughly three city blocks, or approximately 1.5 kilometers in radius under typical conditions. This contrasts with precise location, which on a device with GPS enabled can resolve positions to within a few meters.

That gap is large enough to matter enormously for different types of services. Navigation, ride-hailing, and delivery address lookup require precision. Local weather forecasts, nearby restaurant listings, and regional news aggregation typically do not. The practical consequence is that a significant portion of everyday web location requests could be satisfied by approximate data alone - a point Agarwal's announcement makes directly, noting that "some use cases require precise location" while "other use cases may only need your approximate location - like getting access to local weather and news."

The W3C Geolocation API, which browsers use as the standard mechanism for web-based location access, does not currently define a native approximate mode. The API returns coordinates with whatever precision the underlying device and permission allow. Chrome's new implementation effectively inserts a layer between the device hardware and the API response, capping the precision of what the browser passes through. The W3C published an updated Geolocation API Recommendation on March 24, 2026, formalizing consent rules and privacy controls for browser-based location access - a document directly relevant to how features like Chrome's approximate sharing will interact with the broader web standards ecosystem.

New APIs for developers are coming

The user-facing feature is only part of what Google announced. According to the blog post, Google is also planning to release new APIs for web developers that will allow sites to explicitly request approximate location or declare that they need precise location. This is a significant addition to the existing developer toolset.

Currently, the standard Geolocation API does not give websites a built-in mechanism to signal their precision requirements. A developer who only needs a rough area must still trigger the same permission prompt as one building a turn-by-turn navigation product - which may lead users to grant more access than the feature requires, or to refuse entirely when they would have accepted a limited grant. The new APIs would allow sites to match their requests to their actual needs, potentially increasing the rate at which users approve location access for lower-stakes applications.

Google's announcement does not provide a specific release date for these developer APIs, describing them as planned rather than imminent. Agarwal's post states that Google "encourages developers to review their location needs and only ask for precise location when it's required for the site functionality." That framing positions the API work as part of a broader effort to align the technical capability of location requests with the actual data requirements of individual features.

Desktop is next

Chrome on Android is the initial deployment target, but the feature is not staying mobile-only. According to the announcement, Google will be expanding approximate location sharing to desktop in the coming months. No specific timeline is given. Chrome's desktop user base is substantial - Chrome held approximately 64.7% of the global browser market as of Q4 2024, making any change to its location permission model consequential at scale.

The desktop expansion will require a somewhat different implementation. Desktop machines lack the GPS hardware common to smartphones and instead rely primarily on Wi-Fi network positioning and IP address-based geolocation, both of which are inherently less precise than satellite positioning. That may make the approximate versus precise distinction less sharply defined on desktop, though it will still carry meaning for the subset of desktop users whose machines have sufficiently accurate positioning available.

Why location data accuracy matters for advertising

The marketing industry has a direct stake in how browsers handle location signals. Location-based targeting is a significant component of programmatic advertising, and the precision of available signals determines which targeting strategies are technically possible.

Research published in November 2025 found that IP-to-postal-address linkages achieve just 13% accuracy on average across nearly one billion IP address records from six major data providers. That figure illustrates a core problem: IP-derived location, the fallback when device-native signals are unavailable or denied, is unreliable beyond city level. Device-native location via the Geolocation API, when permission is granted, is measured against a 95% confidence accuracy radius and represents fundamentally better data quality - as covered by PPC Land in its analysis of the W3C Geolocation API update.

Chrome's new approximate option introduces a middle tier into this picture. A user who previously refused all location access to avoid disclosing a precise address might now accept an approximate grant. That shift, if it occurs at scale, could increase the pool of consented location signals available to publishers and advertising systems - but at a reduced precision level. Approximate coordinates are accurate to neighborhood level, not street level. As PPC Land's guide to location marketing has documented, targeting granularity decreases meaningfully as geographic precision declines, with city-level targeting being substantially less effective for hyperlocal campaigns than GPS-level data.

The practical advertising consequence depends heavily on what the developer APIs ultimately look like. If publishers can signal to the browser that they only need approximate location, and users prove more willing to grant that lesser permission, the net result could be higher consent rates with lower data quality per signal. For campaigns where neighborhood-level targeting is sufficient - local retail, regional news, weather-dependent creative - that trade-off may be acceptable. For precision-dependent applications like foot-traffic attribution or proximity-based push notifications, it would not substitute for precise data.

Context: Chrome's broader privacy trajectory

This feature does not arrive in isolation. Chrome has been adjusting its privacy architecture on multiple dimensions. The browser added enhanced permissions controls in September 2024, including a Safety Check that automatically revokes permissions from infrequently visited sites and one-time permission grants for sensitive capabilities like camera and microphone. The approximate location feature extends that general direction - more granular user control over what specific data a site can access.

On the advertising infrastructure side, Google in October 2025 retired most of its Privacy Sandbox technologies after they failed to gain industry adoption, shutting down the Attribution Reporting API, Topics, Protected Audience, and IP Protection among others. That retreat left a gap in the privacy-preserving advertising toolkit that Chrome had spent years developing. The approximate location feature is not a direct replacement for any of those technologies, but it sits within the same broader challenge: how to preserve user data control while keeping web functionality - including advertising-dependent functionality - working at reasonable quality.

Google's decision in December 2024 to permit device fingerprinting for advertising purposes drew criticism from the UK's Information Commissioner's Office, which described the move as irresponsible. The approximate location feature points in a different direction, adding a user-controlled restriction rather than expanding what advertisers can collect without user awareness. These two moves coexist within the same company and the same browser, reflecting genuinely competing pressures in Google's position as both a browser vendor with privacy obligations and an advertising business dependent on data signals.

Location data also intersects with regulatory exposure. Spain's data protection authority fined Yoti 950,000 euros in March 2026 partly on the basis of excessive retention of IP-derived geolocation data - a case that illustrates the legal risk attached to aggressive location data practices under GDPR. Chrome's approximate sharing feature gives websites - and by extension publishers and advertisers - a legitimate mechanism to document that their location data collection was user-initiated and limited to neighborhood precision, which is potentially useful in a regulatory context.

What developers should note now

While the new developer APIs are not yet released, the user-facing change is live on Chrome for Android. Developers whose sites request location today should be aware that some users will begin granting approximate access where they previously either granted precise access or denied entirely. Existing Geolocation API implementations will receive the approximate coordinates transparently - the API call succeeds, but the returned coordinates are less precise than they would be under a precise permission grant. Code that assumes a certain level of precision without validating accuracy could behave unexpectedly.

According to Google's announcement, developers are encouraged to review their location needs now, before the new request-type APIs arrive. That review process - auditing which features genuinely require precise coordinates versus which could function with neighborhood-level data - is likely to become more consequential once the APIs allow sites to actively signal their requirements to the browser.

Timeline

Summary

Who: Google Chrome, announced by Archit Agarwal, product manager at Chrome. The change affects users of Chrome on Android globally, and will later affect desktop users. Web developers are also directly affected by the forthcoming developer APIs.

What: Chrome on Android now allows users to share an approximate, neighborhood-level position with websites instead of their precise GPS coordinates. A new permission dialog presents the two options explicitly. Google has also announced plans to release new web APIs enabling developers to specify whether their features require precise or approximate location.

When: The feature was announced on May 5, 2026. The desktop expansion and developer APIs do not have specific release dates and are described as coming in the following months.

Where: The feature is currently live in Chrome on Android. Desktop expansion is planned. The developer APIs, once released, will apply to web applications accessed through Chrome across platforms.

Why: The change addresses a long-standing gap in browser location permission design, where users had no option between full precise access and complete denial. By adding an intermediate tier, Google aims to give users more proportionate control over location data while preserving functionality for use cases that only need general area information. The move also anticipates forthcoming developer tooling that would allow sites to match their location requests to their actual precision requirements, rather than defaulting to the highest level of access for all use cases.

Share this article
The link has been copied!