Trust6’s golden rule: one client, one vault. It is not an organizational convention, it is the confidentiality boundary of the system.

One vault = one encrypted database = one key

Each vault is a separate encrypted database, protected by its own key, derived from a master key that lives in your system’s secure keychain. Concretely:

  • A client’s conversations, files, tokens and logs exist only in that client’s vault.
  • No operation in the app can read two vaults at once.
  • A token created in one vault (PERSON_001 in “Client Alpha”) literally does not exist in another: the same person mentioned for two clients gets two independent tokens, in two different encrypted databases.

Proof, right in the app

You do not have to take our word for it. In each vault’s audit log, the “Resolve a token” probe lets you paste a token and see its resolution:

  • In the vault where it was created: “Resolved in this vault”, with the real value.
  • In any other vault: “Unknown token in this vault”.

That is a direct demonstration that isolation is not a display policy but a property of the data itself.

What it means day to day

  • Create a vault as soon as a new client comes in, even for a single question.
  • Never recycle one client’s vault for another.
  • The dictionary belongs to each vault: “Client Alpha” terms never influence “Client Beta” analyses.
  • Your draft does not follow you from one vault to another, by design: carrying it over would be a leak between clients. See Switching vaults.