Transparency alternatives to Weglot
Other Translation and localization vendors we measure, sorted by how much we found at them and not at Weglot. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from Weglot on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Weglot has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Weglot” is the one that closes them.
| Vendor | Score | Found there, not found at Weglot | Found at Weglot, not found there | |
|---|---|---|---|---|
| Lokaliselokalise.comSee also Transparency alternatives to Lokalise | 87/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | 1 Certifications named | Compare |
| wxrkswxrks.comSee also Transparency alternatives to wxrks | 83/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| Transifextransifex.comSee also Transparency alternatives to Transifex | 61/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| LingoHublingohub.comSee also Transparency alternatives to LingoHub | 74/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| Locizelocize.comSee also Transparency alternatives to Locize | 65/100 | 4 Data processing agreement, No third-party tracking before consent, Notice before subprocessors change, +1 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Smartcatsmartcat.comSee also Transparency alternatives to Smartcat | 65/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Traduoratraduora.coSee also Transparency alternatives to Traduora | 43/100 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Wordbeewordbee.comSee also Transparency alternatives to Wordbee | 39/100 | 3 Status page with history, No third-party tracking before consent, Named privacy contact | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| DeepLdeepl.comSee also Transparency alternatives to DeepL | 48/100 | 2 No third-party tracking before consent, Named privacy contact | 1 Certifications named | Compare |
| Crowdincrowdin.comSee also Transparency alternatives to Crowdin | 43/100 | 2 Status page with history, Named privacy contact | 1 Public pricing | Compare |
| Phrasephrase.comSee also Transparency alternatives to Phrase | 26/100 | 2 Status page with history, Named privacy contact | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Localizelocalizejs.comSee also Transparency alternatives to Localize | 22/100 | 2 Status page with history, Named privacy contact | 4 Data location stated, Public pricing, Certifications named, +1 | 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.