Privacy
Your hikes describe where you go and when. That is why they stay on your device.
What the app stores, and where
Routes, elevation, heart rate and summaries are written to a database on your phone. Recording needs no account and no connection — the whole recording path works offline, and that is enforced in our build, not just intended.
What leaves your device
Weather and air-quality lookups send an approximate location to the provider so it can answer. Map tiles are fetched as you pan. Nothing else about a hike is transmitted to run the app: there is no account, no sync service, and no profile.
Permissions, and why each one
Location, including in the background. Without it, recording stops when the screen does — this is the permission the app cannot work without.
Heart rate and health data. Only if you want effort metrics, and only written back to your platform's health store with your consent.
Notifications. Optional, used to tell you the recording state changed.
Getting your data out, and getting rid of it
Any hike can be exported as GPX, and the full history can be archived to a file you keep. Deleting a hike deletes it. Uninstalling the app removes the database with it.
This website
This site is static and currently sets no cookies and runs no analytics. If that changes, non-essential cookies and scripts will be gated behind consent where required, on a property with no connection to anything the app records. The site never receives your hikes, health data or location.
This page describes intended behaviour during development. The binding privacy policy ships with the app at release — see Legal. SummitPulse is a working name.