VWhose she is
Whose she is.
She works inside a record of your business. This chapter is custody: whose model she runs on — which is not one answer — what happens to what she learned if you leave, and why what she learns is kept apart from what she is authorized to do.
We’re building her own voice.
And the models behind it.
Sabina already includes a model we trained and operate. We are building her own speech and extending that owned model path across the service. Our goal is to keep business content out of outside AI services; that transition is not complete.
As of 6 September 2026, the production voice worker’s settings point to local transcription and our trained reasoning model on rented infrastructure. Transcription and reasoning are separate components. External AI services still handle speech synthesis, message reasoning, and analysis after the call ends on current paths. Removing those dependencies is unfinished migration work, not the intended product architecture. Do not treat the service as outside-AI-free today.
When she is wrong, we answer for it. We remain responsible for the service we provide, including the outside dependencies still in its path. The record of what she did is held in our own system.
The record of a company is part of what an owner hands down. Held on someone else’s terms, it isn’t fully his.
What happens to what she learned if you leave.
Status · designed and filed · not yet runningEach serious buyer asks this eventually, and it is the question this category answers worst: what happens to what she learned about my company if I go?
The answer she is built to give: your contribution comes out. It is removed from what has been learned, and you receive a written attestation that it was removed.
Read the stamp beside the heading before you rely on the paragraph above. That is the design, and it is filed as design. Removal triggered by your leaving is specified; it is not running in production today, and nothing about this site should be read as saying it is. Two things follow. First, what your contribution would come out of is the cross-company panel described on what compounds, which does not exist yet either. Second, until the mechanism runs, what is deliverable is narrower than the paragraph above: deletion of your tenant record, as described under Deletion below and in the agreement. The attestation is part of the design, not something to rely on today. This page will carry the date the stamp changes.
What she learns is not what she’s authorized to do.
What she learns about your business sits in a separate system from the one that governs what she is authorized to do in it. Insight and authority are kept apart on purpose, and the purpose is this: what she learns never turns itself into an action inside your business. Nothing she reads, notices or infers writes her a grant.
Authority is a written object: a sentence you sent her, naming a capability, in force until you withdraw it. Learning is recorded elsewhere, and the gate described on the authority page reads the sentence, not the learning. She may know, from six months of your record, exactly which customer would accept a discount. Knowing it grants her nothing.
Separate systems, by design.
Stated in the shortest form we can state it.
Where she lives
Inside your systems, on your domain, under your identity. The people she deals with are dealing with your company.
What’s separated
Each company that runs her is separated by tenant-scoped access control on shared infrastructure — not a database or schema of her own. Access is scoped to a single company’s identity at the point data is read or written, and the access controls are designed so that one company’s record is not reachable through another’s session.
What we do with your record
We operate it for you. You can read all of it. Tenant-scoped access control governs who may read or write the record; it does not keep a conversation out of outside AI services. Those remaining paths are disclosed in the dated custody chapter above while we build and complete the owned model path. Ordinary hosting, storage and communications infrastructure are separate dependencies. We do not hand your record to another customer or sell it. Any use by us beyond operating it for you needs your specific consent, revocable in writing at any time. What you get back if you leave, and in what form, is a term of the agreement, not a line on this page.
Training
We do not use your business data to train a general model sold to anyone else. What accumulates for you accumulates for you. Said precisely, because the precision is the point: that is a statement about what we do. What the outside companies in her path may do with what passes through them is governed by applicable agreements, not by this sentence.
Deletion
You can require deletion of your record. What that removes and what it necessarily preserves — the fact that something existed and was deleted — is stated plainly in the agreement, not buried. One limit belongs in the same breath: it reaches our own system. It does not reach whatever an outside company holds on its own terms, and we will not describe a deletion as going further than we do.
The commitments governing anything that could ever rise out of your record into a cross-company picture are written out in full on what compounds, including the one that says we will never tell your competitor what to charge.
Ask the harder version of any of these.
Diligence questions get a direct answer from the person who built her, at the formal job-description call — the fourth of five stages, before you decide.