Support & Contact

Yes. iPhone alone, Apple Watch alone, and both together are all supported. A run started on the watch is handled entirely by the watch, and the record is sent to the iPhone's logbook once it ends. Starting from the iPhone wakes the watch app automatically; from there the iPhone handles GPS and calculations while the watch measures heart rate and shows the display.

If the device tracking GPS shuts down, that run stops. When it ends normally, everything up to that point stays in the logbook. However, force-quitting the iPhone app during a run started on the iPhone can leave the watch display frozen on its last values, and that run may not reach the logbook. It is still saved to the Health app in that case. This is a known limitation we are working on.

By default every run is stored only on your device, through Apple's SwiftData. Tapping the backup button in Settings saves them to your own iCloud; this never happens automatically. Runs are also saved to Apple's Health app.

Records stored on the device are deleted with it. If you backed up from Settings beforehand, you can reinstall, sign in with the same Apple Account, and tap restore to bring them back. Backup is not automatic, so it has to be tapped before deleting. Workouts saved to the Health app remain regardless.

There are no third-party analytics or advertising SDKs, and no third party including the developer can access your data. Only three things leave the device: your current location, sent to Apple's WeatherKit to show weather on the pre-flight screen; your records going to your own iCloud when you tap the backup button; and a once-a-day check for a newer version on the App Store. All three are handled by Apple and none is accessible to the developer. The update check sends only the app identifier and a country code, never your running data. The privacy policy page covers this in detail.

Alerts are based on the target and tolerance you set in Mission Flight mode. The target can be either pace or heart rate, so check which one is selected along with the tolerance value. A narrower tolerance means more frequent alerts. If it still looks wrong, let us know through the form below.

The app raises it when nothing has arrived from the Apple Watch for more than fifteen seconds. It usually means the run was ended on the watch but that signal never reached the app. Choosing to end the run keeps everything recorded up to that point, and choosing to keep running carries on as before. If watch data starts arriving again the alert clears by itself. It can also appear when the connection drops briefly mid-run, in which case you can dismiss it and keep going.