How Anestheo protects clinical accounts and patient information.
Every account is authenticated before any clinical data is loaded. Application pages verify your session on load and redirect if you are not signed in.
Patient records are protected at the database layer with row-level security, so a clinician can only read and modify the patients assigned to them. Privileged operations run through audited, permission-checked database procedures rather than direct table writes, and sensitive workflow columns cannot be changed by the client directly.
Uploaded patient documents are held in a private storage area that is not publicly accessible; only the owning patient and their assigned clinician can retrieve them. Traffic between your browser and Anestheo is served over encrypted HTTPS/TLS.
If you believe you have found a security issue, please email support@anestheo.com with the details. Please do not share the issue publicly until it has been addressed.
This page describes the security model as currently implemented. See also Data Protection and the Privacy Policy.