Booking data and UK GDPR: what small organisations should collect (and what to leave out)
This is a practical guide, not legal advice. For your own situation, read the ICO's guidance or speak to an adviser.
Every booking form is a data collection form. Churches, charities and small businesses often collect far more than they need, usually because a template asked for it. Under UK GDPR, that's a problem as well as a risk.
The principle that matters most: data minimisation
UK GDPR says personal data should be "adequate, relevant and limited to what is necessary" for the purpose. The ICO's guidance on data minimisation explains this in detail, including the advice to review what you hold and delete what you don't need.
For a booking, ask: what do we actually need to hold this appointment and contact the person about it? Usually:
- A name, so you know who to expect
- One way to contact them, for the confirmation and any changes
- The time and service
That's often it.
What to leave out
- The reason for visiting. It's rarely necessary to hold the slot, and it's often sensitive (health, money, family, faith). If you need it for triage, make it optional and limit who can see it.
- Date of birth and address, unless the service genuinely depends on them.
- Free-text notes about the person in the booking system. Case notes belong in a system built for them.
- "Nice to have" questions that nobody reads.
Storage limitation: don't keep it forever
The ICO's storage limitation guidance says you shouldn't keep personal data longer than you need it. For bookings, decide a retention period (for example, six months after the appointment), then delete or anonymise contact details. Keep anonymous counts for reporting.
Who can see what
- Give each person the least access they need. A front-desk volunteer doesn't need everyone's contact details.
- Don't show names on waiting-room screens. Numbers work.
- Keep a record of who accessed contact details, if your system supports it.
Tell people what you do
A short privacy notice on your booking page should say what you collect, why, who processes it (for example, your booking provider and email service), and how long you keep it.
Make requests easy to handle
People can ask for a copy of their data or for it to be erased. Pick a system that can export one person's records or erase their details without a support ticket.
How Calnify helps
- A reason for visiting is never required, and every field except a name can be made optional.
- Extra questions can be marked sensitive, so only owners and admins can read answers.
- Waiting-room screens and text messages never show names or reasons.
- Each organisation sets a retention period; contact details are deleted automatically after it.
- Admins can export or erase one customer's details, and access to contact details is logged.
Further reading: the ICO's guide to the data protection principles.