Transparency alternatives to Swapcard
Other Event management vendors we measure, sorted by how much we found at them and not at Swapcard. This is a comparison of disclosure, not of features or fitness.
12 shown of 49 that differ from Swapcard on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Swapcard has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Swapcard” is the one that closes them.
| Vendor | Score | Found there, not found at Swapcard | Found at Swapcard, not found there | |
|---|---|---|---|---|
| Stovastova.ioSee also Transparency alternatives to Stova | 78/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| EventWorksgeteventworks.comSee also Transparency alternatives to EventWorks | 43/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 5 Data location stated, Public pricing, Certifications named, +2 | Compare |
| Mentimetermentimeter.comSee also Transparency alternatives to Mentimeter | 65/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | nothing | Compare |
| Bizzabobizzabo.comSee also Transparency alternatives to Bizzabo | 48/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Crowdcastcrowdcast.ioSee also Transparency alternatives to Crowdcast | 43/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Certifications named, Named privacy contact | Compare |
| Zuddlzuddl.comSee also Transparency alternatives to Zuddl | 43/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Fourwavesfourwaves.comSee also Transparency alternatives to Fourwaves | 48/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Slidoslido.comSee also Transparency alternatives to Slido | 48/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Schedsched.comSee also Transparency alternatives to Sched | 43/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Timely Eventstime.lySee also Transparency alternatives to Timely Events | 32/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Public pricing, Certifications named, Named privacy contact | Compare |
| SpeechWirespeechwire.comSee also Transparency alternatives to SpeechWire | 30/100 | 2 Subprocessor list, No third-party tracking before consent | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | Compare |
| BigMarkerbigmarker.comSee also Transparency alternatives to BigMarker | 29/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 4 Data location stated, Public pricing, Certifications named, +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.