A lock screen is useful, but privacy is bigger than a lock screen. A private progress photo app should make its whole data path understandable: where a photo begins, where it is stored, when it can leave and what happens if the app is deleted.
Start with the data path
Ask whether photos are uploaded to a company server, synchronised through an account or kept in private device storage. The clearest privacy model is one you can describe in a sentence.
Body Log keeps its records in the app’s local container and does not include an account, analytics service or app-operated cloud backend.
Review permissions in context
Camera access should be used for captures you initiate. Photo-library access should be limited to media you deliberately choose to import. Biometric authentication should be handled by the operating system rather than exposing biometric information to the app.
- Why is each permission needed?
- Is access broad or user-selected?
- Does the app save a second copy to the Camera Roll?
- Can optional access remain off?
Look beyond the first unlock
Private content can reappear in the app switcher, screenshots or an unlocked session left in the background. Automatic locking and screen-capture protection help reduce those exposures.
No software can control someone photographing the physical screen, so privacy still includes how and where you use the device.
Understand backup trade-offs
Local-only storage reduces routine data sharing, but it also makes deletion and device loss important. A portable backup should be deliberate, verifiable and easy to restore.
If an exported backup is not encrypted, it needs the same care as the original photos. Privacy does not stop at the export button.
The takeaway
Privacy is a complete system: minimal permissions, understandable storage, secure access, honest backup guidance and no hidden upload path.
Body Log articles are general educational material about keeping a personal record. They are not medical advice or a substitute for professional care.