Events & Tickets
Event Organizer Terms
The terms that apply to workspaces that publish events, take RSVPs and sell tickets through Site Engine.
Last updated: October 2026
1. You are the seller
When you sell a ticket through Site Engine, you — the organizer — are the merchant of record. The attendee's payment goes directly into your own connected payment-gateway account. Site Engine does not touch, hold, advance or guarantee ticket revenue, and is not a party to the sale between you and the attendee.
Every attendee-facing promise — the event happening, the ticket being honoured, the refund policy — is yours to keep.
2. Payments & gateways
- Paid ticketing requires a live gateway you configure yourself — Stripe, Paystack or PayPal — under Settings → Integrations. Your gateway's own onboarding, verification (KYC) and payout terms apply to you directly.
- You are responsible for keeping gateway credentials valid and your account in good standing. We surface gateway health warnings; we cannot fix your gateway account.
- Payment processing fees are charged by your gateway to your account — they are separate from any platform subscription or commission.
- You must present an honest checkout: accurate event details, real prices, and the refund terms you intend to honour. Do not use the billing features to disguise one product as another.
3. Your obligations to attendees
- Deliver the event as described — date, venue, format and content. Material changes (date, venue, lineup) must be communicated to ticket holders promptly.
- Honour every issued ticket — including complimentary and transferred tickets — up to the capacity you sold.
- Staff the door. The check-in desk accepts QR scans and manual codes; scanned tickets cannot be reused. Entry rules beyond the ticket (age, ID, security) are yours to set and enforce.
- Publish and honour a clear refund policy. The platform's default checkout wording is a floor, not a ceiling — you may be more generous, never less lawful.
- If you cancel, you must refund ticket holders. A cancelled event with unpaid refunds is the fastest route to disputes, chargebacks and account suspension.
4. Refunds & disputes
- Attendees request refunds through their My Tickets panel; requests land in your refund queue for approval or denial. Approving voids the tickets and frees the seats — the actual money moves inside your own gateway, and the queue tells your staff to complete it there.
- You control refund decisions because you hold the funds. Leaving requests unanswered damages your standing with both attendees and the platform.
- Checkout records each buyer's policy acknowledgment, timestamp and IP address, and check-in scans are logged — use these as evidence when fighting a chargeback in your gateway's dispute process.
- Patterns of unresolved chargebacks or refund abuse may lead to suspension (see below).
5. Platform commission
- In commission mode, a percentage of each paid ticket order is recorded as platform commission. This mode requires a split-capable gateway connection (Stripe or Paystack) — without one, tickets run in keep-100 mode and no commission accrues.
- Commission is calculated on the order total at sale time and shown in your payment records. Refunded orders no longer earn commission.
- Your subscription plan and commission are independent — one does not replace the other.
6. Plan limits & capacity
- Your plan may cap event capacity, ticket-tier count and maximum ticket price. Limits are enforced at save time — submissions above a cap are trimmed, not silently accepted.
- Overselling is technically impossible: capacity checks are atomic across all sales channels (ticket tiers, RSVP seats and pending checkout holds all count).
- Reservation holds expire automatically (10 minutes) — abandoned checkouts return seats to sale without action from you.
- Do not create artificial duplicate events to circumvent capacity, tier or price caps.
7. Prohibited events & fraud
- No tickets for events that will not happen — no phantom events, bait-and-switch listings, or "fundraisers" that are not what they claim.
- No unlawful events, or events whose sale would breach sanctions, licensing or venue rules in the jurisdictions involved.
- No deceptive pricing: hidden mandatory fees, fake early-bird windows, or "free" events that charge at the door without disclosure.
- No use of ticketing to launder funds, process unrelated payments, or move money for third parties.
- No self-purchases designed to inflate sales figures or game waitlist notifications.
The platform may pause ticket sales or suspend a workspace while credible fraud, dispute or safety concerns are investigated.
8. Attendee data
- You are the controller of your attendees' personal data — names, emails, purchase records and check-in times collected for your event. Site Engine is the processor hosting it for you.
- Collect only what your event needs; use custom form fields responsibly — never for card numbers, passwords or identity documents.
- Attendee contact details may be used for event communications and lawful follow-up only — not sold, shared or added to unrelated marketing without consent.
- Post-event, use the attendee-data purge to delete registrations, tickets and waitlist rows — it keeps anonymous sales counts while removing identities. Honour applicable privacy law (POPIA, GDPR) for your audience.
- Check-in staff see attendee lists — keep staff access limited to people who need it, and remove them when they leave.
9. Tools we provide
- Event pages (hosted and via your connected website), RSVP management with approval flows, tiered ticketing, timed reservation holds, waitlists, early-bird pricing, comp-ticket issuance, QR check-in with rotating door codes, ticket transfer, refund queue and attendee-data purge.
- Events can be duplicated and saved as reusable templates; events with paid sales cannot be deleted — archive them to preserve the accounting trail.
- Connected-website API keys: the embed key is read-only and safe for browsers; the secret key can confirm payments — keep it server-side. Rotate keys you suspect are exposed.
10. Suspension & enforcement
- We may unpublish an event, pause ticket sales or suspend a workspace for: credible fraud reports, excessive chargebacks, cancelled events with unpaid refunds, prohibited content, or abuse of platform limits.
- Suspension of ticket sales does not erase existing obligations — tickets already sold must still be honoured or refunded.
- Serious or repeated violations lead to workspace termination under the main Terms of Service.
- If you believe an enforcement action was a mistake, contact us — humans review these.
Questions about this policy?
Reach the team through the contact page — a human replies.