Dredfit does not collect any data. None. No account system, no analytics, no advertising, and no network requests of any kind.
Your entire training history — workout records, the variation and dose of every movement, and adjustments — is stored locally on your device. Dredfit has no servers and never transmits it. If you delete the app, this data is deleted with it, with two exceptions: workouts already written to Apple Health or Health Connect stay there until you remove them there, and a copy already in your phone's own backup (below) lives as long as that backup does.
On iPhone, standard iOS device backups (iCloud or local) may include the app's data as part of your device backup, under Apple's own privacy terms.
On Android, Dredfit takes part in Android's own app backup. If backup is turned on for your phone, Android copies the app's data — your history and settings, body weight included — to your Google account about once a day, and restores it whenever Dredfit is installed again on a phone signed in to that account: after a reinstall, or on a new phone. Google keeps that copy in your account's backup — on Android 9 and later, when the phone has a screen lock, end-to-end encrypted with its PIN, pattern or password — under Google's privacy policy; we cannot read it. You can turn backup off in your phone's settings.
You can export a complete backup to a plain JSON file at any time from Settings. The backup holds your training history together with your settings (among them rest days, reminder time, sounds, the pull-up-bar switch, your body weight together with the note that Apple Health or Health Connect is supplying it — a note a restored backup does not act on, because whether the number comes from there is answered by this phone's own health store and nothing else — and the bookkeeping of which workouts have been written there). That file goes wherever you send it — through the share sheet on iPhone, through the system's save dialog to a place you pick on Android — and we never see it. You can also import such a backup back into the app, on either platform: importing only reads the file you picked and transmits nothing.
After a milestone — and from the Progress tab — Dredfit offers a share card: a small image with your workout count and total steps (or the milestone itself), your progress curve and the date — and on a round-number milestone (the 10th, 25th and every 50th workout), “Then … — Now …” with how long ago you started — rendered entirely on your device. Like the backup, it goes only where you send it through the share sheet, and nowhere otherwise.
Dredfit sends nothing over a network, so there is no transmission to protect. On the phone, its data sits in the app's private storage, which iOS and Android keep from other apps; Apple Health and Health Connect give it only what you allow, and only while you allow it.
Dredfit can write finished workouts to Apple Health, and reads a short, named list of values back so that each workout can carry an estimate of what it cost. All of it is off by default and starts only after you turn it on in Settings and grant permission.
When it is on, each completed workout is written as a single Functional Strength Training entry containing its start time, end time and duration and the identifier that workout has in Dredfit's own history (its number in that history and the moment it ended), plus the standard device record iOS attaches to any Health entry (device model and OS version). Where it can be worked out, the entry also carries an estimated active-energy figure, labelled with the revision of the estimate that produced it and with the same identifier. No heart rate, no body measurements, no exercise details. The estimate is left out rather than guessed — among other cases when there is no weight to scale it by, when nothing was actually performed, or when another app recorded the same session.
The permission is not write-only. Dredfit also asks to read six things, and reads them to work that estimate out on your phone. Your weight is the value the whole figure scales by; your height, date of birth and sex refine only the resting share that is subtracted from it; the resting energy your device has already recorded covers those same minutes; and your workouts are read so that a session another app recorded at the same time is not counted twice. That last permission is not a narrow one: Health grants access to workouts as a whole. For that check Dredfit reads those that overlap the span from the start of the oldest workout it has yet to write to the moment it writes — usually just the minutes of the session you have finished, but on a first export of past workouts, every workout since the oldest of them. Workouts are also read for a second reason: before writing one, Dredfit looks for an entry it wrote itself under the same identifier, whatever its date, so that a workout already in Health is not written a second time. That lookup is limited to Dredfit's own entries. What Dredfit reads from Health is used on your phone, and we never receive it; the one value it keeps — your weight, with the date Health recorded it — is stored with the app's own data, so it is part of any backup you export.
Each of the six can be refused on its own. Refusing your weight means no calories are written unless the app already holds one — typed in by you, restored from a backup, or kept from an earlier read, which a later refusal does not erase; you can clear it in Settings. Refusing your height, date of birth or sex only makes the estimate rougher. Refusing your workouts is different: Health never tells an app whether a read was allowed, so Dredfit cannot tell nothing found from not permitted, and the check against double counting stops working without saying so. That is why Settings carries a switch named for what it does — Leave calories out — and its caption names both reasons to want it: an Apple Watch already records the same workouts, so the session would otherwise count twice, or you simply want no estimate written.
You can revoke access any time in Settings → Health → Data Access & Devices → Dredfit, or turn the switch off inside the app. Workouts already written stay in Health until you delete them there.
On Android, Dredfit can write finished workouts to Health Connect, Android's store for health and fitness data on your phone, and reads a short, named list of values back so that each workout can carry an estimate of what it cost — the job Apple Health does on iPhone. All of it is off by default and starts only after you turn on Save workouts to Health Connect in Settings and allow it on Health Connect's own permission screen. Health Connect is part of Android from version 14; on Android 10 to 13 it is Google's Health Connect app, which Settings offers to install.
Dredfit asks for five permissions, and each can be refused on its own. Two are to write. Exercise: each completed workout is written as one calisthenics exercise session containing its start and end time (with the time-zone offset of each), the identifier that workout has in Dredfit's own history (its number in that history and the moment it ended), and the device it was recorded on (a phone, its maker and model). Active calories burned: where it can be worked out, an estimated active-energy figure over the same minutes, labelled with the revision of the estimate that produced it and with the same identifier; refuse this one and the workout is written without it. No heart rate, no body measurements, no exercise details. The estimate is left out rather than guessed — among other cases when there is no weight to scale it by, when nothing was actually performed, or when another app recorded the same session. A workout written again under the same identifier replaces the one already there, so it is never in Health Connect twice.
Three are to read, and they are read only to work that estimate out on your phone. Weight: your newest weight is the value the whole figure scales by. Basal metabolic rate: the resting energy of the workout's own minutes is subtracted from it — read only where a resting rate has actually been recorded, never a figure Health Connect fills in by itself. Exercise: other apps' exercise sessions, so that a session another app recorded at the same time is not counted twice. For that check Dredfit reads the sessions that began between a day before the oldest workout it has yet to write and the moment it writes — usually just the last day or so, but on a first export of past workouts, every session since the day before the oldest of them — and uses only which app wrote each one and when it ran. Height, date of birth and sex are not read on Android. Health Connect lets an app read other apps' entries from no earlier than 30 days before it was first granted a permission, and Dredfit does not ask for more.
What Dredfit reads from Health Connect is used on your phone, and we never receive it; the one value it keeps — your weight, with the date Health Connect recorded it — is stored with the app's own data, so it is part of any backup you export and of your phone's own backup. Refusing your weight means no calories are written unless the app already holds one — typed in by you, restored from a backup, or kept from an earlier read, which a later refusal does not erase; you can clear it in Settings. Refusing basal metabolic rate only makes the estimate rougher. Refusing exercise means Dredfit cannot see another app's recording of the same session, so if a watch or another app already records your workouts, turn on Leave calories out in Settings — the same switch is there if you simply want no estimate written.
You can withdraw any of these permissions at any time in Health Connect — in your phone's settings on Android 14 and later, in the Health Connect app on Android 10 to 13 — or turn the switch off inside the app. Workouts already written stay in Health Connect until you delete them there; Health Connect can delete everything one app wrote. Other apps you allow to read from Health Connect can see the workouts Dredfit wrote, under their own policies. Google describes Health Connect as a database stored on your device.
If you enable the reminder, Dredfit schedules a local notification on your training days. It is generated and delivered on your device — there is no push server and nothing is transmitted. Turning the reminder on asks for permission to show notifications. Android forgets scheduled alarms when the phone restarts, so on Android Dredfit is told when the phone starts up, its clock or time zone changes, or the app is updated, and sets them again.
During a workout on Android, Dredfit shows an ongoing notification — the exercise or what the rest leads into, the set, and the countdown — in the notification shade and on the lock screen, as the Live Activity does on iPhone. It is carried by a foreground service of the type Android sets aside for fitness apps (“health”), which keeps the countdown and its 3-2-1 going while the screen is off or another app is in front — at zero it waits for you to come back — and it ends when the workout does. On Android 13 and later, the first workout that shows it asks for permission to show notifications, unless the reminder already has; refusing hides the notification and changes nothing else. That service type requires one of a short list of permissions: Dredfit holds the one Android grants without asking, “high sampling rate sensors”, for that reason only, and reads no sensor.
We never receive the app's data, so there is nothing for us to share, sell, or process, and nothing is processed on any server. Dredfit contains no analytics and no advertising, and makes no network requests of any kind; the Android app does not even hold Android's permission to use the internet.
The iPhone app contains no third-party SDKs. The Android app is built on the platform's standard libraries — Google's AndroidX, the Health Connect client among them, and JetBrains' Kotlin libraries — and carries exactly one SDK beyond them: Google's Play In-App Review (which brings two Google Play services libraries with it), used only for the rating card described next.
After some milestones, Dredfit may ask your phone's store to show its rating card — the App Store's on iPhone, Google Play's on Android. The card is shown and sent by the store, not by Dredfit: Dredfit never learns whether it appeared, what you rated or what you wrote. What you submit goes to Apple or Google under their own terms; Google states that the rating and review are used to post your review on Google Play or, for a version of the app in a closed test, shared privately with the developer. So a review is the one thing you write that can reach us: in public, as anyone can read it, or privately from a closed test.
Besides you and the apps you yourself allow to read from Apple Health or Health Connect, the only parties your data can ever reach are Apple and Google, and only through operating-system features you control. On iPhone: workouts you opt into writing to Apple Health, and app data included in a standard iCloud or local device backup, held under Apple's privacy terms. On Android: app data included in your phone's backup to your Google account, held under Google's privacy policy. In every case, we never see it.
We retain nothing, so there is no retention period on our side: your data lives on your device until you delete the app, and we never hold a copy. Privacy laws such as the GDPR and CCPA give you rights of access, deletion, and portability — with Dredfit you exercise all of them directly on the device: the JSON export is your complete portable copy of your history and settings, and deleting the app is erasure, with the exceptions noted above — workouts already written to Apple Health or Health Connect stay there until you remove them there, and a copy in your phone's own backup lives as long as that backup does. There is nothing to request from us, because there is nothing we could produce; questions are still welcome at the address below.
On Android, erasing everything takes three places: Dredfit itself (uninstall it, or clear its storage in your phone's settings), Health Connect (delete the data Dredfit wrote there), and your phone's backup in your Google account, which keeps a copy while backup is on and restores it whenever Dredfit is installed again — you manage it in your Google account.
Dredfit is a general-fitness tool for a general audience and does not knowingly collect data from anyone, including children — because it does not collect data at all.
If this policy ever changes, the effective date above changes with it and the updated version is published on this page.
Dredfit is developed and published by Dmitry Novikov, an independent developer, who is the responsible party for this policy.
Questions about this policy: dredfort.42@gmail.com