Transparency alternatives to Boardable
Other Board and meeting management vendors we measure, sorted by how much we found at them and not at Boardable. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Boardable on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Boardable has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, 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 Boardable” is the one that closes them.
| Vendor | Score | Found there, not found at Boardable | Found at Boardable, not found there | |
|---|---|---|---|---|
| Circlebackcircleback.aiSee also Transparency alternatives to Circleback | 61/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Status page with history | Compare |
| Knowaknowa.coSee also Transparency alternatives to Knowa | 52/100 | 4 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), +1 | 1 Status page with history | Compare |
| Otterotter.aiSee also Transparency alternatives to Otter | 52/100 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | 1 Status page with history | Compare |
| Read AIread.aiSee also Transparency alternatives to Read AI | 48/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 1 Certifications named | Compare |
| Supernormalsupernormal.comSee also Transparency alternatives to Supernormal | 43/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Status page with history | Compare |
| Board Intelligenceboardintelligence.comSee also Transparency alternatives to Board Intelligence | 22/100 | 3 HTTPS enforced with HSTS, Notice before subprocessors change, Named privacy contact | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Firefliesfireflies.aiSee also Transparency alternatives to Fireflies | 48/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| BoardProboardpro.comSee also Transparency alternatives to BoardPro | 39/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 Status page with history | Compare |
| BoardEffectboardeffect.comSee also Transparency alternatives to BoardEffect | 17/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 3 Data location stated, Status page with history, Public pricing | Compare |
| ShareVaultsharevault.comSee also Transparency alternatives to ShareVault | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Public pricing | Compare |
| Semblysembly.aiSee also Transparency alternatives to Sembly | 30/100 | 1 HTTPS enforced with HSTS | 2 Status page with history, Certifications named | Compare |
| Process PAprocesspa.comSee also Transparency alternatives to Process PA | 26/100 | 1 security.txt (RFC 9116) | 2 Status page with history, 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.