Start with a single location request
On November 4, 2026, we inspected useGeolocation.ts in BAKUO’s local demo project. It requests a position with getCurrentPosition() on initial load and holds the result in React state. This differs from continuous tracking with watchPosition().
The absence of a server request inside that hook does not establish that no part of the service transmits location. Inspect the components receiving the coordinates and any map, advertising, or analytics code. Testing network behavior in the public deployment is a separate task from this source review.
Separate coordinates from distance calculations
Downloading shop coordinates and calculating distances locally can avoid sending the user’s position to a distance-sorting API. The server supplies the directory; the browser calculates each shop’s distance from the supplied position.
Location accuracy still matters. The browser’s coords.accuracy conveys uncertainty in the estimate. Displaying many decimal places does not make the original position more accurate, and nearby shops may change order. Straight-line distance is also different from walking time or route distance.
Test allowed, denied, and timed-out requests separately
The inspected hook stores coordinates and accuracy on success, and clears coordinates on failure. It returns an alphabetical-sorting message for denied permission and a retry message for timeout. A chosen region must not silently be presented as the user’s actual location.
Location access depends on a secure context and permission. See the Geolocation documentation for those conditions. Separately check that regional search or the full list remains usable when location fails.
- Allow permission in a fresh browser state and check which position distance sorting uses.
- Deny permission and check that distance is removed while name or regional browsing remains available.
- Check unavailable-position and timeout messages, including whether the page keeps retrying automatically.
What the Network panel can establish
- Clear developer tools’ Network log and reload with all request types visible.
- Run nearby sorting and inspect request URLs, query parameters, and bodies for coordinates.
- Open an external map from the same state. Distinguish destination coordinates from a user origin in the new URL.
- Compare allowed and denied states and record the browser, date, and actions tested.
This provides evidence for the observed session. Looking only at Fetch/XHR, or observing no request once, cannot establish that nothing is ever stored. Other requests and server-side processing need separate examination. Log retention depends on the server and external service settings and policies.
Draw a clear boundary in the privacy explanation
Explain which feature uses location, what remains possible after denial, and which service opens for an external map. Keep local distance arithmetic distinct from the processing performed by external services.
Support does not need an exact current position or travel history to begin investigating. A screenshot of the problem, permission state, and browser type are often enough to narrow it down. See the BAKUO product guide for visiting a shop.