Transparency alternatives to Cloudbeds
Other Restaurant point of sale vendors we measure, sorted by how much we found at them and not at Cloudbeds. This is a comparison of disclosure, not of features or fitness.
12 shown of 41 that differ from Cloudbeds on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cloudbeds has 8 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Cloudbeds” is the one that closes them.
| Vendor | Score | Found there, not found at Cloudbeds | Found at Cloudbeds, not found there | |
|---|---|---|---|---|
| SevenRoomssevenrooms.comSee also Transparency alternatives to SevenRooms | 70/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | 1 Data location stated | Compare |
| Mewsmews.comSee also Transparency alternatives to Mews | 57/100 | 4 Status page with history, Certifications named, Uptime SLA with a figure, +1 | 1 Notice before subprocessors change | Compare |
| SpotOnspoton.comSee also Transparency alternatives to SpotOn | 30/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | Compare |
| Apaleoapaleo.comSee also Transparency alternatives to Apaleo | 43/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Cloverclover.comSee also Transparency alternatives to Clover | 30/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Zettlezettle.comSee also Transparency alternatives to Zettle | 30/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Lollyitslolly.comSee also Transparency alternatives to Lolly | 26/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Deliverectdeliverect.comSee also Transparency alternatives to Deliverect | 22/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | Compare |
| Ottertryotter.comSee also Transparency alternatives to Otter | 57/100 | 2 Status page with history, Public pricing | nothing | Compare |
| Hotelkithotelkit.netSee also Transparency alternatives to Hotelkit | 52/100 | 2 Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Tableintablein.comSee also Transparency alternatives to Tablein | 35/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Aldeloaldelo.comSee also Transparency alternatives to Aldelo | 30/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 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.