Your patients trust you. You should be able to trust us.
How Clinicly is built to keep patient data private, separate and recoverable.
Records in a restricted zone
Clinical notes, intake answers and documents are stored in their own database and file store, separate from scheduling and accounts. Only one internal service can reach them, and it checks every request's clinic and role again.
Append-only audit log
Every read, change, download, search and denied attempt on patient data is recorded with who, what, when and from where, in a separate log that can be added to but never edited or deleted.
Clinic isolation in the database
Each clinic's data is separated by row-level security in the database itself, and every endpoint is tested against access from another clinic.
Roles and least privilege
Five roles, scoped by location. Billing and front desk staff never see clinical notes. Every internal service has its own credentials.
Encryption
HTTPS on every public address. Documents are encrypted with a per-clinic key. Backups are encrypted before they leave the machine that made them.
Tested backups
Frequent encrypted backups of every database, and timed restore drills of the records zone from backups alone.
Your data is yours
The clinic owner can export all of the clinic's data at any time.
Deletion on request
When a patient asks, their data is deleted across scheduling, records and messaging. The audit log keeps only an anonymous reference.
Early access and privacy
Clinicly is in early access and is a demonstration product. Please don't enter real patient information. Use invented names, example.com addresses and +1-555-01xx phone numbers. Email and SMS are delivered to a sandbox only; nothing reaches a real inbox or phone.
We don't sell or share data, and we don't use third-party trackers or analytics on this site or in the app.