Privacy Notice

This notice is provided under Türkiye's Personal Data Protection Law No. 6698 (KVKK) to explain the personal data processed through the Klinbook software.

This English version is a translation provided for convenience. The Turkish text is the binding version.

1. What is this notice about?

Klinbook is software in which clinics keep their appointment, patient file, treatment, stock and payment records. This notice explains which personal data is processed when the software is used, where that data is kept, with whom it is shared, and the rights of data subjects.

It covers two groups of data subjects: patients who apply to a clinic, and clinic employees who use Klinbook.

This website (klinbook.com) contains no cookies, analytics software or tracking code of Klinbook's own, and no client-side script runs on its pages. However, the site is published through Cloudflare as its content delivery network; Cloudflare processes visitors' IP addresses and connection information for security and delivery purposes and may set its own cookies. See section 7 for details.

2. Data controller and data processor

For patient and employee data, the data controller is the clinic using the software. The clinic decides which patient is recorded, which data is entered and how long the data is used.

Klinbook is a data processor that handles this data only on the clinic's instructions and only as far as the software needs in order to work. Klinbook does not use clinic data for its own purposes, does not sell it and does not process it for advertising.

For the data Klinbook processes in its own customer relationship (the contact details of clinic representatives, subscription and billing records, support correspondence), Klinbook is the data controller.

In this context the data controller is: MEHMET ALİ BÖBECİ, Kınıklı Mah. Fakülte Cad. Böceci Apt. No: 16 İç Kapı No: 3, 20160 Pamukkale / Denizli, Türkiye. Tax office: Pamukkale, tax ID 1860738864. Phone: +90 530 609 46 88. Email: destek@klinbook.com.

See section 11 for the status of registration with VERBİS, Türkiye's data controllers' registry.

3. Personal data processed

The table below shows the fields the software actually holds in its database. Whether a field is filled in depends on how the clinic uses it; mandatory fields are marked.

Data groupData processed
Patient identity dataFirst and last name (mandatory); identity type and number — Turkish ID number, passport or foreign ID number (mandatory); date of birth; gender; patient number.
Patient contact dataPhone number, email address, postal address.
Appointment dataAppointment date and time, doctor, appointment status, where the appointment was created, and the reason for the appointment and for any cancellation as free text.
Health data (special category)Patient notes and medical alerts. The content of these two fields is end-to-end encrypted — see section 4. Also the procedures performed and the materials used in them.
Financial dataProcedure fees, collections, refunds, patient balance and related document records.
Stock dataWhich patient a serial-tracked material was used on.
Employee dataFirst and last name, email address, phone, position, employment type, start and end dates, tax number; in encrypted form, gross salary, social security number and IBAN; payroll items (gross and net pay, social security premiums, income and stamp tax, additions and deductions).
Account and session dataThe user's email address, a verification hash of the password (the password itself is not stored), last sign-in time, app preferences, mobile notification token.
Transaction security dataAudit log: which user viewed or changed which record and when; these records also include the IP address and browser or app information.
Communication recordsA record of WhatsApp and email notifications sent. These records hold the recipient's number or address in masked and hashed form, not in the clear.

Payment card details are never stored by Klinbook at any stage. Subscription payments are taken on the payment provider's own page; Klinbook records only the status and amount of the payment and the reference number the provider issues.

4. Encryption: what Klinbook can and cannot read

This section exists to state plainly the aspect of the software most open to misunderstanding. The software has two separate encryption schemes, and they do not protect to the same degree.

The content of patient notes and medical alerts is end-to-end encrypted. Encryption and decryption happen on the clinic's own device; the server stores only encrypted bytes. The Klinbook server does not hold a key that could open this content and has no function for doing so. The unavoidable consequence is this: if a clinic loses all of its users' passwords and its recovery key together, this content becomes permanently unreadable. Klinbook has no method, backup key or support procedure for recovering it.

An employee's gross salary, social security number and IBAN are encrypted on the server. This protects against an attacker with direct access to the database files; it does not mean Klinbook cannot read this data. The decryption key is in the application's own configuration.

All other fields — including the patient's name, identity number, phone, address, appointment reason, financial records and payroll amounts — are held in the database in the clear. These fields are protected by disk-level encryption, TLS in transit and authorisation rules within the application. Klinbook can technically read these fields.

Identity numbers, names, phone numbers, email addresses, dates of birth, postal addresses and note content are not written to application logs; these field names are masked in the logging layer.

5. Purposes and legal grounds

Data is processed so that the clinic can deliver healthcare and meet the administrative, financial and legal requirements of doing so. The main purposes are: planning and reminding of appointments, keeping patient files, recording procedures and materials used, charging and collection, staff and payroll management, securing accounts and detecting unauthorised access.

The main legal grounds a clinic relies on are: necessity for the formation or performance of a contract (KVKK art. 5/2-c), compliance with the data controller's legal obligations (KVKK art. 5/2-ç — in particular the record-keeping obligations of tax and commercial law), and legitimate interest provided it does not harm the fundamental rights and freedoms of the data subject (KVKK art. 5/2-f).

Health data is special-category personal data. It is processed by healthcare professionals under a duty of confidentiality for the purposes of delivering healthcare and planning its financing (KVKK art. 6/3). Where these conditions are not met, explicit consent is required. Which processing activity rests on which legal ground must be stated in the notices and consent texts of the clinic, as data controller; this point is listed in section 11.

6. Where data is kept and transfers abroad

Klinbook runs on Amazon Web Services (AWS), and all data is processed and stored in AWS's Europe (Frankfurt) region — technically eu-central-1. The database, cache, file storage, backups and application servers are in this region.

