Data Processing Agreement
Version: 20 November 2026
This agreement governs the processing of personal data between the clinic or business using the ZILKO service and FUBER LTD, under Article 12(2) of the Turkish Personal Data Protection Law No. 6698 (“KVKK”). It forms an integral annex to the ZILKO Terms of Use and is accepted electronically at sign-up or by the admin in the panel. The Turkish version prevails.
Parties
- Data Controller: the clinic or business using the ZILKO service (the “Clinic”).
- Data Processor: FUBER LTD — registered in England and Wales under number 14783209; 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom; hello@fuber.ltd (“ZILKO”).
1. Subject and scope
ZILKO processes personal data on behalf of and on the instructions of the Clinic to handle communication with the Clinic’s patients and customers by phone, WhatsApp, Instagram and Messenger, and to book and record appointments.
2. Data and data subjects
- Data subjects: the Clinic’s patients and prospective patients, people who call or message the Clinic, the Clinic’s staff.
- Categories: identity, contact, message contents, call recordings and transcripts, appointment details, images (photos, x-rays) and health data (special category).
3. Clinic’s obligations
- Ensure a legal basis under KVKK Art. 5 and 6 for the processing.
- Inform data subjects under KVKK Art. 10. ZILKO provides a ready, clinic-specific patient notice page and the assistant shares its link (or the Clinic’s own notice) in its first reply of every conversation; the Clinic is responsible for the accuracy of its content.
- If the call-recording announcement is turned off, inform callers about recording by other means.
- When using automated calls and bulk import, ensure contact permissions and obligations under Law No. 6563 / the Message Management System (İYS).
- Set retention periods in the panel and fulfil its own VERBİS registration obligation (if any).
4. ZILKO’s obligations
- Process data only on the Clinic’s instructions and for the purposes in this agreement; never use it for its own purposes, sell it or share it for advertising.
- Take the technical and organisational measures required by KVKK Art. 12 and the Board’s adequate measures for special category data: TLS in transit, encrypted storage of access keys, separation of clinic data, role-based access, access and activity logs, confidentiality obligations for staff.
- Data minimisation: remove phone numbers, email addresses, Turkish ID, IBAN and card numbers from text sent to AI providers; share only the patient’s first name; route AI requests only to providers that do not retain data or train on it.
- Automatically delete call recordings (including the copy at the voice provider), message contents, media files and call transcripts when the retention periods chosen by the Clinic expire.
- Notify the Clinic of a data breach without delay (within 24 hours at the latest) and provide the information the Clinic needs to notify the Board and data subjects.
- Forward data subject requests (KVKK Art. 11) to the Clinic and assist in answering them.
- Delete, destroy, anonymise or return data on the Clinic’s request or at the end of the agreement, subject to legal retention obligations.
- Provide information demonstrating compliance on the Clinic’s reasonable request.
5. Sub-processors
The Clinic authorises ZILKO to use the sub-processors below. ZILKO informs the Clinic before adding a new sub-processor; the Clinic may object on reasonable grounds.
| Sub-processor | Service | Location |
|---|---|---|
| OpenRouter → OpenAI, Anthropic, Google (only providers that do not retain data or train on it) | Message replies, summaries, analysis | USA and others |
| OpenAI | WhatsApp voice call model | USA |
| Vapi | Phone line and voice assistant infrastructure | USA |
| Deepgram (via Vapi) | Speech-to-text | USA |
| Meta Platforms | WhatsApp, Instagram, Messenger | USA / Ireland |
| Cloudflare | Storage of call recordings and files (EU jurisdiction), site infrastructure | EU / global |
| Oracle Cloud | Server hosting | United Kingdom (London) |
| Google Firebase, Apple | Mobile notifications to the clinic team | USA |
| MXroute | USA / EU | |
| DigiDentis and other booking systems the Clinic connects | Appointment sync | Chosen by the Clinic |
6. Transfers abroad (KVKK Art. 9)
- ZILKO’s servers and some sub-processors are outside Türkiye. As no adequacy decision has been announced by the Board, transfers are made under the standard contracts announced by the Board under KVKK Art. 9(4).
- The Board’s “Controller to Processor” standard contract is signed between the Clinic and ZILKO and notified to the Authority within five business days of signature. ZILKO provides the completed contract and the information needed for the notification.
- “Processor to Processor” standard contracts are signed between ZILKO and sub-processors abroad and notified within five business days.
- For a sub-processor that does not sign a standard contract, ZILKO replaces the provider, stops data from reaching it or processes the data in Türkiye or in a country with adequate safeguards.
7. Term and termination
This agreement enters into force with the service agreement and ends when it ends. On termination, the deletion / return obligation in section 4 applies.