Privacy policy
IronLedger logs your training on your device and does not require an account. We do not sell data, we do not run advertising, and there is no paid tier, so there is nothing we gain from knowing more about you than the app needs to work.
If you sign in, your training record also syncs to our database, where we can read it. Health data moves only when you switch a connection on. You can export your history to CSV, or everything as a JSON backup, at any time, and delete it from this page when you want it gone.
What this policy covers
This policy applies to the IronLedger mobile app on iOS and Android, and to this website. It describes what data exists, where it lives, and who can reach it. It does not cover the separate privacy practices of Apple or Google, each of which governs its own platform.
Data stored on your device
Your training record is written locally first. Sessions, sets, loads, reps, RPE and RIR values, notes, programs and personal records are all stored on the device you logged them on. No account is required to log training, and if you never sign in, the local copy is the only copy.
- •Logging works fully without an account, and nothing is synced while you are signed out
- •Uninstalling the app removes local data on most platforms, so export first if you want to keep it
Data on our servers
If you create an account and sign in, IronLedger syncs your training record so it survives a lost phone and reaches your other devices. That copy is stored in our database and is readable by us, which is the honest position: it is not end-to-end encrypted, and we could be compelled to produce it. It is protected by row-level security so that no other user can read it, and it is transmitted over TLS.
- •Workout sessions, including every logged set, load, rep, RPE and RIR value
- •Programs, custom exercises and personal records
- •Your account email address and display name
- •Nothing syncs until you sign in, and signing out stops it
Health permissions
Health data is read or written only after you enable a connection and the operating system grants the permission. IronLedger writes completed strength workouts to Apple Health and reads body weight so calorie estimates use a current number.
- •Permissions are requested when you turn a connection on, never at first launch
- •A workout written to Apple Health has to be deleted in Apple Health, because IronLedger does not remove a record once it has written it there
- •Revoking a permission stops the sync immediately and does not affect your local log
Third-party connections
Strava, Oura and Health Connect appear in the app as coming soon. None of them can be connected yet, so IronLedger sends no data to them and receives none from them.
Analytics and crash reports
The app carries no advertising and no advertising SDKs, and nothing here is sold or shared for marketing. It does use two third-party services, named here rather than described vaguely.
PostHog records product analytics: which screens are opened and which actions are taken. When you are signed in, your account identifier is attached to those events, so this is not anonymous.
Sentry records crashes and performance. A crash report includes the view hierarchy, which records the layout of the screen at the moment it failed. Since version 1.10.0 it does not include a screenshot.
Your rights and choices
You can export your history to CSV, or everything as a JSON backup, at any time, delete your local data from your device, delete your account and the synced copy that belongs to it, and revoke any health permission from your phone’s settings. Most of these do not require contacting us at all.
Changes to this policy
Material changes will be reflected in the last-updated date at the top of this page. A change that expands what data is collected will be announced before it takes effect, not after. Questions go to support@ironledger.app.