What a Shared Location Contains
One shared point, with its accuracy range
When the person accepts, their location comes back with its accuracy range. It is one point at the moment of the tap, not an ongoing trail. PingLocate shows no map or status screen: the answer belongs to the request you sent.
- One shared point, with its accuracy range
- The range with each result
- One point per accepted request, not a trail
- Nothing shared until the person accepts
The shared location is the easiest part of the flow to misread. It is one point, at the moment the person accepted, with a range that says how much that point is worth.
What the result is made of
Two things come back from the phone: a position and an accuracy range. The position is the best estimate the device could produce at that moment. The range tells you how much to trust the position, since it is the distance between the true position and the point shown.
A tight range means the phone had a good reading. A wide range means it was working from something coarser, so the honest reading is an area rather than a place. The range comes with every result, because a confident-looking dot that is kilometers off would tell you less than the range does.
Where the accuracy comes from
A phone works out where it is in three ways.
- Satellites. The phone listens to positioning satellites, which is the most precise method and the slowest to start. It needs a view of the sky, so it works far better outdoors than in a basement.
- Wi-Fi networks. The device matches the networks around it against a database of known network locations. This works indoors, where satellite signals struggle, and it is less precise.
- Cell towers. The phone knows which towers it can reach, and a tower can be several kilometers away. This is the coarsest method, and it is why a device with location services off usually produces a city-level estimate measured in kilometers, and sometimes nothing at all.
The device reports the best it can get, with the range that goes with it.
A worked example: reading two results
A point arrives with a range in tens of meters, near a specific junction. That is a satellite fix, and you can use it the way you would use a street address.
A second request, sent an hour later, comes back with a range wide enough to cover most of a town. That is the network fallback, and it means the phone could not get a better reading. Treat it as an area rather than an address.
If you need a tighter point, send a second request when the person is outdoors, with location services on and a moment to wait for the reading.
What the result never shows
The result is a snapshot. It does not move when the person moves, it does not keep a history, and it does not tell you when they arrive anywhere. Nothing is installed on the phone, so nothing can keep reporting after the page closes.
A request also returns nothing at all until the person accepts. If you need a continuous view of a device, that is an app with ongoing permission, and a different product.
The result compared with the alternatives
A device finder, such as Find My on iOS or Find Hub (formerly Find My Device) on Android, shows a device tied to your account and updates as it moves. It needs nobody’s cooperation, which makes it the better first step for your own lost phone.
A family locator app can show movement over time, and it asks both people to install it and keep a permission open. That is the right shape for a standing arrangement and the wrong shape for a single question. A shared location is at its best for one question asked once.
For the wider choices around locating someone, read whether a phone can be tracked without the person knowing.
Questions about this feature
How do I read the accuracy range?
The range is the area the device says it could be inside; the reported point is the center of that area. A tight range is a street-level answer, and a wide one is a town-level answer. Read the range before the point, because the center of a wide range is not a precise address.
Can I see them moving in real time?
No. PingLocate shares one point at the moment they tap, not an ongoing trail. For continuous tracking you need a monitoring app installed with their permission, which is a different product.
Is the location stored on my account?
There is no account to store it in. The result belongs to the request it answers, and it does not build a history of past points. The underlying request data is kept only as long as needed to run the service; the Privacy Policy has the retention details.
Why does the result show a wide range instead of a precise point?
Because the device could not get a better reading. Indoors, or with location services off, the phone falls back to Wi-Fi and cell estimates, which are coarser. The range is the device being straight about what it could work out.
Does the point move if they move?
No. The result shows the location at the moment they accepted, and it does not change even if they walk away. A newer point needs a new request and a new tap from them.
What should I do if the point looks wrong?
Read the accuracy range first, because a wide range means an area rather than a place. If the range was tight and the point still looks wrong, ask them to share once more from outdoors, with location services on.
Can I see where they were earlier?
No. A request produces one point for one moment, so there is no history and no earlier position to look at. Nothing runs on the phone between requests either.
Related reading
SAVE THIS SOURCE
Keep PingLocate close
Add us to your Google preferred sources, so the guide you need is easier to find next time.