Keep backup filenames meaningful

Know the data boundary

A meaningful filename helps you choose the right dataset before an import replaces local records. The default export name includes a date, which is a useful starting point.

Use the supported file workflow

Retain the .json extension and include a clear date or short purpose if you rename the file. Avoid names that expose unnecessary personal details in a shared folder listing.

There is no account or automatic custom-server backup in this release. The privacy text also states that the app's private local storage is excluded from automatic cloud device backups; exported files are your separately chosen copies.

Check the copy you actually have

If you make several exports on one day, add a simple version cue such as before-edit or after-transfer. Keep the wording consistent enough that you can distinguish the copies later.

Manage each retained copy

A filename is a clue, not proof of contents. Check the context and known export time before restoring a file, especially when several devices have independent ledgers.

Erasing local data does not delete files you previously exported. Reinstalling or changing devices can remove access to local records, so verify a saved backup before those actions if you want the ledger to remain recoverable.

A worked walkthrough

Imagine a folder with three files all renamed to a vague variation of final. One came from the old phone, one predates an important correction, and one contains today's ledger. Without clear names, choosing among them before replacement becomes unnecessarily risky. A date plus a brief version cue can distinguish those complete states without embedding private journal details in the filename. Retain the .json extension so the file remains recognizable in the picker. If you have independent datasets on two devices, include a simple source cue as well, but remember that names do not merge their contents. Before restoring, connect the chosen file to what you know was present at export time. Naming is a navigation aid, not validation of the actual data. A useful name reduces guesswork while the app's format checks establish a different kind of validity.