Security Center
Seed Phrase & Private Keys
A practical imtoken guide to seed phrase & private keys, including core concepts, verification steps and risk-aware usage.
imtoken staff will never ask for your seed phrase, private key or verification code.
Core concepts
From a risk perspective, offline backups and screenshot risk deserve an independent review. Once a transaction is confirmed on-chain, a wallet normally cannot reverse it unilaterally. DApps and smart contracts can also introduce permission and contract risks, so every signature, approval and transfer should be understood before it is accepted.
For seed phrases, first define its role in the current task, then check whether private keys and offline backups are consistent. When screenshot risk is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For recovery boundaries, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: seed phrases
- Cross-check: private keys and offline backups
- Review carefully: screenshot risk
- Verify afterward: recovery boundaries
Checks before you act
After a Seed Phrase & Private Keys task is completed, review recovery boundaries and seed phrases to make sure the outcome matches the intent. Long-lived approvals and persistent connections should be revisited periodically. Good wallet hygiene is a repeated process of checking critical details and retaining traceable on-chain information, not a one-time setting.
For private keys, first define its role in the current task, then check whether offline backups and screenshot risk are consistent. When recovery boundaries is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For seed phrases, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: private keys
- Cross-check: offline backups and screenshot risk
- Review carefully: recovery boundaries
- Verify afterward: seed phrases
How to evaluate a live request
To understand Seed Phrase & Private Keys, treat offline backups and screenshot risk as parts of the same on-chain workflow. The interface is only the entry point; the selected network, current chain state and permission scope determine what actually happens. Confirm the destination, source and network before continuing so the meaning of the request stays clear.
For offline backups, first define its role in the current task, then check whether screenshot risk and recovery boundaries are consistent. When seed phrases is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For private keys, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: offline backups
- Cross-check: screenshot risk and recovery boundaries
- Review carefully: seed phrases
- Verify afterward: private keys
Risks and boundaries
screenshot risk rarely appears in isolation. It often intersects with recovery boundaries and seed phrases. A useful pattern is to separate each action into four checks: identify the object, verify the network, review permissions, and confirm the result. If one of those checks cannot be completed, stop and verify rather than relying on an unfamiliar site or remote instructions.
For screenshot risk, first define its role in the current task, then check whether recovery boundaries and seed phrases are consistent. When private keys is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For offline backups, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: screenshot risk
- Cross-check: recovery boundaries and seed phrases
- Review carefully: private keys
- Verify afterward: offline backups
How to verify the outcome
When using imtoken for Seed Phrase & Private Keys, prioritize information that can be independently verified, such as addresses, network names, contract addresses, transaction hashes and block-explorer records. Visual design, urgency messages or claims from an unknown support account are not substitutes for verifiable on-chain details.
For recovery boundaries, first define its role in the current task, then check whether seed phrases and private keys are consistent. When offline backups is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For screenshot risk, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: recovery boundaries
- Cross-check: seed phrases and private keys
- Review carefully: offline backups
- Verify afterward: screenshot risk
Security checklist
- Never share your seed phrase, private key or verification code.
- Verify the address, network and amount before sending.
- Review each DApp signature and token approval independently.
- Use transaction hashes and block explorers to verify on-chain status.
- Revoke approvals and disconnect sessions that are no longer needed.