VitalRoute Support
Documentation
Everything you need to deploy the receiver, configure a destination, and sync:
- README — overview and build instructions
- Receiver deployment (server/)
- Receiver deployment guide
- The in-app setup guide (Destination screen) walks through the whole process.
Bug reports and feature requests
Please open an issue on the GitHub issue tracker. Include your iOS version, device model, and what you expected versus what happened. Never include real health data in a bug report.
Common questions
Where does my health data go?
Only to the HTTPS endpoint you configure. The developer operates no servers and receives nothing. See the privacy policy.
Why isn't background sync delivering instantly?
iOS schedules background work and throttles it; delivery is never guaranteed to be immediate, and it pauses entirely after a force-quit until you next open the app. Opening VitalRoute catches everything up right away. This is expected platform behavior, not a malfunction.
The connection test passes but sync fails
The test checks reachability, TLS, and your API key without sending records. If sync still fails, check that your receiver is reachable from outside your network (HTTPS with a certificate your device trusts) and review the receiver logs. The README's troubleshooting section covers common causes.
Can I use this without a server?
The app opens and navigates without a destination configured, but its purpose is routing health data, so there is nothing to see until you set up a receiver. The receiver is a single Docker Compose command on your own hardware.
Does VitalRoute work on iPad or Mac?
VitalRoute is an iPhone app. It is not distributed for iPad or Mac.