Security
These are the safeguards built into the platform today. We describe them plainly and update this page when they change.
Passwords are stored as salted bcrypt hashes. Staff and platform users sign in with two-factor authentication, and sessions use short-lived tokens.
Every person has a role, and the API checks each permission on every request. Sensitive actions such as approving financing, granting roles and selling collateral need a second person.
Operator staff are limited to their organisation, and branch staff to their branch. Financing partners see only requests under their own programmes.
Sign-ins, approvals, valuations and money movements are written to an audit log that the application cannot edit or delete.
Batches of audit and ledger records are fingerprinted and anchored on a public ledger, so later changes to history would be detectable.
Each Ar-Rahnu receipt carries an integrity fingerprint of its terms. Evidence files such as photos and assay reports are hashed when uploaded and kept in private storage.
Valuations, ledger entries and financing events are append-only. The application connects to its database with an account that cannot change table structures or history.
Sign-in and public forms are rate limited, and every input is validated on the server.
Please tell us through the contact form with “Security” in your message. Don't include account passwords or customer data.
