ProductPrivacy and compliance centre
Privacy texts live from day one, requests answered on time
Klinikbook's compliance centre fills privacy notice and consent templates with your clinic's details, publishes them in versions on your portal, and tracks data subject requests to their deadline while carrying out what you decide. You remain the data controller: the final texts and the decisions are yours.
- Versioned notices and consents
- Data requests with deadlines
- A retention policy

Was your privacy notice copied from another website?
How it usually goes
- The privacy notice was adapted from someone else's site.
- There is no separate explicit-consent text for health data.
- Nobody knows which version was published when.
- A data request waits in an inbox; the deadline is in nobody's calendar.
With Klinikbook
- Templates are filled with your legal name and address, then published.
- Every version is kept unchanged and readable on the portal.
- Each request shows its deadline, with a reminder three days before.
- You decide; Klinikbook carries the decision out.
Consent records
Who agreed to what, and when, on the contact
Privacy notice confirmations, explicit consent, photo and marketing consent sit in the contact's consent history, with the text and version each was given on. On the portal's My data page the patient sees and withdraws them.
- Marketing consent per channel
- Photo and video consent per use
- Restriction of processing

Access
You decide who sees what
Everyone signs in with their own account and sees what their role allows. Klinikbook's team looks at your workspace only if you allow it, for a limited time and without seeing patient records.
- An activity log with CSV
- Support access for 1 to 72 hours
- The data processing agreement in the workspace

What the compliance centre includes
- Photo and marketing consentTemplates for photo and video consent with each use ticked separately, and marketing consent per channel.
- Data requestsCopy (zip), rectification, erasure, restriction and objection; from the portal or logged by you, each with its deadline.
- Retention policyLost leads and intakes never sent are deleted daily once the period you set has passed.
- Licence recordsRecord your licences and authorisations, and optionally have Klinikbook check them in the register for a “verified” mark.
How it works
Review the ready texts
When the workspace is created, the privacy notice and consent text are prepared from the country pack and published; adapt them to how you work.
Publish a new version
The portal, lead forms and booking page show the version you publish; earlier versions stay on record.
Close requests on time
You are notified of each request; you decide, and the outcome reaches the person by e-mail and on the portal.
Sources
- Law No. 6698 on the Protection of Personal Data (Turkish) — Mevzuat Bilgi Sistemi, 2016-04-07
- Regulation (EU) 2016/679 (General Data Protection Regulation) — EUR-Lex, 2016-04-27
Who is the data controller, and what is Klinikbook's role?
Your clinic is the controller for your patients' data. Klinikbook processes it on your behalf as processor, as set out in the data processing agreement accepted when the workspace is created.
Can I use the template as it is?
It is filled with your clinic's details, but every clinic works differently. Adapting and publishing it is your responsibility; we recommend a lawyer checks it.
Where is the data kept?
The servers are currently in Germany. The Türkiye pack's privacy notice template describes this as a transfer abroad; review that part too before publishing.
What happens when a patient asks for erasure?
You log the request and decide. If you erase, the person is removed from every part of Klinikbook; the request and the steps taken remain as evidence.
Can Klinikbook staff see our patient data?
No. Support sees only your activity log, only through time-limited access you grant, never patient records, and every look is logged.
Related reading
30-day free trial
Try Klinikbook with your own team
Every feature is open for 30 days, and no card is needed to start.
