Transparency alternatives to TicketSpice
Other Venue ticketing vendors we measure, sorted by how much we found at them and not at TicketSpice. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from TicketSpice on at least one criterion we measured for both. Public transparency score, not a product or security rating.
TicketSpice has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at TicketSpice” is the one that closes them.
| Vendor | Score | Found there, not found at TicketSpice | Found at TicketSpice, not found there | |
|---|---|---|---|---|
| AudienceViewaudienceview.comSee also Transparency alternatives to AudienceView | 48/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 2 Data location stated, Public pricing | Compare |
| Rollerroller.softwareSee also Transparency alternatives to Roller | 35/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| Agile Ticketing Solutionsagiletix.comSee also Transparency alternatives to Agile Ticketing Solutions | 17/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 2 Data location stated, Public pricing | Compare |
| Skiddleskiddle.comSee also Transparency alternatives to Skiddle | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| VISITvisit.comSee also Transparency alternatives to VISIT | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| accessoaccesso.comSee also Transparency alternatives to accesso | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| DICEdice.fmSee also Transparency alternatives to DICE | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| n-gage.ion-gage.ioSee also Transparency alternatives to n-gage.io | 26/100 | 1 HTTPS enforced with HSTS | 1 Public pricing | Compare |
| TicketingHubticketinghub.comSee also Transparency alternatives to TicketingHub | 17/100 | 1 HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Vantixvantixsystems.comSee also Transparency alternatives to Vantix | 13/100 | 1 HTTPS enforced with HSTS | 2 Data location stated, Public pricing | Compare |
| Connect&GOconnectngo.comSee also Transparency alternatives to Connect&GO | 9/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| Fatsomafatsoma.comSee also Transparency alternatives to Fatsoma | 9/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, Public pricing, Named privacy contact | 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.