Help

The city, street by street.

As of 21 September 2026. This is a courtesy translation; the Polish version is the reference.

Tup Quest is a game about the city, not a fitness app. You walk, streets turn coral on the map, and along the way you find places from records, films, books and memes. There is no pace, no heart rate, no step goal.

Below are the questions people actually ask. If yours isn't here, write to d.ptaszek@gmail.com.

Streets on the map

I walked this street and it didn't get marked

It's almost always one of five things.

1. It isn't a "street" as the game understands it. We count roadways and living streets: primary, collector, local, residential, home zones and pedestrian streets. We don't count pavements, park paths, shortcuts across a lawn or access roads to car parks — those are separate objects on the map that simply aren't on the list to collect. Motorways and expressways aren't either, because you can't walk them.

2. Too short a stretch. A street is split into segments between junctions. A segment counts once you've walked the clear majority of it — about 60 percent of its length. Turning into a street and turning back after twenty metres isn't enough.

3. The walk wasn't on. In the default mode ("Only during a walk") nothing counts until you press "Start a walk".

4. GPS had a bad day. We reject fixes with accuracy worse than 60 metres, and those between 40 and 60 metres count more slowly — more of them are needed before a segment is credited, and fixes implying a speed above 13 km/h — that's no longer a walk but a ride. In narrow streets between tall buildings the signal bounces off walls and can drift by tens of metres.

5. The street is outside the chosen city. Every city is a separate file with its street network. Anything beyond the administrative boundary has nothing to match against.

What to do: walk the segment again, its full length, with the walk on, ideally not right against a building wall.

A street I didn't walk got marked

That happens too, and honestly so: matching a position to a street has a tolerance of somewhere between a dozen and about thirty-five metres, depending on the street class and signal quality. If a named courtyard lane or passage runs fifteen metres parallel to your route, GPS can point at the neighbour instead of you.

The other cause is signal bounce in dense buildings and position jumps after leaving the metro or a shopping centre. GPS jumps of more than 50 metres at an unrealistic speed break the drawn track and don't count towards distance — but the street under such a fix may still be credited. That's why a neighbouring one sometimes pops up.

For now there's no way to un-mark a single street — the only cleanup is a full reset in Settings. If it happens every time in one specific place, write to us: it usually means the street data there needs a fix.

Does the app drain the battery?

GPS is one of the more expensive parts of a phone and there's no point pretending otherwise.

In the default mode ("Only during a walk") the battery is used only between "Start a walk" and "Finish" — roughly like running navigation. After the walk ends the app doesn't touch location at all. If you close the app mid-walk instead of pressing "Finish", background position reading is switched off at the next launch.

In "Automatically in the background" mode the phone asks for position all day, so consumption is noticeably higher. That's a deliberate trade: convenience for battery.

In practice: finish the walk when you get home. A walk never ends by itself, even when you stand still — a café, lunch or a film won't interrupt it. If you forget to finish it, it keeps running until you tap "Finish": on iPhone you see it as the blue location indicator, on Android as a persistent notification. The walk's time counts up to your last movement, so a forgotten walk doesn't skew your stats, but it does use battery until you finish it. You can lock the screen if you granted the “Always” location permission — then keeping the app in the foreground improves nothing. Without it, a walk is recorded only while the screen is unlocked; the app tells you which mode you are in.

Why does the app ask about notifications?

We ask once, at your first walk. The permission lets us show two things: on Android, a persistent notification while a walk is running, and on both phones the Sunday weekly summary if you turn it on in Settings. There are no other notifications — no reminders, no nudges. It all happens on the phone, with no server. You can refuse: the game works the same.

What's the difference between the two tracking modes?

Only during a walk (default, nothing to change) Streets are marked from pressing "Start a walk" until "Finish". The screen can be locked, but only if you granted the "Always" location permission — without it a walk is recorded only while the screen is unlocked and the app is in front. The app tells you which mode you are in. Outside a walk it doesn't know your position.

