Transparency alternatives to Kadence
Other Workplace and visitor management vendors we measure, sorted by how much we found at them and not at Kadence. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from Kadence on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kadence has 8 gaps in what we could measure: Data processing agreement, Data location stated, 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 Kadence” is the one that closes them.
| Vendor | Score | Found there, not found at Kadence | Found at Kadence, not found there | |
|---|---|---|---|---|
| OfficeRnDofficernd.comSee also Transparency alternatives to OfficeRnD | 65/100 | 5 Data processing agreement, Data location stated, Uptime SLA with a figure, +2 | 2 Public pricing, Certifications named | Compare |
| FacilityOSfacilityos.comSee also Transparency alternatives to FacilityOS | 61/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | 2 Subprocessor list, Status page with history | Compare |
| Sinesine.coSee also Transparency alternatives to Sine | 59/100 | 4 Data location stated, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 2 Public pricing, Certifications named | Compare |
| Clearoomsclearooms.comSee also Transparency alternatives to Clearooms | 57/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 2 Status page with history, Certifications named | Compare |
| Sign In Solutionssigninsolutions.comSee also Transparency alternatives to Sign In Solutions | 39/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Subprocessor list, Status page with history, Public pricing | Compare |
| Teamgoteamgo.coSee also Transparency alternatives to Teamgo | 65/100 | 3 Data location stated, HTTPS enforced with HSTS, Notice before subprocessors change | nothing | Compare |
| Robinrobinpowered.comSee also Transparency alternatives to Robin | 48/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Subprocessor list | Compare |
| Sign In Appsigninapp.comSee also Transparency alternatives to Sign In App | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Subprocessor list, Status page with history | Compare |
| desk.lydesk.lySee also Transparency alternatives to desk.ly | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Subprocessor list, Status page with history, Certifications named | Compare |
| Yoffixyoffix.comSee also Transparency alternatives to Yoffix | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Subprocessor list, Status page with history, Certifications named | Compare |
| Seattiseatti.coSee also Transparency alternatives to Seatti | 30/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Subprocessor list, Status page with history, Public pricing | Compare |
| Freespaceafreespace.comSee also Transparency alternatives to Freespace | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 4 Subprocessor list, Status page with history, Public pricing, +1 | 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.