Security
Built for materialnonpublic information.
Magnum applies AI to the most sensitive documents a bank holds, so it is built around three commitments: each firm's data kept separate, need-to-know access to deals inside the firm, and an audit trail of who did what. Deal data is never used to train models.
Team Members
Everyone at the firm with access to this workspace.
See every dealOwner and Admin roles
Need-to-knowMembers see deals they created or are staffed on
01The Controls
- 1.1
Each firm's data kept separate
Your deals, files and documents are isolated from every other firm on the platform.
- 1.2
Need-to-know deal access
Each deal has its own deal team. Members see only the deals they created or are staffed on; viewers are read-only; owners and admins oversee every deal and manage roles.
- 1.3
Your data never trains a model
Magnum uses AI to file documents, draft deal materials and answer questions about your deals. Deal data is never used to train models.
- 1.4
Logged, deal by deal
The audit trail records sign-ins, uploads and downloads, document edits, versions and shares.
- 1.5
Encrypted connections and files
Every connection uses TLS 1.2 or later; stored files are encrypted with AES‑256.
- 1.6
Stored in the United States
All customer data is stored in US‑based infrastructure.
Share Document
Add Recipients
People with Access 3 recipients · shared by Tobias Wren, Oct 19, 6:12 PM
- MHMargaret Hollowaym.holloway@abcprecision.testChief Financial Officer, ABC Precision ComponentsShared Oct 19
- DRDaniel Reyesd.reyes@abcprecision.testChief Executive Officer, ABC Precision ComponentsShared Oct 19
- CQClara Quinnc.quinn@qrtlaw.testPartner, QRT Law LLP, company counselShared Oct 19
Access Until
Recipients can open the document until the end of this day.
Email verification is always required for shared documents.
40events1failedLast activeOct 20, 4:12 PM
Tuesday, Oct 20, 20265 events
Uploaded ABC_
Failed·Deal Data Room·Extraction timed out
Saved version 4 of Project Basalt — Confidential Information Memorandum
Deal Documents
Edited Investment highlights in Project Basalt — Confidential Information Memorandum
Deal Documents
Updated the details of Project Basalt
Deals
Signed in with a password
Sign-ins · Chrome 141 · macOS · 203.0.113.24
Monday, Oct 19, 20263 events
Shared Project Basalt — Confidential Information Memorandum with 3 recipients
Deal Documents
Changed the stage of Project Basalt from CIM Preparation to Marketing
Deals
Signed in with a password
Sign-ins · Chrome 141 · macOS · 203.0.113.24
02Four Questions Compliance Asks
- Residency
- United States.
- Export
- Available on request.
- Retention
- Kept while the account is active; deletion on request after closure.
- Incident response
- Affected firms are notified.
03Where We Are Today
- Per-firm separationIn place
- Need-to-know deal accessIn place
- EncryptionIn place
- Role-based accessIn place
- Audit loggingIn place
- SOC 2 Type II reportOn the roadmap
- Information-barrier controls between deal teams (beyond need-to-know staffing)On the roadmap
Security questions?
We walk your CISO or Chief Compliance Officer through the architecture.
Emailsage@esapiens.ai