The cargo is precious.
We treat it that way.
You carry client books, investor identities, and capital in motion. Here is exactly how it's protected, written for your IT reviewer, not for a badge wall.
Tenant isolation at the database
Every row in every table is scoped to your workspace and enforced by row-level security in Postgres itself, not just application code. One tenant per work domain, by design.
Encryption where it counts
TLS everywhere in transit. OAuth tokens, investor PII, and authenticator secrets are AES-256-GCM encrypted at the application layer on top of encrypted storage. Revealing investor PII requires a fresh password step-up.
Real two-factor authentication
Authenticator apps (TOTP), SMS, and email codes, with single-use backup codes for recovery and admin reset as the fallback. The investor portal requires 2FA, no exceptions.
Passwords screened against breaches
A 12-character complexity policy enforced server-side, and every new password is checked against the HaveIBeenPwned corpus using k-anonymity, the password itself never leaves our servers.
Verified integrations
Our Microsoft integration is a verified publisher (TenthAvenue Labs LLC) in the Entra ecosystem. Google access is limited to calendar scopes. Connect and disconnect per member, tokens revocable any time.
Accountable by default
Sensitive actions, invitations, role changes, 2FA resets, domain changes, PII access, land in an audit log. Sign-ins from providers inherit your identity provider controls, including offboarding.
Have a security questionnaire?
Send it over. We answer them directly, with the engineers who built the controls in the loop.
Contact us