Transparency alternatives to Cal.com
Other Scheduling vendors we measure, sorted by how much we found at them and not at Cal.com. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from Cal.com on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cal.com has 5 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, No third-party tracking before consent. The column “Found there, not found at Cal.com” is the one that closes them.
| Vendor | Score | Found there, not found at Cal.com | Found at Cal.com, not found there | |
|---|---|---|---|---|
| Reclaimreclaim.aiSee also Transparency alternatives to Reclaim | 78/100 | 3 Subprocessor list, Data location stated, Status page with history | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Chili Piperchilipiper.comSee also Transparency alternatives to Chili Piper | 52/100 | 3 Data location stated, Status page with history, No third-party tracking before consent | 4 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change, +1 | Compare |
| Appointletappointlet.comSee also Transparency alternatives to Appointlet | 39/100 | 2 Subprocessor list, Data location stated | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | Compare |
| Nowstanowsta.comSee also Transparency alternatives to Nowsta | 30/100 | 2 Data location stated, Status page with history | 6 Data processing agreement, Public pricing, Certifications named, +3 | Compare |
| Calendlycalendly.comSee also Transparency alternatives to Calendly | 65/100 | 1 Data location stated | nothing | Compare |
| SavvyCalsavvycal.comSee also Transparency alternatives to SavvyCal | 48/100 | 1 Data location stated | 3 security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact | Compare |
| Motionusemotion.comSee also Transparency alternatives to Motion | 43/100 | 1 Subprocessor list | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change | Compare |
| SimplyBook.mesimplybook.meSee also Transparency alternatives to SimplyBook.me | 35/100 | 1 Data location stated | 4 Data processing agreement, Certifications named, security.txt (RFC 9116), +1 | Compare |
| YouCanBook.meyoucanbook.meSee also Transparency alternatives to YouCanBook.me | 35/100 | 1 Data location stated | 4 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change, +1 | Compare |
| Timifytimify.comSee also Transparency alternatives to Timify | 32/100 | 1 Status page with history | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Planfyplanfy.comSee also Transparency alternatives to Planfy | 30/100 | 1 Data location stated | 5 Data processing agreement, Certifications named, security.txt (RFC 9116), +2 | Compare |
| Traffttrafft.comSee also Transparency alternatives to Trafft | 30/100 | 1 Data location stated | 5 Data processing agreement, Certifications named, security.txt (RFC 9116), +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.