Security
What protects your books, and what does not exist yet
Security pages are usually written to reassure. This one is written to be checkable: everything below is either implemented today, or listed under what is not.
In place today
Controls that are implemented
Tenant isolation
- Every request resolves its organization from a signed, validated token - never from a body, parameter or header
- Every query is scoped by that organization, and cross-tenant reads return 'not found' rather than 'forbidden' so record ids cannot be probed
- A platform administrator gets no implicit access to any customer's business data; that requires real membership, like anyone else
Authentication
- Passwords hashed with Argon2id
- Short-lived access tokens with separate, organization-scoped tenant tokens
- Refresh-token rotation, with sessions you can list and revoke
- Email verification and time-limited password-reset tokens
- Rate limiting on the API
Authorization
- A permission catalog of over 250 codes across every module
- Ten role templates plus custom roles built from the same catalog
- Permissions re-checked against the database on every request, so revoking access takes effect immediately rather than at next login
Auditability
- Every create, update and delete recorded with actor, timestamp, and before and after state
- Financial-year period locking, so a closed period cannot be edited
- Voucher reversal writes a counter-entry rather than deleting the original
- Document deletion keeps a tombstone so the trail survives the file
Data handling
- Encrypted connections in transit
- Uploaded documents stored in object storage behind short-lived, single-object signed URLs
- Uploads validated by content sniffing rather than by the declared type or file extension
- Per-tenant storage key namespacing as defence in depth on top of the row-level check
Not yet
What we do not claim
A security page that lists only strengths is not a security page. These are the gaps we would want to know about if we were evaluating us.
- No SOC 2, ISO 27001 or any third-party audit certification. None has been carried out.
- No independent penetration test has been commissioned to date.
- No customer-managed encryption keys, and no field-level encryption beyond password hashing.
- No SSO or SAML - authentication is email and password with session management.
- No two-factor authentication yet. It is on the roadmap and is the single most requested item.
- Uploaded documents are not virus-scanned.
- No published uptime SLA or status page.
Reporting a vulnerability
If you believe you have found a security issue, email support@lekhaiq.com with enough detail to reproduce it. We will acknowledge receipt, and we will not pursue action against good-faith research that avoids privacy violations, service disruption and data destruction.
Put your whole business on one ledger
Start free, invite your accountant, and see your first month close without a reconciliation spreadsheet.
No card required to start · Cancel any time · See pricing