Chrome Android Adds Approximate Location Sharing

Google this week announced that Chrome for Android now supports sharing only an 'approximate location' with websites, replacing the previous all-or-nothing approach to location permissions. The update gives users a meaningful new privacy control that limits how precisely websites can pinpoint their real-world position.

The feature mirrors a similar capability already built into Android's native app permission system, but now extends it directly into the browser — where millions of users interact with location-hungry websites every day.

Key Takeaways

• Chrome for Android now offers an 'approximate location' option when websites request geolocation access
• Users no longer have to choose between sharing their exact GPS coordinates or blocking location access entirely
• Google says approximate location is sufficient for services like weather forecasts and local news
• Precise location remains available for use cases like food delivery, ride-hailing, and ATM searches
• The update aligns Chrome with Android's existing app-level location permission model
• This represents a broader industry trend toward granular privacy controls in browsers

Google Bridges the App-Browser Privacy Gap

Since Android 12 launched in 2021, the operating system has offered users the ability to grant apps either 'precise' or 'approximate' location access. This was widely praised as a privacy-forward design choice. However, that same level of control was notably absent from Chrome's web-based location permissions — until now.

When a website requests location data through Chrome, users previously faced a binary choice: share your exact coordinates or deny the request entirely. The new approximate location option introduces a middle ground that balances usability with privacy.

Google explained the rationale in straightforward terms. Ordering takeout, scheduling a delivery, or finding the nearest ATM genuinely requires precise location data. But checking the local weather forecast or reading neighborhood news? An approximate location — accurate to roughly a 1-to-2 mile radius — works perfectly fine.

How the New Permission System Works

The updated permission flow appears when any website invokes the browser's Geolocation API. Instead of a simple 'Allow' or 'Block' prompt, Chrome now presents users with a more nuanced set of options.

When a site requests location access, users can choose from the following:

• Precise location: Shares exact GPS coordinates, suitable for navigation and delivery apps
• Approximate location: Shares a generalized area, typically within a few kilometers of the user's actual position
• Block: Denies the location request entirely
• One-time access: Grants location permission for the current session only

This granular control means users can, for example, share approximate location with a news website while reserving precise location for a food delivery platform — all within the same browser. The setting is stored per-site, so users do not need to re-configure their preferences on every visit.

Why This Matters for User Privacy

Location data is among the most sensitive categories of personal information. A user's precise GPS coordinates can reveal where they live, where they work, which doctors they visit, and what places of worship they attend. Data brokers and advertisers have long exploited precise location data harvested from both apps and websites.

By offering approximate location sharing, Google effectively limits the granularity of data that websites can collect. Instead of knowing that a user is standing at a specific street corner, a website would only know they are somewhere within a broader neighborhood or district.

This is a significant improvement for several reasons. First, approximate location data is far less useful for building detailed behavioral profiles. Second, even if a data breach occurs, the leaked location information poses less risk to individual users. Third, it aligns with growing regulatory expectations — including GDPR in Europe and various state-level privacy laws in the U.S. — that call for data minimization principles.

Privacy researchers have long argued that the web platform lagged behind native mobile operating systems in offering meaningful location controls. Chrome's update directly addresses that criticism.

The Broader Industry Context

Google's move fits into a wider trend across the tech industry toward more privacy-centric browser features. Apple's Safari has implemented aggressive anti-tracking measures for years, including Intelligent Tracking Prevention (ITP). Mozilla's Firefox offers Enhanced Tracking Protection by default. And even Microsoft's Edge has introduced various privacy dashboards and tracking prevention tiers.

However, location permission granularity has been an area where browsers have been slower to evolve compared to mobile operating systems. Apple introduced approximate location controls in iOS 14 back in 2020, and Android followed with Android 12 in 2021. Bringing this same level of control to the browser is a logical — if somewhat overdue — step.

The update also arrives at a time when regulators worldwide are scrutinizing how tech companies handle location data:

• The FTC in the United States has taken enforcement actions against data brokers selling precise location information
• The EU's Digital Markets Act imposes stricter data-sharing requirements on designated gatekeepers, including Google
• Several U.S. states, including California, Virginia, and Colorado, have enacted comprehensive privacy laws that address location tracking
• India's Digital Personal Data Protection Act of 2023 also includes provisions related to sensitive personal data, including location

Google, as both the maker of Chrome and the operator of the world's largest advertising network, faces unique scrutiny on these issues. Offering users more control over location sharing helps the company demonstrate good faith on privacy — even as its core business model depends heavily on targeted advertising.

What This Means for Web Developers

For developers and businesses that rely on the Geolocation API, this change has practical implications. Websites that request location data may now receive approximate coordinates rather than precise ones, depending on user preferences.

Developers should audit their location-dependent features and determine which ones truly require precise positioning. A restaurant locator, for instance, may need to adjust its radius search when receiving approximate data. A weather widget, on the other hand, will function perfectly with neighborhood-level accuracy.

Best practices going forward include:

• Explaining clearly why your site needs location data before triggering the permission prompt
• Designing graceful fallbacks for when users choose approximate location over precise
• Avoiding unnecessary location requests — only ask when the feature genuinely requires it
• Testing with approximate coordinates to ensure the user experience remains smooth
• Updating privacy policies to reflect how different levels of location data are handled

Google has historically encouraged developers to follow the principle of least privilege — requesting only the minimum permissions necessary. This update reinforces that philosophy at the browser level.

Looking Ahead: Privacy Controls Will Only Get More Granular

Chrome's approximate location feature is unlikely to be the last privacy enhancement Google rolls out for its browser. The company has been gradually introducing more user-facing controls as part of its broader Privacy Sandbox initiative, which aims to phase out third-party cookies while still enabling some form of interest-based advertising.

We can expect future updates to potentially include more contextual permission prompts — where Chrome might intelligently suggest approximate versus precise location based on the type of website making the request. Machine learning models could, in theory, determine that a weather site does not need exact coordinates and default to approximate sharing.

The update also raises questions about whether desktop Chrome will receive similar treatment. Currently, the approximate location feature appears to be limited to Android. Given that desktop browsers also handle location requests via the Geolocation API, extending this control to Chrome on Windows, macOS, and Linux would be a natural next step.

For now, Android users should ensure they are running the latest version of Chrome to access the new location controls. The feature is rolling out gradually, so it may take a few days to appear for all users worldwide.

In a digital landscape where every data point matters, giving users the ability to share 'close enough' instead of 'exactly here' is a meaningful step toward better privacy — and one that the rest of the browser ecosystem will likely follow.