Built to pass your security review.
ClinaraONE handles scheduling and credentialing for anesthesia groups, so protecting staff and patient-adjacent data is the job. Here is exactly how we do it — no vague promises, only controls your team can verify.
How we protect your data
The controls below are built into the product today. Each is something your security team can verify.
Encrypted in transit and at rest
Every connection is served over TLS. The most sensitive secrets — two-factor keys and integration credentials — are encrypted with AES-256-GCM before they are stored, and passwords are salted and hashed with scrypt, never kept in a form anyone can read back.
Each organization's data is walled off
Every record belongs to exactly one organization, and Postgres row-level security enforces that wall inside the database — not just in application code. It fails closed: with no valid tenant context, a query returns zero rows rather than everything.
Least-privilege database access
The application serves every request through a restricted database role that owns nothing and cannot bypass row-level security. The privileged owner connection is used only for migrations and setup, never to answer a user request.
A complete audit trail
Every change to your data writes an append-only audit record — who did what, when, and in which organization — atomically with the change itself. Nothing important happens without a paper trail, and the trail is never edited or deleted.
Two-factor authentication
Accounts can require a time-based one-time code (TOTP) from any standard authenticator app, with one-time recovery codes as a backup. When it is on, a password alone is never enough to sign in.
Built on SOC 2 Type II infrastructure
Our managed service runs on a cloud platform and a managed-Postgres provider that each maintain SOC 2 Type II compliance. This describes the infrastructure we build on; ClinaraONE does not claim to hold its own SOC 2 report.
Run it in our cloud, or in your own
Keep everything in-house if you prefer: ClinaraONE self-hosts in your cloud or on-prem from the same codebase, with the exact same database-level tenant isolation. The isolation model does not fork between the two — only the configuration differs.
Questions from your security team?
We're glad to walk through our controls, share how tenant isolation works, and provide documentation for your review. Reach out and we'll set up time.