Preserve the source conversation and capture relevant context, sender details and dates in unedited screenshots. Keep a separate recoverable copy with appropriate access controls. Screenshots help organize a record; they do not establish authenticity or guarantee acceptance by a court.
Capture the whole thread
- Capture the surrounding conversation. Overlap successive screenshots so a reviewer can follow their sequence; this technique is described in the NCJFCJ evidence guide.
- Include the visible sender identifier and message date. A saved contact name alone does not verify who actually sent a message.
- Record the capture date separately from the message date. Keep the image unedited and put explanatory notes in an index.
- For supported iMessage conversations, tap Edited to view earlier versions and capture the visible history. Capture an unsent-message notice if present; the notice does not recover the removed content. Apple documents differences for older software and other message types.
- For online material, keep the account identifier and exact URL with the capture. Note any content that was not loaded or could not be captured.
Keep the source, not just the pictures
In Settings → Apps → Messages → Keep Messages, Apple offers automatic removal after a chosen period. Forever avoids that particular scheduled deletion; it is not a backup or a guarantee against manual loss. With Messages in iCloud enabled, deletions propagate to the other devices using it. Recently Deleted is temporary recovery, not long-term preservation.
Keep the underlying conversation and attachments as well as screenshots. Before using an export service, ask your lawyer which formats are suitable and review what access the service requires. Do not delete source material merely because a screenshot set looks complete.
Posts, shared devices and the other parent’s accounts
Capture material you are authorized to access. A remembered password is not a reason to enter another person’s account, and children should not be asked to gather material from a parent’s private device. Ask your lawyer how to obtain records you cannot lawfully access yourself.
If monitoring or abuse is involved, plan with an advocate before making changes that may be noticed. Some services notify others about screenshots or recordings; check the particular feature using harmless test content. Avoid relying on a shared account or device to keep the collection private.
Copies and where they go
| Copy | Where | Why |
|---|---|---|
| Source conversation | Retain the conversation and its attachments | Screenshots do not replace the underlying material. |
| Unedited captures | Keep an ordered set with original filenames recorded | Read every image at full size to check legibility. |
| Independent copy | Use suitable storage with controlled access | Test retrieval without relying on the same phone. |
| Working set | Create separate labeled copies for highlights or redaction | Keep a record of changes and preserve the unedited set. |
| Delivery set | Follow your lawyer’s requested method and format | Keep the delivered version and confirmation of receipt. |
Check the handoff before sending
Use a simple index: item number, message date, capture date, source app, sender identifier, filenames and a short factual description. Mark uncertain dates or missing portions rather than filling them in from memory.
For a long conversation, check that no lines are missing between images and that each file opens. Send through the channel agreed with your lawyer. A successful upload screen and confirmed receipt are different things; record the confirmation you actually receive.
Where Photo Vault fits
New Photo Vault Lossy imports store compressed picture samples and needed media tracks without embedding whole source files. Existing archives with retained originals keep their original-resource export path. New still-image exports are reconstructed JPEG or PNG files, with captured metadata stored separately in the encrypted index. Local encryption uses a device-only installation key. This does not establish preservation of a full conversation, its context or an evidence trail. PhotoVault: Encrypt & Compress 1.0 runs on iPhone and iPad (iOS/iPadOS 26+) with AES-256-GCM local archive encryption and Secure Share (.pvsecure) export; always verify exported backups independently. Keep original captures and source records in independently recoverable storage.
The app offers a password, pattern or device-authentication gate; device authentication can fall back to the device passcode. After a Photos import, Photo Vault can request permission to delete eligible originals. Decline the iOS confirmation to keep them. It has no encrypted backup service of its own, so do not treat an import as a complete preservation or privacy workflow.
Local rules govern electronic evidence and disclosure. A family lawyer or court self-help service can advise on the requirements for your case.
PhotoVault: Encrypt & Compress 1.0 is available on the App Store for iPhone and iPad (id6824412013). Archive tests covered image reconstruction, metadata, video and Live Photo handling, append and deletion compaction. This is not a verified public release or a complete test of the workflow in this guide. Physical-device launch, final ZIP and sharing behavior, and portable recovery remain unverified. Encryption requires a new archive or successful migration; the device-only key is not a portable backup service.
Sources & further reading
- NCJFCJ and NNEDV: How to Gather Technology Abuse Evidence for Court
- Apple iPhone User Guide: Unsend or edit messages
- Apple iPhone User Guide: Delete messages and attachments
- NNEDV Safety Net: documentation and safety considerations