Track
Privacy
Updated 22 October 2026. This describes the early Track beta.
On your iPhone
You choose which Apple Health categories Track may read. The app stores its local Record in an encrypted database, with its key in the iPhone Keychain. The current app does not write to Apple Health. Camera access is used to scan a pairing code.
Servers and assistants
A fresh install does not connect to a Track-operated data service. You can explicitly pair a runtime or connect an optional Health server. That server receives the data needed for the connection you enable. Pairing a runtime and granting assistant access are separate decisions.
Track supports encrypted Record sync between paired devices. A runtime that is allowed to process your data can read that data. Storage protection depends on the domain and deployment; the current Finance runtime uses a local SQLite database protected by filesystem permissions and relies on device encryption.
Your choices
You can change Health permissions in iOS Settings and manage connections in Track. Disconnecting a server does not delete records already held by that server. Review the app’s removal options and the server’s storage separately.
Beta feedback and this website
TestFlight distribution and its diagnostic reporting are handled by Apple. If you send feedback, include only the details you want to share. This website is hosted by Cloudflare and has no additional analytics script or sign-up form.
Questions
Contact Velislav about privacy, deletion, or a suspected security issue. Track remains in active development and has not received an independent security audit.