PRIVACY & SECURITY

Operational security for wallet holders and dApp users. Eoonia is built fail-closed — ambiguous sessions and transactions resolve to "not approved," never "probably fine."

SECURITY GUIDE

FAIL-CLOSED BY DEFAULT

If a transaction, session, or credential status cannot be confirmed, the wallet blocks the action. No silent bypass, no auto-sign shortcuts. Unknown state is treated as untrusted — the safe default for self-custody wallets.

  • Biometric gate before signing sensitive transactions
  • Encrypted Hive storage — keys never leave the device
  • WalletConnect sessions require explicit per-tx approval

OPERATIONAL PRACTICES

Back up your recovery phrase offline, enable biometrics, and verify dApp sessions before approving. Public documentation covers wallet security without exposing internal infrastructure.

  • Recovery phrase: write offline — Eoonia cannot recover it for you
  • Private keys: never transmitted to Eoonia servers
  • WalletConnect: approve each session and transaction individually
  • Creator Studio: review pallet calls before signing on-chain txs