Last updated 8 May 2026
A plain-English summary of how Heirlume is built to handle the most sensitive data in your life. The detailed technical posture lives on our security page.
Heirlume runs on managed services that are independently SOC 2 Type II certified. We chose providers whose own audits we can rely on so that your data sits inside a hardened perimeter from the day you sign up.
Heirlume itself does not yet hold a SOC 2 report. We've adopted the controls a SOC 2 audit examines — encrypted-at-rest storage, TLS-only transport, role-based access, signed-token invitations, audit logging, documented subprocessors, and the principle that the smallest possible amount of data leaves your browser. A formal Type II audit is on our roadmap as we approach the general availability of our Family Office tier.
Until then, we believe the right framing is: Heirlume runs on SOC 2-certified infrastructure, and we don't claim certifications we don't yet hold.
Sign-in goes through WorkOS AuthKit, with multi-factor authentication supported. Beneficiaries, executors, trustees, and guardians you invite connect through consent-based, role-aware tokens that you can revoke at any time. Each role sees only what you've authorized.
We don't store your bank login credentials — Plaid does. We don't store full credit card numbers — Stripe does. We don't store unencrypted copies of your vault credentials anywhere on our servers. We don't track you across the web.
Security researchers and customers can report concerns to security@heirlume.ai. We commit to acknowledging reports within two business days and to good-faith collaboration with researchers acting in good faith.
Advisors, family offices, and enterprise prospects who require formal documentation should contact legal@heirlume.ai. We can share our security controls summary, subprocessor list, and the underlying SOC 2 reports of our infrastructure providers under NDA.
This page summarizes Heirlume's current security and compliance posture in plain English. The full technical detail lives at /legal/security.