Security built into the platform
Recovery data is sensitive. These controls exist in the product today; limits and open items are published openly.
Updated 2026-10-20
Controls
- Authentication: hashed passwords, lockouts and throttling, mandatory TOTP two-factor for privileged roles, recovery codes, device/session management.
- Re-authentication: password and a fresh code for sensitive actions such as API keys and MFA resets.
- Authorisation: role-based permissions (see the published matrix in-app) plus maker-checker segregation of duties.
- Isolation: tenant from session only; automated cross-tenant access sweep in the test suite.
- Encryption: AES-256-GCM for documents, secrets and backups; key rotation tooling.
- Integrity: append-only ledger and audit trail enforced by database triggers; hash-chained audit with verification.
- Web: CSRF protection on every browser POST, strict content security policy, secure cookies.
- Integrations: HTTPS-only outbound webhooks, private-network destinations refused, signed payloads, scoped API keys.
- Operations: health checks, incident log, access reviews, tenant-controlled expiring support access, encrypted scheduled backups.
Honest limits
No independent penetration test or formal certification has been completed for this software. Evaluate it in staging, run your own assessment, and read the published release audit before processing real borrower data.
Questions
Is data encrypted?
Uploaded documents, stored secrets and backups are encrypted with AES-256-GCM using an application key you control. Use HTTPS for data in transit.
Is the software certified?
No certification is claimed. Controls are documented and tested; independent assessment is recommended before production use.