Security Posture

Scope of this page

This is a high-level description of security posture only. It is not a security certification and does not constitute a guarantee.

Tenant isolation and access

• Multi-tenant separation using row-level security (RLS), including FORCE RLS, and request-scoped tenant context as part of the platform's isolation model.
• Authentication and access control for clinic and administrator users.
• Clinic-scoped access so views remain limited to a single tenant.

Logging and audit

Administrative actions are recorded through audit logging, supporting an admin audit posture for review.

Data discipline

Storage is metadata-only by default; raw prompt and output content are not stored in the current product doctrine.

Operational resilience and security audit

A security audit and operational-resilience evidence are a mandatory release-candidate gate before paid pilots or real clinic data. This work includes dependency and vulnerability scanning, backup and tested restore, and a breach and incident-response runbook. These are operational practices and planned controls, not guarantees.

What this page does not claim

This page does not claim SOC 2, ISO, penetration-test, or other security certification, and it does not claim that the platform is breach-proof or secure by guarantee. Specific encryption and hosting-region details are not asserted here and must be confirmed in the security and legal documentation.