Training Diary
Privacy Policy
In short: Training Diary collects nothing. It has no user accounts, no advertising, no analytics, and no network code of any kind. Everything you record stays in the app's private storage on your device and is never sent over a network. It deliberately leaves in two ways: a backup file, if and when you choose to export one yourself (section 6), and the name of the exercise you are timing, which a timer alert shows when one fires (section 4). Section 6 also covers device-to-device transfer to a new handset, which Android and your phone's manufacturer decide rather than this app.
1. Who this policy is from
Training Diary is developed and published by Thierry Vandamme ("we", "the developer"). This policy explains what the app does — and does not do — with information, and applies to the Android version distributed through Google Play.
2. Data we collect
We collect no personal data. The app does not ask for your name, email address, phone number, date of birth, gender, body measurements, health identifiers, contacts, photos, or location. There is no registration, no sign-in, and no user profile.
The app contains no advertising SDK, no analytics SDK, no crash-reporting SDK, and no HTTP client. It does not open network connections, so nothing is sent over a network. Your data deliberately leaves the app in two ways: the backup file you choose to export yourself, and the exercise name a timer alert shows when one fires (see section 4); section 6 also covers device-to-device transfer, which Android and your phone's manufacturer decide rather than this app.
3. Data the app stores on your device
The training information you enter is saved locally so the app can show it back to you. It is stored in a private SQLite database and a small preferences file inside the app's own sandboxed storage directory, which other apps on your device cannot read.
| What is stored | Why |
|---|---|
| Training sessions — date, optional session name, and a link to the session it was duplicated from | To list and reopen your past workouts, and to show what you did last time |
| Exercises you create — name, optional target area, optional default rest time, and their order and duration within a session | To build and replay your routines |
| Sets — repetition count, weight in kilograms, elastic band used, whether the set is counted in repetitions or timed, warm-up and cool-down flags, and whether its timer has been played | To record and review your performance |
| Elastic bands — colour and number | To let you log resistance-band work |
| Sound preference — the alert volume for the rest timer | To remember your chosen timer volume |
| Whether you have already been shown the explanation about precise alarms | So the app asks once instead of on every timer |
This content is created entirely by you. It is never uploaded to a server and is not accessible to the developer. It leaves this private storage when you export it yourself, or when your phone carries out its own device-to-device transfer to a new handset — section 6 covers both. The name of the exercise you are timing also appears in a timer alert when one fires (see section 4).
4. Permissions the app requests
Notifications (POST_NOTIFICATIONS) — used solely to alert you when a rest timer finishes. The alert names the exercise you were timing, so, like any other notification, it can be visible on your lock screen and to any app you have granted notification access. Notifications are generated on the device; nothing is sent to or received from a server.
Exact alarms (SCHEDULE_EXACT_ALARM) — used solely so the rest timer fires at the exact moment it should, even when the screen is off or the app is in the background.
The app requests no other permissions, beyond one signature-level permission an Android support library declares for its own internal use, which is invisible to you and grants nothing to any other app. It has no access to the internet, camera, microphone, location, contacts, or health and fitness platforms, and no general access to your files — only the single file you pick yourself in your device's file picker when you export or restore a backup (see section 6).
5. Sharing and third parties
We do not sell, rent, share, or disclose your data — because we never receive it in the first place. There are no third-party services, SDKs, processors, or partners integrated into the app.
Google Play
The app is distributed through Google Play. Google independently collects certain information when you download, install, or update an app — for example device and installation data, and, if you have enabled automatic sharing of diagnostics on your device, crash reports. That collection is performed by Google, not by the app, and is governed by Google's Privacy Policy. Any statistics we can see in the Google Play Console are aggregated and anonymised, and we cannot use them to identify you or to view your training data.
6. Backups, export and import
Automatic Android backup is explicitly disabled for this app (android:allowBackup="false"), and the app configures no cloud backup of its own. It does not copy your training data to Google Drive, and it sends it nowhere. What a given phone does during a direct device-to-device transfer when you set up a new handset is decided by Android and by your phone's manufacturer rather than by this app, so we do not claim to control it. Please also be aware that with automatic backup disabled, uninstalling the app permanently deletes your training history.
Instead, the app gives you a manual backup you control yourself, under Settings → Export data. Exporting writes your sessions, exercises, sets and elastic bands to a single JSON file, and your device's own file picker asks you where to put it. The file is written directly to the location you choose; the app sends it nowhere and keeps no copy of it.
Two consequences are worth being explicit about:
- An exported file is outside the app's sandbox. If you save it to a cloud folder, email it to yourself, or hand it to another app, your training data goes wherever you sent it, and this policy no longer governs it — the receiving service's does.
- The file is ordinary, unencrypted JSON, readable by anyone who obtains it. Store it somewhere you consider private.
Settings → Restore backup is the reverse: you pick a previously exported file, the app shows you what it contains and asks you to confirm, then replaces everything currently in the app with it. Nothing is read from your device other than the single file you select.
7. Retention and deleting your data
Because all data stays on your device, you are in full control of how long it is kept. There is no server-side copy for us to retain or for you to request the deletion of.
- Delete individual sessions, exercises, sets, or elastic bands from within the app.
- Erase everything at once via Settings → Apps → Training Diary → Storage → Clear storage on your device.
- Uninstalling the app removes the database and all preferences.
- Files you exported yourself are not covered by any of the above — they live wherever you saved them and only you can delete them.
These actions are irreversible; make sure you no longer need the data before proceeding.
8. Security
Your data is held in the app's private storage area, isolated by the Android application sandbox so that other installed apps cannot read it. On devices with a screen lock, it also benefits from Android's device-level file encryption. The app opens no network connections, so there is no transport to intercept. Anyone with unlocked physical access to your device can, however, open the app and see your training history — so keep a device lock enabled.
9. Children
Training Diary is a general-audience fitness log. It knowingly collects no personal information from anyone, including children under 13 (or the equivalent minimum age in your jurisdiction).
10. Your rights
Privacy laws such as the GDPR and the CCPA grant rights to access, correct, export, or delete personal data held by a company. As we hold no personal data about you on any system we control, there is nothing for us to look up, correct, or erase on your behalf — you exercise the equivalent control directly, on your device, as described in section 7.
11. Changes to this policy
If a future version of the app changes how information is handled, this policy will be updated and the "Last updated" date at the top revised before that version ships. Material changes will also be noted in the Google Play release notes.
12. Contact
Questions about this policy or about privacy in the app can be sent to:
Email: thierry.vandamme@pm.me