Why “Client,” not “Secure” or “Vault” or “Shield.”

We looked at close to ninety names before this one, across ten different naming strategies — the security-metaphor route (vault, shield, sentinel), the compliance-acronym route, the invented-word route. Almost all of them led to the same place: a word that describes the product's defenses, aimed at whoever's evaluating the vendor.

That's backwards from how the people who actually need this talk about the problem. A lawyer doesn't say “I need better data security” — they say “I can't put client information into a tool I don't control.” A title company doesn't think about vendor risk in the abstract; they think about whose closing file is on the line. “Client” is the word every target vertical already uses, unprompted, to describe the specific thing they're most liable for protecting.

So the name doesn't lean on a security metaphor at all. It just names whose data this protects, and lets the rest of the product — dedicated hardware, a stated deletion policy, a hosting disclosure instead of a buried one — do the job a metaphor would otherwise have to do.

The pitch, in one line, is the same as the name: private AI for businesses that can't use ChatGPT — their data never leaves their control, never trains anyone's model.