Trust and security

A plain-language summary of how LgTranslate is built. The terms and the data processing agreement are drafts that wait for review by counsel; the sub-processor list will follow.

Availability

Translations are published as static, versioned files to your own site and two independent CDNs. Visitors never wait on our application servers, so an outage on our side stops editing and publishing but not what visitors see. The limits: the visitor's browser needs JavaScript and a working loader, and a first-time visitor who cannot reach any copy of your files sees your original language.

Integrity of published translations

Each published manifest is signed. The loader ignores a manifest that is unsigned, signed with an unknown key, or older than one it has already seen, and shows the original text instead.

Your data and accounts

Data is kept separate per customer, and access without a customer context is refused.
Secret API keys are shown once and stored only as hashes.
Only the text to translate and the language pair are sent to a translation engine. Never keys, emails or IP addresses.
You can export your translations at any time.

Privacy

For visitors to your site we act as a processor on your behalf; for your own account data we are the controller. This is our working assumption and is being confirmed with counsel before launch. See the privacy page.

Reporting a problem

A security contact and disclosure policy will be published here before launch.

Questions about security or data?

Create a free account How it works