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