Privacy and consent
What KTB records, who decides, and the documentation-only promise.
KTB Health is built around a simple position: the physician decides, KTB records. This page explains what that means for patient data.
What is recorded
- The consultation note — transcript and structured anamnesis, edited and approved by you.
- Session audio — when capture is enabled, audio is stored securely so the transcription pipeline can do its job (see Transcription and audio).
- Consent timestamp — the moment you declare patient consent is kept as an audit trail (LGPD).
What KTB does not do
- It does not diagnose, triage, or recommend treatment — anywhere, ever.
- It does not make clinical decisions; every draft is machine output that a clinician reviews and owns.
- It is not a replacement for the medical record system your clinic is legally required to maintain — it's a documentation tool that feeds it.
Consent
Recording an encounter requires the patient's consent. You declare it in the app before capture starts, and that declaration is timestamped. If consent is withdrawn or wasn't given, don't record — the feature is designed around that gate, not around bypassing it.
Your clinic's responsibilities
KTB provides the tooling; your practice remains the data controller. That means your clinic's privacy policy, retention schedule, and patient notices apply. Work with your administrator on retention and access policies — KTB enforces access control and keeps the consent trail, but policy is yours to set.
Questions
For data-handling details relevant to procurement or compliance review, see the Business section.