Plain facts for your IT, security and privacy reviewers:
Where something is not in place yet, this page says so.
Sophia answers company questions only from approved company sources. She does not fall back to the internet for prices, security or product capabilities.
When the approved sources do not answer, she says so, offers a next step and logs the question for review.
The higher-authority current source wins a disagreement. When sources rank equally, she does not answer that point and it goes to review.
Conversations can propose knowledge changes. A person approves each one, and regression tests run before release.
Sophia can only use a defined set of tools: search approved knowledge, show approved material, record qualification, book, write a CRM record, hand off.
A meeting is booked only after the visitor confirms one specific time. A failed booking is reported as failed.
Every booking, record and handoff carries an idempotency key, so a retry never creates a duplicate.
| Service | What it does in a conversation |
|---|---|
| OpenAI | Speech and reasoning models that hear the visitor and produce answers |
| LiveKit Cloud | Real-time audio transport between the browser and Sophia |
| Anam | Avatar video, only when the avatar is switched on |
| Cloudflare | Delivery of the website |
| Your server | The application, the knowledge, transcripts and records, on a server rented in your company’s name, installed and updated by HumanOps |
Retention at OpenAI, LiveKit and Anam follows their own terms. These accounts and the server are opened in your company’s name, so they bill you directly and you set the spend limits. HumanOps works inside them on an invited seat.
Conversation transcripts and traces on the Sophia server are deleted after 7 days by default. Returning-visitor memory keeps business context only, tied to the browser, and the visitor can clear it at any time. The visitor’s IP address is not stored to pick a language.
Text inside your documents and inside visitor messages is treated as data. An instruction hidden in a document does not change what Sophia does, and she never reveals her internal instructions. API keys stay on the server. The browser receives only a short-lived token for one conversation.
A visitor can ask for a person at any time. On this site, in HumanOps working hours, a person from HumanOps joins the conversation live, on camera, and the screen splits between Sophia and the person. Sophia says whether a person is available right now. Outside those hours the visitor gets a reply within one working day or books a meeting. For your deployment, who receives a handoff, through which channel and in which hours is set during implementation. Legal, contract, discount and complaint topics always go to a person. Sophia says she is an AI whenever asked, and the page discloses that the voice and avatar are AI-generated.
Book 30 minutes and we go through it line by line, including the parts that are not ready yet.