Roamly
    Planning

    Handling traveller data on group trips under UK GDPR

    • Last reviewed
    • 6 min read
    • For universities, schools, sports teams, production crews, event organisers, corporate groups

    The short answer

    Under UK GDPR you should collect only the traveller data you need, tell people how you will use it, share each supplier only the fields it needs, keep sensitive information such as medical and dietary details tightly controlled, and delete it when the trip and its reconciliation are finished. If you lose control of the data, a notifiable breach must be reported to the ICO without undue delay and where feasible within 72 hours. This is general information, not legal advice.

    Key takeaways

    • Collect only what each stage of the trip needs, and ask for passport and medical details later rather than at first sign-up if you can.
    • Health information is special category data. Dietary and access requirements can reveal health or belief, so treat them as sensitive.
    • Share with each supplier only the fields it needs: a coach company needs names and times, not passport numbers.
    • Set a retention period for each data type, delete data you no longer need and do not keep it 'just in case'.
    • Know your breach process in advance: the ICO expects notifiable breaches to be reported without undue delay, where feasible within 72 hours of becoming aware.

    What traveller data do group trips collect?

    Group trips gather more personal data than most activities: names, contact details, dates of birth, passport and visa details, emergency contacts, medical conditions, dietary and access needs, photos and payment information. Some of it is shared with airlines, hotels and transport companies, and some stays with your leaders on the trip. Under UK GDPR, you are responsible for how each item is collected, used, shared and kept.

    Our guide to conference and delegate travel discusses how registration data should flow into bookings. The same principles apply to any group.

    What does data minimisation mean in practice?

    The ICO's guidance on data minimisation says personal data must be adequate, relevant and limited to what is necessary for its purpose. It advises being clear about why you need data before collecting it and not collecting it speculatively. For a group trip, that means mapping each data item to a purpose and a recipient.

    Map each item to a purpose and recipient before collecting it
    Data itemWho actually needs itPractical approach
    Name and contact detailsOrganiser, leaders, most suppliersCollect at sign-up
    Passport detailsAirline, visa authority, hotel where requiredCollect when bookings need them, from the people who need them
    Medical informationTrip leaders and, if needed, medical respondersCollect on a dedicated form; limit access to named leaders
    Dietary and access needsCaterers, hotels and transport in anonymised or minimal formShare only the requirement, not the person's reasons
    Emergency contactLeaders and home contactKeep a secure copy at home base
    Payment dataPayment processorDo not store card details in spreadsheets

    Ask for flight details only from travellers who will use your transfers, and only ask for passport details from those whose bookings need them.

    How should you treat medical, dietary and access information?

    The ICO treats health data as special category data, and says processing it needs a lawful basis plus a separate condition. Dietary requirements can reveal health conditions or religious belief, and access requirements can reveal disability. The ICO's own privacy notice for its events treats dietary and access information as special category data, asks for it only after places are allocated and does not share it with venues in an identifiable form, which is a useful model.

    • Ask only what you need, and explain how the information will be used.
    • Limit access to the named leaders who need it, and store paper forms securely.
    • Give suppliers the requirement (for example 'vegetarian meal') without the individual's medical reason.
    • Delete or destroy the information when the trip and any incident follow-up are complete.

    What do you need to tell travellers and what must you agree with suppliers?

    The ICO says that when you obtain personal data from someone other than the individual, for example a school passing on pupil details or a company providing staff lists, you must provide privacy information within a reasonable period and no later than one month. The deadline is earlier if you use the data to contact the individual or disclose it to someone else. Privacy information must also tell people the categories of data and its source. The ICO adds that its guidance is under review because of the Data (Use and Access) Act, so check the current version.

    Where a supplier handles data on your behalf, such as a booking system or an event registration tool, the ICO says UK GDPR requires a written contract with a processor. Under Article 28 it must cover, among other terms, processing only on documented instructions, a duty of confidence, security measures, rules on sub-processors, help with individuals' rights, and deletion or return of data at the end. Airlines and hotels often act as controllers in their own right, so you will not always be able to dictate their terms. Ask each supplier which role it takes.

    How long should you keep traveller data?

    The ICO's storage limitation guidance says you must not keep personal data for longer than you need it, and that the UK GDPR does not set fixed periods. Your periods should follow from your purposes and you should be able to justify them. It also says to avoid indefinite 'just in case' storage, to document standard periods where possible and to review them regularly.

    • Set a deletion date for each data type when you plan the trip, for example after the final reconciliation and any claim period.
    • Include leaders' phones, messaging groups and shared drives in your deletion plan.
    • Keep what the law or an insurer requires, and record why.
    • After an incident, retain only what you need for the investigation, insurance claim or legal obligations.

    What if something goes wrong with the data?

    If data is sent to suppliers outside the UK, such as hotels in other countries, the transfer rules may apply. The ICO's guide to international transfers was restructured in January 2026, so read its current version or ask your data protection officer.

    How Roamly can help

    Roamly helps organisers collect only the information each booking needs and send each supplier the fields it requires. Our consulting service can help build trip forms and a simple data-handling plan, and our free travel document checklist lists what to gather. For anything beyond general guidance, take advice from your data protection officer or the ICO. To discuss a trip, contact us.

    Sources

    1. ICO: Principle (c), data minimisation
    2. ICO: Principle (e), storage limitation
    3. ICO: What is special category data?
    4. ICO: Privacy notice, attend an event, seminar or workshop
    5. ICO: When should we provide privacy information?
    6. ICO: What needs to be included in the contract?
    7. ICO: Personal data breaches, a guide

    General guidance only, checked against the sources above on 30 October 2026. Entry rules, airline policies and official advice change, so confirm the current position with the linked source before you travel.

    Questions organisers ask

    Not necessarily. UK GDPR gives several lawful bases and you must choose and record the right one. Health data also needs a separate condition because it is special category data. Ask your data protection officer which applies to your organisation.

    Usually not. The ICO's data minimisation principle says data should be limited to what is necessary, so share with each supplier only the fields it needs for its service.

    Only as long as you need it for the purpose. UK GDPR sets no fixed period, so decide and record your own, for example after reconciliation and any insurance claims, and delete or anonymise afterwards.

    Any security incident that leads to accidental or unlawful loss, access, disclosure or alteration of personal data. A lost phone with traveller details or an email sent to the wrong group is an example.

    They can be practical, but they spread personal data across personal devices and phone numbers. Agree rules in advance, limit what is shared in the chat, and delete the group and its contents after the trip.

    Ready to discuss your travel programme?

    Tell us where your group is going and we'll set out how we would plan it.

    Start a Proposal