Security and data handling

Voxlera handles health-related personal data for dental clinics, which Turkish law (KVKK) and, for EU patients, the GDPR treat as special-category data. Everything below applies to embeds today and will apply to the API.

#Tenant isolation

Each clinic’s data is isolated at three levels: in the application, in the data access layer, and in the database itself through row-level security. A request made for one clinic can’t read or change another clinic’s data, even if the application had a bug.

#Transport and storage

• All traffic uses HTTPS.
• Call recordings are stored in private storage and are only ever served to authorised staff; there are no public recording links.
• Secrets that clinics give Voxlera, such as messaging-provider tokens and calendar access tokens, are encrypted at rest. Only the last few characters are ever shown back.
• A clinic’s practice-management API key is passed to the integration relay and not stored in Voxlera’s database.

#Consent and disclosure

• Voxlera only contacts a patient on a channel with an active consent record, and keeps the evidence of each consent.
• Every AI call opens by saying it is automated and recorded. Clinics cannot remove this.
• The embeds collect consent with a checkbox that is unticked by default, and show a link to the clinic’s privacy notice when the clinic has one.

#Patient rights

Clinics can export all data held about a patient, or erase it, from the dashboard; requests to correct data or restrict its processing are handled with Voxlera’s help. Erasure removes the patient’s identifying details, message and call content, and recordings, while keeping an anonymised record that consent once existed — which the law requires. See Privacy and KVKK.

#Audit logging

Changes to patient data, and deliberate access to it (such as playing a recording or exporting a patient’s data), are written to an audit log that records who did what, when, in which clinic.

#Guidance for integrators

• Collect only what you need. Don’t add fields to a clinic’s site that duplicate what the embed collects.
• Don’t copy patient data out of Voxlera into other systems without the clinic’s documented agreement and a lawful basis.
• Don’t put personal data in URLs, logs or analytics events — including on pages that host an embed.
• Keep your site’s analytics away from the embed. It runs on a separate origin, so your page’s scripts can’t read it; don’t try to work around that.
• Report problems privately. If you find a security issue, tell the clinic’s Voxlera contact rather than posting it publicly.