Legal Structure for Use of Someone’s TICKET Services
These terms govern your access to Someone’s TICKET platform. By accessing the system, you confirm full acceptance of these terms. The structure applies to all users, including administrators, developers, agents, partners, or end clients who interact with the system through web or API channels.
1. Definitions
- “Platform” means the whole system provided under the Someone’s TICKET brand
- “Client” means the legal entity or individual with registered access rights
- “End User” means any customer or individual who receives a ticket
- “Ticket” means any unit generated by the system for event entry
- “Event” refers to any organized session, gathering, or performance
- “Session” refers to a time-specific entry window tied to an event
- “Agreement” means this complete set of terms and all references within
2. Access and Eligibility
Access requires age above the legal minimum, local business registration, and a valid identity submission. You confirm that all submitted information remains accurate and traceable to your organization or entity. No shared credentials may exist across unrelated companies or projects.
3. Account Setup and Roles
You may assign roles to internal staff, project members, or partners. Each account type comes with a default access level. Admin access includes ticket creation, scan visibility, and event setup. Viewer access limits all interaction to log view and reporting.
Passwords must meet minimum security requirements. Accounts expire after periods of complete inactivity. Access keys remain bound to IP range and project scope.
4. Ticket Creation and Event Definition
Each ticket issued by the platform must be attached to a valid event. You define price, access window, entry rule, and cancellation conditions.
Ticket status may reflect the following states:
- Active
- Expired
- Scanned
- Canceled
- Blocked
Event data within your account zone may remain visible for audit, export, or compliance use. Someone’s TICKET will retain no usage authority outside your configured limits.
5. API and Webhook Usage
Your integration with the platform requires secure API keys. You remain responsible for all traffic, data use, and logic built under your access. Webhooks must connect to secure URLs with encryption and token validation enabled.
The system sends webhook payloads under signed headers with retry logic enabled. Delivery logs and status codes remain visible in your admin panel.
6. Payment Routing and Processor Choice
You remain free to use your payment processor. Someone’s TICKET never collects card data, payment records, or customer details. Your system controls invoicing, refund rules, and fraud checks.
Payment triggers must link to ticket creation endpoints. The platform rejects payment-unlinked ticket flow. Access will become active once ticket generation is complete according to your rules.
7. Data Security and Ownership
Your data remains under your complete control. Someone’s TICKET retains no claim over ticket records, user details, event metadata, or internal reports.
All data transfers follow encrypted channels. No external system may access logs or transactions without verified keys. Each session auto-closes upon timeout or an invalid request flag.
Audit logs remain accessible for 30 days. You may request export or deletion through your admin contact.
8. Platform Updates and Downtime
Scheduled maintenance notices appear in your panel at least 24 hours in advance. Emergency patches may occur with zero lead time in case of system risk.
You receive uptime tracking, incident reports, and system health summaries from your assigned account channel.
The platform follows a continuous update cycle. Endpoints, status codes, or data format changes come with full notice inside the integration panel.
9. Termination and Account Closure
You may request termination of access through written instructions. Your request closes all open sessions and removes project access tokens within 24 hours. Someone’s TICKET will remove account access and deactivate associated APIs.
The remaining records will remain accessible for export within the following 7-day window. Past scan logs, sales records, and API sessions may be archived for billing or audit review.
10. Governing Law and Dispute Structure
All matters follow the legal framework of the United Arab Emirates. In case of dispute, parties will first attempt resolution via direct contact. If unresolved, matters move to the Dubai International Arbitration Centre under commercial rules.
