About Sealda

We built Sealda around a single rule: if we don't store it, no one can leak it. Your recovery phrase never reaches our servers. Your PIN is never transmitted. Your balances are computed by querying public chain RPCs from your own device. There is no "Sealda account" to phish or unlock — there are only your keys, on your hardware.

Self-custody is not a feature, it's a contract. You hold the keys; you carry the risk. We give you the tools to hold them well — Argon2id-stretched PIN, AES-GCM-sealed vault, biometric unlock, hidden-wallet passphrase — but we cannot unlock anything for you. There is no support agent who can recover funds. There is no email reset flow. If you lose your recovery phrase, the funds are gone, and we have no mechanism that could change that.

Sealda is a project, not a company. There is no legal entity sitting between users and the chain. The clients build only on audited open-source cryptographic primitives (see "Built on standards" below). The relay endpoints we operate (push notification subscription and a multi-frame QR pairing handoff) are minimal, stateless, and documented in the privacy policy.

We do not raise from VCs. We do not run a token. We do not sell ads. The only thing we want from you is that you keep your phrase safe — because we can't.

iOS bundle: app.sealda.wallet.

• BIP-39 mnemonic + BIP-32 / BIP-44 derivation paths.
• @noble/curves and @noble/hashes for signatures and hashing.
• Argon2id PIN stretching, AES-256-GCM authenticated encryption.
• Public RPCs (TronGrid, Etherscan, BSC public nodes) for chain reads.

Questions, security disclosures, beta requests — write to [email protected].