Automatically in the background (optional, you turn it on in Settings) The app marks streets whenever you move, without pressing anything. It needs the system's "Always" permission, so before the system asks we show our own screen explaining that in this mode location is read even with the app closed. Walks split themselves: a break longer than 20 minutes ends one and starts the next. It uses more battery.

In both modes the data stays in exactly the same place — on your phone. You can switch modes in Settings at any time.

Cities

My city isn't there

The list has all 18 regional capitals of Poland: Warszawa, Kraków, Łódź, Wrocław, Poznań, Gdańsk, Szczecin, Bydgoszcz, Toruń, Lublin, Białystok, Katowice, Rzeszów, Kielce, Olsztyn, Opole, Zielona Góra and Gorzów Wielkopolski. Each city is a pre-built file: the whole street network, the district boundaries, a few hundred places, and in eleven cities also cultural collections — the rest are waiting for theirs.

We build cities one by one, checking the results by hand. The picker shows only cities with a complete data set — there's no "coming soon" entry. A city appears only when it can really be played.

Tell us which city you walk in. It genuinely affects the order.

Will there be more cities?

All 18 regional capitals are already in the app. Next in line are the larger county-level cities — Gdynia, Częstochowa, Radom, Sosnowiec, Bielsko-Biała. We don't promise dates, because every city has to be prepared and checked by hand.

Cultural collections catch up separately: today there are 30 of them in 11 cities, and they arrive faster than cities do.

Progress is saved separately for each city. Switching city deletes nothing — come back and everything is where you left it.

Finds and collections

Cultural collections are currently 30 sets and 350 places in 11 cities. Bydgoszcz, Rzeszów and Opole have only the street network and ordinary places for now — in the Discover tab you'll see a note that collections are in the works.

Collections and the descriptions of their places are in Polish for now. Routes — the ticklists in the Discover tab — have English descriptions.

I was at this place and it didn't get found

A place is found when you get within 40 metres (cultural-collection places: 60 metres), with a margin for GPS accuracy. Passing by on a tram isn't enough.

The three most common reasons:

• The app wasn't collecting position at the time. In the default mode a walk has to be running.
• The pin is somewhere other than you think. Points are geocoded from addresses, so they sometimes land in the middle of a block or on the far side of a courtyard. Walk up to the pin shown on the map, not to the facade you associate with it.
• You were inside the building. Under a roof GPS gets thoroughly lost. Step outside the entrance for a moment.

Sometimes a point is simply misplaced. Places labelled "flagged for verification" are our honest "still checking this". Report it and we'll fix it.

How do I report an error in a cultural place, or suggest a new one?

One e-mail to d.ptaszek@gmail.com.

An error: city, collection name, place name and what's wrong — wrong address, venue closed, untrue story. One sentence on how you know is enough.

A new place: an address or a point on the map, two sentences on why the place matters (a record, a film, a book, a meme, history), and a link if there is one. Collections are edited by the Tup Quest editors, so we read every suggestion.

An error in the map itself — a missing street, a wrong name, a street that no longer exists — is usually OpenStreetMap data, because that's where the street network comes from. You can fix it directly in OpenStreetMap; the fix reaches us at the next rebuild of the city data. Or write to us and we'll report it for you.

Points, levels, league

How does the league work and when does it reset?

League points count from Monday:

• 1 pt for a new street,
• 2 pts for a found place,
• 3 pts for a cultural-collection place.

Distance, time and steps give no points. Discovery counts, not effort.

The new round starts on Monday, by your phone's clock. The weekly counter returns to zero; the history of previous weeks stays in the League tab.

Five leagues and weekly point thresholds: Bronze 0, Silver 40, Gold 120, Platinum 300, Diamond 600. The league simply follows the current week's points — there are no penalties for a break, no relegation for inactivity. On Monday everyone starts from zero.

A street counts once. Walking the same street a second time adds no points — but the new side street next to it does.

The league is computed entirely on your phone and works even if you don't want to compare yourself with anyone.

