Terms of Service
Last Updated: July 9, 2026 // Registry Token: TOS-V1.2.0
These Terms of Service ("Terms") constitute a legally binding agreement between you ("User," "Attendee," or "Organizer") and SticketShop ("we," "our," or "us"). By accessing our web application, executing a payment gateway checkout, or provisioning a cryptographic ticket pass, you agree to be bound entirely by these Terms. If you do not agree, you must immediately terminate platform access.
1. Platform Account Registry & Access
To claim, view, or manage digital entry passes, users must authenticate using an authorized identifier (Email or Phone Number). You agree that:
- You are solely responsible for maintaining the security of your authentication sessions.
- You will provide an accurate name, email, and phone number, as these strings form the structural anchor for ticket allocation routing.
- SticketShop reserves the right to terminate accounts that attempt to spoof credentials or manipulate secure internal validation networks.
2. AI-Driven Dynamic Pricing & Valuation
For designated high-demand, bulk allocation, or private events, SticketShop utilizes an automated valuation layer powered by Google AI Studio.
- The engine evaluates client-submitted guest profiles and order volume to establish real-time, custom per-unit pricing.
- All valuations generated by the system are final at the exact millisecond the payment link is generated. Users acknowledge that pricing is dynamic and may shift based on automated profile recalculations prior to initialization.
3. Financial Clearance & Gateway Processing
All monetary transactions on SticketShop are authorized securely via our integration with Paystack.
- No Refund Policy: Due to the programmatic resource allocation of digital ticketing queues, all sales, processing fees, and bulk transactions processed through Paystack are strictly final and non-refundable unless an event is permanently canceled by the organizer without a rescheduled timeline.
- Ticket creation passes are only written to the database registry upon the verified return of a successful webhook authorization token from Paystack.
4. Secure Ticket Allocation, Sharing, & Claim Logic
SticketShop enforces absolute data integrity regarding ticket transfers to eliminate scaling fraud and public scalping:
A. The Sharing Path: When an organizer or primary purchaser allocates a ticket block using a recipient’s Name and Phone Number/Email, a placeholder token is escrowed. If using the phone-sharing path, the communication is managed client-side via device-level WhatsApp deep linking.
B. Lock-In Resolution: Once the recipient logs in and their authenticated credentials match the allocation string, the tickets are severed from the sender and locked permanently to the recipient's active account.
C. Secondary Markets: Private event tickets are fundamentally non-transferable onto public secondary marketplaces. Any attempt to scraped access strings or bypass verification protocols will result in immediate ticket revocation without financial recourse.
5. Private Event Isolation & Access Control
Events initiated with an explicit privacy configuration (`isPrivate: true`) operate under strict obfuscation parameters:
- Private events are mathematically omitted from global search results, indexing APIs, and public feeds. Access is granted solely through high-entropy tokenized URL distributions.
- Organizers maintain absolute authority over access validation at physical gates. The system tracks multiple occupancy slots under single nested matrix arrays (`totalAllocated`, `unclaimedCount`). Staggered or full check-in resolutions executed at the door by the organizer's terminal are absolute and legally binding.
- Every event automatically holds two (2) administrative passes in secure platform escrow for standard system verification and enforcement.
6. Limitation of Liability
SticketShop acts solely as a secure software infrastructure provider and database registry handler. We assume no liability for physical safety, venue operational disputes, event cancellations, local network outages affecting offline verification synchronization, or conduct occurring inside an activation space hosted by an independent organizer.