Privacy begins at capture
A private progress-photo workflow should not create a public-library copy and ask you to clean it up later. Photos taken in Body Log move directly into the app’s private container.
The smallest useful data path wins
No account, analytics service or app-operated cloud backend sits between you and the journal. Body Log stores the record locally unless you deliberately export it.
No AI gets an opinion
Body Log does not upload intimate photos for body-fat estimates, physique ratings, symmetry scores or generative coaching. The person keeps the interpretive role.
Earlier and later—not before and after
A permanent before-and-after pair implies a finished transformation and gives one image more value. Body Log lets any two dates answer the question you have now.
Every field is a choice
A photo-only check-in is complete. Weight, measurements, nutrition, cycle context, mood, energy and notes are available when useful and absent when they are not.
Distance can be a feature
Gentle mode can hide weight without deleting it. Past progress lock can make older records unavailable until you deliberately choose to review them.
No streak debt
A missed check-in does not produce failure, punishment or a backlog. The next useful entry is enough.
Local storage needs honest limits
Deleting the app can delete its local record. Portable backups need deliberate saving and safe storage. Privacy includes explaining those trade-offs before they matter.
The journal is not healthcare
Body Log records what you enter and helps you review it. It does not diagnose changes, estimate clinical measurements or prescribe actions. Health concerns belong with a qualified professional.