Age limits, warnings and refunds: the parts of a haunt bindro will not decide

Which half of the age rule does bindro actually enforce?

The booker’s. Their date of birth is checked against this vertical’s minimum inside the transaction that would otherwise take the money, so an under-age booker is refused before a payment intent exists — and a date that will not parse is refused too, because a rule that garbage bypasses is not a rule.

Everybody else on the order is covered by a required tick-box in which the booker confirms the whole party meets the limit. That is an attestation. It is worth having — it puts the claim on the record and on the person making it — but it verifies nothing, and bindro does not check anyone’s ID. For haunts it does not even prompt the person scanning to confirm they saw one, because this vertical does not declare that capability.

Practical consequence: publish the age on your own page, staff the gate to check it, and state in writing what happens to somebody turned away — because the platform’s answer is that they can refund themselves up to the moment their slot starts, and after that it is your call.

What does the intensity warning actually do?

It blocks. The intensity, strobe and medical acknowledgement is a required box on every booking, checked on the money path, and the order does not complete without it. That is genuinely worth something: nobody buys an entry to your show without first being told, at the moment of paying, that it involves what it involves.

It is not a screening tool. Nothing asks about photosensitive epilepsy, nothing routes a heart condition to a person, nothing is read back by anybody. The box is a record that the warning was shown and accepted, kept for two years. The wording of the warning — how loud, how dark, how close the actors get, whether they touch — is yours to write and yours to keep accurate.

What happens with under-18s?

The booker commits on their behalf at checkout, in a required box, and that is the whole of the mechanism on a haunt. Nothing is emailed to a parent to countersign, and no entry is refused at the gate for a missing signature.

This is worth being blunt about, because the platform does have a real guardian countersign flow — a link to the guardian’s own address, and a door that refuses an unsigned minor — and haunts do not have it. It depends on checking people in by name, and a haunt scans bands. So if a signed parental consent matters to your insurer, collect it your own way and treat the checkbox as the commitment it is, not as a signature you hold.

How do refunds behave, and what can I control?

Every buyer can refund themselves in full from the link in their confirmation email, right up to the moment their slot starts. There is no notice window to configure, no partial refund to set and no fee you can withhold — this is the platform’s buyer-protection floor, not a setting.

After the slot has started the link stops working and the decision is entirely yours, from the console. Refunds reverse in a fixed order — your proceeds, then the tax, then the platform fee — and a chargeback debits you in full, because that is what a chargeback is.

Plan around the floor rather than against it. A bad forecast on the Friday of closing weekend can empty a night before you have decided anything, and the defence is not a policy setting: it is a peak-night price high enough to be worth keeping, a page that says clearly what happens in rain, and a season pass in the hands of the people who come whatever the weather.

• Self-service refunds are full refunds, until the slot starts.
• After the slot starts, only you can refund, from the console.
• Refunds reverse organiser proceeds first, then tax, then the fee.
• No deferrals and no credit notes here: you cannot move somebody to another night.

What do I do about access requirements and medical questions?

There is a field for access requirements — step-free routes, seating, an assistance animal, a quiet space — and it is classed as health data, which is load-bearing rather than decorative: health-classed answers are excluded absolutely from analytics exports and from any AI context, in every vertical, with no override.

Read them before the night. Nothing summarises them, nothing flags them and nothing tells your gate that the couple arriving at nine need the step-free route. And be aware of where they live: the retention sweep anonymises attendee identities on a schedule, while answers that belong to the ORDER — access requirements and the booker’s date of birth here — stay on the order.

What you must not do is invent a field. An answer whose key is not in this vertical’s configuration is refused at validation rather than stored, precisely so that no haunt can start collecting medical detail through a box nobody classified, nobody set a retention rule for, and nobody excluded from an export.

What should be on my own page rather than on bindro’s?

The show’s rules. Your age limit and how it is checked; what the intensity warning means in your barn; whether actors make contact; your re-entry rule, which the software does not enforce; what happens in rain; and where the queue starts. bindro will collect the acknowledgement and take the money, but every one of those sentences is a promise made by a haunt, not by a platform, and a haunt that leaves them unwritten is the one arguing about them at the gate.