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