Transparency alternatives to Motive.io
Other E-learning authoring vendors we measure, sorted by how much we found at them and not at Motive.io. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from Motive.io on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Motive.io has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Motive.io” is the one that closes them.
| Vendor | Score | Found there, not found at Motive.io | Found at Motive.io, not found there | |
|---|---|---|---|---|
| Aristarist.coSee also Transparency alternatives to Arist | 52/100 | 5 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, +2 | 1 Data location stated | Compare |
| Attensiattensi.comSee also Transparency alternatives to Attensi | 22/100 | 4 Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 3 Data location stated, Public pricing, Certifications named | Compare |
| Immerseimmerse.onlineSee also Transparency alternatives to Immerse | 48/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 2 Public pricing, Certifications named | Compare |
| Lectoraelblearning.comSee also Transparency alternatives to Lectora | 43/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | 1 Public pricing | Compare |
| Vectorsolutionsvectorsolutions.comSee also Transparency alternatives to Vectorsolutions | 30/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Public pricing, Certifications named | Compare |
| Intellumintellum.comSee also Transparency alternatives to Intellum | 26/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | 3 Data location stated, Public pricing, Certifications named | Compare |
| Courseboxcoursebox.aiSee also Transparency alternatives to Coursebox | 48/100 | 2 Data processing agreement, HTTPS enforced with HSTS | nothing | Compare |
| Easygeneratoreasygenerator.comSee also Transparency alternatives to Easygenerator | 41/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Ottolearnottolearn.comSee also Transparency alternatives to Ottolearn | 39/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Certifications named | Compare |
| ClickLearnclicklearn.comSee also Transparency alternatives to ClickLearn | 30/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 1 Data location stated | Compare |
| Virtivirti.comSee also Transparency alternatives to Virti | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, Certifications named | Compare |
| Zenlernewzenler.comSee also Transparency alternatives to Zenler | 24/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, Certifications named | 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.