Security and privacy

Your clinic's data security

Patient data protected at every step: who accesses it, how it is stored and how it can be recovered.

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.

Sign in securely

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.

Everything is recorded

The audit trail, under Settings → Audit, shows who created, changed or deleted information, with date and time, and keeps the history for 12 months.

Backups we test

There is a daily encrypted copy outside the database provider, daily provider backup and a weekly restoration test in a separate database.

Your data belongs to you

The clinic can export its data as CSV and export one patient's data for access and portability requests.

Transparent infrastructure

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

Security without empty promises

Do you read my clinic's data?

Data is isolated per clinic and staff access is by invitation, with optional or required 2FA and an audit trail of who did what.

What happens if I cancel?

You can export clinic data to a spreadsheet without asking support.

What if the server goes down?

We keep daily encrypted copies, including an external one, and test weekly that they restore correctly.

Want to see these controls in your clinic?

Talk with us about Clinnu and implementation for your team.