A Face ID badge does not explain an app’s entire data path. Before storing intimate progress photos, look at how the app captures, moves, processes, displays, backs up and deletes them.
Capture and copies
Ask whether a photo is saved to the general library, copied into the app or captured directly into private app storage. If you import an existing image, find out whether the original remains where it was.
Fewer unnecessary copies usually means fewer places to manage.
- Does capture create a Camera Roll copy?
- Is photo-library access broad or user-selected?
- Can imported originals be identified and removed separately?
Accounts, cloud and AI
Find out whether the core app requires an account, whether photos are uploaded for sync and whether any analysis sends them to another provider. ‘Processed securely’ is not the same statement as ‘never transmitted’.
- Can the app work without signing in?
- Who operates every server that receives a photo?
- Are images used for AI analysis or model training?
- Can cloud features remain fully off?
Access and screen exposure
Check what happens after the first unlock. An app can have Face ID and still show sensitive content in the app switcher or remain open after you leave it.
- Does the app lock automatically?
- Is there an app-specific passcode fallback?
- Does it reduce screenshots, recordings and app-switcher exposure?
Recovery and deletion
Local storage needs a recovery story. Cloud storage needs a deletion story. In either case, you should understand how to retrieve your record and what happens when the app or account is removed.
- Can you export your complete record?
- Is the export encrypted?
- Can a backup be tested before deletion?
- Does deleting the app remove the only local copy?
The takeaway
Trust the complete data path, not a single privacy badge: capture, copies, processing, access, recovery and deletion all count.
Body Log articles are general educational material about keeping a personal record. They are not medical advice or a substitute for professional care.