Support
The things people ask first.
My hike stopped recording when the screen went off.
That is the background location permission. On iOS it is “Always”; on Android it is “Allow all the time”. Granting location only “While using the app” lets recording stop the moment you put the phone away. The app has a link straight to the right settings page.
There is no heart rate on my hike.
Heart rate comes from the watch, so it needs the watch app running the same hike and permission to read heart rate. A hike recorded on the phone alone has no heart-rate data — that is expected, not a fault.
How much battery does a hike use?
Continuous GPS is the dominant cost on any tracker, and a long hike is a heavy session on both phone and watch. Sampling drops automatically while a hike is paused. Per-device figures come from our battery test runs and will be published here before release.
The watch and phone disagree, or the hike did not sync.
Each metric has exactly one owner: the watch owns heart rate and calories, the phone owns distance, elevation and pace. If the two are briefly out of contact the watch queues what it recorded and sends it when they reconnect, so the hike reconciles into one record rather than two.
It paused my hike and asked if I was driving.
Vehicle detection is a heuristic. It pauses and asks rather than deciding, and it can never finish a hike on its own. If it guessed wrong, resume and the hike continues.
How do I get my data out, or delete it?
Any hike exports as GPX, and the whole history can be archived to a file. Deleting a hike deletes it from the device. There is no account and no server copy to also delete.
Still stuck?
A support contact address goes here before the beta opens. The app can also produce a diagnostics export — device, app version and permission states, with your hike data included only if you explicitly choose to attach it.