What we keep, and what we don't.

Nahgoo is an app about walking to real places. That means it is an app that could very easily know too much about where you go. This page is the specific, checkable version of what it actually stores.

Last updated 21 July 2026

The short version

Nahgoo does not store your location. Not your GPS coordinates, not a trail, not a history of where you have been standing.

What it stores is which public places you captured, and when — the coordinates saved against a capture are the place's coordinates, the same ones on the public map, not yours.

Your live position is used in the moment to draw the map, measure how far away a pin is, and ask what is nearby. Then it is gone. Nothing writes it down.

That distinction is the whole of this policy, so it is worth being plain about the part that is still sensitive: a list of places you were within 25 metres of, each with a timestamp, is a record of where you have been — even though it is assembled out of public coordinates rather than your own. It is treated that way below.

What is stored in your account

Your account itself

An email address and a password. The password is handled by our authentication provider and is never visible to us in a readable form.

Your captures

For each place you capture:

The place's name, description and coordinates — the pin's, not yours — saved so a captured spot can be put back on the map later, even if the source data stops returning it.
The date and time you captured it.
Which guide it belonged to, and the category it was filed under.

Plus the totals built out of those: how far you have travelled, and which stamps you have earned. Guides you have made or saved, and gems you have submitted, are stored against your account too.

This is readable only by you. It sits in your own row, protected by row-level security, and nothing in the app shows one person's captures to another person. That is a design rule, not just a current fact.

A short-lived integrity record

To tell a real capture from a faked one, each capture also records how accurate your GPS reading was at that moment, how far from the pin you were, whether the app was in simulate mode, and a timestamp. None of these are coordinates.

This is deleted after 30 days, automatically, leaving only two values: a version number, and whether simulate mode was used. It is evidence with an expiry, not history.

Who else receives anything

A map app cannot work without asking other people's servers for things. Here is every one of them, and what it sees.

CARTO — map images

Sees: your IP address, and which square of the map you are looking at, continuously while the map is open.

This is the largest one, and it is inherent to showing you a map: the images are fetched by your phone as you pan and zoom.

Photon, by Komoot — search suggestions

Sees: what you type into search, and your approximate position — rounded to about 11 metres — as you type it.

The position is sent so that searching "main street" finds the one near you rather than the first one on earth.

Nominatim, by the OpenStreetMap Foundation — addresses

Sees: the coordinates of a pin you tapped, which are public coordinates, and your IP address. Also what you type, if search falls back to it.

Used to turn a pin into a street address you can read.

Supabase — accounts, database and the nearby-places service

Sees: your account, everything listed above as stored, and your exact position at the moment the app asks what is nearby.

That position is rounded to a roughly 5.5 km square as soon as it arrives, and the results are cached against that square in a shared table that carries no user identifier at all — so the cache cannot say who asked.

Place data itself comes from OpenStreetMap and Wikipedia. Those are read-only: the app fetches from them through the service above, so they receive nothing from your device and never see your IP address.

We do not use advertising networks, third-party analytics, or tracking pixels. Nothing here is sold, and nothing here is shared for advertising.

How long it is kept

Your captures, stamps, guides and totals: for as long as your account is open. They are the point of the app — a passport that quietly erased your stamps after a year would be a broken product rather than a privacy improvement. They stay until you ask for them to go.

The integrity record: 30 days, then automatically stripped to two non-locational values.

The nearby-places cache: about three weeks, keyed to a 5.5 km square, with no user attached.

Asking for your data, or its deletion

You can ask us what is held on your account, ask for a copy of it, or ask for it to be erased. Depending on where you live you may have these as legal rights; we will honour the request either way.

Two things a deletion does not automatically reach, stated here because the app states them too:

Gems you have submitted. Once approved, a gem is a public place on a shared map that other people navigate to. Removing your account does not remove it by default — tell us if you want a submission taken down as well, and we will handle it as part of the same request.
Guide codes you have already shared. A code you sent to somebody keeps working for them after your own copy is gone.

Changes to this policy

If what the app stores changes, this page changes in the same release, and the date at the top moves. It is written from the code rather than alongside it, so a change to one is meant to be a change to both.