Trust & Security
How Socratic handles
clinic information.
Socratic is designed for clinics handling sensitive health information, with clear boundaries around what information is used, how it is protected, and what it is not used for.
Updated 16 March 2026
What information Socratic handles
Socratic handles the information needed to provide the service in practice.
That can include consult content, note drafting context, and, if your clinic connects Cliniko, the nearby appointment and note context needed to prepare and save notes in the right place.
What that information is used for
Socratic uses this information to provide the service to your clinic.
That includes capturing consult context, preparing notes, keeping work available while you are using the product, and, where relevant, supporting your note workflow with connected systems.
What clinic information is not used for
Clinic data is used to provide Socratic to your clinic.
It is not used to train Socratic's own models.
How information is protected
Data is transmitted over encrypted connections and stored encrypted at rest on hosted infrastructure.
Access is tied to signed-in accounts and the clinic context connected to those accounts.
How this relates to Australian clinics
Socratic is designed to support Australian clinics handling personal and health information with the care expected when working with sensitive information.
That includes narrow service-related use of data, careful handling of clinic information, and clear boundaries around what that information is used for.
Providers behind the product
Socratic relies on established providers for hosting, storage, account access, transcription, and language features.
If your clinic is reviewing infrastructure or providers as part of internal diligence, we are happy to answer specific questions directly.
More questions?
If your clinic wants more detail for internal review, we are happy to talk through:
- what information Socratic handles
- what that information is used for
- how information is protected
- what providers sit behind the product
- what your team should expect in practice