Security overview

Hosting

Klinikbook runs on servers of Contabo in Germany. The databases, queues, caches and files run on private networks of those servers and are not reachable from the internet; connections from the internet arrive through Cloudflare's protected network.

Encryption and files

• Every connection to Klinikbook is encrypted (TLS), and browsers are told to use encrypted connections only (HSTS).
• Documents and photographs a workspace stores are kept in private storage and opened only through links that expire within minutes.
• Files uploaded to the platform are checked against the format they claim to be, and documents are scanned for malware before they are stored.

Separation between workspaces

Every workspace's records are separated twice: in the application, and by row-level security in the database itself, so a request for one workspace cannot read another's records even if the application made a mistake.

Sign-in and permissions

• Passwords are stored only as salted hashes (PBKDF2); repeated wrong attempts lock the account for a while.
• Two-step sign-in with an authenticator app; required for workspace owners and administrators and for all Klinikbook staff.
• Sessions expire after inactivity and after a fixed time, and can be ended from the account.
• Inside a workspace, roles decide who may see and do what; patients reach only their own records through the portal.

Records and staff access

• Significant actions in a workspace are written to its activity log, and actions of Klinikbook staff to the platform's audit trail.
• Klinikbook staff do not open a workspace's patient records; support looks inside a workspace only with the permission of its owner or an administrator, for a limited time, and on the record.
• Access to the servers is limited to authorised staff, with personal keys, and is recorded.

Backups, updates and monitoring

The databases are backed up every day and the backups are kept for 14 days. The software and its dependencies are kept up to date, and the service is monitored continuously.

Incidents and reports

A security incident affecting personal data in a workspace is notified to its owner without undue delay, where possible within 48 hours, as the Data Processing Agreement describes.

If you find a security weakness, please write to [email protected] with “Security” in the subject before disclosing it. We answer and keep you informed while we fix it.