Security
A clinical record deserves specifics.
This page says what protects your patients' records in Clinidiary today — and, further down, what is next on the roadmap.
Private by design
Your records stay with your practice
Every record is tied to your own practice and is seen only by your team. We test exactly that, two clinics side by side, before every release.
Encrypted in transit, everywhere
Every connection — browser to server, patient portal, booking page — is HTTPS with certificates renewed automatically, so every path to the application is encrypted.
Nightly backups, kept and checked
The database is dumped every night and before every deployment, with a rolling window retained and a documented restore procedure that is tested, so a backup is one you can rely on.
Who can get in
Three separate front doors
Clinic staff, patients, and Clinidiary's own administrators are three separate identity systems with separate sign-ins on separate hostnames. Each sign-in opens its own screens and only those: patients their portal, staff their practice.
Passwords done properly, and passkeys
Passwords are stored with Argon2id — the current standard — and rate limiting slows guessing to uselessness. Staff can sign in with passkeys (face or fingerprint) instead, and two-factor codes are available to every account. For our own administrator accounts, two-factor is permanent and always on.
Permissions the server enforces
Six roles across more than fifty permissions, every one checked on the server itself. Clinical records stay with the people who treat: reception, accounts and marketing roles are locked out of them by design, and every data-reading route is verified guarded by an automated check on every release.
How the records behave
Each clinic sees only its own
Every query is scoped to the practice it belongs to. A clinic's staff, patients, notes and money are visible to that clinic alone, always.
Every clinical record is kept
Signed notes stay exactly as signed — corrections are amendments. Sent letters are archived for good, each carrying a fingerprint proving it is exactly what was sent, and a stamp of who printed it and when. Indian law keeps clinical records for years, and the software keeps them for you.
Everything is on the record
An audit trail records who did what and when — sign-ins, changes, sends, prints, even actions by our own team on your practice, which are written into your log where you can read them.
What we keep out of reach
Card numbers stay with the card processor
When card payments run through the platform, a payment processor holds the card and Clinidiary keeps only a reference — every time, for every payment.
Secrets are write-only
Connected services' keys can be set and replaced, and they stay sealed once saved: staff, the API and our support team see only that a key is set.
If something goes wrong, there is a plan
A written breach-response procedure sets out the first hour, the first day, and the notification obligations under India's DPDP Act and the CERT-In directions — all decided in advance.
On the roadmap, said plainly
We hold ourselves to the same standards the established players advertise, and we will list each one here once it is true. In progress, in order:
- Independent penetration testing — third-party, scheduled, with findings actioned and re-tested.
- Off-site backup copies — nightly backups already exist; copies to a second location harden them against the worst day.
- Certified compliance (SOC 2 class) — the controls are being built and documented now; certification follows the audit period.
- Verified encryption at rest — stated here once verified end to end.
Questions about any of this — or a security concern to report — reach a person at the contact page, and security reports are read first.