Security documentation.
Wallet safety, transaction approval, token risk signals, no seed phrase policy, and responsible disclosure.
01
Security Model
The security model prioritizes user-controlled execution, explicit wallet approval, and transparent risk communication.
No seed phrase collection.
Transaction previews before supported actions.
Risk signals are informational and not guarantees.
Security reviews and disclosures are handled through official Encrypted Layer channels.
02
Wallet Safety
This reference page defines Encrypted Layer policy, implementation boundaries, and product behavior for this area.
Keep product status accurate.
Make wallet and execution assumptions explicit.
Prefer clear previews over hidden abstraction.
ghostos docs --topic "wallet safety"03
Transaction Approval
This reference page defines Encrypted Layer policy, implementation boundaries, and product behavior for this area.
Keep product status accurate.
Make wallet and execution assumptions explicit.
Prefer clear previews over hidden abstraction.
ghostos docs --topic "transaction approval"04
Token Risk Signals
This reference page defines Encrypted Layer policy, implementation boundaries, and product behavior for this area.
Keep product status accurate.
Make wallet and execution assumptions explicit.
Prefer clear previews over hidden abstraction.
ghostos docs --topic "token risk signals"05
No Seed Phrase Policy
Encrypted Layer and Ghost OS will never ask users to enter a seed phrase.
Do not share seed phrases with websites, apps, support accounts, or team members.
Treat any seed phrase request as malicious.
Support flows should never ask for secret recovery phrases.
06
Responsible Disclosure
Security reports should go through official Encrypted Layer channels.
Include affected surface, reproduction steps, impact, and relevant transaction or contract context.
Do not exploit or access user data while researching a report.
Security updates are published through official Encrypted Layer channels.