Privacy
COS GP is an alpha clinician testing environment. This page describes how data is handled today, what is not yet implemented, and the architectural direction toward GDPR and NHS-readiness.
What we collect
- Clinician account: email and authentication metadata.
- Consultation data created by clinicians: messages, AI summaries, structured outputs, sign-off decisions, audit events.
- Patient identifiers entered by clinicians (e.g. name, NHS number, DOB). During alpha, do not enter identifiable patient data — use test personas only.
How data is protected
- All consultation data is scoped per clinician using Postgres row-level security.
- Authentication via secure email/password; sessions persist via the platform's auth provider.
- Secrets are stored as server-side environment variables, never in client code.
- Audit log captures clinician actions on consultations and AI outputs.
What is not yet in place
- NHS organisational workspaces, role hierarchies and DPIA documentation.
- Patient-side consent flows, deletion requests and data export tooling.
- Production-grade encryption-at-rest review and pen-testing.
Your responsibilities as an alpha tester
- Do not enter identifiable patient data.
- Do not use COS GP for real patient care or in emergencies.
- Treat all AI output as a draft requiring clinician judgement.
Contact
For data questions during alpha, contact your workspace admin. Production data handling and DPO contact details will be published before any live patient use.