Dredfit does not collect any data. None. No account system, no analytics, no advertising, no third-party SDKs, 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 — the one exception being workouts already written to Apple Health, which stay in the Health app until you remove them there.
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.
You can export a complete backup to a plain JSON file at any time from Settings. The backup is the app's whole state — 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 Health is supplying it — a note a restored backup does not act on, because whether the number comes from Health is answered by this phone's Health and nothing else — and the Health-export bookkeeping). That file goes wherever you send it through the iOS share sheet — we never see it. You can also import such a backup back into the app: 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) and the date, rendered entirely on your device. Like the backup, it goes only where you send it through the share sheet, and nowhere otherwise.
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, 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 identifier that workout has in Dredfit's own history. 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 no longer write-only. Dredfit also asks to read six things, and reads them for one purpose: 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, and Dredfit reads those falling inside the minutes of the session it is about to write. Health data stays on your device under Apple's protection, and we never receive it.
Each of the six can be refused on its own. Refusing your weight means no calories are written at all; 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.
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.
We never receive your data, so there is nothing for us to share, sell, or process, and nothing is processed on any server. Dredfit contains no third-party SDKs, no analytics and no advertising, and makes no network requests of any kind.
The only party besides you your data can ever reach is Apple, and only through operating-system features you control: workouts you opt into writing to Apple Health, and app data included in a standard iCloud or local device backup. In both cases it is held under Apple's privacy terms, and 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 everything the app stores, and deleting the app is erasure — with the one exception noted above: workouts already written to Apple Health stay there until you remove them in the Health app. There is nothing to request from us, because there is nothing we could produce; questions are still welcome at the address below.
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