Privacy
A precise coordinate is sensitive information. This page says exactly what happens to yours, in specifics rather than reassurances.
What Locus does with your pin
When you place a pin, its coordinate is held in the page you are looking at and sent in the body of one request to the GeoHistory API, so that the API can answer which records are nearest. When you move the pin or close the tab, it is gone. That is the entire lifecycle.
What Locus does not do
- No accounts, sign-in, profiles or saved searches.
- No cookies, local storage, session storage or other browser storage of any kind.
- No analytics, tracking pixels, advertising tags or third-party scripts.
- No coordinate in the address bar, so nothing lands in your browser history, in a shareable link, or in a referrer header.
- No coordinate sent anywhere except the one GeoHistory request. Map tiles are fetched by viewport tile index and carry no pin.
- No use of your device location, and no ability to ask for it.
- No server of its own. Locus is static files; there is nowhere here to log anything.
How that is enforced rather than promised
Claims like these are worth little on their own, so they are held in place mechanically:
-
The request that carries the coordinate uses
POSTwith the coordinate in the body, specifically so it cannot appear in a URL, a proxy log, or a referrer. -
That request sets a
no-referrerpolicy at its own call site, so the API is not told which page made it. -
The site sends
Permissions-Policy: geolocation=(), which makes the browser refuse the location API even if some future dependency asked for it. - An automated test fails the build if any source file references browser storage, navigation state, a beacon, or the location API, or if network calls appear in more than the single module allowed to make them.
The page-level referrer policy sends the origin — www.locustimeline.org — and
never the path, because map providers refuse tiles to entirely unidentifiable clients.
Since no coordinate is ever in a path, there is no path worth hiding.
What the API sees
GeoHistory receives the coordinate, a radius, and the filters Locus applies. Its access logs record the request path, the status, the duration and a truncated client address; the request body is not logged, so the coordinate is not written down there either. The service is rate-limited per client, which is the one reason it keeps any client identifier at all.
The hosting
The site is static files on Cloudflare Pages and the basemap comes from OpenFreeMap. Both see ordinary web requests — a page, a stylesheet, map tiles for the area you are looking at — as any host and any map provider must. Neither is given your pin, and neither is asked to run any code on Locus's behalf.
If this ever changes
A future version may add a "use my location" button. If it does, it will be an explicit action you take, never automatic and never the default, a refusal will be an ordinary outcome, and the coordinate will be handled exactly as a dropped pin is today. Nothing on this page is planned to be relaxed; if something has to be, it will be changed here first.
The source is public at github.com/noffsingercb/locus, which means none of the above has to be taken on trust.