The Market for Your Movements — The Location Data You Never See

You do not need a hidden GPS device for your movements to become data. Ordinary apps, account settings and advertising infrastructure can turn location into a commercial signal—sometimes with consequences that extend far beyond a map.

Consider a phone that has never triggered an unwanted-tracker alert. There is no mysterious object under the car, no battery-powered tag tucked into a bag, no obvious reason to use a handheld radio detector. Yet the phone may still reveal where its owner spends time through ordinary software permissions and commercial data flows. This is one of the more unsettling truths of location privacy: the most consequential tracking can be perfectly invisible to an RF sweep.

Location is unusually expressive information. It can be a direction to a restaurant, a route to a meeting, or a record of repeated visits to places that are deeply personal. The technical act of attaching latitude and longitude to an event looks neutral. The inference that can be drawn from many such events is anything but.

1. How a modern phone learns its position

A smartphone can estimate location through several inputs. GNSS signals provide a way to calculate position using satellites. Wi-Fi and cellular observations may help especially when satellite signals are weak. Motion sensors provide clues about recent movement. The operating system can combine these inputs into a location estimate for navigation and other apps, depending on device capabilities and settings.

Applications do not all receive location in the same way. Some ask for precise location; others function with approximate location. Permission choices may distinguish between access while an app is being used and persistent access in the background. A weather app, a photo app and a navigation service have different practical needs, even if all three can request the same broad category of data.

The first meaningful privacy step is therefore to review individual permissions and ask whether the data request makes sense for the service offered. A good app does not need every capability simply because a phone can provide it.

2. The hidden significance of repeated observations

A single location ping may have limited meaning. A sequence can reveal routines: departures, recurring stops, common travel corridors and differences between weekdays and weekends. Location histories can also be inaccurate. A poor fix may place a device across a street, a shared device may travel with someone else, and a delayed update may misrepresent when a person was present.

Still, the ability to infer routine from repeated observations is powerful. This is why removing a name from a dataset does not automatically make every record harmless. Location patterns can be distinctive, and combining them with other available facts can raise re-identification risks. Privacy is not only about hiding a label in a database; it is about controlling what can be inferred from a trail.

The same logic applies to advertising audiences built from location signals. If someone can define a virtual boundary around a place and identify devices seen within it, the resulting information may reveal more than a simple preference for nearby shops.

3. A data broker sits between apps and a buyer

The term data broker describes businesses that collect, aggregate, license or sell information gathered from many sources. Location information can enter commercial ecosystems through app integrations, advertising-related systems and other arrangements. The precise route depends on each company's practices; it would be wrong to assume every app sells exact coordinates or that every data broker uses the same model.

Regulatory enforcement illustrates why the distinction matters. In 2024 the US Federal Trade Commission finalized an order relating to X-Mode and Outlogic over sensitive location-data practices. In 2025 it finalized an order concerning Gravy Analytics and Venntel. These cases provide concrete examples of how regulators have examined the collection, sharing and sale of location-derived information.

The cases do not mean every location-data service is illegal. They show that permission, notice, the sensitivity of visited places and downstream use are substantive issues—not cosmetic paragraphs in a policy page.

4. Why geofencing is both useful and sensitive

Geofencing describes the creation of a virtual geographic boundary that can be used to trigger an action or classify a location event. In a harmless consumer setting, an app might remind someone about a grocery list near a supermarket. In fleet operations, it might indicate that a company vehicle arrived at an authorized site. But applied to sensitive places or without adequate permission, similar mechanisms can become intrusive.

A boundary on a map is not evidence of identity by itself. GPS positions have uncertainty, devices can be shared, and a person may have merely passed nearby. Responsible systems avoid turning imperfect location observations into categorical conclusions about an individual's actions or beliefs. The more sensitive the inference, the more important the standards for consent, minimization and accuracy become.

The FTC's orders highlight the potential consequences of deriving and distributing sensitive categories from movement data. They also provide a reminder that a location dataset can be sensitive even when the raw rows contain no names.

5. What a device scan will never tell you

An RF detector may help investigate certain physical transmitters. It does not reveal which third-party app has received your location through a legitimate operating-system API, which old account still has sharing access, or how historical observations have been stored by a service. Even a perfectly executed physical inspection is not a comprehensive audit of digital permissions.

Conversely, changing a phone's app permissions will not necessarily stop a standalone GPS tracker in a vehicle or a Bluetooth tag attached to belongings. These are separate technical pathways. Confusing them can produce a false sense of security: the phone is "locked down," but the vehicle account is still shared; the car was swept for RF emissions, but an app still has long-term background location permission.

Our RF sweep explainer examines the physical side. The Trackers We Carry explains the difference between tags, GNSS devices and connected cars.

6. A practical privacy review without technological theatre

Begin with the phone's privacy dashboard or location settings. Identify apps that have persistent location access, particularly those whose functions do not obviously require it. Consider whether approximate location would suffice. Review permissions when installing an app and revisit them after major changes in your habits or software use. Keep the operating system current so its permission and unwanted-tracking features can evolve.

Next, examine account-based location sharing. Navigation services, family-sharing features, fitness apps, car apps and cloud accounts may expose different histories or ongoing access. Review who is authorized to see this information, remove access that is no longer needed and protect important accounts with strong authentication.

Finally, distinguish today's settings from yesterday's data. Revoking a permission can limit future access, but it does not necessarily erase information already collected by third parties. Where services provide history controls, retention settings or deletion requests, review those options. The available rights and mechanisms depend on the service and jurisdiction.

7. The future of location privacy depends on context

Navigation is useful partly because it knows where a person wants to go. Emergency response, accessibility tools and lost-item recovery demonstrate the value of location-aware systems. The aim should not be to portray every location technology as suspicious; it should be to make collection proportionate, transparent and genuinely under user control.

The deeper scientific lesson is that location has multiple layers: an estimate produced by sensors, an observation stored by software, an inference drawn from repeated observations, and a decision made about what to do with it. A device may protect its radio signals and still participate in an opaque data economy. A map may hide a person's name and still reveal their routines.

The most effective privacy strategy is therefore plural. Understand the hardware, audit the software, review the accounts and ask who retains the data after a journey ends. In a world saturated with coordinates, protecting privacy means protecting the stories those coordinates can tell.