Security Overview

• Role-based access with row-level security on every client-facing table.
• Append-only audit log covering transactions, corrections and sign-offs.
• Capacity-aware signature workflow with authoriser and reason recorded.
• Staff-only authentication; no public sign-up and no family-facing routes.
• Server-side validation on inputs and typed RPC boundaries between client and server.

• Email + password sign-in with leaked-password protection enabled at the identity provider.
• Session management provided by our authentication sub-processor.
• Optional Google OAuth for staff sign-in.

• Encryption in transit (TLS) and at rest, provided by our hosting sub-processor.
• Database backups managed by the hosting sub-processor.
• Payment card data handled entirely by our payments sub-processor; card details never touch CareLedgerPro servers.
• UK/EU-aligned regions used where available.

• Transactions and ledger entries are append-only.
• Corrections are recorded with the original entry preserved and a reason captured.
• Voids record who voided, when and why; original rows are preserved.
• Audit records can be exported as CSV for internal review.

CareLedgerPro includes an in-app breach register so staff can record incidents they have assessed, with timeline notes and links to supporting evidence. It is a record-keeping aid; the Controller remains responsible for assessment, ICO notification and communications with affected individuals. See Incident Response.

CareLedgerPro is not independently certified against ISO 27001, SOC 2, Cyber Essentials, or DSPT. The provider remains the data controller and is responsible for user provisioning, offboarding, device security, and their own incident-response process.

If you believe you have found a security issue, please email support@careledgerpro.co.uk with reproduction steps. We aim to acknowledge reports within one working day.