Siri requires location for explicit queries

i’ll try this again and see if this fits what you would want everyone else to see.

I’m raising a concern about Siri and Apple’s continued requirement for location access—even when a user provides complete, explicit information.

For example, if I ask: “City Market in Delta, Colorado,” I’ve already supplied the business name, city, and state. That should be more than enough to return accurate results. Instead, Siri often insists on accessing my current location before proceeding. At that point, it’s no longer about improving results—it becomes a hard dependency that overrides user intent.

This creates a frustrating contradiction. Apple promotes privacy and gives users the option to limit or disable location access, yet in practice, core functionality is restricted unless that permission is granted. That doesn’t feel like a real choice—it feels like a requirement disguised as an option.

Decades ago, tools like the Yellow Pages worked with far less information and no tracking at all. Today, with vastly more advanced technology, it’s difficult to understand why a clearly defined query still cannot be processed independently of my physical location.

What makes this more frustrating is that this issue has been raised repeatedly, yet the typical response is a generic walkthrough on how to toggle location settings. That does not address the underlying problem. The issue is not how to enable or disable location services—it’s why they are required in situations where they add no value.

If Apple is serious about privacy, then users should be able to access basic search and assistant functionality without being forced to disclose their location. Otherwise, the privacy controls feel superficial rather than meaningful.

I would strongly encourage the development team to revisit how Siri handles explicit queries and reduce unnecessary reliance on location data. Simplicity should mean fewer requirements—not more.