Help & policies

Privacy policy

What we collect when you buy a ticket, why, and who sees it.

Last updated (Dhaka)

The short version

  • We collect what is needed to issue your tickets and check your payment, and nothing for advertising.
  • We never see your bKash PIN or balance.
  • The organizer sees your details; door staff see only what they need to let you in. Nothing is sold or shared for marketing.
  • One cookie, and only if you sign in. No newsletter.
  • You can ask what we hold about you, and ask us to correct or delete it.
On this page8 sections

This site is run by a single organizer to sell tickets to their own events. It collects the minimum needed to do that and nothing for advertising.

1What we collect

#
When you register
Your name, email address and mobile number, the tickets you chose, and the order reference.
When you pay
The bKash transaction ID and the mobile number you sent the money from. We never see your bKash PIN or balance.
On tickets
The attendee name on each ticket, and any name changes, with the time they were made.
At the door
When, and at which entrance, each ticket was checked in, and a log of every scan made at the door.
If you sign in
Your email address; for each sign-in, the IP address and browser it came from; and a session cookie. There is no password.

2Why

#

To hold and issue your tickets, to match your payment against the bKash statement, to email you your order page and tickets, to check tickets in at the door (and print the backup list), and to reach you if the event changes. Your mobile number is also how Find my order proves an order is yours.

3Who sees it

#

The organizer, when checking payments, answering your messages and running the door. Door staff see only what they need to let you in. Nobody else, and nothing is sold or shared for marketing.

What door staff see
Attendee nameOn every ticket they scan
Ticket typeOn every ticket they scan
The last 3 digits of the phone that bought the ticketNever shown — when they look someone up by name they ask for them, and the system checks them
The ticket list kept on a door phoneAttendee names and ticket types, and a saved copy of the gate page with its last scans, so the gate keeps working without signal — ticket codes only in scrambled form, and all of it deleted from the phone when its session ends
Printed backup listAttendee names, ticket types, ticket codes and order references

4Where it lives

#

Order and ticket data is stored in our own database. Emails are sent through Amazon Web Services, which handles your email address for that purpose only. Event cover images are stored on Cloudflare. Nothing about you is sent to analytics or advertising services.

5Cookies

#

One cookie, and only if you sign in: it keeps you signed in. (The phones door staff scan with get one more, holding their gate pass.) There are no tracking or advertising cookies.

6Emails

#

You receive emails about your order only: payment instructions, your tickets, a rejection if a payment could not be matched, a notice if your hold expires, news of a change to an event you hold tickets for, and sign-in links you asked for. There is no newsletter.

7How long we keep it

#

Order records — with the check-in record and the log of door scans — are kept after the event so that questions about payments and entry can be answered and the accounts reconciled. Ask, and we will delete the personal details on an order once the event has passed and no payment question is open.

8Your rights

#

Ask us what we hold about you, to correct it, or to delete it, using the contact details below. Quote your order reference if you have one.