IRON.LOG

Privacy Policy

Effective date: September 4, 2026

This Privacy Policy explains how IRON.LOG Gym Workout Tracker ("IRON.LOG", "the app") handles information. IRON.LOG is developed by Veyaraki.

Privacy-first design: IRON.LOG is designed to work offline for workout tracking. Workout history, routines, sets, repetitions, weights, cardio data and statistics are stored locally on the user's device. The main exception is advertising provided by Google AdMob and external pages or email actions that the user deliberately opens.

1. Workout and Fitness Data

IRON.LOG may store information entered or generated by the user, including workout routines, exercise names, sets, repetitions, weights, rest information, workout dates and durations, cardio distance, duration and calories, custom exercises, notes, history and statistics.

This workout and fitness data is stored locally on the device using a local SQLite database. IRON.LOG does not require an account or login, and the developer does not operate a server that receives this workout database.

2. Local App Preferences

The app may store preferences and settings locally on the device so that the app can remember the user's configuration and continue to function correctly between sessions.

3. Backup, Export and Import

IRON.LOG provides user-initiated local data portability features. Users can export an IRON.LOG backup as a JSON file and import a compatible JSON backup. The app can also import supported CSV workout exports, including compatible Hevy and Strong exports.

File selection is performed through Android's system document picker. The app reads only the file that the user explicitly selects for import. These files are processed locally by IRON.LOG and are not uploaded by the app to the developer's server.

If a user separately chooses to move, share or store an exported file using another app or cloud service, that third-party service's own privacy practices apply.

4. Android System Backup

IRON.LOG allows Android's standard application backup mechanism. Depending on the user's Android device, Google account and backup settings, Android or Google may include eligible app data in a system backup. This is an operating-system service rather than an IRON.LOG cloud account or developer-operated backup service. Users can manage device backup settings through Android/Google settings.

5. Advertising

IRON.LOG uses the Google Mobile Ads SDK / Google AdMob to display advertisements. AdMob is the primary component of the app that communicates with an online advertising service during normal use.

According to Google's documentation for the Google Mobile Ads SDK, the SDK may automatically collect or share information such as the device's IP address, user interactions with the app or ads, diagnostic and performance information, and device or advertising identifiers for purposes including advertising, analytics and fraud prevention.

Advertising data is handled by Google under Google's own terms and privacy policies. Where required by applicable law, consent or other privacy controls may be presented for advertising.

6. External Actions Initiated by the User

IRON.LOG does not load remote exercise GIFs, remote exercise animations or external web fonts as part of normal workout tracking. The following external actions occur only after the user chooses them:

Once an external website, Google Play or an email provider is opened, that service's privacy practices apply.

7. Bug Reports and Contact

The Report a Bug function does not silently transmit a report. It opens an email composer. If the user chooses to send an email, the developer will receive the information that the user voluntarily includes in that message, such as the email address, message text and any attachments the user chooses to send.

Support messages may be retained for as long as reasonably necessary to respond to the request, troubleshoot the issue, maintain relevant records or comply with legal obligations.

8. Permissions and Device Access

IRON.LOG may use Android permissions or platform capabilities required for its features, including internet/network access for AdMob, vibration/haptics, wake/foreground functionality used during active workout-related operation, and Android's document/file mechanisms for user-initiated import and export.

The app does not require precise GPS location, camera, microphone, contacts or SMS access for normal workout tracking.

9. Data Retention and Deletion

Workout and app data stored locally remains on the device until it is deleted through app functionality, the app's storage is cleared, or the app is uninstalled, subject to any separate Android system backup that may exist.

Because the developer does not maintain an IRON.LOG account containing the user's workout database, the developer generally cannot access or remotely delete locally stored workout history.

10. Data Sharing and Sale

The developer does not sell the user's locally stored workout database. The app does not upload that database to a developer-operated cloud service. Third-party processing associated with AdMob, Android system backup, Google Play, the user's browser or the user's email provider is governed by the relevant third party and the user's settings.

11. Security

IRON.LOG minimizes remote handling of workout data by keeping core workout information on the device. No method of electronic storage or transmission can be guaranteed to be completely secure, and users should protect their device and any exported backup files appropriately.

12. Health and Medical Disclaimer

IRON.LOG is a workout logging and fitness tracking tool. It is not a medical device and does not provide medical diagnosis, treatment or professional medical advice. Users are responsible for deciding whether exercise is appropriate for them and should seek qualified professional advice when needed.

13. Children's Privacy

IRON.LOG is not directed to children under 13. The developer does not knowingly operate an IRON.LOG account system designed to collect personal information from children under 13.

14. Privacy Rights

Depending on the user's location, privacy laws such as the GDPR may provide rights relating to personal data. Most workout data handled by IRON.LOG is stored locally and is not held by the developer. For information voluntarily sent to the developer by email, users may contact the developer to make an applicable privacy request.

Requests concerning information processed independently by Google or another third-party service should also be directed to that service where appropriate.

15. Changes to This Privacy Policy

This Privacy Policy may be updated when IRON.LOG's features, third-party services or legal requirements change. The current version will be published at the Privacy Policy URL provided in the app and Google Play listing.

16. Contact

Developer: Veyaraki
Email: veyarakidev@gmail.com