Three questions wearing one word.

“Is it confidential?” is nearly always three questions at once, and they have different answers. Does our material become training data for somebody else's model. Can someone inside the firm reach material they should not. And if we are asked to account for how a piece of work was produced, can we.

Answering only the first — which is the easy one — is why so many of these conversations stall without anyone being able to say quite why.

Your corpus is indexed for your organization alone and is never pooled with anyone else's. It is not training data for a public model.

Where you approve an external model provider for part of a workflow, that provider's handling is governed by your approved configuration and their terms. Which is precisely why model access is a policy you set rather than a default we set for you: the answer to this question should be one your firm wrote down, not one a vendor chose on your behalf.

Confidentiality inside a firm is not one wall. It is many, and they are specific — to a matter, a client, a team, sometimes a single person. A retrieval system that can read everything is, the first time someone asks a pointed question, a way around all of them at once.

Permissions on the source documents travel into retrieval, and the rule is absolute: nothing is surfaced to a person that they could not already open themselves. Where walls exist they are mapped before indexing, and tested against questions whose answers are known.

Every answer names the document, the date and the page it came from, and opens the original. Access, ingestion, model changes and administrative actions are logged and reviewable.

In a professional setting this turns out to matter most. The point is not that the system is trusted — it is that it does not have to be, because any statement it makes can be checked against the underlying material before anyone relies on it.

No system is unhackable. Anyone who tells you otherwise is describing a brochure rather than an architecture.

Software alone does not create legal privilege. Privilege follows the relationship and the conduct around the material; no architecture confers it, and no vendor can tell you your obligations are met.

A certification is not a security guarantee. It records that a process was audited on a date. It does not tell you where your data sits, who can reach it, which models see which work, or what is logged — and those are the questions worth asking, of us and of everyone else you evaluate.

Judgment stays with the person who signs the work. Retrieval and drafting are bounded deliberately: the system finds and composes, and it does not decide.