Client financial data, sealed at rest and in transit.
Tax returns, financial plans, estate documents, and onboarding files are among the most sensitive data in anyone's life. Koaich keeps them encrypted under keys your firm holds — so a breach of our infrastructure produces ciphertext, not your clients' financial picture.
What you get
Per-client vault isolation
Each client's documents, notes, and correspondence live in a vault with its own encryption boundary. A breach, a subpoena, or a mistaken share of one client's vault doesn't touch any other.
Encrypted file storage
Tax returns, K-1s, estate plans, account statements — each file encrypted with its own key, wrapped to each authorized team member. File contents are never readable server-side.
Secure document delivery to clients
Send a financial plan, tax return, or sensitive report to a client who doesn't use Koaich. They receive a metadata-only email; the document decrypts on their device. Their email provider and ours both see ciphertext.
Encrypted client communication
Advisory notes, follow-up correspondence, and client Q&A — E2E encrypted on device. Post-quantum hybrid key agreement on 1:1 threads protects the key exchange against long-term interception.
TTLs on working materials
Draft notes, interim documents, and working correspondence can self-expire. Final deliverables stay; the working noise around them doesn't accumulate indefinitely.
The underlying cryptography
Every claim above is grounded in a specific primitive. Not marketing.
- →X25519 + ML-KEM-1024 (NIST FIPS 203) hybrid key agreement for 1:1 client threads
- →Per-file symmetric keys wrapped to each authorized recipient
- →Sender-Key group messaging with forward secrecy on joins and key rotation on member removal
- →WebAuthn passkeys — authentication keys never transmitted to servers
- →Shamir's Secret Sharing across your own devices for recovery — no vendor-side reset
Get on the waitlist.
We're onboarding financial professionals first. Read the architecture if you want detail.