PAIA Manual
Prepared under section 51 of the Promotion of Access to Information Act 2 of 2000, as amended, for [EventU to confirm: registered name of the business that operates EventU], which runs EventU.
Last updated: 22 October 2026
This document is a draft awaiting legal review. Highlighted text in square brackets is still to be confirmed.
Acronyms and Abbreviations
| Term | Meaning |
|---|---|
| EventU | [EventU to confirm: registered name of the business that operates EventU], which runs the EventU platform |
| DIO | Deputy Information Officer |
| IO | Information Officer |
| PAIA | Promotion of Access to Information Act 2 of 2000, as amended |
| POPIA | Protection of Personal Information Act 4 of 2013 |
| Regulator | Information Regulator of South Africa |
| Republic | Republic of South Africa |
Purpose of This Manual
This manual helps you to:
- see which records EventU makes available without a request;
- understand how to request access to a record EventU holds;
- see which records EventU keeps because other laws require them;
- find the contact details of the Information Officer and Deputy Information Officer;
- find the Regulator’s Guide on how to use PAIA;
- know why EventU processes personal information, about whom, who receives it, whether it leaves South Africa, and how it is kept secure.
Key Contact Details
| Detail | Contact |
|---|---|
| Business Name | [EventU to confirm: registered name of the business that operates EventU] |
| Registration Number | [EventU to confirm: CIPC registration number] |
| Information Officer | [EventU to confirm: Information Officer's name] |
| Information Officer Telephone | [EventU to confirm: Information Officer's telephone number] |
| Deputy Information Officer | [EventU to confirm: Deputy Information Officer's name] |
| Access to Information Email | privacy@eventu.co.za |
| Postal Address | [EventU to confirm: postal address] |
| Physical Address | [EventU to confirm: physical address] |
| Telephone | [EventU to confirm: telephone number] |
| General Email | booking@eventu.co.za |
| Website | eventu.co.za |
The Guide on How to Use PAIA
Under section 10 of PAIA, the Regulator has published an updated Guide on how to use PAIA and POPIA. It explains your rights, how to make a request to a public or private body, the fees, and the help and remedies available to you. It is available in every official language and in braille.
You can get the Guide from the Information Officer on request, or from the Regulator’s PAIA resources page. The Information Officer keeps a copy for public inspection during normal office hours in [EventU to confirm: the two official languages the PAIA Guide is kept in].
The Regulator’s contact details:
- Physical address: Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191
- Telephone: 010 023 5200
- General enquiries: enquiries@inforegulator.org.za
- PAIA complaints: PAIAComplaints@inforegulator.org.za
- POPIA complaints: POPIAComplaints@inforegulator.org.za
- Website: inforegulator.org.za
Records Available Without a Request
| Category | Records | How to Get Them |
|---|---|---|
| Public documents | Privacy Policy, Terms of Service, Organiser Terms, this manual, pricing and developer documentation | On eventu.co.za |
| Public event information | Published event listings, organiser storefronts and public event galleries | On eventu.co.za |
| Your own account information | The personal information EventU holds about you | Your privacy dashboard |
Records Kept Under Other Laws
EventU keeps records under the following laws, where they apply to it:
| Category of Records | Applicable Legislation |
|---|---|
| Memorandum of Incorporation, registers and company records | Companies Act 71 of 2008 |
| This PAIA manual | Promotion of Access to Information Act 2 of 2000 |
| Records of personal information processing | Protection of Personal Information Act 4 of 2013 |
| Tax records | Income Tax Act 58 of 1962 and Tax Administration Act 28 of 2011 |
| VAT records, where EventU is registered for VAT | Value-Added Tax Act 89 of 1991 |
| Consumer transaction and refund records | Consumer Protection Act 68 of 2008 |
| Electronic transaction records | Electronic Communications and Transactions Act 25 of 2002 |
| Employment records, where EventU has employees | Basic Conditions of Employment Act 75 of 1997, Labour Relations Act 66 of 1995, Employment Equity Act 55 of 1998 and Unemployment Insurance Act 63 of 2001 |
Subjects and Categories of Records
| Subject | Categories of Records |
|---|---|
| Business administration | Incorporation documents, resolutions, registers, contracts with suppliers and service providers |
| Finance and tax | Financial statements, invoices, Paystack settlement and reconciliation records, tax returns |
| Buyers and attendees | Accounts, orders, tickets, check-in records, food and drink choices, marketing preferences and opt-outs, privacy requests |
| Organisers | Organisation profiles, team members and roles, door staff assignments, events, refund policies, payout account details, uploaded compliance documents, activity logs |
| Vendors | Business profiles, portfolio media, verification documents, quotes, bookings, payout details, reviews |
| Event content | Event galleries, photo removal requests, lost and found reports |
| Developers | API tokens (stored as one-way hashes), request logs, webhook subscriptions and deliveries |
| Security and operations | Audit logs, rate-limit and anti-abuse records, email and message delivery records |
Processing of Personal Information
Purpose of Processing
EventU processes personal information to:
- sell and deliver tickets and run check-in at events;
- pay organisers, vendors and resale sellers through Paystack;
- process refunds and handle payment disputes;
- connect organisers with vendors and support event catering;
- send service messages, and marketing to people who opted in;
- prevent fraud and keep the platform secure;
- meet its tax, accounting and other legal obligations.
Data Subjects and Their Information
| Data Subject | Personal Information |
|---|---|
| Buyers and attendees | Name, email address, phone number, orders and tickets, check-in records, food and drink choices, answers to an organiser’s questions (which can include ID or passport numbers and health information), Paystack’s payment record (the payment number, reference, amount, fee, status, channel and dates, with no part of the card number, no customer details and no IP address), IP address, marketing preferences, from 22 October 2026, the record of the terms they accepted or were shown (which document and version, where and when; no IP address or device details) |
| Organisers and team members | Name, contact details, role, organisation details, bank account and identity details needed for the Paystack payout account, uploaded compliance documents |
| Door staff | Name and email address of the account, the event and organisation they were added to, who added them and when, the tickets they scan and when, and audit records of adding, removing and scanning. The organiser who adds them gives the email address |
| Vendors | Business and contact details, profile and portfolio media, verification documents, bank details for payouts, busy times from a linked calendar (never entry titles) |
| People in event photos | Images in event galleries |
| People reporting lost property | Name, contact details and a description of the item |
| Website visitors | IP address, browser and device information, security records |
| Suppliers and service providers | Names and contact details of contact people |
Who Receives It
| Recipient | Why |
|---|---|
| Event organisers | Attendee details for their own events, for check-in and running the event; and the people they added as door staff |
| Vendors booked for an event | What they need to deliver, such as food and drink counts for a caterer |
| Paystack | Payments, payouts, refunds and payout accounts |
| Supabase | Database and sign-in hosting |
| Hetzner | Server hosting |
| Hostinger | Email delivery |
| Meta (WhatsApp) | Ticket and event messages, where WhatsApp messaging is on |
| Calendar linking, when a user chooses it, and place suggestions when an organiser or vendor types their city | |
| Anthropic | Reading a menu a vendor chooses to import; the file is not stored |
| The software developer that builds and maintains EventU | Building, supporting and fixing the platform under contract, which can mean seeing the information it holds |
| Authorities and professional advisers | Where the law requires it, and for audit and legal advice |
Transfers Outside South Africa
EventU’s database is in Ireland, in the European Union (Supabase), and its servers are in Germany, in the European Union (Hetzner, Falkenstein). Some of the providers listed above, including Meta, Google, Anthropic and Hostinger, may process personal information in other countries. EventU transfers personal information outside South Africa only as section 72 of POPIA allows.
Security Measures
- The site is served only over encrypted connections (HTTPS).
- Each organisation’s data is kept apart by row-level security rules in the database.
- Full card numbers never reach EventU’s systems; payments run through Paystack. Of Paystack’s payment record, only the payment’s own details are stored.
- Door staff are added for one event and can scan only that event’s tickets; removing them ends their access.
- Staff roles are held in the database where users cannot change them.
- API tokens are stored as one-way hashes, and webhook deliveries are signed.
- Confidential documents are stored outside the public web folder and shown only to authorised members of the organisation and to EventU staff.
- Checkout and other sensitive actions are rate-limited.
- Organiser and administrator actions are recorded in audit logs.
- Marketing opt-outs are checked before every WhatsApp message and are kept after an account is deleted.
How to Request Access to a Record
- Complete Form 02, Request for Access to Record, and send it to the Information Officer at privacy@eventu.co.za or the postal address above.
- Describe the record clearly enough for it to be found, say how you want access, and state the right you want to exercise or protect and why you need the record for it.
- Include proof of your identity. If you ask on behalf of someone else, include proof that you may act for them.
- For your own personal information you can also use your privacy dashboard.
Fees. A requester other than a personal requester pays the request fee prescribed for private bodies, currently R140. Access fees for copies, search and preparation may also apply, and a deposit may be asked for. The current amounts are in the Regulator’s fee structure.
Timing. EventU decides a request within 30 days of receiving it. It may extend this once, by up to 30 more days, and will tell you why. If a record concerns someone else, EventU tells that person and lets them respond before deciding.
Refusal. PAIA lets a private body refuse access on the grounds in Chapter 4 of its Part 3, for example to protect another person’s privacy, confidential or commercial information, someone’s safety, or legally privileged records. A refusal is given in writing with reasons. Access must still be given where PAIA’s public interest test requires it.
If you disagree. You may complain to the Regulator using its Form 05, Complaint Form, or apply to court, within the time PAIA allows.
Availability of This Manual
This manual is available:
- on this page;
- for inspection at EventU’s office during normal business hours, at [EventU to confirm: physical address];
- to anyone on request, for the prescribed copying fee;
- to the Regulator on request.
Updating This Manual
EventU reviews this manual regularly and updates it when its records or processing change. The date at the top shows the current version.
Issued by [EventU to confirm: Information Officer's name], Information Officer, [EventU to confirm: registered name of the business that operates EventU].