LiftJot
English

Data guide

Data, backups and exports

LiftJot keeps no developer-server copy of your log. Depending on your platform, your settings, and your installed version, Apple or Google may transport a recovery copy the app prepared, but that process is best effort and outside our control. Creating a backup yourself remains the way to hold a portable copy of your own.

Use a .workoutlog file to restore. CSV is a readable export of performed sets, not a LiftJot restore file. LiftJot adds no encryption of its own to either one.

Create a portable backup

  1. Open the app’s data controls and choose to create a backup.
  2. LiftJot prepares and checks a .workoutlog file in its own storage area.
  3. Use the operating-system share sheet to save or send a copy to a destination you trust and expect to keep.
  4. Confirm that the copy actually arrived before relying on it.

The backup contains the portable LiftJot record: workout history, day notes, exercises, categories, and the settings needed to restore. It leaves out timer state and other device or runtime state.

The most recent backup stays in the app’s storage area. LiftJot makes a best-effort attempt to remove older ones it created, so earlier files may remain. There is no in-app screen that lists or deletes them.

What an operating-system backup can do

Depending on your platform, your settings, and your installed version, LiftJot may prepare a limited rotating set of recovery copies and mark them as eligible for operating-system-managed device backup or transfer. A recovery copy holds the same portable record as a backup you make yourself. The app's working data—its live storage, timer state, diagnostics, temporary files, and the safety copies described below—stays outside that eligibility.

Apple or Google controls whether transport happens. The operating system may never carry a recovery copy, LiftJot cannot confirm whether it did, and any copy may be out of date. A message in the app saying a recovery copy was prepared means only that a local eligible file was created and checked—not that it is backed up, safe, or recoverable. Treat it as a fallback, never as a substitute for a backup you made yourself.

Restore a backup

  1. Open the app’s data controls and choose to restore.
  2. Select a LiftJot .workoutlog file.
  3. Review the preview and confirm only if it is the record you intend to use.

LiftJot checks and previews the file first. Before a restore changes your current training record, it prepares and checks a safety copy of what you have now, then commits the restore as a single step. Restoring replaces your current record with the file’s contents. If validation or writing fails, your current record is left unchanged; a safety copy that was already prepared may remain.

Move between devices

Create the backup on the old device, complete and confirm a save through a route you trust, then restore that copy on the new device. The same .workoutlog format is designed to work across LiftJot on supported iPhone, iPad, and Android devices.

Export CSV

Exporting CSV from the app’s data controls prepares a new file in the app’s storage area and then opens the operating-system share sheet. It holds one row per performed set, with the date, exercise and category, weight and reps, distance and time, their units, and any day note. Targets you have not performed yet are not included.

Use CSV for a spreadsheet, a coach, personal analysis, or another tool. It does not carry the complete app structure, and LiftJot cannot restore from it. CSV files are not pruned automatically and can accumulate.

Retention and deletion limits

On iOS, the backups and CSV exports you created remain eligible for Apple-managed device backup; on Android, the app's own backup rules cover only the recovery copies described above. The safety copies LiftJot prepares around restore and import are configured to be excluded on both. Clearing your workout history removes the local recovery copies along with your history, but it does not delete backups, CSV exports, safety copies, or any copy saved elsewhere. It cannot retract anything Apple or Google has already transported.

Directly after a successful restore, the app offers to delete the safety copy from that operation. Otherwise LiftJot provides no in-app list or deletion control for the files in its storage area, so a safety copy kept after a failed restore or a failed clean-up may remain. Delete copies saved outside LiftJot separately at every destination, where that destination’s own privacy, security, backup, and retention terms apply.

Store files safely