Security and privacy, by architecture
What leaves your building
bitHuman cloud
- Portrait
- Uploaded once to create the avatar (Reaches bitHuman)
- Live audio
- Reaches bitHuman, encrypted in transit (Reaches bitHuman)
- Avatar video
- Rendered by bitHuman, streamed to you (Reaches bitHuman)
- Usage reports
- Metered by bitHuman (Reaches bitHuman)
Your servers
- Portrait
- Uploaded once to create the avatar (Reaches bitHuman)
- Live audio
- Goes where the conversation runs (Your services)
- Avatar video
- Stays on your machine (Stays on your hardware)
- Usage reports
- No audio, video or conversation text (Reaches bitHuman)
On the device
- Portrait
- Uploaded once to create the avatar (Reaches bitHuman)
- Live audio
- Goes to your app's voice services (Your services)
- Avatar video
- Renders and stays on the device (Stays on your hardware)
- Usage reports
- Usage metering only (Reaches bitHuman)
Fully offline
- Portrait
- Uploaded once to create the avatar (Reaches bitHuman)
- Live audio
- Stays on the machine (Stays on your hardware)
- Avatar video
- Stays on the machine (Stays on your hardware)
- Usage reports
- Metered on the machine (Stays on your hardware)
With the web embed, the conversation runs on bitHuman's servers, even when the avatar renders in the tab.
Controls
Encrypted in transit
Connections use HTTPS (TLS); WebRTC encrypts real-time audio and video in transit (DTLS-SRTP).
Roles and audit log
Organization roles, an audit-log API, and secret rotation that revokes the old secret immediately.
No training without opt-in
“We do not use your content to train our AI models unless you explicitly opt in.”
Deletion
Deleting an agent deletes its records, including transcripts, and its model files.
No stored transcripts
Sessions that render on your hardware store no transcript at bitHuman.
Created in the cloud
Creating an avatar from a portrait happens in the bitHuman cloud, in every mode.
Compliance starts with where the data goes
HIPAA, GDPR and CCPA obligations follow the data, so we start with architecture.
In on-device, self-hosted and offline deployments, patient and customer conversations stay in systems you already govern, and your existing programs apply.