Audience gathered at an event venue

Legal and privacy

Privacy notice

How TownTickets handles personal information across accounts, events, tickets, orders, organiser verification, and support.

Effective 5 August 2026

This notice explains TownTickets' current information-handling practices. It should be read together with the Terms of Use and any event-specific notice supplied by an organiser.

1. Who this notice applies to

This privacy notice applies to people who visit TownTickets, create an account, buy or receive tickets, join a waitlist, order event products, organise an event, submit verification documents, contact support, or otherwise use the platform.

TownTickets operates in South Africa and processes personal information with regard to the Protection of Personal Information Act, 2013 (POPIA) and other applicable South African requirements.

2. Information we may collect

Account information may include your name, email address, profile image, password credential or Google account identifier, account role, and session information.

Transaction and event information may include ticket selections, event attendance records, order references, payment status, refunds, transfers, check-ins, waitlist entries, delivery or collection choices, and communication linked to an event or order.

Organiser information may include business and contact details, identity and selfie documents, company registration records, bank-confirmation documents, event information, payout records, and verification decisions.

Technical information may include device and browser details, IP-derived security or approximate location signals, timestamps, logs, cookie identifiers, and information needed to prevent abuse and keep the platform reliable.

3. Google sign-in

When you choose Sign in with Google, TownTickets receives a Google account identifier, your verified email address, and, when available, your name and profile picture. The permanent Google account identifier is used to recognise the same account safely over time.

TownTickets does not request access to your Gmail messages, Google Drive files, contacts, calendar, or other Google services for account sign-in.

4. How we use information

We use personal information to create and protect accounts, process bookings and orders, issue and validate tickets, operate event check-in, communicate important service information, support organisers, review verification submissions, prevent fraud, resolve disputes, comply with legal obligations, and improve the reliability of TownTickets.

We may also use limited contact information for relevant service updates. Promotional communication will be handled in accordance with applicable law and available opt-out choices.

5. Payments

Payments may be processed by an external payment provider. TownTickets receives the payment reference, amount, status, and related order information needed to complete or reconcile a transaction. Card or banking credentials entered directly into a payment provider's service are handled by that provider under its own terms and privacy practices.

6. When information may be shared

Information may be shared with the relevant event organiser where necessary to manage attendance, customer support, delivery, collection, refunds, safety, or an event-specific obligation.

We may use service providers for hosting, databases, email delivery, storage, payment processing, fraud prevention, and operational support. They receive only the information reasonably necessary for their role and are expected to protect it.

Information may also be disclosed where required by law, a lawful authority, a court process, or where reasonably necessary to protect users, TownTickets, organisers, or the public.

7. Security and retention

TownTickets uses access controls, protected sessions, encryption in transit, restricted administrative functions, and other technical and organisational safeguards appropriate to the platform. No online service can guarantee absolute security.

Information is kept only for as long as reasonably needed for the purpose for which it was collected, legitimate operational needs, dispute handling, fraud prevention, accounting, tax, regulatory, or other legal obligations. Retention periods may therefore differ by record type.

8. Cookies and local storage

TownTickets uses essential cookies and similar browser storage for secure sign-in, session continuity, fraud protection, preferences, and core platform operation. Blocking essential cookies may prevent account and checkout features from working correctly.

9. Children and learner events

Some events may involve schools, learners, or families. A parent, guardian, school, or authorised organiser should provide or manage a child's information where consent or authorisation is required. Organisers remain responsible for obtaining permissions that apply to their event activities.

10. Your choices and rights

Subject to applicable law and identity verification, you may ask whether TownTickets holds personal information about you, request access to it, ask for inaccurate or outdated information to be corrected, object to certain processing, withdraw consent where consent is the basis for processing, or request deletion where TownTickets is no longer authorised or required to retain the information.

Some information cannot be deleted immediately where it must be retained for completed transactions, fraud prevention, disputes, tax, accounting, regulatory, safety, or other lawful purposes.

11. Contact and complaints

Privacy questions or requests can be sent to info@towntickets.co.za. Please provide enough information for TownTickets to identify the relevant account or record without sending passwords or unnecessary identity information by email.

You may also lodge a complaint with the Information Regulator of South Africa if you believe your personal information has been handled unlawfully.

12. Updates to this notice

This notice may be updated when TownTickets services, providers, or legal obligations change. The current version will remain available on this page with its effective date.