This means personal data is processed outside Türkiye. At the time of writing, the legal mechanism for the transfer abroad under KVKK art. 9 (standard contract, undertaking or explicit consent) has not been determined. This is listed plainly in section 11.

Database disks and file storage are encrypted; the database accepts no unencrypted connection; all traffic between browsers or the mobile app and the server travels over HTTPS. Backups are taken in the same region by a managed backup service.

7. Recipients

The service providers below are used. Amazon Web Services and Cloudflare are mandatory and not a matter of choice: the entire software runs on AWS — this is the transfer abroad described in section 6 — and this website is published through Cloudflare. Whether the other providers in the table are used depends on Klinbook's configuration and the clinic's preferences.

ProviderData transferredPurpose
Amazon Web Services (Frankfurt, eu-central-1)All data in the softwareServers, database, file storage, backup and email delivery (Amazon SES).
CloudflareIP address and connection information of visitors to this sitePublishing the klinbook.com pages and content delivery. Cloudflare processes this data for security and delivery purposes and may set its own cookies. The software's own data is outside this scope.
Meta (WhatsApp Business Platform)Recipient's phone number and message contentSending appointment reminder and information messages over WhatsApp.
Apple (APNs)Device notification token and notification textSending push notifications to clinic employees' mobile devices.
iyzicoSubscriber's billing email and payment amountCollecting the Klinbook subscription. Card details never reach Klinbook.

Beyond these, transfers made on the statutory requests of authorised public institutions are reserved. Klinbook never uses data for advertising, profiling or sale to third parties; the software contains no analytics or tracking tool.

8. Retention and deletion

Nothing in Klinbook is permanently deleted. This is a deliberate product decision: patient records, clinical data and financial records are retained, and anonymisation is applied to the record instead of deletion. The software runs no bulk data destruction job.

The account of a clinic whose subscription ends is closed logically: access is stopped at the authorisation layer, while the data continues to be kept, undeleted and isolated. When the clinic subscribes again it regains full access to its records.

The database holds a retention marker (purge_after). This field is only a marker for review; no job reads it and it deletes no data.

Audit logs are kept indefinitely and cannot be changed; they are protected both by a database-level constraint and by revoking the application user's privileges.

A patient's deletion request is met by anonymising the record: first and last name, identity number, phone, email, date of birth, gender, address and the medical alert field are cleared, and the encrypted content of patient notes is reset; financial and operational records are kept because of the retention obligations of tax and commercial law. The details of this process and how to request it are on a separate page, available in Turkish.

Account closure and data deletion page (Turkish)

Anonymisation cannot be undone in the live database. However, backups taken before it preserve the state at that moment; if a backup is restored in a disaster recovery scenario, anonymisations must be reapplied, and this step is part of the recovery procedure.

9. Your rights under KVKK art. 11 and how to apply

Under KVKK art. 11, as a data subject you have the right to: learn whether your personal data is processed; request information if it is; learn the purpose of processing and whether data is used accordingly; know the third parties in Türkiye or abroad to whom data is transferred; request correction of incomplete or inaccurate data; request erasure or destruction under the conditions set out in the law; request that corrections and erasures be notified to third parties to whom the data was transferred; object to an outcome against you arising solely from analysis by automated systems; and claim compensation for damage caused by unlawful processing.

Applications about patient data are made to the clinic, which is the data controller. The clinic meets the request through the Klinbook software.

You can send questions about how the software works, and cases where you cannot reach the clinic, to destek@klinbook.com. As a data processor, Klinbook forwards the requests it receives to the relevant clinic and acts on the clinic's instructions.

The software has no interface that shows a data subject their own audit records directly; such requests are met manually through the clinic.

10. Technical and administrative measures

The technical measures actually applied in the software today are:

  • Passwords are stored hashed with the argon2id algorithm; the password itself is not kept anywhere.
  • Each clinic's data is separated row by row in the database itself, not in the application layer: the rule starts closed, and no record is returned unless it has been established on which clinic's behalf the work is being done.
  • Every operation is checked against which clinic the user belongs to and which role they hold; an operation with no explicitly defined permission is refused.
  • Session tokens are short-lived, the refresh token is single-use, and all sessions end when a password is changed.
  • Rate limits apply to the sign-in, password reset, online booking and verification code endpoints.
  • Personal data and secret fields are masked in application logs.
  • Audit logs cannot be changed or deleted.
  • The database and file storage are kept encrypted; all network traffic travels over TLS.

11. Matters not committed to in this notice or not yet settled

The following had not been decided at the time of writing. They are deliberately left open; none of these items should be read as a commitment.

  • Registration with VERBİS (the Data Controllers' Registry) has not been made.
  • There is no signed data processing agreement (DPA) between a clinic and Klinbook; the text is ready and awaits signature with the pilot clinic.
  • The basis under KVKK art. 9 for processing data abroad (Frankfurt) has not been determined.
  • Because this website has no cookies of Klinbook's own, no separate cookie policy has been prepared. Cookies of Cloudflare, which publishes the site, are outside this assessment.
  • The screen for writing a patient note exists today only in the mobile app; a note-writing screen in the web panel is not yet live.
  • There is no interface where a data subject can see their own access records.
  • There is no separate deletion flow for people who filled in the online booking form but did not become patient records.

12. Changes to this notice

This notice is updated as the software evolves. The version in force is always published on this page. When the legal review is complete, the draft warning at the top of this page will be removed and the notice's effective date will be stated.