Security

Patient data deserves more than a password

Healy is built for clinics, so protecting patient information is part of the design, not an add-on. Here is how it works.

Clinic isolation

  • Every record belongs to exactly one clinic, enforced by the database itself (row-level security), not only by application code.
  • Links between records are constrained to the same clinic, so cross-clinic references are impossible.
  • Platform administrators see clinic metadata and counts, never patient conversations or appointments.

Patient verification

  • A WhatsApp number is not treated as proof of identity.
  • Patients confirm their identity before any appointment is shown, booked, moved or cancelled.
  • Outside WhatsApp's 24-hour window, only pre-approved templates without clinical details are sent.

Staff access

  • Every staff member has their own login; shared accounts aren't needed.
  • Roles (admin, receptionist, billing staff) decide what each person can see and do.
  • Roles are checked on every request, so a role change or removal takes effect immediately.
  • Passwords are hashed with Argon2id, and repeated failed logins lock the account temporarily.

A careful assistant

  • The assistant handles administration only and never gives medical advice.
  • Its answers about the clinic come from content your clinic approved and published.
  • It can only use a small set of actions, and every action is re-checked against the patient's verified identity and your clinic's rules.
  • A booking is only reported as confirmed after the clinic system confirms it.

Auditing and retention

  • Bookings, messages, staff actions and setting changes are recorded in an append-only audit trail.
  • Message contents expire after a retention period; the audit record of what happened remains.
  • Patient contact details fetched from the clinic system are used for the task at hand and not stored.

Secure by default

  • Connections are encrypted in transit.
  • Incoming WhatsApp messages are accepted only with a valid signature from Meta.
  • Sessions are kept in secure, HTTP-only cookies that page scripts can't read.

Found a security issue?

Please tell us privately so we can fix it quickly. We appreciate responsible disclosure.

Contact us