Benefits
Protect Events is for the signup and the ticket sale. The people who have to explain the policy afterwards get a record, not a story from the night.
Before arrival
Guests capture a passport or driving licence when they sign up or buy the ticket. By the time the event opens, approved people are already on the list. You are not meeting the document for the first time in a crowd.
Consistency
An 18+ night and a younger show should not depend on who is working. Each session carries a minimum age. The date of birth on the document is compared with that number, the same way, on every signup and every purchase.
Your pipeline
Under age and expired documents are declines. Signs that a document has been edited, or photographed off a screen, wait for your team. You see why it was held, and you approve or decline with the evidence in front of you.
Brand
The hosted flow takes your display name, colours and wording. The Arch can sound like The Arch. Your team still works in the Protect Events console, where the list, the review pipeline and the API keys live.
Systems
The check only helps if the sale can use it. Create a session from your backend when someone registers or pays, keep your own reference, and take signed webhooks for created, approved, declined and needs review.
Care of data
Checks run in the UK. Images are sent over HTTPS and stored encrypted. ID images are deleted after 30 days. A check that is still in your review pipeline keeps its images until your team decides. Guest images are not used to train models unless that arrangement is explicitly in place.