Every record belongs to one clinic
Clinic context is resolved from the request and applied across the product's workflows. One clinic's patients, invoices, messages and images are not reachable from another clinic's session.
Security & data
This page describes controls that exist in the product today. Where something is an operational practice rather than a certification, we say so — a dental clinic choosing software should not have to decode marketing language to find out what is actually protecting its patients.
Controls in the product
Clinic context is resolved from the request and applied across the product's workflows. One clinic's patients, invoices, messages and images are not reachable from another clinic's session.
Nine clinic roles and twenty-two permissions. The check runs on the server for pages, actions and API routes alike — not in the browser, where it could simply be skipped.
The tokens that let us send on your behalf are stored encrypted and scoped to your clinic. They are never exposed to the browser.
Inbound WhatsApp traffic is verified against an HMAC-SHA256 signature before anything is persisted. An unsigned request is rejected outright.
Sensitive actions write audit records, so there is an operational trail of who did what. Clinical corrections are recorded rather than silently overwriting the original.
Operational exports are part of the product. Choosing ConphiDent does not mean your clinic's history becomes hostage to it.
Accounts & files
The parts of the system most likely to be asked about in a procurement conversation, stated plainly.
Being straight with you
Questions before you commit
We would rather answer a difficult security question on a call than have you find the answer later.
See also our privacy policy and data deletion process.