KVKK
KVKK-aligned data processing: the clinic is controller, VetBis is processor
For patient and pet owner records the data controller is your clinic; VetBis processes that data on the clinic's instruction. For account, invoice and support data the controller is MTY Teknoloji A.Ş. The binding texts are the KVKK privacy notice and the personal data processing policy; this page does not summarise them.
The nine rights under KVKK Article 11
To learn
Learn whether personal data is processed.
To request information
Request information if it has been processed.
To learn the purpose
Learn the purpose and whether it is used accordingly.
Transfer information
Know the third parties data is transferred to, in Turkey or abroad.
Correction
Ask for correction if it is incomplete or inaccurate.
Erasure and destruction
Ask for erasure or destruction within the conditions of the law.
Notice to third parties
Ask for corrections and erasure to be notified to third parties that received the data.
Objection
Object to an adverse result produced solely by automated analysis.
Compensation
Claim compensation for damage caused by unlawful processing.
Who is controller, who is processor
The same software involves three separate roles. Which role does what decides who an application goes to.
- Data controller
The clinic
- Decides the purpose and method of processing patient and owner records.
- Prepares the privacy notice and explicit consent texts.
- Registers with VERBİS where the registration duty applies.
- Holds the duty to notify the Board and the person in case of a data breach.
- Answers owners' applications.
- Data processor
VetBis
- Keeps records on the clinic's instruction.
- Provides tools such as role and branch permission, consent records and the audit log.
- Does not become the controller in the clinic's place and does not issue notices on its behalf.
- Data controller
MTY Teknoloji A.Ş.
- Is the controller of its own customer account, invoice and support data.
- These activities are described in the KVKK privacy notice.
Consent recorded per channel
The product stores an owner's contact permissions per channel and records the date of consent. The example scheme below shows how a change of permission reaches the screen; it is not real patient data.
Reflected on the record
- WhatsApp reminder consent withdrawn, choice and date recorded
Live flowA permission changes 2 / 2
Steps
- 1Current choicesThe owner's per-channel and per-topic permissions are visible.
- 2A permission changesA channel permission is withdrawn and the row updates.
Example scheme. Notification delivery providers are in a separate readiness state; see the notifications feature page for details.
Permission choices are managed on the record; the clinic's obligations on consent history are set out in its own privacy notice.
How to apply
Applications about patient and owner data go to the relevant clinic first; the clinic is the controller. For the account, invoice and support data that MTY Teknoloji A.Ş. processes itself, write to the address below with documents that verify your identity. Applications are concluded within 30 days at the latest.
- Application receivedIdentity is verified
- ReviewWhich role answers is decided
- AnswerWithin 30 days at the latest
Live flowAnswer 3 / 3
Steps
- 1Application received
- 2Review
- 3Answer
Application email