The online leaderboard is optional: you join it by entering a nickname in the League tab. Until you do, you're not on it at all. After entering a nickname, the only things that leave the phone are: a random player identifier, the nickname, the city name, the week number and three numbers (streets walked, places found and collection places) plus the points computed from them. The league on your phone adds up points from all cities, but only points earned in that one city go to the city leaderboard. No coordinates and no tracks.

How do friends' groups work?

A whole-city leaderboard can be discouraging — someone always walks more. A group is a private leaderboard where you race only the people you invite yourself.

You start a group in the Groups tab, name it, and the app draws an eight-character code. Send it to friends, they enter it on their side, and from then on you see each other's scores in one place. One person can belong to several groups at once — one with the work crew, one with family.

A group shows exactly what the city leaderboard shows: nickname and points for the current week. Not where anyone walked, which streets or when.

The code works like a key: anyone who learns it can join. If a group should stay closed, just stop passing the code around.

Why calories in the walk summary?

Out of contrariness. After a walk we show one calorie figure and immediately convert it into pierogi, doughnuts or a kebab — because that's the honest place for that metric in a game about the city.

It isn't a measurement. We compute it with a fixed factor from distance, assuming a weight of 75 kg. We don't ask for weight, height, age or sex and don't intend to — so the number is about a hypothetical passer-by, not about you. We don't save it, don't send it anywhere, and it doesn't affect points.

If you count calories seriously, you need a different app. This one is about streets.

Do steps affect points?

No. Not points, not level, not league.

We show steps in one place, in Profile, captioned "side effect", because it's a curiosity, not a goal. There's no step goal, pace or heart rate — and there won't be. Points come only from new streets, found places, completed districts, city milestones and the daily challenge.

We read the pedometer locally from the system (Apple Motion; activity recognition on Android). The step count is never sent anywhere or stored in the app's database — we read it live from the system to show it in Profile. If you don't see steps, the system permission is missing or the phone doesn't provide them — it has no effect on the game.

Data and privacy

Do my data go to a server?

GPS tracks and detailed walk history are stored locally. The app also uses the network for map backgrounds, updates and the optional features listed below.

There's no account, login, e-mail or password. Walked streets, found places, walks, points and badges are saved in a database on your phone.

GPS tracks are not sent to the leaderboard or usage statistics. The route database is excluded from iOS system backups; Android app backup and device-to-device data transfer are disabled. Progress does not move automatically to a new phone. If you share a summary image or diagnostic export yourself, you send it to the app you choose. See the Privacy policy.

The app does keep five network connections, and that has to be said plainly.

1. Map tiles from OpenFreeMap (tiles.openfreemap.org). As with any online map, the tile provider sees your device's IP address and which map fragments it requested. We do not send a GPS track or player ID. Requested map fragments can nevertheless reveal the area being viewed.

2. Update check with Expo (u.expo.dev). At launch the app asks the Expo server whether a newer version of the JavaScript layer exists and downloads it if so. That request carries: the app's installation identifier (a random UUID assigned at installation, not the advertising identifier and not a hardware identifier), the runtime version, the platform and the update channel. None of your game data goes there — no streets, no places, no position. The service is run by Expo Project Services, a US company, so this is a transfer of data outside the European Economic Area; the privacy policy has the details.

3. Leaderboard and groups — only if you join them. Entering a nickname in the League tab is that moment. What leaves then: a random player identifier, the nickname, the city name, the week number and three numbers. Nothing else.

4. Usage statistics — only with your consent. Withdraw it in Settings; see the next question for details.

5. Error reports (Sentry, EU region) — only with consent to statistics and error reports. We send JavaScript error reports, including the app version and where the error occurred in code. Native crash reporting, session tracking and performance monitoring are disabled. User and network-request context is removed. See section 4.4 of the Privacy policy.

Connections 3 and 4 go to our own database — a Supabase project on servers in Ireland, in the European Union. Connection 5 goes to Sentry, also in the European Union.

