For the industries we serve — semiconductor, life science, aerospace, manufacturing — a specification or a filing can be commercially sensitive long before it is public. Confidentiality is part of how the work is set up.
Confidentiality obligations cover the contracting entity and the people who actually handle your files — translators and reviewers.
Our standard practice is to route each project only to the specialists it requires, rather than exposing files more widely than the work calls for.
Agree access, transfer, provider and retention requirements for the project. Quality-management certification does not establish an information-security certification.
Where a project needs specific handling, retention or destruction terms, they can be agreed at the outset and built into the workflow — and they govern over this general description.
This page describes how we generally treat the material you send us. It sits alongside — not in place of — the specific confidentiality terms in your engagement; where the two differ, your signed terms control.
| Area | Our standard practice | What you can agree separately |
|---|---|---|
| Who sees your files | Routed only to the specialists the project requires, on a need-to-know basis. | A restricted-access team, defined before any files are shared. |
| NDA coverage | Obligations extend to the individuals handling the work — project managers, translators, reviewers — not only to the contracting entity. | Additional or client-specific non-disclosure terms, put in place before files move. |
| AI tooling | AI assists inside our controlled workflow under human direction. If no-training is required for your project, tell us before sharing files so we can confirm the processing route and applicable terms. | Specific constraints on AI tooling, set at the briefing stage so the workflow is built accordingly. |
| Transfer and storage | Secure channels for receiving and returning files; access granted on a need-to-know basis. | Your own portal or preferred transfer method, and agreed storage conditions, where practical. |
| Retention and destruction | Material kept as long as needed to deliver the work and to meet legitimate business, legal or accounting obligations. | A defined removal schedule after delivery — raised at the start so it is built into the engagement rather than handled ad hoc. |
Where your signed terms differ from anything on this page, your signed terms control.
Files you submit for quotation or translation are used for one purpose: to scope, quote and — if you engage us — deliver your project. We do not repurpose them for anything else.
While a project is active, our standard practice is to keep working files within our delivery workflow and to limit access to the team members involved in that project.
Our confidentiality policy requires project managers, translators and reviewers who handle client material to be covered by appropriate confidentiality terms. Where individual coverage is a procurement requirement, request the relevant evidence before work starts.
For engagements with heightened requirements, additional or client-specific non-disclosure terms can be put in place before any files are shared.
Where AI assists a project, it operates within our human-directed delivery workflow. API-based tools may connect directly to a model provider or through a third-party service. A model brand alone does not identify the processing route. Agree any provider, location or tooling restrictions before sensitive material is shared.
If no-training is required for your project, tell us before sharing files so we can confirm the processing route and applicable terms. Any requirements for retention, processing location or deletion can be discussed at the same time.
Our standard practice is to grant access on a need-to-know basis and to prefer secure channels for receiving and returning files. If you have a preferred secure transfer method or portal, we will work with it where practical.
For projects that require it, we can discuss additional handling arrangements — such as restricted-access teams or agreed storage and transfer conditions — as part of setting up the engagement.
We keep project material for as long as needed to deliver the work and to meet legitimate business, legal or accounting obligations. Where you specify retention or destruction terms for your files, those terms govern.
If you would like files removed on a particular schedule after delivery, raise it at the start so it can be built into the engagement rather than handled ad hoc.
Our credentials page displays ISO 17100:2015 and ISO 9001:2015 certificates with their printed scopes and a dated CSA Research Top 100 Global 2022 badge. These do not certify information security, guarantee data deletion or establish a current annual ranking.
Tell us the controls your sector or procurement policy requires so we can assess feasibility and record the agreed handling. Certification scope should not be inferred from the service-level name.
Much of our work involves regulated filings and protected intellectual property — chip datasheets, medical registrations, patents, safety documentation. For these, confidentiality and accountability are treated as part of quality, not as separate concerns.
If your project carries specific compliance, security or IP requirements, the most effective time to define them is before work begins. Bring them to the briefing and we will confirm what we can accommodate.
If you need an NDA in place first, or want to confirm how a particular project would be handled, reach out and we will set expectations clearly up front — before any files change hands.
Start a confidential conversation →This page describes our general approach for information purposes and is not a contract. The confidentiality terms of your engagement, once signed, govern our work.