DRAFT. For lawyer review. Not legal advice.
Tiket.ing Terms of Service for Organisers
Version [version]. Effective [effective date].
1. Who we are and what these terms cover
1.1 These terms are between [Pixel Haven legal name], [registered address], company number [company registration number] ("Pixel Haven", "we", "us") and the organisation that creates a tiket.ing account to sell tickets or book spaces ("you", "the Organiser").
1.2 Tiket.ing is an online platform. It lets you publish events, sell tickets and bookings, check people in at the door, and manage people lists. We run the platform. You run your events.
1.3 The person who signs up for the Organiser confirms that they have authority to bind the Organiser.
2. Your account
2.1 You sign up on tiket.ing. You must give true information. Pixel Haven reviews every new Organiser before it can publish events. We may approve or reject a signup. If we reject it, we give a reason.
2.2 While your signup is waiting for approval, you can set up your venues, events, staff and payment gateways. You cannot publish events or take bookings.
2.3 You are responsible for everything done under your account. You choose your staff and the roles they have. You must keep staff access up to date and remove people who leave. If your tenant settings require two-factor sign-in, your staff must use it.
2.4 Pixel Haven staff may enter your account only to give support, only with a recorded reason, and only for the permissions in the platform rules. You can see these visits in your audit log.
3. Your address
3.1 Your site is at {your-name}.tiket.ing. Some names are reserved. We may refuse a name that could mislead people, for example a name that looks like a bank, a government body or another brand. [LAWYER: confirm.]
3.2 You cannot change your address yourself. You can ask us to change it. Old links keep working for [12 months].
3.3 If your plan allows it, you may use your own domain. You must control the domain and follow our DNS steps. We may remove a domain that you stop controlling.
4. Selling tickets and taking money
4.1 You connect your own payment gateway (for example BML Connect or MIB) or use bank transfer with a slip. Ticket money goes straight to you. Pixel Haven does not receive, hold or pay out your ticket money. [LAWYER: confirm this does not make Pixel Haven a payment service.]
4.2 You are the seller. The contract to sell a ticket is between you and the customer. You set prices, capacity, dates, audience and rules. We charge customers no service fee.
4.3 You keep your gateway credentials safe. We store them encrypted and show them to nobody. If you change them, we ask you to confirm yourself again. If you think they have leaked, tell your gateway and us at once.
4.4 You are responsible for refunds, chargebacks, gateway fees and bank fees. You set a refund policy for each paid event (26.8). Refunds are made only by your staff with refund permission, or by Pixel Haven support when you ask. Customers cannot refund themselves.
4.5 You are responsible for any tax on your ticket sales. Tiket.ing shows your price as one number and does not work out your tax. [LAWYER: confirm.]
4.6 You must honour the tickets you sell. If you cancel an event or a session, you must follow the cancellation steps in the planner and refund as your policy and the law require.
5. Our fee
5.1 You pay Pixel Haven a monthly fee for the plan you choose ([plan fees]). Plan names, prices and limits are on our pricing page and may change with [notice period] notice.
5.2 A month is billable when booking opens in that month. The month is counted in Maldives time (Indian/Maldives). If any session of a paid event opens booking in a month, that month must be paid before you can publish it. Events with no money (free events, with a price of zero) never need a paid month.
5.3 We do not give automatic free trials. Pixel Haven may grant a free month by hand. Each grant is recorded with a reason.
5.4 We issue an invoice for each billable month. Tax at the rate in force is added on top. [LAWYER: confirm how tax is shown.] You may pay by online gateway or by bank transfer, which our staff confirm.
5.5 If a month is unpaid, you cannot publish events that open booking in that month. Events already on sale are not taken down for this reason alone. [LAWYER: confirm.]
5.6 Fees already paid are not refunded when you close your account, except [as the law requires / as we decide]. [LAWYER]
6. What you must not do
6.1 You must not use tiket.ing to: sell goods or events that are unlawful in the Maldives; mislead people about an event or an organiser; sell tickets you do not intend to honour; collect personal data you do not need; attack, probe or overload the platform; get around limits, queues or bot checks; share staff logins; or upload files that are harmful or that you have no right to use.
6.2 You must not copy another tenant's data or try to see another tenant's data.
6.3 You must have the rights to the images, logos and text you upload. We may remove content that breaks these terms or the law.
7. Your customers and their data
7.1 You decide why and how you use your customers' and your people lists' personal data. We process that data for you to run the service. The data-processing note (26.6) forms part of these terms.
7.2 If you load people lists, you must be allowed to do so. If the list holds children's data (for example students), you must: collect only what you need; tell parents and guardians what you do with it; use the consent wording or your own lawyer-approved wording; set a retention period; limit who on your staff can see it; and delete it when it is no longer needed. [LAWYER: confirm each duty.]
7.3 You must not put children's data into places that are not designed for it, for example free-text fields not marked as sensitive.
7.4 You must follow the rules of the product about who may see children's data: only roles you give the people.view, people.view_sensitive and form_answers.view permissions can see it. Every read is logged. You are responsible for choosing those roles well.
8. Scanning, kiosks and offline use
8.1 Tickets carry a signed QR code. Scanning checks the code and the ticket's status.
8.2 Offline scanning. Scanner devices can keep scanning without a network, using a list stored on the device. While devices are offline, two devices can admit the same ticket. We report these cases to you after the devices sync. A ticket that was refunded or cancelled after the list was downloaded may still be admitted offline. You accept this risk when you use offline scanning.
8.3 Kiosks. A web page cannot lock a tablet. You must lock kiosk tablets with the tablet's own tools (for example Guided Access on iPad). We cannot check this for you.
8.4 You must keep scanner phones locked, not share staff logins, and remove lost devices from your device list at once.
9. Messages
9.1 We send sign-in links and platform messages from our own sender. You may connect your own SMS account (for example MessageOwl) for notifications. You are responsible for the content you send and for your SMS provider's charges.
9.2 We use a mail service that has daily sending limits. During a very large sale, some emails may be delayed. Tickets are always available on the booking page and in the app.
10. Our service
10.1 We work to keep tiket.ing available, but we do not promise it will never fail. [service level]. [LAWYER: decide whether to promise any uptime.]
10.2 We may change or remove features. We will give [notice period] notice of a change that harms you, unless the change is needed for security or the law.
10.3 Big sales may use a waiting room. Pixel Haven may lower the admission rate, force the waiting room on, or pause sales on an event to protect the platform.
11. Suspending and closing
11.1 We may suspend your account if there is fraud, unpaid fees, abuse, a legal need, or another serious reason. We record the reason and tell your Owner by email. While suspended, your site shows a notice, new bookings stop, and existing tickets still scan.
11.2 You may close your account if you have no future sessions with confirmed bookings. We give you an export window of [30 days] to download bookings, payments, people lists and form answers. After the window, the account is closed, your people lists, form answers and form uploads are deleted, and your address stays reserved. [LAWYER: confirm the window and what is kept.]
11.3 We keep bookings, payments and invoices for [retention for financial records]. [LAWYER]
12. Intellectual property
12.1 Tiket.ing, its software and designs belong to Pixel Haven. You get a right to use the service while these terms apply.
12.2 You keep the rights to your content. You give us the right to store, process, show and deliver it to run the service for you.
13. Responsibility
13.1 To the extent the law allows, Pixel Haven is not responsible for: your events; your customers' claims against you; losses from a gateway, bank, mobile network, or other provider failing; or indirect losses. [LAWYER]
13.2 Our total responsibility to you for any claim is limited to [limit of liability]. [LAWYER]
13.3 You will cover claims against Pixel Haven that come from your events, your content, or your breach of these terms. [LAWYER]
14. Changes to these terms
We may update these terms. We give [notice period] notice by email to your Owner and in the planner. If you keep using the service after the date, you accept the new terms. If you do not accept, you may close your account.
15. Law and disputes
These terms are governed by [governing law and courts]. [LAWYER]
16. Contact
[Pixel Haven legal name], [registered address], [contact email].
Questions? Contact us