Frequently Asked Questions

Does Locus keep my location?

No. There are no accounts, no cookies, no analytics and no saved searches. The pin you place is held in the page you are looking at and sent in one request to the GeoHistory API so it can answer. It is not written to your browser's storage, not put in the address bar, and not stored on a server — there is no server here to store it on.

Because the coordinate is never in a URL, there is nothing to leak through your history, a shared link, or a referrer header. Privacy lists the specifics.

Will it use my device location?

Not in this version. Locus only ever reads a pin you placed yourself. The page also ships a permissions policy that refuses the browser location API outright, so the claim is enforced by the browser rather than promised by the copy.

A "use my location" button may arrive later. If it does, it will be an explicit action, never automatic, never the default, and saying no will be an ordinary outcome rather than an error.

Why did it say "nothing within 5 km"?

Because there was nothing within 5 km, and Locus would rather tell you than quietly widen the circle and let you assume otherwise. It searches 5, then 15, then 50, then 150 kilometres, stopping at the first circle that can fill a list of twelve.

A small town usually fills at 50 km and genuinely rural country at 150 km. That is the record being thin, not the search being broken. The radius actually used is always printed above the list.

Why are the results out of distance order?

They are in date order on purpose. The twelve records are chosen by how close they are and then shown oldest first, so what you read is a small chronology of one place rather than a ranking.

The numbers on the map markers match the reading order, which is why marker five can sit closer to your pin than marker one. They are list positions, not a score.

Why are there no births or deaths?

Locus asks for them to be left out. Near a dense city centre, the overwhelming majority of the closest records are births and deaths of minor figures — measured at 85 to 94 percent on the probes used to design this — and including them turns "what happened here?" into "who was born here?"

They are still in the dataset and a later view may show them deliberately. They are just not allowed to crowd out the twelve slots.

Why is every result the founding of a nearby town?

This happens at the wide rungs, and it is the record showing its shape. Municipal foundings are by far the best-covered category of place-anchored history in Wikidata, so once a search has to reach 50 or 150 kilometres they can fill the list on their own.

Moving the pin toward a larger town usually produces a denser, more varied answer. It is a genuine limitation of the data rather than a bug, and worth knowing before you judge a region by its list.

I dropped a pin in the ocean and got nothing.

Correct behaviour. Open water holds almost no place-anchored records, and Locus returns an empty answer that says where it looked rather than inventing coverage or reporting an error.

It said it could not reach the service, or asked me to wait.

Two different things, both normal. The history service rests when nobody is using it, so the first request of the day can be slow or fail while it wakes; the retry button is there and your pin is kept.

If you moved the pin many times quickly you may hit the service's rate limit. Locus reads the wait the service asks for and re-enables the retry button when it expires — usually seconds.

Can I share what I found?

Not as a link, and that is the trade. A shareable link would have to carry the coordinate in the address, which is exactly the thing Locus refuses to do. Every card links to its own source, so those links are yours to send.

Where does the history come from?

Wikidata and Wikipedia, assembled into a dataset by the GeoHistory project. The Resources page has the details and the links, and every card carries a link to its own source under CC BY-SA.

How does it decide what to show?

It asks one open dataset for the records physically nearest your pin, widening the circle only as far as it must, and shows the closest twelve in date order. How this works explains it properly.

Is this related to Circa?

Same history, different question. Circa takes a life and shows the history that surrounded it; Locus takes a point and shows what was nearest to it. Both are clients of the same open dataset and neither depends on the other. Why this exists has the longer version.