Security
Privacy for the documents that matter: how Traxlate protects sensitive translations
The kind of work this is built for
Legal and immigration translation is a regulated space. The documents that come through Traxlate routinely contain information that is sensitive under GDPR: names, passport numbers, addresses, medical history, criminal records, financial disclosures. The decisions we made about how to handle that data needed to be ones we could explain, clearly and confidently, to a lawyer reviewing our service before uploading a client's asylum application or divorce decree.
GDPR end-to-end
The platform is GDPR-compliant across every stage — submission, processing, storage, retrieval, deletion. There is no ambiguity about which data protection regime applies and no CLOUD Act exposure on the processing path. For users handling politically sensitive material — asylum seekers, journalists, activists — that distinction is not theoretical.
Never used to train, never shared
Your source text and translated output are never used as training data. They are never sent to OpenAI, Anthropic, Google or any other third-party AI provider. They are never sold, never shared with advertisers, and never accessed by anyone outside of your account except under a valid legal warrant in a specific jurisdiction.
Retention you control
We retain uploaded documents for 30 days by default — configurable down to 7 days, up to 1 year, or set to immediate deletion on completion. The immediate-deletion option is in the job submission form under Advanced options and is the right setting for highly sensitive workflows: confidential M&A documents, sealed court records, sensitive medical records.
For regulated industries
For enterprise customers — law firms, immigration practices, healthcare networks, financial services, government contractors — we provide Article 28 GDPR data processing agreements, subprocessor lists, retention attestations, and audit support. These documents help you document your own data processing chain for regulatory audits and client commitments.
Contact support@traxlate.com for the full enterprise privacy package.
The trade-off we made
Building this way costs more than the alternatives. We accept that cost because the alternative — handling sensitive documents through infrastructure with broader exposure, or routing translations through third-party AI vendors that retain or train on your input — is not compatible with the use cases Traxlate was built for.
Privacy is not a marketing claim layered on top of the product. It's part of the product, and we will not undo it.