From 5 October 2026 there is one more recipient you won't find on the list of connections, because your phone never connects to it: Amplitude. Until that day nothing is forwarded there. It is a product-analytics tool — charts and funnels built from those same events. Our server forwards a narrowed version of the statistics to it from the database in Ireland, and the project sits in the EU region. Coordinates, track traces, street and place names, your nickname, group names and GPS diagnostics do not go there.

What Tup Quest doesn't have: ads, cross-app tracking, an advertising identifier, data sales, data brokers, advertising profiles, or decisions made about you automatically.

What we won't claim, because it would be a stretch: that nobody here analyses behaviour. If you switch statistics on, your events line up in Amplitude as a sequence under one identifier, and return-rate charts are built from that. It is analysis of player behaviour — done to develop the game, not to show you or sell you anything.

And usage statistics?

They are off by default. With your consent, the app sends events such as “Discover screen opened” or “walk finished, 4 new streets”. These contain no GPS track or specific street and place names. The server adds the player ID, so events can be linked to leaderboard entries. These data are pseudonymous, not anonymous.

They go to our own database in Ireland and, from there, in a narrowed form, to Amplitude. We don't store the IP address with events; only the server gateway sees it, as with any request on the internet. We don't pass your address to Amplitude at all: every forwarded event has 0.0.0.0 hard-coded, and the connection itself leaves our server, not your phone.

The switch: Settings → Statistics and error reports. A single consent covers both recipients — you cannot accept our database and refuse Amplitude. Turning it off stops new events and clears both queues: the one on your phone and the one on our server waiting to be forwarded to Amplitude. It cannot recall a request already sent, or data forwarded earlier. See section 4.3 of the Privacy policy.

How do I delete my data?

In Settings → Data → Delete account and all data, confirm deletion. The app deletes your guest account, scores, linked analytics, memberships and groups you created (also for their other members), then local walks, GPS tracks and progress. We also erase anything waiting to be forwarded to Amplitude and send it a request to delete its copy — Amplitude carries that out, so it does not happen in the same moment. Internet access is required for server deletion. Without confirmation, local progress is retained for retry. Analytics, diagnostics and automatic tracking are switched off. This cannot be undone.

Uninstalling alone removes the local database, but leaves server records. If you cannot access the app, contact d.ptaszek@gmail.com; include your player ID if available. See Data deletion.

Do I need internet?

For the map, yes. Tiles download from the network, so without coverage the map won't draw.

Everything else works offline. The street network, districts and places live in the city file inside the app, and GPS needs no internet. Streets are credited without coverage, finds too, points too. When you're back in coverage the map fills in — the progress is already saved.

The network is also used by the update check at launch and — if you use them — the leaderboard and groups. Without coverage the app simply starts with the version it already has, and scores are sent at the next connection.

In a tunnel, the metro or a basement there's no satellite signal and nothing counts. That's a limitation of GPS, not of the app.

Money and age

Tup Quest is free. No ads, no in-app purchases, no subscription, no premium version. There's nothing to buy, so nothing to ask about with refunds.

Age rating: 4+ / PEGI 3. The app isn't aimed at children under 13, but contains nothing unsuitable for younger users.

Contact

Write freely — a bug, a place suggestion, a request for a city, a privacy question, odd map behaviour.

d.ptaszek@gmail.com https://tup.quest

Documents worth a look before asking about privacy:

• privacy policy: https://tup.quest/en/privacy
• terms of service: https://tup.quest/en/terms
• this help page: https://tup.quest/en/help

You can open all three from the app: Settings → Documents.

One person stands behind Tup Quest, so a reply may take a moment. We reply in Polish or English and read every message.

If you're reporting a bug, it helps to include: phone model, system version, app version (Settings → About), the city and a description of what happened. Don't send screenshots with your track visible if you'd rather not — a street name is enough for a report.

Street and place data: © OpenStreetMap contributors, ODbL licence. Map: OpenFreeMap. Cultural collections: Tup Quest editors.

Publisher: Cybird Consulting Dariusz Ptaszek.