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