Transparency alternatives to Treatwell
Other Salon and spa booking vendors we measure, sorted by how much they publish that Treatwell does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from Treatwell on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Treatwell 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, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Treatwell does not” is the one that closes them.
| Vendor | Score | Publishes, and Treatwell does not | Treatwell publishes, and they do not | |
|---|---|---|---|---|
| Slickgetslick.com | 39/100 | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | 1 security.txt (RFC 9116) | Compare |
| Boulevardjoinblvd.com | 30/100 | 4 Status page with history, Public pricing, Uptime SLA with a figure, +1 | 1 security.txt (RFC 9116) | Compare |
| GlossGeniusglossgenius.com | 30/100 | 3 Data processing agreement, Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Salon Ultimatesalonultimate.com | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Schedulistaschedulista.com | 30/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Studiobookrstudiobookr.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Terminzterminz.com | 22/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| You'reOnTimeyoureontime.com | 22/100 | 2 Data location stated, Public pricing | 1 security.txt (RFC 9116) | Compare |
| Booksybooksy.com | 18/100 | 2 Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| Beubeuapp.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Freshafresha.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Mangomintmangomint.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | 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.