Security & your data
Your clinic trusts us with appointments, patient files and payments. This page explains, in plain terms, who owns that data, where it lives and how we protect it. We only describe what is in place today.
You own your data
Your clinic's data belongs to you. We are its custodians: we store and process it to run the service for you, and you remain its owner.
You can export any dataset, or everything at once, at any time from Settings → Data, as Excel or CSV files. You do not need to ask us.
If you cancel, we keep your data for 90 days so you can come back or download it. After that, it is deleted.
Where your data lives
- Database: Neon serverless PostgreSQL. Neon is part of Databricks, which acquired it in 2025. Our database runs on Amazon Web Services (AWS) in the European Union, in Frankfurt (eu-central-1).
- Application: hosted on Vercel, in its EU region in Frankfurt (fra1).
Certifications our providers hold
Clinivly runs on infrastructure from providers that are independently audited. These certifications belong to our providers, not to Clinivly itself.
Neon
Our database provider.
- SOC 2 Type 1
- SOC 2 Type 2
- SOC 3
- ISO/IEC 27001
- ISO/IEC 27701
- GDPR
- CCPA
Vercel
Our application hosting provider.
- SOC 2 Type 2
- ISO/IEC 27001
Amazon Web Services
The data centres our database runs in.
- ISO 27001
- SOC 1
- SOC 2
- SOC 3
How we protect it
Encryption in transit
Every connection to Clinivly uses HTTPS (TLS), so data travelling between your browser and our servers cannot be read on the way.
Encryption at rest
Our database provider encrypts the data it stores on disk.
Extra encryption for sensitive fields
Sensitive values, such as national ID numbers and saved payment tokens, are encrypted by Clinivly itself (AES-256-GCM) before they are written to the database.
Each organization's data kept apart
Row-level security in the database limits every query to the data of one organization, so one clinic can never see another clinic's records.
Roles and permissions
You decide who on your team can see and do what. Each role has its own permissions.
Two-factor authentication
Sign-in can be protected with a one-time code from an authenticator app, with backup codes.
Confirmation for sensitive actions
Sensitive actions, such as exporting all of your organization's data, ask you to confirm it's you again first.
Audit log
Sign-ins and important changes are recorded, so you can see who did what and when.
Card details stay with Paymob
Subscription payments are handled by our payment provider, Paymob. You enter your card on Paymob's page; card numbers never reach our servers. We keep only a reference to a saved card, with its brand and last four digits.
Backups and recovery
Our database provider offers continuous point-in-time recovery, which lets us restore the database to an earlier moment if something goes wrong.
Questions about security
If you have a question about security, or you think you have found a problem, email us at Clinivly@gmail.com.