Event terms and policies
These policies explain your booking, refund rights and how your information is used.
Policy version: dd18f531c73542cae033a5460cf0a7d544d8b4a1edd36aaff40aae8506c32648
Event and ticketing terms
EVENT AND TICKETING TERMS - DRAFT FOR APPROVAL Prepared 8 September 2026. This development preview accepts test orders only. No money is taken in demo mode and test tickets do not grant admission. The intended live-sale terms below require approval and complete business/contact details before real sales open. 1. Who provides what CRFM is the event organiser and is responsible for organising and delivering the event. The full legal entity trading as CRFM, its address and event support contact must be confirmed before launch. Peravix Group LTD supplies the ticketing platform, ticket issuance, payment collection arrangements and ticket validation technology. It is not the event organiser, venue operator, promoter of the event programme or provider of on-site entertainment. Card payments, when enabled, will be handled through Stripe; describing Peravix as the ticketing/payment provider does not mean that it operates the card network or is itself Stripe. The intended arrangement is that the admission contract is with CRFM, with Peravix providing ticketing and payment collection on CRFM's behalf. The written agency arrangement, seller identity and Stripe account structure must be confirmed before live sales. These terms do not override the parties' actual legal roles. 2. CRFM's event responsibilities CRFM is responsible for the event description, programme, performers, date and times, venue arrangements, capacity, permissions and licences, appropriate insurance, accessibility arrangements, safeguarding where applicable, and compliance with applicable event requirements. CRFM must arrange suitable staff, security and health and safety measures, working with the venue and other suppliers as required. CRFM is responsible for event delivery, event changes or cancellation, admission policies and event-related complaints and remedies. These responsibilities are not transferred to Peravix merely because it collects payments, issues tickets or supplies a scanner. 3. Peravix's ticketing responsibilities and liability Peravix is responsible for carrying out its own ticketing and payment-handling services with reasonable care and skill and for its own applicable data protection and consumer obligations. Peravix does not supervise or control the event, venue or CRFM's staff and is not responsible for an event-delivery failure caused solely by CRFM or its event suppliers, rather than by Peravix's own acts or omissions. Nothing in these terms excludes or limits liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation, or any other liability that cannot lawfully be excluded. Your statutory consumer rights, rights concerning Peravix's own services, and lawful payment-provider remedies remain unaffected. This is not a waiver of all claims against Peravix or the venue. 4. Prices, booking and payment Check the event, date, venue, age restrictions, quantity and email address before ordering. Advertised ticket prices are in pounds sterling and include all mandatory charges and any applicable taxes. No additional booking, payment or email fee is added at checkout. The event page shows the early-bird deadline in UK time, and the order total is shown before payment. Availability and price are checked on the server. Starting checkout temporarily reserves tickets but is not payment confirmation. Tickets are issued only after verified successful payment, or after the explicitly labelled demo step in this preview. A payment return page alone is not proof of purchase. If checkout expires, start a new booking and review the price again. Arrangements between CRFM and Peravix do not reduce your statutory rights or refund entitlements. 5. Tickets and entry Each admission has a unique QR code. Keep tickets and private receipt links secure; do not post them publicly. Each valid ticket can be checked in once. Duplicated, already-used or refunded tickets will not grant a further entry. Contact ticket support if a ticket is lost or an incorrect scan is reported; staff must investigate against the order record. CRFM and the venue manage entry in accordance with the age, accessibility and reasonable safety rules disclosed before purchase. They must apply those rules fairly and lawfully. Any transfer, re-entry or identification requirements must be stated before sales open; undisclosed restrictions are not created by these draft terms. 6. Changes, cancellation and refunds CRFM is responsible for communicating event changes promptly and providing the remedies required by law. If CRFM cancels the event, the proposed policy is a refund of the admission price paid. For postponement or a significant change, customers must be told the available options and any refund entitlement before being asked to accept an alternative. Final customer charges, refund contact and processing times must be confirmed before launch. Peravix will assist with ticket records and payment/refund administration within its role. Customers must not be required to wait for the post-event settlement between the businesses to exercise a refund right. This policy does not exclude remedies for a failure of Peravix's own service or override statutory rights. The voluntary change-of-mind and transfer policy remains to be agreed and disclosed before live sales. Do not assume that a general online-shopping cooling-off period applies to a dated event, or that all tickets are automatically non-refundable. This preview processes test refunds only. 7. Help and complaints Event, venue and programme enquiries should be directed to CRFM. Ticket delivery, payment records, technical problems and refund administration enquiries should be directed to Peravix. A complaint involving both parties should be coordinated rather than simply passed back and forth. Verified contact details for both businesses, Peravix's company number and registered address, and CRFM's full legal identity must be published before real bookings are accepted. 8. Your agreement and policy changes Before booking you must actively accept the event and ticketing terms and acknowledge the privacy notice. A copy of the wording and its version is recorded with your order, with the booking timestamp, and is available with your private receipt. Later edits do not retrospectively replace the terms recorded for an existing order. Material changes to an existing booking require the appropriate notice and any consent or remedy required by law.
Privacy notice
TICKETING PRIVACY NOTICE - DRAFT FOR APPROVAL Prepared 8 September 2026. Use fictional buyer details in this development preview. Real email delivery and live payments are disabled. 1. Who is responsible for your information Peravix Group LTD operates the ticketing service and CRFM organises the event. Their data protection responsibilities depend on what each actually decides and does with personal information, not just the labels in the event terms. Before live sales, the parties must document whether each activity is carried out as an independent controller, joint controller or processor, and publish the relevant legal identities, addresses and privacy contacts. Calling Peravix a payment provider does not remove its data protection duties. 2. Information used by this service We record the buyer's name and email address, event and quantity, prices, order and payment references, payment/refund status, ticket identifiers and check-in records. We keep the accepted terms and privacy wording, version and booking time. Staff accounts, security/session information, audit records and hashed rate-limit identifiers support access control and misuse prevention. The preview does not ask for card details. When Stripe Checkout is connected, card details are entered with Stripe, not into this website's booking form. 3. Purposes and legal bases The intended live service uses necessary booking, payment, ticket delivery and admission information to perform the relevant contract or take requested steps before it. Fraud prevention and proportionate security monitoring may rely on legitimate interests following the required assessment. Accounting or legally required records rely on applicable legal obligations. Each controller must confirm and document the basis for its own activities before launch. Acknowledging this notice is not consent to marketing and is not used as blanket consent for all processing. This checkout does not enrol buyers in marketing. Any future optional marketing requires a separate appropriate choice and compliance with applicable rules. 4. Who receives information Access is limited to authorised Peravix ticket-support staff and CRFM event staff who need booking or admission information for their duties. The service uses hosting/security providers and, when configured, Stripe and a transactional email supplier. Payment collection and information sharing must reflect the agreed controller/processor arrangements. The final supplier list, any international transfers and the safeguards for them must be confirmed before live sales. Personal information is not offered for sale by this service. 5. Storage and retention Ticket records are held separately from the radio website with access controls and backups. This preview keeps daily database backups for up to 30 days; that is a backup rotation period, not a promise that all buyer data is deleted after 30 days. A documented retention/deletion schedule for orders, financial records, admission logs, support records, uploads and backups must be agreed and implemented before live sales. Relevant information may need to be retained for legal obligations or the resolution of a dispute, with access limited accordingly. 6. Your rights and contact Depending on the circumstances, you may request access, correction, erasure, restriction or portability of your personal information and object to processing. Where consent is used, you may withdraw it without affecting earlier lawful processing. These rights have legal limits; they do not necessarily require deletion of financial records that must be kept by law. Verified privacy contacts for both businesses must be added before launch. You may complain to the Information Commissioner's Office at ico.org.uk. 7. Cookies and ticket security The ticketing application uses an essential staff-session cookie for signed-in staff. Its booking flow does not require advertising cookies or marketing consent. Hosting and security services are used to protect the website; their final configuration must be reviewed before live sales. Treat receipt links and QR codes as private credentials. Report suspected disclosure to ticket support so the order can be investigated. 8. Changes to this notice The notice presented at booking is retained with the order. Updated information will be provided when processing changes require it. The outstanding identity, contact, supplier, transfer and retention details in this draft must be completed before it is used for real customer sales.