Privacy Policy
Last updated: 23 October 2026
This policy is written in plain words to describe how Ticketless actually works. It is not legal advice, and Kampong Labs recommends having it reviewed by a qualified adviser before relying on it as your final compliance document.
Who we are
Ticketless (ticketless.kamponglabs.com and the event pages under it) is run by Kampong Labs in Singapore. We follow Singapore's Personal Data Protection Act 2012 (PDPA).
Our Data Protection Officer is reachable at kamponglabs@gmail.com.
Who decides what is collected depends on the event. When an organisation runs an event (a company, school, community group or venue), the organisation decides what guest data to collect, and Kampong Labs handles it for them as their data intermediary. When hosts use Ticketless for a wedding or family event, they use it for personal purposes. For our own website, enquiries and technical data, Kampong Labs decides.
What we collect
Guests
- Your email address -- to send a one-time sign-in code, to email you your ticket link, and (where the organiser has it turned on) a post-event summary of what you redeemed.
- Ticket and redemption activity -- which booths, passport tasks, trivia quests and lucky draw entries are linked to your ticket, so the event can track redemption limits and run its lucky draw fairly. If the event uses NFC cards or tags, taps are recorded too.
- Spin the wheel -- only for events that use it: the prize you won on your one spin (or that you got no prize), when you spun and when you collected it at the prize counter, linked to your ticket.
- GEVME ticket numbers -- only for events that sell tickets through GEVME: the GEVME ticket numbers scanned at the registration counter are stored with the tickets they were exchanged for, so we can issue those tickets and recover them if they are lost. The event's organisers and admins can see and download them in the event's ticket list. A number is removed when its ticket is deleted, and all of them are deleted with the event's guest data, 90 days after the event ends.
- Voting contestants' name, contact number and photo -- only for events with a contest that residents vote on: a contestant's real name, contact number and a photo taken at the registration counter when they sign up. They are only visible to the event's organisers and admins, never to residents, counter volunteers (once registered) or the public, and are used only to contact the contestant about the contest. The contestant's nickname and photo are shown to everyone who votes. The name, number and photo are all deleted with the event's guest data, 90 days after the event ends (the photo file is removed from storage within about an hour after that); the nickname stays with the poll.
- Food and drink orders and queue places -- only for events that use them: what you ordered at a counter (the items and options you chose, with the time it was placed, prepared and collected, or forfeited if it wasn't collected), and your place in a queue (your queue number and when you joined, were called and were served). Orders are free: no payment details are collected. If you press "Alert me", your browser's notification address is linked to your ticket so we can tell you when your order or turn is ready.
- Event-specific details -- only for events that use them: your table and the time you arrived (seated events), your RSVP reply with party size and dietary needs (dietary needs are shared with the event's caterer and never shown on screen), your name and mobile number at a registration desk, and certificates of attendance.
- Photos, questions and wishes -- see "Photo wall and Q&A" below.
Organisers and staff
- Name, work email, role and the events you manage.
- Actions you take in the console (for example edits and exports), kept as an audit record.
People who contact us through the website
- Name, email, phone (if given), organisation and your message.
Technical data
- Standard web request data such as IP address and browser type. We use it to stop abuse (for example, guessing sign-in codes) and to fix errors. In our error logs, an IP address is stored only as a salted hash, not in readable form. The one exception is the short-lived rate-limit record that limits sign-in code requests: it keeps the IP address as it is for 2 days, then deletes it.
We do not ask guests for payment card details, bank details or government ID numbers. Organisers should not upload NRIC numbers unless the law requires it.
Why we collect it
- To run the event you signed in to: your ticket, redemptions, lucky draw and event emails.
- To keep Ticketless secure, working and free from abuse.
- To reply to enquiries and to look after our customers.
- To meet our legal duties.
For guests, we rely on the consent you give when you sign in, and on the organiser's notice to you. We do not sell your information and we do not share it with anyone for their own marketing.
Who we share it with
The organisers and staff of the event you joined can see your event data. Kampong Labs staff can see it to run and support the service. We also use these service providers (sub-processors) to run Ticketless:
| Service | What it does for us | Data it handles | Country |
|---|---|---|---|
| Supabase | Database and sign-in. Stores all event data. | Everything described above: emails, tickets, redemptions, RSVPs, photos, questions, enquiries. | Singapore |
| Vercel | Hosts the website and runs our server functions. | Web requests (IP address, browser type) and the data passing through the site. | United States company; servers in Singapore |
| Sentry | Finds and fixes errors. | Technical error details and short masked screen replays. Emails, phone numbers and NRIC-like numbers are removed first. | Germany (European Union) |
| Resend | Delivers our emails (sign-in codes, ticket links, reminders, summaries). | Your email address, the email content and delivery status. | United States |
| Anthropic | AI drafting for organisers (for example programmes, announcements, seating suggestions and guest list import) and, for weddings, checking guest wishes and photos before the couple approves them. | Text, images and PDFs the organiser chooses to send, and, for weddings, guest wishes and photos sent for checking. Personal contact details (emails, phone numbers, NRIC-like numbers) are removed from guest lists, RSVP messages, wishes, seating notes and feedback before sending. | United States |
| Meta Platforms (WhatsApp Business Platform) | Delivers WhatsApp messages, only when an organiser uses WhatsApp sending (for example wedding invitations, reminders and thank-yous). | The recipient's phone number, the household name and the message text. Not used unless WhatsApp sending is switched on for the event. | United States and Ireland |
Anthropic only receives what an organiser chooses to send: text, images and PDFs for AI drafting and, for weddings, guest wishes and photos for checking. We remove personal contact details from guest lists, RSVP messages, wishes, seating notes and feedback before sending; text an organiser writes to be published as written is sent as it is. By default, under its commercial terms, Anthropic does not use that text or its replies to train its models. We may also share information when the law requires it.
Sending data overseas
Some of these providers are outside Singapore (the United States, Germany and Ireland). When your data goes overseas, we only use providers that have signed a data processing agreement with us that requires them to protect it to a standard comparable to the PDPA. We keep the number of providers small and send them only what they need.
Photo wall and Q&A
Photos you upload to an event's photo wall are reviewed by the event's staff first. After they approve it, your photo is shown on the event's screens and to other guests. It is deleted with the event's data. Only upload photos you have permission to share. Questions you ask speakers and wishes you leave for hosts are shown on screen only after the event's staff approve them. Wishes may be kept by the hosts as a keepsake.
Children
Some events are for children, such as school and community events. Organisers of these events must get consent from a parent or guardian where the law needs it, and must tell parents what is collected. If you think a child's details were given without a parent's consent, write to us and we will help sort it out.
How long we keep it
| Data | How long |
|---|---|
| Guest data (emails, tickets, redemptions, RSVPs, photos, questions, wishes) | Deleted automatically 90 days after the event ends, unless the organiser agrees a different period with us. |
| Wedding data | Deleted 90 days after the event. |
| Certificates of attendance | Kept for 24 months so people you show one to can check it. After that your name is removed. |
| Error logs | 30 days. |
| Sign-in rate-limit records (these keep the raw IP address, to stop abuse) | 2 days. |
| Error reports held by Sentry | Up to 90 days, then Sentry deletes them. |
| Email delivery logs | 90 days. |
| NFC card and tag activity logs | 90 days. |
| Spin-the-wheel result (the prize you won, when you spun, and when you collected it) | Deleted with the event's guest data, 90 days after the event ends. The organiser's prize list stays. |
| Voting contestants' name, contact number and photo (entered at the counter, name and number only visible to the organiser) | Deleted with the event's guest data, 90 days after the event ends. The photo file is removed from storage within about an hour after that. The nickname shown in the vote stays with the poll. |
| Food and drink orders, queue places and alert subscriptions | Deleted with the event's guest data, 90 days after the event ends. The organiser's counters and menu stay. |
| Website enquiries | 24 months after the last contact, unless the person becomes a customer. |
| Database backups | Deleted data can remain in encrypted backups for up to 7 days. |
You can ask us to delete your data earlier. The law may sometimes require us to keep certain records for longer.
Security
Sign-in uses a one-time code instead of a password. Access to event data is limited to that event's own organiser accounts. Connections are encrypted, staff access is controlled, and error reports are scrubbed before they leave our systems. No system is completely risk-free. If a data breach could cause you significant harm, we will tell the Personal Data Protection Commission (PDPC) and affected people as the PDPA requires.
Your rights
Under the PDPA you can:
- ask what personal data we hold about you and how we use it (access);
- ask us to correct data that is wrong (correction); and
- withdraw your consent to our using your data. Tell us and we will explain what that means for you.
To ask, email kamponglabs@gmail.com. Tell us your name, the email you used and the event. We may need to check it is really you. We reply within 30 days. If we need longer, we will tell you why and when.
If you were a guest at an organisation's event, please contact the organiser first, because they decide what is collected. If you write to us, we will pass your request on and help the organiser answer it.
Cookies and local storage
Ticketless uses only what it needs to work: your language choice, your signed-in ticket, display settings and small remembered choices on your own device. We do not use advertising or tracking cookies, and we do not run third-party analytics or advertising scripts. You can clear this data in your browser at any time, but you may need to sign in again.
Changes to this policy
We may update this policy as the product changes. The date at the top shows when it last changed. Material changes will be shown here.
Contact us
Data Protection Officer: kamponglabs@gmail.com