imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
imtoken Knowledge

Device Security

A practical guide to device security with clear concepts, user checks and risk boundaries before wallet actions are confirmed.

On this page
  1. Device locks and updates
  2. Public Wi-Fi
  3. Shared computers
  4. Browsers and extensions

Device locks and updates

Device locks and updates is an essential part of understanding Device Security. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Device locks and updates is an essential part of understanding Device Security. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Practical checks

  • Confirm the current account and network
  • Never share a seed phrase, private key or verification code
  • Read the full transfer, signature or approval request before confirming

Public Wi-Fi

Public Wi-Fi is an essential part of understanding Device Security. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Public Wi-Fi is an essential part of understanding Device Security. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear

Shared computers

Shared computers is an essential part of understanding Device Security. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Shared computers is an essential part of understanding Device Security. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear

Browsers and extensions

Browsers and extensions is an essential part of understanding Device Security. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Browsers and extensions is an essential part of understanding Device Security. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear