Security
Care records hold some of the most sensitive information there is. This is how we look after it.
Separation between organisations
Every organisation's data is isolated by row-level security in the database. Application code runs each request as a restricted database role pinned to one organisation, so even a coding mistake cannot return another organisation's records. Automated tests check this on every change.
Access inside your organisation
- More than fifty separate permissions, and built-in roles from support worker to owner.
- Support workers see participants only while they are on their shifts.
- Behaviour support, medical and clinical information need their own permissions.
- Two-factor authentication, which organisations can require for staff.
Records that cannot be quietly changed
The audit log is append-only and each entry is chained to the one before it, so alteration is detectable. Signed agreements, signatures, attendance, medication records and claim history cannot be edited in the database.
Encryption and hosting
Data is encrypted in transit (TLS). The database, backups and documents are encrypted at rest with AWS KMS. Sensitive fields such as two-factor secrets and Medicare numbers have an additional layer of field encryption. Customer records and documents are hosted in Australia (AWS Sydney), and the services that process them are in Australia, except Pin Payments (Australian company. Pin does not publish where it hosts data, and its privacy policy allows disclosure to the United Kingdom, New Zealand and the United States, so billing contact details may go there). Phone push notifications, which an organisation can turn on, go through Apple and Google and carry no personal details. The privacy policy lists every service.
Inclusi staff access
Our support team cannot see your data unless your administrator approves a specific request, read-only, for at most 72 hours. Every action during that time is logged with the request.
What we are still doing before launch
An independent penetration test has not been done yet. A privacy impact assessment of the platform was drafted in November 2026 and is waiting for independent legal review. We plan to finish both before general availability and will publish a summary here.
Report a vulnerability
Email security@inclusi.com.au. Please give us reasonable time to fix an issue before disclosing it.