A direct-message contact path should be treated as a contact-entry check. A helpful tone does not replace a known Ledger entry, and a private message should not become the place where device-side actions are decided. The user should compare support path, Ledger Wallet context, device screen, and a limited record.
Support entry comes before the message thread
Record where the message arrived and what it asks the user to do. Then return to a known Ledger support or app entry before continuing. If the known entry does not show the same task, keep the message as a note and stop there.
The entry verification checklist helps compare contact path, app state, device screen, and local record without adding unnecessary detail.
Ledger Wallet context should frame any device task
If the message mentions setup, recovery, update, or connection, open Ledger Wallet from the known entry path and read the app context first. Device-side action should still be reviewed on the hardware screen before completion.
- Record the contact path and requested task.
- Compare the message with Ledger Wallet context.
- Do not share recovery phrase or PIN details in a message thread.
Safe records should not include secret content
A record can include date, page path, app version, device model, and final decision. It should not include private backup content. The Clear Signing review checklist is a stable reference when screen wording and final approval need to be compared again.
Repeat the known-entry check when contact changes
If the conversation moves to another page or account, repeat the same known-entry check. That keeps the method useful as a process and avoids turning private-message contact into the action path.
