Trust and compliance
Trust is a set of specific commitments, not a badge.
This page says what we actually do with documents, what we do not do, and what we are prepared to put in a contract. Where something is not settled yet, it says so rather than implying more than we can deliver.
What we commit to
These are commitments we are prepared to put in writing in an engagement agreement.
Your documents are not training data
We do not use engagement material to build or train models, and we do not pass it to third parties for that purpose.
No client names, no published samples
We do not name clients on this site and we do not publish documents as case studies. Agencies work under confidentiality with their own customers and the same applies to us.
Access is narrow by design
Where systems connect to us, access is scoped to the specific agent, document set and duration agreed — not issued as a broad key.
Deletion on request
Documents processed for an evaluation or an engagement are deleted on request. What that means in detail is set out in the engagement terms.
What we do not claim
This is the part most trust pages leave out, which is why they are not very useful.
We do not display certification badges we do not hold. If a certification becomes relevant to your procurement, ask us directly and we will tell you exactly where we stand rather than pointing at a logo.
We do not claim a specific jurisdiction for data processing on this page, because that depends on the deployment shape you choose and is properly settled in the agreement rather than on a marketing page.
We do not describe our security posture with adjectives. If your procurement process requires specific answers, send the questionnaire — we would rather answer the real questions than write reassuring prose.
How the pipeline handles your files
Concretely, in the order it happens.
A submitted document is inspected page by page to decide how each page should be processed. The content is translated with your terminology applied, then reviewed by a separate model from the one that produced the translation, then checked visually against the source.
The finished document is returned to you. Evaluation documents are not retained as reference material and are not used as marketing examples.
Where a document cannot be sent outside your infrastructure at all, that is the private deployment conversation — and it changes the whole shape of the engagement, so it is worth raising in the first message.
Trust questions
Are you ISO certified?
Ask us directly and we will tell you exactly where we stand. We do not display certification marks we do not hold.
Is our data used for training?
No. Engagement material is not used to build or train models, and it is not passed to third parties for that purpose.
Where are documents processed?
That depends on the deployment shape you choose, and it is properly settled in the engagement agreement rather than stated on a web page. Tell us what your requirements are.
Can you sign our NDA?
Usually. Send it and we will tell you plainly if there is something we cannot agree to, rather than letting it sit.
Do you keep our documents after the project?
Evaluation material is deleted on request, and the specifics are set out in the engagement terms. We do not retain documents as reference or marketing material.
Can documents stay inside our own infrastructure?
That can be assessed as a private deployment. It is a delivery project with licensing and handover, not a setting — but for some organisations no other arrangement works.
Send us a real file. See what comes back.
Pick the document that normally causes you the most trouble — the scanned one, the chart-heavy one, the one with the tables. We will run it and send the finished file back so you can judge the layout yourself.
- No signup, no self-service portal — you send a file, we run it.
- You get the finished document back, not a screenshot of one.
- If it is not good enough, you have lost nothing.