Privacy

What stays on your device

Your workouts, sets, exercises, readiness check-ins and derived trends are stored locally on your iPhone. The app is fully usable with no account and no network connection, and in that configuration none of your training data leaves the device.

What is sent to a server, and only if you ask

Sync is optional and off unless a server address is configured. When it is enabled, your workout records are sent to that server so they can be restored on another device. That server is a small self-hostable service — if you run your own, your data never reaches us at all.

Voice logging sends the audio clip you recorded to the same server for transcription and parsing, and receives back a draft that you review before anything is saved. Clips are used for that request only.

Apple Health

LoadCurve requests read-only access to heart-rate variability, resting heart rate and sleep in order to estimate daily training readiness. It never writes to Health, and it does not request any category it does not use. Health data is read on demand, used to compute a readiness score on-device, and is not included in sync payloads.

You can decline Health access entirely; readiness then runs on your subjective check-in alone.

Accounts

The only sign-in method is Sign in with Apple, which lets you hide your email address. We store the identifier Apple issues and a session token. There is no password to lose.

What we do not do

No third-party analytics or advertising SDKs are embedded in the app. Your training data is not sold, shared with data brokers, or used to build cohort or leaderboard products. There is no social feed and no comparison against other users.

Deleting your data

Deleting the app removes the on-device database. If you enabled sync, you can delete the server-side copy from Settings, or — if you self-host — by removing the record from your own database.

Contact

Questions about any of this: hello@loadcurve.app.