Alternatives to DICE
Other Venue ticketing vendors we measure, sorted by how much they publish that DICE does not. This is a comparison of disclosure, not of features or fitness.
11 shown of 11 that differ from DICE on at least one criterion we measured for both. Public transparency score, not a product or security rating.
DICE has 10 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, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and DICE does not” is the one that closes them.
| Vendor | Score | Publishes, and DICE does not | DICE publishes, and they do not | |
|---|---|---|---|---|
| AudienceViewaudienceview.com | 61/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 security.txt (RFC 9116) | Compare |
| TicketSpiceticketspice.com | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Prismprism.fm | 17/100 | 2 Data location stated, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Fatsomafatsoma.com | 22/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| accessoaccesso.com | 9/100 | nothing we found there and not here | 1 security.txt (RFC 9116) | Compare |
| Connect&GOconnectngo.com | 9/100 | nothing we found there and not here | 1 security.txt (RFC 9116) | Compare |
| Leap Eventsleapevents.com | 9/100 | nothing we found there and not here | 1 security.txt (RFC 9116) | Compare |
| PatronManagerpatronmanager.com | 9/100 | nothing we found there and not here | 1 security.txt (RFC 9116) | Compare |
| Digiticketsdigitickets.co.uk | 0/100 | nothing we found there and not here | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Eventixeventix.io | 0/100 | nothing we found there and not here | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Galaxy Ticketinggatewayticketing.com | 0/100 | nothing we found there and not here | 2 HTTPS enforced with HSTS, 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.