Skip to content

PRIVACY-POLICY.md

Latest commit

 

History

History
131 lines (82 loc) · 3.56 KB

PRIVACY-POLICY.md

File metadata and controls

131 lines (82 loc) · 3.56 KB

IRONLOG Privacy Policy

Last updated: 2026-04-11

This Privacy Policy explains how IRONLOG handles information in the Android app and related project materials.

1. Summary

IRONLOG is designed to be local-first.

By default, workout logs and related training data are stored locally on your device. Some optional features, such as backups, notifications, progress photos, and Google Drive backup targets, may process additional data as described below.

2. Data IRONLOG may process

Depending on how you use the app, IRONLOG may process:

  • workout history
  • exercise logs
  • bodyweight entries
  • body measurements
  • progress photos
  • plan and program data
  • backup metadata
  • notification settings
  • recovery inputs
  • locally generated analytics and milestones

3. Local storage

Most training data is stored locally on the device using local app storage and SQLite.

This may include:

  • workouts
  • plans
  • progress metrics
  • recovery-related inputs
  • custom exercises
  • local backup metadata

4. Optional backups and exports

IRONLOG supports optional backup and export features.

These may include:

  • encrypted local backup files
  • SQLite exports
  • CSV exports
  • JSON or interoperability exports
  • optional Google Drive backup targets if enabled by the user

If you choose to export or back up data, the exported data is processed according to the destination you choose.

5. Google Drive backup

If you connect Google Drive, IRONLOG may upload encrypted backup files to the Google Drive location you authorize.

This may include:

  • hidden AppData storage
  • a visible Drive folder selected or created for backups

IRONLOG does not claim ownership of your Google account data. Access is used only for the backup feature you explicitly enable.

6. Notifications

If you enable notifications, IRONLOG may use local device data such as workout history, streak state, bodyweight logging activity, and notification settings to schedule reminders and other local notifications.

7. Progress photos

If you use progress photos, IRONLOG may access:

  • camera input
  • photos selected from your gallery

Photos are stored locally unless you export them or include them in a backup flow that you explicitly choose.

8. Analytics and tracking

IRONLOG is intended to work without mandatory third-party analytics.

If future versions add external analytics, crash reporting, payments, or backend services, this policy should be updated to reflect that change before wider release.

9. Sharing

IRONLOG does not sell personal data.

Data may be shared only when:

  • you export it
  • you back it up to a destination you selected
  • you choose a platform share action
  • disclosure is required by law

10. Security

IRONLOG uses practical safeguards such as:

  • local-first storage
  • encrypted backup flows where configured
  • release signing
  • defensive app-hardening measures as the product matures

No method of storage or transmission is perfectly secure, and absolute security cannot be guaranteed.

11. Your choices

You can choose whether to:

  • enable notifications
  • connect Google Drive backup
  • export data
  • import data
  • use progress photos
  • configure backup passphrases

12. Children's privacy

IRONLOG is not intended for children under the age required by applicable law to use such an app without consent.

13. Changes

This policy may be updated as the app evolves, especially if cloud features, payments, analytics, or other external services are added.

14. Contact

For privacy-related questions: