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

How that is enforced rather than promised

Claims like these are worth little on their own, so they are held in place mechanically:

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.