This page describes the measures Clinigim takes today to protect your data. Every item here matches running code.
Server and database run in a data centre in Türkiye; patient files and the encrypted backup copy sit in separate, non-public storage in the European Union.
All traffic travels over encrypted connections; sensitive clinical notes are stored encrypted in the database.
Authorisation defaults to deny; permissions are re-checked on every request, and clinics can’t reach each other’s data.
A strong password rule, two-step verification and sign-out on all devices.
Change history on core records and a patient-file access log are kept while the account exists; the audit log on the clinic’s screen is kept for 24 months.
The database is backed up regularly and backups are kept apart from the server.
The application server and the database run in an enterprise data centre in Türkiye; the encrypted backup copy of the database is kept in data centres inside the European Union.
Patient files are kept in separate, non-public storage in data centres inside the European Union. A file is served only to an authenticated user who is authorised to see it; files have no public link.
The providers we use and their obligations are governed by the Data Processing Agreement.
All traffic between the browser and the server travels over an encrypted connection (TLS); unencrypted connections are refused.
Free-text clinical notes are stored in the database with strong, industry-standard encryption, and later tampering with a stored record is detectable. The same protection applies to the change history of those notes.
Other patient information is protected by access, authorisation and network controls.
Authorisation denies by default: if no permission has been explicitly defined for an action, the action cannot be performed.
Roles and permissions are re-checked on every request. When a clinic owner revokes a staff member’s permission, the change applies immediately — there is no need to wait for them to sign out.
Each clinic’s data is kept separate and the separation is enforced on the server: one clinic cannot reach another clinic’s records.
Passwords follow a strong password rule; common and weak passwords are warned about before they are accepted.
Two-step verification works with an authenticator app and single-use recovery codes. Each user can switch it on for their own account; a clinic owner can require it for their staff.
Repeated failed sign-in attempts are limited.
“Sign out on all devices” closes every open session on the server side. Changing or resetting a password also ends open sessions.
A change history is kept for the main records: who made each change, and when.
A clinic can read its own audit log inside the app — who did what, and when. Those entries are kept for 24 months; if the clinic is deleted, they are permanently deleted 30 days later.
Every access to patient files, and every export, is recorded too.
A full database backup is taken regularly.
Backups are stored apart from the server — losing one machine does not mean losing the data.
The restore steps are written down and reviewed regularly.
If you have found a vulnerability, write to us. We ask you not to disclose it publicly until we have confirmed and fixed it; in return we commit to answering you and shipping the fix quickly.
Please do not touch real patient data, do not run tests that would disrupt the service, and do not keep any data you reach.