Visitor Map

We estimate a coarse region from your IP address and round it to roughly 11 km before it’s stored, under a random one-time ID — never your account, email, wallet, or any identifier. The same goes for the approximate city of an active connection to our API: our server reads it from the location Cloudflare attaches to the request, and it is drawn like any other dot, with no label and no identity. When that estimate is not available, all we record is the country your network reports; that is stored as a country-level sighting and drawn as a dot at the middle of the country, which is not where anyone actually was. Your live dot on the map expires automatically after 5 minutes of inactivity, same as always.

What we keep: to show a 24-hour history, daily averages and a layer showing every place a visit has ever been recorded from, we keep an aggregated count — how many visitors were seen near a rounded point, in a given period. That aggregate never records which specific visitor it was, only that someone was near that rounded point at that time. Those counts are kept indefinitely, because at this coarseness they identify nobody. What expires is the detail: after 30 days each record is coarsened from roughly 11 km to roughly 110 km and from hourly to daily — those older points are then labelled as the wider regions they have become, so nothing on this map is ever drawn as more precise than it really is. The times shown next to a point follow the same rule: rounded to the hour while the record is recent, and to the day once it has been coarsened, so a point never discloses the moment one visitor was seen. The short-lived table used to avoid counting the same person twice in one hour is deleted after 2 days. The optional “all-time visitors” layer (off by default) draws from this aggregate only, never from individual visit records.