Ledgerline holds the money trail of your projects, so we treat security as part of the product. Ledgerline is currently in pilot, and this page describes how it is built and run.
Your organisation's data stays yours
- Separate workspaces: every record belongs to one organisation, and every request is checked against the organisation and role of the person making it.
- Roles and limits: owners decide who can see a project, record spending, approve or release funds, and up to what amount.
- Private receipts: receipts and files are stored privately and only opened through links that expire after a few minutes.
- An activity log that can't be edited: every approval, release, edit and budget change is recorded with who did it and when.
- Nothing is deleted: corrections are recorded as new entries, so the history stays complete.
Protection in transit and at rest
- All traffic between your devices and Ledgerline is encrypted with TLS.
- Databases, backups and file storage are encrypted at rest by our cloud providers.
- On mobile, sign-in tokens are kept in the phone's secure storage, and the app can be locked with Face ID, fingerprint or a PIN.
Sign-in
- Sign-in uses one-time codes sent by email or SMS, or Google, so there are no reused passwords to leak.
- Sessions can be ended from any device, and owners can remove a person's access immediately.
Backups and availability
- Databases are backed up daily and backups are kept for 35 days.
- Ledgerline runs on established cloud providers with monitoring and error alerts.
Inside MLabs
- Only staff who need it for support or maintenance can access production systems, and that access is logged.
- We don't look inside a customer's workspace unless the customer asks us to, for example for support, or the law requires it.
Reporting a security issue
If you think you have found a vulnerability, email ledgerline@mlabs.ng with the subject "Security". Please give us reasonable time to fix it before telling anyone else. We will reply within two working days and keep you updated.