Transparency alternatives to Colossyan
Other Digital adoption and enablement vendors we measure, sorted by how much we found at them and not at Colossyan. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Colossyan on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Colossyan 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 Colossyan” is the one that closes them.
| Vendor | Score | Found there, not found at Colossyan | Found at Colossyan, not found there | |
|---|---|---|---|---|
| Spekitspekit.comSee also Transparency alternatives to Spekit | 78/100 | 5 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +2 | 1 security.txt (RFC 9116) | Compare |
| Synthesiasynthesia.ioSee also Transparency alternatives to Synthesia | 65/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| ElevenLabselevenlabs.ioSee also Transparency alternatives to ElevenLabs | 67/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 1 HTTPS enforced with HSTS | Compare |
| Pitch Avatarpitchavatar.comSee also Transparency alternatives to Pitch Avatar | 57/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Crayoncrayon.coSee also Transparency alternatives to Crayon | 35/100 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| Murfmurf.aiSee also Transparency alternatives to Murf | 57/100 | 2 Subprocessor list, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Oraiorai.comSee also Transparency alternatives to Orai | 43/100 | 2 Subprocessor list, Notice before subprocessors change | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| WellSaidwellsaid.ioSee also Transparency alternatives to WellSaid | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Bigtincanbigtincan.comSee also Transparency alternatives to Bigtincan | 39/100 | 2 Status page with history, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Kompytekompyte.comSee also Transparency alternatives to Kompyte | 26/100 | 2 Uptime SLA with a figure, Named privacy contact | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| HeyGenheygen.comSee also Transparency alternatives to HeyGen | 43/100 | 1 Named privacy contact | nothing | Compare |
| Poisedpoised.comSee also Transparency alternatives to Poised | 39/100 | 1 Named privacy contact | 1 security.txt (RFC 9116) | 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.