Security
Your ledger, your payroll and your customer list live here. This is what protects them, stated plainly enough that your auditor can check it.
Controls
Encryption
TLS 1.2 or higher in transit, with HSTS. Data at rest is encrypted at the volume level, and document uploads are stored outside the web root with signed, expiring access URLs.
Access control
Role-based permissions per module and per action, scoped to a company. Approval authority is separate from edit rights, so the person who raises a payment is not the person who releases it.
Authentication
Password hashing with a modern adaptive algorithm, optional two-factor by authenticator app, session expiry on inactivity, and immediate revocation on deactivation.
Audit logging
Every mutating action writes an activity row recording actor, timestamp, source address and the values before and after. Posted ledger entries cannot be altered — corrections post as reversals.
Backups
Encrypted daily backups with 30-day retention and point-in-time recovery. Restores are tested on a schedule, not assumed to work.
Separation of environments
Production credentials are not present in staging or development, and no production data is copied into either without irreversible anonymisation.
Reporting a vulnerability
How to reach us
Email the security inbox with steps to reproduce. We acknowledge within one working day and give you a fix timeline within five.
What we ask
Give us reasonable time before disclosing publicly, do not access or modify data that is not yours, and do not run tests that degrade service for other customers.
What we promise
We will not pursue legal action against good-faith research that follows the above, and we will credit you when the fix ships if you want to be named.