# Event Registration Database: What Organizers Need to Track

> There is no public Laces database. See what an event registration database should track, what organizers get in the app, and how attendee data stays private.

Source: https://laces.run/blog/event-registration-database (HTML version of this page)

There is no public Laces database. Each organizer's registration records stay private in the Laces app, where the organizer's team can see who registered, who has paid and who has collected their kit, then export that list for their own event.

[Create your event](https://laces.run/app): Every registration lands in one list as it happens. Create your event in the app, free for organizers.

If you searched for a "Laces database" to look up other people's entries, it does not exist. If you are an organizer deciding how to keep your own records, the rest of this guide explains what to track and how to protect it.

## What is an event registration database?

It is the organized record of who signed up for your event, which ticket they chose, whether they paid and whether they turned up. For a small event it might be a spreadsheet. The trouble starts when the form, the payment messages and the door list live in three different places, and someone has to match them by hand.

A useful record answers four questions quickly:

- Who is coming?
- What did they pay for?
- Has the money come through?
- Have they arrived or collected what they are owed?

## How would you build one yourself?

If you are building your own, in a spreadsheet or a real database, keep separate facts in separate places. A workable structure has five parts:

| Table | One row per | Holds |
| --- | --- | --- |
| Events | Event | Name, date, venue |
| Ticket types | Ticket on sale | Name, price, limit, and which event |
| Orders | Purchase | A unique reference, the buyer, the amount, payment status and time, and the payment reference |
| Registrations | Person attending | Name, contact, ticket type, answers, and which order |
| Check-ins | Scan or tick | Which registration, what time, who did it |

Then a few rules will save you later:

1. **Give every record an identifier that never changes.** Names repeat, and people change their phone numbers. Never use either as the key.
2. **Record times rather than yes or no.** "Paid at 14:02" tells you more than "Paid: yes".
3. **Don't delete failed payments.** Mark them, so you can see what happened when someone calls.
4. **Decide who can see what before you add anyone.** A shared spreadsheet usually gives everyone everything.
5. **Set a deletion date when you create it.** Say how long you will keep the data, and who deletes it.

Leave out what you don't need. National ID numbers and health details in a shared sheet are a serious risk if that sheet leaks. Whether you need them at all is a question to settle before collecting them.

Building this yourself is reasonable for a small free event. It gets harder once money is involved, because someone has to match payments to names by hand. Laces keeps these records for you, so there's nothing to design.

## What do organizers get in the Laces app?

Organizers work in the Laces app on a phone, or in the same app in a browser. Each event opens on four tabs:

- **Overview:** earnings, kits collected and orders over time.
- **The people list:** who is coming, on which ticket, and their payment and kit status. The tab takes its name from the event type, such as Runners or Guests. You can search it by name, phone or order code.
- **Orders:** one row per order, what was paid and where it got to.
- **Earnings:** the money for that event.

Nothing here needs typing in. When a participant registers and pays from your event link, the entry appears on its own.

## Which fields should you collect?

A name, phone number and email are always required. You can switch on gender and age group, and add your own questions. If an entry comes with a kit, you can collect shirt size too. You read the answers on each order in the app.

Ask only for what you will use. Every extra question is another place where someone on a slow connection may give up. If you cannot say what you would do with an answer, drop the question.

Medical details need a deliberate decision. They are treated as special personal data, seen only by the organizer and their designated medical staff, and the Privacy Policy sets a 90-day limit after the event for keeping them.

## Why should "registered", "paid" and "checked in" stay separate?

These are different facts, and mixing them causes most record problems:

- **A person can start registering and never pay.** Laces keeps those orders, marked pending, failed or expired, instead of throwing them away. You can nudge them or send a pay link.
- **One order can carry several people.** A group signing up together pays once, so three orders can mean ten people. Orders tells you what was paid. The people list tells you who is coming.
- **Paying is not arriving.** Each person has a ticket, and everyone on one order shares its QR code. Scanning it at the door confirms it is paid, and picking the person records the check-in. You can see that time on the scan screen, but the app has no attendance list or count, and check-ins aren't in the exports. If you need a total, keep a tally at the gate.
- **Cash stays outside this record.** Laces takes payment through the event page and does not record cash. If you accept it, keep a separate signed list and reconcile it yourself. Someone who arrives unpaid can register on their own phone from your link instead, and then joins the same list.

[Talk to the team](https://laces.run/contact): Tell the team what you track today and they can talk through how it would work on Laces.

## How do you export your attendee list?

From the app you can download an event's orders as CSV, Excel or PDF, with one row per order, and its paid participant list as CSV, with one row per person. The participant file includes answers to your own questions, but only when an owner or admin downloads it. Exports work one event at a time, not across all your events at once, and only people with the finance, admin or owner role can export.

A good habit is to export only what a job needs. A caterer needs a headcount, not phone numbers. Once you have finished with a downloaded file, delete it from shared drives and group chats. A list passed around WhatsApp is out of your control.

## Who on your team can see what?

Match each person's role to their job. Revenue stays with the finance, admin and owner roles, so volunteers and event managers never see it. Registration answers are limited to the people you trust with them. A volunteer or pickup point lead is always tied to a single event, so a person scanning tickets sees that event and nothing else. Our guide to [managing volunteers and staff](https://laces.run/blog/how-to-manage-event-volunteers-and-staff) explains each role.

## What is public, and what is not?

An [event listing](https://laces.run/events) shows public details such as the event name, date, place, organizer and price. An event page may also show how many people are going, with up to five sets of initials, once at least three have confirmed. It never shows names, phone numbers or email addresses.

Attendee records are not published and are not a public directory. Entering one event does not put someone on another organizer's list. Order pages open with an order code and are excluded from search engines through robots.txt, so do not post order codes or screenshots of your list in public.

## What are your duties as an organizer?

The organizer is the controller of the registration data for their event. The [Privacy Policy](https://laces.run/legal/privacy) sets out the details, written against Uganda's Data Protection and Privacy Act 2019. The organizer agreement adds that you must not sell the data, or disclose it to a sponsor or partner without the participant's consent.

The policy also gives retention periods. Registration data is kept for 24 months after a completed event, and order and payment records for 7 years. The policy says plainly that these periods are applied on request and on review, not by an automatic timer on every record. Participants can ask for a copy of their data or ask for it to be deleted, though financial records of a completed purchase generally have to be kept.

## Can developers connect to Laces data?

There is no direct database access. There is a Partner API for organizers who want to take registrations on their own site, described on the [developers page](https://laces.run/solutions/developers). An owner or admin creates keys in the app and chooses what each key can do.

Reading orders and their registrations is an extra permission that is off until you switch it on, and it only covers your own organization. The API has no attendee-list or check-in endpoint and no bulk export, so use the app for those. The [API documentation](https://docs.laces.run) has the details.

## Frequently asked questions

### Does Laces have a public database?

No. Public event details are on the events page, but participant records are private to each event's organizer and their team.

### What is the minimum I need to record?

An event reference, a way to contact each person, their ticket type, their registration and payment status, and any consent you need. Add more only when you know what you will do with it.

### Can I export my attendees?

Yes. Owners, admins and finance members can download an event's paid participant list as CSV from the app, one event at a time. Orders are also available as CSV, Excel or PDF.

### Should attendee emails be visible on Google?

No. Keep names, phone numbers and emails off public pages. Never publish your exported list, and share it only with people who need it to run the event.

### Can I look up someone else's entry?

No. A participant finds their own ticket with their order code at [laces.run/o](https://laces.run/o). There is no search across other people's entries.
