Transparency alternatives to Lernsax
Other School management vendors we measure, sorted by how much we found at them and not at Lernsax. This is a comparison of disclosure, not of features or fitness.
12 shown of 58 that differ from Lernsax on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Lernsax has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Lernsax” is the one that closes them.
| Vendor | Score | Found there, not found at Lernsax | Found at Lernsax, not found there | |
|---|---|---|---|---|
| Fidelofidelo.comSee also Transparency alternatives to Fidelo | 35/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Veracrossveracross.comSee also Transparency alternatives to Veracross | 35/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Edsbyedsby.comSee also Transparency alternatives to Edsby | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Gradelinkgradelink.comSee also Transparency alternatives to Gradelink | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Shkoloshkolo.comSee also Transparency alternatives to Shkolo | 26/100 | 3 Public pricing, Certifications named, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Sycamore Leafsycamoreleaf.comSee also Transparency alternatives to Sycamore Leaf | 26/100 | 3 Data processing agreement, Public pricing, Named privacy contact | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Finalsitefinalsite.comSee also Transparency alternatives to Finalsite | 33/100 | 2 Status page with history, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Sduisdui.deSee also Transparency alternatives to Sdui | 26/100 | 2 Data location stated, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Skywardskyward.comSee also Transparency alternatives to Skyward | 26/100 | 2 Data location stated, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Ayotreeayotree.orgSee also Transparency alternatives to Ayotree | 23/100 | 2 Data location stated, Public pricing | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Classterclasster.comSee also Transparency alternatives to Classter | 22/100 | 2 Public pricing, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Ellucianellucian.comSee also Transparency alternatives to Ellucian | 22/100 | 2 Public pricing, Named privacy contact | 2 No third-party tracking before consent, 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.