Each clinic isolated from the others
Each clinic's data is separated by row-level isolation in the database: one clinic can never see another's data. Staff join by invitation only.
Security and privacy
Patient data protected at every step: who accesses it, how it is stored and how it can be recovered.
Each clinic's data is separated by row-level isolation in the database: one clinic can never see another's data. Staff join by invitation only.
Two-factor authentication (2FA) via an authenticator app, optional per person and something the clinic can require for the whole team, automatic logout on inactivity and a list of connected devices.
The audit trail, under Settings → Audit, shows who created, changed or deleted information, with date and time, and keeps the history for 12 months.
There is a daily encrypted copy outside the database provider, daily provider backup and a weekly restoration test in a separate database.
The clinic can export its data as CSV and export one patient's data for access and portability requests.
The database is hosted in São Paulo (Brazil) on Supabase. The application runs on Vercel and WhatsApp is operated by Meta. Tests use fictional data only.
Frequently asked questions
Data is isolated per clinic and staff access is by invitation, with optional or required 2FA and an audit trail of who did what.
You can export clinic data to a spreadsheet without asking support.
We keep daily encrypted copies, including an external one, and test weekly that they restore correctly.
Talk with us about Clinnu and implementation for your team.