Privacy & security
Eoonia Wallet is built for self-custody first. This guide covers how keys, credentials, and app data are handled — without publishing internal infrastructure secrets.
Self-custody model
| Principle | What it means |
|---|---|
| Keys on device | Mnemonics and private keys stay in encrypted local storage (Hive) |
| Local signing | Transactions are signed on your phone or computer — never on our servers |
| No seed recovery | We cannot reset your password or recover your phrase |
| Biometric gate | Face ID / fingerprint required before signing |
Encrypted storage
- Hive — encrypted local database for accounts, tokens, and settings
- QuantumSecuritySystem — AES/RSA/PBKDF2 key handling with rotation research
- Hardware wallets — Ledger support for high-value accounts
Eoonia ID & credentials
Eoonia ID lets you store and present verifiable credentials in the wallet:
- Credentials you import stay on device until you choose to present them
- Selective disclosure — share proofs, not raw documents
- Full issuer infrastructure lives on KryptoOS (separate product)
Network privacy
- RPC endpoints are configured per network — use public testnet URLs in docs only
- WalletConnect sessions are scoped — approve each dApp connection explicitly
- No automatic upload of transaction history to Empoorio servers
Best practices
- Write your backup phrase on paper — never in cloud notes or screenshots
- Enable biometrics and auto-lock
- Verify recipient addresses before sending
- Revoke unused WalletConnect sessions in Settings
- Use testnet for Creator Studio experiments before mainnet
Reporting issues
Use GitHub issues on empoorio/Eoonia_Wallet for bugs. For security-sensitive reports, follow the responsible disclosure process published in the repository.