Data and privacy
Recording notice, retention, caller erase, and where call data goes.
Calls to a clinic can contain health information. These settings live in Settings → Data & privacy and are changed by owners and admins.
Callwise is not yet certified or audited for HIPAA, GDPR or KVKK, and has no business associate agreements with its providers. Don't route real patient calls through this build.
Recording and the recording notice
| Setting | Effect |
|---|---|
| Record calls (on/off) | When off, no audio is stored. Transcripts and summaries are still kept. |
| Recording notice | The sentence the agent says at the start of a recorded call, for example "This call may be recorded so we can improve our service." |
Consent rules for recording differ between US states and between countries; some need every party to agree. Check yours before turning recording on.
Recordings are kept in a private storage bucket. A file can only be opened by someone with at least view on Receptionist in that workspace. Nobody can upload or replace a recording from the app.
Retention
Retention days sets how long recordings and transcripts are kept. The demo workspace uses 365 days.
Erasing a caller
From a caller's profile, Erase caller data removes their name, phone number and notes and anonymises their past calls. It needs publish on Callers and can't be undone. The action is written to the audit log.
Where call data goes
| Service | Gets | Status in this build |
|---|---|---|
| Telephony carrier | The call audio and phone numbers | Simulated |
| Speech (speech to text, text to speech) | Call audio and the agent's replies | Part of the voice service contract |
| Anthropic Claude | Transcripts, to write summaries and classify intent and sentiment | Simulated by built-in rules; real calls only in local database mode with ANTHROPIC_API_KEY |
The full list with the facts to verify is under Connections.
Audit log
Owners and admins can see an audit log of sensitive actions such as publishing, erasing callers and changing access. A user can only write entries as themselves, never as another user or as the system.