ForgeLog — Privacy Policy
Last updated: 11 September 2026
ForgeLog is a gym training log that runs entirely on your phone. This policy explains what it does
with your information. The short version: it keeps everything on your device and sends nothing
anywhere.
What ForgeLog collects
Nothing is collected. ForgeLog has no accounts, no sign-in, no servers, and no analytics. It
does not build a profile of you, does not measure how you use it, and does not contain advertising
or any advertising identifier.
The app has no INTERNET permission. It is not able to make a network connection at all, whatever
it might otherwise have wanted to do with one.
What ForgeLog stores, and where
Everything you enter is written to a database in the app’s own private storage on your phone, which
no other app can read. That is:
- Your programs, training days, and the exercises and targets in them
- Your exercise library, including any notes, pointers and how-to links you add
- Your logged workouts: every set, its reps, weight, duration, distance, rest, RPE, RIR and notes
- How a session or an exercise felt, and any notes you wrote about it
- Your settings: units, default rest, which day your week starts on, and the rest-timer alerts
ForgeLog does not ask for, and has no way to read, your name, email address, phone number, contacts,
location, photos, health-platform data, or any device or advertising identifier.
When data leaves your phone
Only when you choose to send it, in one of these three ways:
- You export it. Settings offers a JSON backup and a CSV export. Both open your phone’s own
file picker so that you choose where the file goes. Once written, that file is outside ForgeLog’s
control and is governed by wherever you put it — a folder on the phone, a cloud drive, whatever
you picked.
- You open a how-to link. If you add a link to an exercise and tap it, ForgeLog hands that web
address to your browser. From that point your browser’s privacy policy applies, not this one.
ForgeLog does not fetch the page itself.
- You move to a new phone. Android’s direct device-to-device transfer is allowed to carry your
training history to your new phone, so you do not lose it when you upgrade. This goes straight
from one device to the other.
ForgeLog is explicitly excluded from Android’s cloud backup, so your training data is never
copied to Google’s servers by the operating system’s automatic backup.
Permissions, and what each is for
- Foreground service and special use foreground service — keeps the workout you are
currently logging alive with a notification while you are in another app or have the screen off,
so its clock keeps running and you can get back to it.
- Notifications — shows that ongoing workout notification, with the session time and the rest
countdown. If you decline it, the app still works; you just do not see the notification.
- Vibrate — buzzes when a rest period ends, if you have that switched on in Settings.
- Wake lock — keeps the phone’s processor awake for the length of a rest period, so the
countdown reaches zero on time while the screen is off. It is released the moment the rest ends.
None of these can read anything about you.
Deleting your data
- Settings → Delete all data removes every program, exercise and logged workout from the device.
It asks you to type a word first, because it cannot be undone.
- Uninstalling ForgeLog deletes its database and settings with it.
There is nothing held anywhere else, so there is nothing to ask us to delete and no account to close.
Children
ForgeLog is a general-purpose fitness tool and is not directed at children. It collects no data from
anyone, of any age.
Changes to this policy
If the app ever changes in a way that affects this policy, this page will be updated and the date at
the top changed with it. Because ForgeLog does not collect anything, there is no history of past
data handling to disclose.
Questions about this policy: [your contact email]
ForgeLog on GitHub