When a request touches backup words, PIN values, device approval, or app access, pause and return to a known Ledger entry. The checklist is intentionally short: entry path, Ledger Wallet context, device screen, backup boundary, and local record.
Official entry comes before any sensitive request
Record where the request appeared and what it asks the user to do. Then reopen Ledger Wallet or support from a known path. If the same task does not appear there, do not continue from the request path.
The entry verification checklist gives a compact structure for source path, app state, device state, and local record.
Backup content stays outside pages and messages
Recovery phrase words and PIN values are not support text, form text, or chat text. A record can say that the backup boundary was checked, but it should not include the secret content itself.
- Return to the known entry.
- Read the device screen before approval.
- Keep recovery phrase and PIN values private.
Ledger Wallet context should match the device screen
Ledger Wallet should explain the task before the device asks for an action. The recovery phrase explainer is the stable reference for what belongs in private backup records.
Use the checklist as a stop-and-compare habit
End with path, app state, device-screen wording, backup boundary, and decision. That keeps the rule practical without turning the article into a warning list.
