Written by the ApexWallet Security TeamPublished:

Security & Cryptographic Architecture

ApexWallet leverages industry-standard cryptography to deliver an experience where security is built into the architecture, rather than added as an afterthought. Here is exactly how we protect your digital assets.

Core Cryptographic Standards

BIP-39 Mnemonic Standards

When you create a wallet, ApexWallet uses standard secure random number generators (CSPRNG) to generate your 12-word recovery mnemonic phrase. This seed phrase is standard and compatible with external non-custodial apps, preventing software lock-in.

Zero-Server Custody

Your private key or seed phrase never reaches our backend database in plain text. Everything remains locked inside your browser session using standard local web storage, protected by cryptographic keys derived directly from your password.

Supabase Authentication & Policies

All database operations are secured using Supabase Row Level Security (RLS) policies. Only authenticated owners can read or append transaction history records, safeguarding user privacy and preventing cross-user account viewing.

Cryptographic Standards

Standard / AlgorithmParametersSecurity Target
Mnemonic PhraseBIP-39 (12 Words)128-bit Entropic Seed Security
Local Database EncryptionAES-GCM (256-bit)Cryptographic storage confidentiality
Key DerivationPBKDF2 with HMAC-SHA256Brute-force resistance

Frequently Asked Questions

Can ApexWallet recover my seed phrase if I lose it?

No. Because we are a non-custodial service, we have no access to your recovery phrase. It is generated locally on your browser. Please write it down on physical paper and store it securely.

Security & Audit Report

We continuously audit our source code dependencies, packages, and configurations to adhere to OWASP Top 10 standards. The project uses pinned dependency structures, audits integrity with strict lock files, and configures full HTTP security headers (CSP, HSTS, X-Frame-Options) to protect against script execution, clickjacking, and MITM hijacking.

Content Security Policy (CSP)ACTIVE & SECURED
Strict Transport Security (HSTS)ENFORCED
Frame ancestors restrictionsDENY