GDPR // Ticketing System Readiness Series
How are leading systems responding to changes in EU Data Protection? In the latest in this series we take a look at Via by Red61
VIA by Red61
VIA has traditionally been thought of as a ‘festival’ ticketing system, however recent additions to both the product and team behind the solution now sees them as an emerging provider to both the attractions and venue ticketing space.
Given their background in the complex world of festival ticketing (think festival, artist, venue all with an interest in data) it is no surprise that Red61 have already invested time into modelling data ownership and permissions for customer contact. As they put it “It’s where we came from, it’s in our DNA”
What we saw
During our session, we discussed the possibilities for multiple permissions per customer as well as the flows of data for ‘agency’ sales. In addition to this we also looked at the flow for collecting named third party consent.
Great to see
Red61 joins a select few systems that from our inspection can currently deliver ‘named’ third party consent. As with other leading systems in this field they perfectly manage the concept of ‘Promoter’ or ‘Producer’ allowing customers to clearly see (and consent) to who their data may be shared with.
Collecting Third Party Permissions and a feature we loved – ‘Preferred Contact Method’
What we didn’t see ……. but is there
VIA supports exposing the questions and answers to both the standard out of the box online ticketing platform that Red61 supply to some of their clients. It also supports this through its API, allowing venues to build a smooth and tailored flow that suits their needs and data permissions accordingly.
Transition Services and Issues
Many of the features that venues will need to be using to remain compliant under GDPR – (if using consent as the basis for processing) are already in VIA, and as such many clients are already using them.
Issue to consider
For those clients who have been using the generic ‘Third Party’ or ‘Producers of shows I go to see’ statements may need to think about campaigns and actions to go out and confirm consents from these customers. Given the data may have already been shared before the 18th May deadline the implications for the users may be minimal, the organisations to which the data was shared may need re-consent.
Stand out feature
We really like not only the features but the attitude around best practice in data sharing / permission gathering. Even though it is not a GDPR requirement, it was so refreshing to see that each customer can set their own ‘preferred method’ for contact, not just once, but for each of the possible future data controllers. Surely a great tool for marketing campaigns not only to hit the right people but also the right way.
It is not surprising given their experience in dealing with complex ticketing networks ( the Edinburgh Fringe Festival – need we say more?) that Red61 seem to have put solid data management and consenting tools at the core of their offering.
This article gives information in relation to what we consider to be best practice. However, compliance is context and fact sensitive and as such following any guidance does not guarantee regulatory or statutory compliance.
The Information Commissioners Office will judge any complaint on its own merits, and organisations in need of context or situation specific legal advice should seek it from an appropriately qualified source.
This work has been made possible by support from Arts Council England