Privacy Policy
Last updated: November 2026
CityWalker is a tool to help you track your walking progress and street coverage. This page explains what data the app uses, what leaves your phone, and who receives it, on both Android and iOS.
1. Location
CityWalker is designed with a privacy first approach. Your walk history stays on your phone.
- During walks: The app uses your device's GPS (Fine/Precise Location) to record your walks and calculate which streets you have covered.
- Background tracking: To keep recording your walk accurately when the app is in the background or your screen is off, the app uses a foreground service with a persistent notification on Android, and background location updates on iOS.
- Outside walks: The app also reads your current location when you add a city, to show which city or street you are in on the Walk and Stats screens, to highlight "you are here" in the region picker, and when you tap "centre on me" on a map. It never tracks you in the background outside a walk.
2. What Stays on Your Phone
Your walk history, GPS tracks, covered streets, and city progress are stored locally in a private database on your phone. They are never uploaded to CityWalker. The only exceptions are the optional View on Computer and Challenges features (both encrypted, described below) and your phone's own backup and transfer features (see section 6).
3. What Leaves Your Phone, and Who Receives It
Every service below receives your IP address as a normal part of connecting to it.
- Cloudflare Workers (CityWalker proxy): Requests for a city's street data go through a Cloudflare-hosted proxy that caches OpenStreetMap data. A request usually names a city or region. When a city is too large to download whole and you are inside it, the app instead requests a small area (about 3 km across) around your current location, and the proxy keeps that area as part of its cache. If a city is too large to download at all, its name is sent so it can be prepared for download later. With that request, the proxy keeps a short scrambled code made from the app's anonymous Firebase identifier (see below) and your IP address. It is a keyed one-way hash: it can't be turned back into either, and I use it only to stop one person filling the list of cities waiting to be prepared. It is deleted with the request, after at most 30 days. Cloudflare may log your IP address and the request for security and abuse prevention.
- Overpass API (overpass-api.de and mirrors): Public OpenStreetMap servers used when the proxy is unavailable. They receive the same request as the proxy, including the small area around your location in the case described above.
- Nominatim (OpenStreetMap): Turns city names into map boundaries and coordinates into place names. It receives the city name you search for, together with an approximate search area around your location. It also receives coordinates, rounded to about 100 metres, when the app needs the name of a place: on Android when it needs a place name, and on iPhone when you open the Walk screen outside a city you have downloaded. When you import a GPX walk, it receives the centre point of the track, rounded to about 100 metres, so the app can name the city it belongs to. On Android this only happens when the walk isn't in a city you have already downloaded, and the start and end points may also be sent if the centre isn't in a town.
- Your phone's geocoder (Google on most Android phones, Apple on iPhone): Receives your current location to look up the name of the city or street you are in (on the Walk and Stats screens, and when detecting your city). On iPhone, it also receives the centre point of an imported GPX track, or your location when you open the Walk screen outside a downloaded city, if Nominatim can't be reached. Google's or Apple's own privacy policy applies.
- Your phone's location services (Google Play Services on Android, Core Location on iOS): Provide your device's location to the app. The platform provider's own privacy policy applies.
- Map tiles (OpenFreeMap via MapLibre on Android, iOS and the View on Computer page; Apple Maps for route previews and the nearby streets map on iPhone): Display the base map. The tile server receives your IP address and the map area being shown. Your walk history is not transmitted.
- Firebase Anonymous Authentication (Google): Each time the app starts, it signs in to Firebase anonymously and uses the resulting identifier to authenticate requests to the CityWalker proxy, for rate limiting and abuse prevention. This happens regardless of the privacy settings below. The identifier is not linked to your name, email, or any other personal information, is not shared with advertisers or data brokers, and is never used for tracking. On iPhone, it may survive deleting and reinstalling the app.
- Firebase Crashlytics (Google, optional, on by default): Crash reports include stack traces, device model, operating system version, app version, and a Firebase installation identifier. No GPS coordinates or walk history are included. You saw a disclosure during onboarding and can turn this off at any time in Settings › Privacy.
-
Aptabase (optional, on by default): I use
Aptabase,
an open-source, cookie-free analytics provider, to understand how the
app is used. Events describe app usage, for example: app opens, walk
starts and completions (duration and distance), suggested and saved
routes (distances), milestones reached, cities added, challenges started, joined, left or
deleted, invite links opened or shared, and Challenges data deleted
(with the team size and how long you were in it in broad ranges, but
never which challenge, its city, or anyone's name), downloads,
permission prompts, and screens viewed. With each event, Aptabase
also receives the app version, device model, operating system,
language, and a random session identifier.
The app never sends your location, the routes you walk, or the streets you have covered to Aptabase. Events do not include the names of the cities you add. Aptabase works out an approximate country and region from your IP address when an event arrives.
You can turn usage stats off at any time in Settings › Privacy.
- View on Computer relay (optional, off unless you use it): If you use the View on Computer feature from a city's Coverage screen, the app builds a snapshot of that city's street coverage (including street coordinates and walk stats), encrypts it on your device with AES-256-GCM, and uploads only the encrypted file to a Cloudflare-hosted relay. The relay never receives the decryption key and cannot read the contents. The encrypted snapshot is deleted after a short expiry or once viewed on your other device. This only happens if you actively start this feature; it never runs in the background.
-
Challenges (Supabase, optional, off unless you use
it): A challenge lets friends combine the streets they have
walked in one city into a team map. Nothing is sent until you open
an invite link or start a challenge. Opening a link only asks the
server whether it is still valid and fetches its locked preview; the
app signs in only when you start or join.
When you do, the app signs in to Supabase with an anonymous account: a random identifier, with no name, email, or phone number. Your phone then shares, with your team only:
- the name you chose for the team;
- which streets in the challenge area you have walked, and the day you first walked each one (only the day, not the time);
- whether you marked a street as walked by hand instead of walking it with the app.
Your GPS tracks, your walk routes, and your walks outside the challenge area are never shared. If the challenge has a start date or leaves out imported GPX walks, the walks it leaves out are not shared either.
All of the above, and the challenge's name, city, and rules, is encrypted on your phone with AES-256-GCM before it is uploaded. The key is kept on the team's phones. An invite link carries a secret in the part after the "#", which browsers and apps never send to a server. The server also keeps a copy of the challenge key for each link, locked with a key made from that secret, so only someone holding the link can open it. Supabase stores the encrypted data, but neither Supabase nor I can read it.
What the server can see: your anonymous identifier, which challenges it belongs to and whether it created them, when it joined or left, when each encrypted upload arrived and how large it is, and each invite link's expiry date and number of uses (stored as a one-way hash, not the link itself), who made each link and when, when a challenge was created or last changed, and whether a member left or was removed. I also see daily totals, such as how many challenges, joins and uploads there were, with no identifiers, names, or content. Supabase may also log your IP address for security and abuse prevention.
Anyone who has an invite link can join until it stops working (after 14 days, or sooner if the person who made it leaves) and can see the challenge's name, city, and the name of the person who sent it. Share links only with people you want in the team. Anyone in the team can make a new link. Expired links are deleted from the server a week after they stop working.
Challenges don't end on their own. What you uploaded stays on the server, encrypted, until you leave the challenge, its leader deletes it, or you use Delete All Data. Uninstalling the app does not delete it.
- Street reports (optional): If you report that a street is not walkable, the app sends the street's OpenStreetMap IDs, the name of the city it's in, the point you tapped on the map, and any reason you type to the CityWalker proxy, where I review it. Reports don't include your name or any account details. The proxy keeps the same kind of scrambled code with each report (see the proxy entry above), only to stop one person flooding the list of reports. It isn't shown to anyone, and it is deleted once I've reviewed the report, or when I clear out reports nobody has touched for six months. Once I've reviewed a report, the reported street (without your reason) can be shown to other people who have it in their city, so they can agree with it. If I confirm it, the street is listed publicly on Streets CityWalker leaves out, again without your reason. I keep each report, its reason and my decision for up to two years, so I can look back on past decisions, and then they are deleted automatically.
- Share from Google Maps (Android, optional): When you share a place from Google Maps into CityWalker, the app opens the shared link to find the place (Google receives this request), then looks the place up with Photon (by komoot) or Nominatim.
- GitHub: The app downloads the list of pre-prepared city regions from GitHub. No personal data is sent beyond your IP address.
- Supabase (app settings): When the app starts, it downloads a short list of settings from a Supabase-hosted database, for example which features are switched on. The same list is sent to everyone. No personal data is sent beyond your IP address.
- Google Play (Android): Used to check for app updates and to show the in-app review prompt. Firebase Authentication also uses Google Play Integrity and reCAPTCHA to protect against abuse.
4. Permissions
- Fine/Precise and Coarse Location: Required to record walks, to show which city or street you are in, and to detect which area of a multi-region city you are currently in.
- Background Location: Allows walk recording to continue when the app is in the background or the screen is off. On Android, this is implemented as a Foreground Service with a persistent notification while tracking is active.
- Foreground Service - Data Sync (Android): Used to download a city's street data in the background when you start a walk before the city has finished loading.
- Notifications: Used to display tracking and download notifications, and walk reminders.
- Internet and Network State: Required to download map tiles and street data, and to check whether you are online.
- Run at Startup (Android): Restores scheduled walk reminders after your phone restarts.
- Wake Lock (Android): Keeps the CPU active during walk recording so GPS samples are not dropped.
- Vibrate / Haptics: Used for short haptic feedback (for example, confirming a walk has started or finished).
- Photo Library (Save Only, iOS): Used only to save a walk summary card image to your photos when you tap Save. The app does not read your existing photos.
- Camera: Used only to scan the QR code shown on the View on Computer web page, to pair your phone with that browser session. The camera is active only while that scanner screen is open. No photos or video are captured, stored, or transmitted.
5. Importing Walks (GPX)
You can optionally import walks from GPX files (for example, exported from Strava, Garmin, or Komoot). When you import a GPX file:
- The file is read directly from your device's storage using the platform's standard file picker.
- Matching the route against city streets happens entirely on your device.
- The file itself and the route are never uploaded. To work out which city a walk belongs to, the centre point of the track is sent to Nominatim, rounded to about 100 metres. On Android this only happens when the walk isn't in a city you have already downloaded, and the start and end points may also be sent if the centre isn't in a town. On iPhone it happens for every import, and if Nominatim can't be reached, the centre point goes to Apple's geocoder instead. The app may then download that city's street data as described above.
6. Backups and Switching Phones
- Android: Your walk history is not included in Google Drive backups; only app settings are. When you copy data directly from your old phone to a new one during setup, your walk history moves with it.
- iPhone: Your walk history is included in your iPhone's iCloud or computer backup, like other app data, so it comes back when you restore or set up a new iPhone. These backups are stored in your own Apple account; I cannot access them.
- Challenges: Challenges don't move to a new phone, on either platform: the anonymous Challenges account and the keys stay on the old phone. On the new phone, join again with an invite link. Your old phone stays in the team as a separate walker and keeps the streets it claimed. To free its place, leave the challenge on the old phone before you stop using it, or, if you lead it, use Delete All Data there so another member takes over.
7. Children's Privacy
CityWalker is rated for all ages and does not require an account. The anonymous Challenges account described in section 3 has no personal details attached. The app never asks for your email or other contact details, from any user, including children. The only name it asks for is the name you choose to show your challenge team, which can be a nickname.
8. How to Delete Your Data
Your walks and progress are stored only on your phone. To delete them:
- Open CityWalker
- Go to Settings
- Scroll to the About section
- Tap Delete All Data
- Confirm deletion
This permanently removes all cities, street data, walk history, GPS tracks, coverage progress, and app preferences from your phone.
Delete All Data does not affect the data held by the services in section 3: anonymous usage events (Aptabase), crash reports (Crashlytics), and the anonymous Firebase identifier. None of these are tied to your name or email, so I cannot look them up by person. Crash reports are deleted automatically after 90 days.
Challenges: If you have started or joined a challenge, Delete All Data also deletes your anonymous Challenges account on the server, and with it everything you uploaded to any challenge and the invite links you made. Your teammates' challenges carry on without your streets. If you led one, another member takes over; if you were its only member, it is deleted. Your teammates' phones remove their copies of your streets the next time they open CityWalker or finish a walk. If the server can't be reached, the app tells you and lets you try again later or delete only what is on your phone. If you delete only what is on your phone, the encrypted copy on the server stays: the phone no longer has the anonymous account needed to delete it, and nothing links that account to you.
From a challenge's screen you can also leave it: your streets, your name and the invite links you made are removed from the server, and your teammates' phones drop their copies. The server keeps a membership record (your anonymous identifier and when you joined and left) so their phones know you left, until you use Delete All Data or the challenge is deleted. As its leader, you can delete it instead: everything uploaded to it is removed from the server, for every member.
9. Changes to This Policy
I may update this Privacy Policy from time to time. You are advised to review this page periodically for any changes.
10. Contact
If you have any questions about this Privacy Policy, contact me at [email protected].
