Security & Compliance
Built for clinical
trust.
Technical documentation for hospital IT teams evaluating M4NG0 OS.
Architecture Overview
System architecture
A locally deployed clinical operating system. The following describes the security architecture governing data storage, access, and transmission.
Deployment Model
- •Installed on hospital-owned hardware (servers, workstations, or dedicated machines)
- •Runs as a standalone desktop application (Electron runtime)
- •No external cloud hosting required for core operations
- •Local SQLite database for all patient and operational data
- •Optional encrypted cloud sync for multi-facility deployments
Data Encryption
- •AES-256 field-level encryption for all Protected Health Information (PHI)
- •TLS 1.3 encryption for all data in transit
- •Encryption keys generated during initial setup
- •Keys held exclusively by the hospital — M4NG0 has zero access
- •Encrypted backup files for offsite storage
Access Control
- •Role-based access control (RBAC) with 7 defined clinical roles
- •Minimum necessary access enforced at the API layer
- •Device registration with department-level terminal assignment
- •Multi-factor authentication support (TOTP)
- •Session timeout and auto-lock after 5 minutes of inactivity
Audit & Compliance
- •Append-only audit log for all PHI access and modifications
- •SHA-256 hash-chained log entries for tamper detection
- •6+ year log retention aligned with regulatory requirements
- •Logs stored separately from the main application database
- •Audit log access restricted to authorized administrators
Data handling policies
How patient data is stored, accessed, and protected within M4NG0 OS.
Data Ownership
The hospital retains full ownership of all patient data. M4NG0 has no access to patient records — no remote telemetry, no analytics collection, no data sharing. Upon contract termination, all data is transferred or securely destroyed.
Storage & Residency
All patient data stored locally on hospital hardware in an encrypted database. Data residency determined by where the hospital deploys M4NG0 OS. Multi-facility cloud sync uses end-to-end encryption with hospital-held keys.
Data Portability & Export
Export all patient data at any time in FHIR R4 JSON, CSV, or structured archives. No vendor lock-in. Export available to authorized administrators.
Breach Response
Documented incident response procedures with defined notification timelines. Includes breach containment, impact assessment, notification protocols, and post-incident review.
Data Retention & Destruction
Records retained per the hospital's policy and applicable regulations (minimum 6 years). Secure deletion with verification ensures PHI is irrecoverably removed from all storage locations including backups.
Documentation
Compliance and legal documentation for technical evaluation and procurement.
Ready for a technical review?
Architectural walkthroughs, security documentation, and deployment planning available on request.