A request for screen photos should be reviewed as a contact-entry and backup-boundary question. The useful answer is not whether the request sounds helpful, but whether the task belongs in Ledger Wallet and what information should remain off-record.
Contact entry should be checked first
Record where the request arrived, what screen it asks to see, and what task it claims to support. Then return to a known Ledger entry and compare whether the same task is visible there.
The entry verification checklist helps separate contact path, app state, device state, and local record.
Device screen can be reviewed without sharing secrets
Device-screen wording is useful for the user to read, but backup words, PIN values, and private recovery details should not be placed into photos, chat windows, or forms. A local note can describe the prompt without copying secret content.
- Record the requested screen type.
- Compare the task inside Ledger Wallet.
- Keep backup and PIN details out of shared media.
Approval wording should be read on the device
If a task reaches the approval step, compare the device screen with Ledger Wallet context. The Clear Signing review checklist is a useful reference when screen wording needs to be read carefully.
Close with a private local record
End with contact path, requested screen, Ledger Wallet state, device-screen wording, and final decision. That keeps the check useful without turning screen sharing into a source of instruction.
