What data does CityWalker collect

CityWalker is designed to keep your data on your device. Your walk routes and the streets you've covered are never sent to CityWalker. What I collect are anonymous usage events to help improve the app and crash reports when something goes wrong.

🔒

Your walk history is never uploaded. The streets you've walked and your routes are stored locally, and your location is never included in any usage event or crash report.

What's stored on your device

Everything CityWalker tracks lives in a local database on your phone. No account, no cloud sync.

Street data. The map of walkable streets for each city you have added, downloaded from OpenStreetMap.
Walks. The start time, end time, and distance of each walk you have recorded.
Coverage. Which street segments you have walked.
Settings. Your unit preference (km or miles), reminder times and privacy toggle states.

What gets sent

To work, the app downloads street data and map tiles. It also signs in with an anonymous identifier so the street data server can limit abuse. When a city is too large to download whole, the street data request covers a small area around your current location. The privacy policy lists every service involved.

On top of that, CityWalker sends two types of data to help me improve it. Both are on by default and you can turn them off in Settings.

Anonymous usage events

These are sent through Aptabase, an open-source analytics provider that does not use cookies. Each event includes the app version, device model, operating system, language, and a random session identifier. The app never sends your location to Aptabase; Aptabase works out an approximate country and region from your IP address when an event arrives.

Show example events

app_opened Sent each time the app opens. Includes days since the previous open.
onboarding_completed Sent once when you finish the first-run setup screens.
walk_started Sent when you tap GO to begin a walk. Includes which walk number this is (e.g. your 3rd walk).
walk_completed Sent when a walk is saved. Includes duration in seconds, distance in metres, and walk number. No route or location data.
walk_abandoned Sent when a walk is discarded instead of saved. Includes how long the walk had been running.
walk_milestone Sent when you reach a walk count milestone (5, 10, 25, 50, or 100 walks).
walk_city_mismatch_shown Sent when you start a walk outside your selected city and the mismatch prompt appears.
walk_city_mismatch_resolved Sent when you make a choice on that prompt. Includes the action taken: switch city, stay, or dismissed.
city_search_started Sent when you initiate a city download. Does not include the city name.
osm_download_started Sent when street data download begins.
osm_download_completed Sent when street data downloads successfully.
osm_download_failed Sent when a download fails. Includes the error reason, no city name.
city_added Sent when a city is successfully added. No city name is included.
city_too_large_shown Sent when the "city too large" prompt is shown.
city_too_large_resolved Sent when you make a choice on that prompt (download a region or cancel).
radius_to_region_upgrade Sent when you complete a region download for a city you previously downloaded by GPS radius, confirming the upgrade.
gpx_imported Sent when a GPX file import finishes. No file name or route data is included.
share_tapped Sent when you tap the share button on a walk summary or the Stats screen.
review_requested Sent when the in-app review prompt is shown.
review_flow_completed Sent when the review prompt flow finishes (whether or not a review was left).
location_permission_result Sent when the location permission prompt is answered, records granted or denied.
notification_permission_result Sent when the notification permission prompt is answered, records granted or denied.

Crash reports

Crash reports are sent through Firebase Crashlytics and include a stack trace, device model, operating system version, app version, and an installation identifier. No location and no walk data. They're used to identify and fix bugs.

How to opt out

Both can be turned off independently at any time.

1

Open Settings in CityWalker.
2

Scroll to the Privacy section.
3

Toggle Send crash reports or Send anonymous usage stats off.

ℹ️

Both toggles are on by default after you complete setup. You can turn either off at any time and nothing is sent from that point forward.

For the full policy, see the Privacy Policy.