Your data
So here is exactly where those records live, who can reach them, and what we have not got in place yet. Every number below was measured, not estimated.
Measured against the production database on 26 August 2026.
These are properties of how the system is built, not settings someone has to remember to switch on. That is why they hold on every page rather than the ones we thought of. Providers working through a security questionnaire can ask us for the detail behind each one.
Separation between providers is enforced at the data layer, on every read and every write, rather than by application code that has to remember to filter. One provider's records are never visible to another, on every page, not just the ones we thought of.
Files are held in private storage scoped to your organisation, protected by the same rules as the database rows they belong to, and download links are short-lived.
Clinical, compliance and financial changes are written to a tamper-evident trail by the database itself. An entry that is edited or deleted shows up as a break in the chain, and the chain can be checked end to end.
Where a change touches personal information, the trail records which field changed and a fingerprint of the value, never the value itself. It proves what happened and who did it without becoming a second copy of the data it protects.
Every check asks whether this person may do this specific thing to this specific kind of record. That is why you can define your own roles, and why a role you made is enforced exactly as strictly as one we shipped.
Sign-in supports an authenticator app, and the operations with the widest reach require a session that has genuinely completed that second step. A password alone is not enough.
The database runs in Sydney and so do the servers that answer your requests. Most vendors quote you the storage location and go quiet about where the processing happens. Both of ours are here.
The two things procurement asks about on the first call, answered here so you do not have to wait for the call. If there is something else you need to know before you can sign anything, ask us directly.
We are working through an independent security assessment now, and the outcome will be published on this page when it is complete. Until then, every control above is real and you can hold us to it, but no outside body has signed it off yet, and we would rather say that plainly than describe ourselves as “aligned with” a standard we have not been assessed against.
CareOp runs on managed, enterprise-grade infrastructure in Sydney, the same operators much of this sector is built on, with public status pages you can check at any time, and we monitor the platform continuously ourselves. We will publish our own measured uptime figure once there is a full year of operating history behind it, because a percentage without a history is a guess. Until then, ask and we will show you the live number.
Email security@careop.com.au with enough detail for us to reproduce it. We will acknowledge it, and we will not pursue anyone who reports a genuine finding in good faith.
If you are working through a procurement questionnaire and need something that is not here, ask, the downloads page has the documents we can hand over today.