Healthcare

Patient-facing avatars that keep conversations inside your network

For workloads involving protected health information, deploy bitHuman on the device or on your own servers with a speech and language stack you control. In that configuration no PHI is sent to bitHuman, and sessions store no transcript with us. Your organization remains responsible for its HIPAA determination; we'll walk your privacy and security teams through each data flow.

Where it helps

A face and a voice where patients and visitors already wait or ask:

  • Front-desk and wayfinding kiosks
  • Patient-education screens
  • Intake assistance
  • Multilingual greeting

How the data flows

The avatar renders on the device or on your own servers, so its audio and video stay there. Speech recognition, the language model and the voice run where you point them: the CLI's local conversation brain on a Mac or Linux machine, or your own services inside your network. bitHuman then receives a credential check when a session starts, the avatar download, and usage reports with no audio, video or conversation text.

Creating an avatar from a portrait happens in the bitHuman cloud; the finished avatar model then runs on your hardware.

Clinical content

Your application controls what the avatar says; clinical content and review stay with your team.

Working with us

Healthcare deployments are set up under an enterprise agreement and review.

Where it renders, and what reaches bitHuman

Your servers

The avatar renders
On your own Mac or Linux machines, on-premises or in your cloud account; a standard Linux PC needs no GPU
The conversation runs
Your choice: the CLI's local conversation brain, your own speech and language services, or bitHuman's
What reaches bitHuman
A credential check when a session starts, the avatar download, and usage reports with no audio, video or conversation text
Internet
To start a session; rendering continues through a network drop of up to 5 minutes

Your servers in the docs

On the device

The avatar renders
On the iPhone, iPad, Mac or Android device in front of the user, or in a WebGPU browser tab
The conversation runs
Your app's choice; with the web embed, on bitHuman's servers
What reaches bitHuman
With your own voice and language services, usage metering only — never audio, video or conversation text
Internet
To start a session; rendering continues through a network drop of up to 5 minutes

On the device in the docs

Questions

Is bitHuman HIPAA compliant?

HIPAA compliance is a property of your program and deployment, not of a single software component. bitHuman can be deployed so that no protected health information reaches bitHuman — on the device, on your own servers with speech and language services you control, or fully offline — and sessions that render on your hardware store no transcript with us. Healthcare deployments are set up under an enterprise agreement and review; contact us to walk through your data flows.

Does customer audio or video leave our network?

When the avatar renders on your hardware, its audio and video stay there. The conversation runs where you choose: the CLI's local conversation brain, your own speech and language services, or bitHuman's cloud voice service. With the first two, bitHuman receives usage metering only — never audio, video or conversation text. In the bitHuman cloud, and with the web embed, audio and conversation are processed by bitHuman and its service providers to run the session.

Does bitHuman train on our data?

No. We do not use your content to train our AI models unless you explicitly opt in.

Next steps