Yes. Medic52 protects sensitive patient data at every stage — while it travels between your device and our servers, and while it is stored. Here is how.
Encryption in transit
All communication between the Medic52 app or web platform and our servers travels over a modern, encrypted TLS (Transport Layer Security) connection — the same class of encryption used for online banking. This applies to both the web platform and the mobile app.
Encryption at rest
Patient data is encrypted on our servers using AWS Key Management Service (KMS). Each resort can have its own encryption key, so one organisation’s data cannot be read with another’s key. Read and write operations pass through this encryption and decryption layer.
Where your data lives
Your data is hosted with Amazon Web Services and stored in the region assigned to your organisation — the United States, Australia, or Canada. It stays in that region. See Where is the data stored?
Access is controlled
- You can only sign in to the web platform or the mobile app with your own email and password.
- Our servers are hardened and access is tightly restricted using techniques such as firewall IP restrictions and SSH-key-based access, and they are checked regularly.
- Photos and witness images captured in the app are attached to the incident and uploaded to Medic52 — they are not left in your device’s photo library. See How do photos work in the Medic52 app?
What you can do to help
The strongest link in day-to-day security is the device in your hand. Lock your device, sign out on shared devices, and never take records out of Medic52 — see How do I keep my mobile device secure?