Our Approach to Security
This section covers how mymeddiCAL approaches security — the controls built into the platform, how different people sign in depending on their role, and the practices running underneath it all on our infrastructure.
Our approach is built around a few simple ideas:
-
Security shouldn't be something a nurse, teacher, or parent has to think about. It should be built in by default, every time — not a setting anyone has to remember to turn on.
-
Access should always match the job. How someone signs in, and what they can see once they're in, is shaped by their role — not left to assumption or convenience.
-
Being straightforward, not just compliant. We'd rather explain how something actually works in plain language than hide behind a badge or a policy document — and if you ever have a question we haven't answered here, you'll get a real answer from a real person.
Here's exactly how that plays out across the platform.
Everything moves over an encrypted connection, end to end.
Every request between your browser, the mobile app, and our servers travels over HTTPS. Our infrastructure runs on Amazon Web Services in Sydney, Australia — your data is processed and backed up here.
Backups run automatically every day, so a hardware fault or a bad deploy is never the reason a record disappears.
