Use case
When the corpus must not leave.
Contracts, patent files, client data, material under a non-disclosure agreement: the obstacle to adoption is rarely answer quality. It is knowing where the documents go.
The three questions we get asked, and the answers
- 01
Where are the documents stored?
On the infrastructure set in the contract. The target architecture provides for hosting and backups in Switzerland. Processing locations, subprocessors and their commitments are named in the contract, not described in general terms.
- 02
What does the model see?
The passages needed for the answer in progress, and nothing else. The full corpus does not travel. The chosen model, how it is hosted and its retention policy are stated in the quotation.
- 03
Who can obtain what?
Source permissions are carried over at indexing time. A user without access to a folder gets neither its content nor its citation. That behaviour is part of the acceptance tests, using control accounts.
What we will not tell you
That a system is “secure” without saying secure against what. The commitments that matter are written down: location, subprocessors, retention periods, logging, reversibility. What is not in the contract is not a commitment.
Reversibility
Your documents remain yours and the index can be rebuilt from your sources. At the end of the relationship, the index and derived data are deleted following a procedure described in the contract, and the evaluation set is handed back to you.
This is the point we recommend negotiating first, with us as with any supplier.
Request an assessment
Tell us about your corpus
Describe your document volumes, the systems they sit in, and the business question that costs you the most time. We reply within two working days, in English, French or German.
- Swiss engineering
- Reply within two working days