What leaves the device, and what doesn’t.

Data handling

The Yoob SDK never transmits audio, video, transcripts or rendered frames. Rendering and speech synthesis happen entirely on the user’s device. A streamed avatar necessarily sends the conversation to a vendor to be rendered; this one structurally cannot.

The Companion product does send what you say to our conversation backend, because that is where the model runs. We do not sell it, we do not use it to train third-party models, and you can delete it — see Privacy.

Model protection

A determined attacker can extract a Core ML model from any iOS application. Compiling it is not protection and we are not going to claim otherwise. What we do is raise the cost and make theft traceable:

• Never in the binary. Weights arrive over an attested channel after install, so a decompiled .ipa contains no model at all.
• Encrypted at rest, with a key provisioned per device and held in the Secure Enclave.
• Per-licensee fingerprinting. Each customer’s weights carry a quality-neutral perturbation, so a leaked model identifies its source. The perturbation is gated through the same quality battery, so it provably does not change output.
• The weights alone are not enough. Correct output depends on a conditioning contract we serve signed rather than compile into the client.

Enterprise controls

What we do not have yet

We are not SOC 2 certified and we are not going to imply it. Several vendors in this market are, and if certification is a hard requirement for your procurement team today, we are not the right choice yet. It is on the roadmap; ask us where it stands.

Reporting a vulnerability

Email security@yoob.com. We aim to acknowledge within one business day. Please give us reasonable time to ship a fix before publishing.

Last updated 26 July 2026.