Alex Morin
Alex Morin writes and maintains the guides on PingLocate. The subject is narrow on purpose: what a phone number can and cannot yield, how a consent-based location request works, and how accurate the result really is.
What Alex Morin covers
- How a request works. The link, the browser prompt, the single point that comes back, and why none of it happens without the other person acting.
- What a number can tell you. Why a phone number is a routing label rather than a position, and why reverse lookups return static detail rather than a live place.
- Accuracy. What GPS, Wi-Fi, cell towers, and network estimates each produce, and why the range matters more than the point.
- Consent and legality. Where a request sits relative to surveillance, and the rules that vary by place.
How the guides are researched
The accuracy vocabulary on this site is deliberate. When a guide says a reading is good to tens of meters, that is the figure a phone produces with a clear satellite fix. When it says city-level at best, that is the network fallback. The guide names which one it means rather than splitting the difference.
Claims about what a request can and cannot do are checked against the browsers people actually carry, because both the permission prompt and the position estimate come from the phone rather than from the service. Where devices differ, the guide says so instead of generalising.
Anything that cannot be demonstrated is not asserted. No percentage, no invented test result, no figure without a source behind it.
Corrections
Spot something wrong and it gets fixed at the source. Email [email protected] with the page and the sentence, and the edit lands in that sentence rather than as a note bolted onto the end.
Every guide is listed on the guides page, newest first.