Confidentiality, NDA coverage, data retention and whether your files are used for model training.
An NDA can be arranged before sensitive files are shared. We can review your template or discuss ours. Delivery personnel work under confidentiality obligations; confirm any project-specific coverage, permitted tools and recipients at the briefing stage.
Our standard practice is need-to-know access within the delivery workflow and secure transfer channels where practical. Agree any required encryption specification, storage location, provider restrictions and retention schedule before files move. We do not publish an unverified universal deletion deadline.
Our policy is not to use client documents to train public or third-party AI models. Provider retention, logging and processing locations are separate questions and must be checked for the agreed route. Human-only or other restricted handling requests should be assessed before engagement; no universal on-premise deployment is promised here.
Project managers, translators and reviewers handling client material work under confidentiality obligations. For a procurement review, ask what evidence and additional client-specific terms can be provided without disclosing other people’s confidential information.
Project material is retained as needed to deliver the work and meet applicable business and legal obligations. Agree any shorter deletion schedule, backup treatment and confirmation method in advance. Translation Memories and glossaries are handled as client-specific assets under agreed reuse and retention terms; no automatic 90-day destruction or certificate is promised.
Acknowledged in 4 hours, quoted in 24. Discuss confidentiality before sharing sensitive files.