Alternatives to DeepL
Other Translation and localization vendors we measure, sorted by how much they publish that DeepL does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from DeepL on at least one criterion we measured for both. Public transparency score, not a product or security rating.
DeepL has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and DeepL does not” is the one that closes them.
| Vendor | Score | Publishes, and DeepL does not | DeepL publishes, and they do not | |
|---|---|---|---|---|
| Lokaliselokalise.com | 87/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | nothing | Compare |
| Transifextransifex.com | 83/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| LingoHublingohub.com | 74/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
| wxrkswxrks.com | 74/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
| Smartcatsmartcat.com | 65/100 | 4 Data processing agreement, Status page with history, Certifications named, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Locizelocize.com | 65/100 | 3 Data processing agreement, No third-party tracking before consent, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Crowdincrowdin.com | 57/100 | 3 Data processing agreement, Status page with history, Certifications named | 1 Public pricing | Compare |
| Traduoratraduora.co | 43/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Phrasephrase.com | 39/100 | 2 Status page with history, Certifications named | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Wordbeewordbee.com | 39/100 | 2 Status page with history, No third-party tracking before consent | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Gridlygridly.com | 30/100 | 2 Status page with history, Certifications named | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| memoQmemoq.com | 30/100 | 2 Status page with history, Certifications named | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.