How long should event organizers keep attendee data?

Keep attendee data for as long as you can explain why your event business needs it, subject to the laws that apply to the record. There is no single GDPR deadline for deleting an attendee list: the right period depends on whether you're delivering an event, handling a refund, keeping accounting records or marketing your next show.

A single deadline would be simpler. Separate periods are more useful. Your accountant may need a sales record after your door team has finished with the guest list. A buyer may want future event announcements after their accessibility request has stopped being relevant. Those records shouldn't all share an expiry date.

So you're an event organizer, the show is over, and the next one is taking over your week. Somewhere there's a ticketing account, a spreadsheet on someone's laptop and an old email audience. What stays? What goes? And who does the deleting?

This guide walks you through separating those records, choosing defensible retention periods and carrying out the cleanup. It uses UK and EU data protection principles as its main reference. Your tax obligations, marketing rules and legal claims depend on your jurisdiction and business, so have the relevant adviser check those parts before adopting a schedule.

Start with the purpose, then choose the period

The first thing to do is stop treating "attendee data" as one thing.

A ticket order has a purpose. A catering note has another. An unsubscribe record has another again. If all you can say about an old file is "that's everyone who came," you haven't identified why you still need the information inside it.

Under Article 5 of the EU GDPR, personal data must be limited to what is necessary and kept in identifiable form only for as long as the purpose requires. Articles 13 and 14 also require information about the retention period or the criteria used to determine it. That means your explanation to attendees and your actual practice need to agree.

The UK's Information Commissioner's Office says its storage limitation guidance does not prescribe specific time limits for different kinds of data. You choose and justify them. The ICO currently marks this guidance as under review following the Data (Use and Access) Act, so check its current position when finalising your policy.

Here's the practical question to ask about each record: what would become harder, impossible or legally noncompliant if we deleted this now?

"We couldn't answer an unresolved refund complaint" is a specific answer. "It might be useful someday" is a weak one. "We need the transaction record for an identified accounting requirement" is specific. "Marketing likes having a big database" doesn't tell you which information marketing needs or whether it can use it.

Give each purpose an ending. The event happens. The complaint closes. The applicable accounting period expires. The person unsubscribes. A review finds that an old marketing contact no longer has a defensible reason to remain active. Without an ending or a review trigger, "for as long as necessary" turns into "until someone remembers."

Separate the records your business actually holds

Start with your next paid event and follow a buyer through it. They place an order, receive tickets, get event updates and arrive at the door. They might transfer a ticket, ask for a refund or tell you about an access need. They might also agree to hear about future events.

Each step can leave a different record. Your retention schedule should follow those differences.

Ticket orders and financial records

You need enough information to fulfil the purchase, reconcile payments and deal with the relevant aftercare. After that, some transaction information may still belong in your accounting records.

For a UK limited company, GOV.UK's company and accounting records guidance says records generally need to be kept for six years from the end of the last company financial year they relate to, with circumstances that require longer retention. That is a rule about the specified records and business type. It does not mean every attendee field should remain attached to them for six years.

Ask your accountant which fields are actually required. An invoice or transaction record doesn't automatically need a dietary preference, a detailed support conversation or a marketing tag. Keeping those together is convenient until you have to explain why they are still there.

Don't confuse the buyer with every ticket holder, either. Someone may buy tickets for friends or colleagues. A requirement to keep information about the purchase doesn't automatically justify keeping extra details about everyone who attended.

Door lists and check-in information

The door team needs to know whether the ticket is valid and whether someone has already used it. They don't need a copy of your entire customer history to answer that question.

After the event, attendance records might support a specific investigation, a refund decision or reporting you genuinely need. Choose the necessary fields for that job. A printed backup list that helped during a network problem has its own cleanup task, even if your main ticketing system is well managed.

Where software already provides access for the door team, use it before making another export. With Loopyah's ticket check-in tools, door staff can scan tickets using their own phones with check-in access. That reduces unnecessary spreadsheet exports.

Access requests, health information and catering notes

Some attendee information deserves a shorter route through your business. A person may tell you about a health condition so you can arrange suitable access. That doesn't make the condition a useful permanent customer attribute.

The ICO explains that processing special category data requires an Article 6 lawful basis and a relevant Article 9 condition, plus applicable UK requirements. Information revealing health can fall into this category. A dietary request may also reveal sensitive information, depending on what it says and the context.

Our event registration form guide helps you decide what to ask before those answers become records you have to manage. Collect what the team needs to provide the arrangement. Share it only with the people doing that work. Review it when the arrangement and any related issue are finished. An active complaint or legal requirement can change the decision for relevant records.

If the same attendee returns, let them provide current requirements. Last year's note can be inaccurate, and automatically carrying it forward can expose information they didn't expect you to reuse.

Marketing contacts and permission records

A marketing contact is a separate decision from a ticket receipt. You need to understand why you may contact that person, what they agreed to and whether the current use still fits.

In the UK, the ICO's electronic mail marketing guidance explains consent and the limited exception for an organization's own customers or people whose details it obtained during sales negotiations, often called the soft opt-in. That exception has conditions, including similar products or services and an opt-out at collection and in each message. A ticket purchase alone doesn't establish that all those conditions were met.

Keep the evidence your chosen approach requires. Where you rely on consent, that may include when and how it was given and the wording shown. Check relevance as well as permission. Someone who subscribed to a particular conference shouldn't be surprised by an unrelated event brand appearing in their inbox.

Write a schedule your team can use

Your schedule must answer, "Can I delete this export?"

For each record category, write the purpose, the fields needed, the rule or reasoning behind the period, when the clock starts, where copies live and who owns the action. Add what happens at the end. "Review" needs a named decision; "delete" needs a way to carry it out.

Be precise about the starting point. "One year" could mean after purchase, after the event, after the final complaint closes or after the last relevant interaction. Pick the date that fits the purpose and confirm your system can identify it.

The example below is illustrative. It is an operating structure for discussion, not a statutory schedule or a recommendation that these triggers suit every event.

Temporary door export

Keep it for admission and immediate reconciliation. In this example, the trigger is completion of the event and reconciliation. The door lead deletes the export and securely disposes of paper copies, after checking any specific open issue.

Access arrangement note

Keep the necessary detail to deliver agreed support and resolve a related issue. Review it when the arrangement is complete and there is no unresolved issue. The operations lead deletes unnecessary detail and assesses any specific exception.

Ticket transaction record

Keep the required fields for accounting and relevant aftercare. The trigger follows the applicable financial requirement or case. Finance confirms the verified period and which information belongs in the retained record.

Active marketing contact

Keep it for relevant, permitted event promotions. A scheduled relevance review or objection triggers a decision. The marketing lead reassesses the lawful use and removes the person from active sending when required.

Marketing suppression record

Keep the minimum information needed to prevent unwanted future promotions. Review the continuing need to honour the objection. The marketing lead checks that imports and new campaigns still respect it.

Identifiable analysis file

Keep it to answer a defined business question. Completion of the analysis triggers review. The report owner effectively anonymises the useful result or deletes unnecessary personal data, rather than keeping the entire working file indefinitely.

These categories let finance retain required records while operations deletes finished access notes and marketing respects an unsubscribe. Each team has a reason for keeping its information and a decision to make when that reason ends. Give them a schedule that makes those decisions clear.

For an actual schedule, replace each example trigger with your chosen trigger and period or decision criteria. Have finance check the financial categories, the person responsible for privacy check the lawful uses, and the operational owner confirm that the cleanup can happen.

Keep the schedule somewhere the people doing these jobs can easily find it. When a teammate leaves, hand their cleanup responsibilities to someone else. A document naming a former employee as the owner won't remove a single file from your shared drive.

Try an awkward record. A buyer attended, requested a refund and unsubscribed. Can your schedule tell you what happens to their purchase, complaint and marketing status separately? If the answer is "keep everything," the schedule needs more work.

Walk one finished event through the schedule

Imagine you run a paid workshop series. This is an invented example to show the decisions, not a claim about a Loopyah customer. The latest workshop has finished, payments have been reconciled and one attendee still has an unresolved complaint about admission.

The event manager starts with the temporary door list. They ask the door lead whether reconciliation is complete and whether the complaint requires any specific entry. The relevant evidence goes to the person handling the complaint with restricted access. The rest of the temporary list follows the approved deletion rule. The door lead confirms that the printed backup and downloaded copy have also been dealt with.

Finance checks the transaction records against the business's accounting requirements. It keeps the required purchase information in the agreed location. It keeps the required payment record without preserving the entire registration form.

Next, the operations lead checks the access notes. The arrangements were delivered and there are no related open issues. Under the example business's approved schedule, the unnecessary notes are removed. If an arrangement had led to a complaint, that particular record would go through a separate decision instead.

The marketing lead checks who may receive the next workshop announcement. Someone who opted out stays out. Someone with a continuing relevant permission can remain eligible, subject to the business's review criteria. The marketing lead uses the current record rather than last month's downloaded audience.

Finally, the event manager keeps a sales summary for planning. It shows ticket revenue, refunds and attendance totals. They assess whether the report needs individual records and whether its groups reveal anyone. They document the useful findings, then handle the working file under the analysis category.

Each owner confirms completion in the closeout record. Leave attendee names out. A short entry identifying the file category, location, action and date is enough for the team's operational record, with exceptions tracked separately.

The open complaint remains visible on the closeout list with an owner and a review point. It doesn't stop the whole event from closing, and it doesn't become an excuse to keep unrelated information. When the complaint is resolved, its owner checks the approved next step.

People decide what happens to each record, then check the copies. If your current process depends on the founder remembering which freelancer downloaded which file, fix that handoff before the next workshop goes on sale.

Keep the audience you can use responsibly

Past buyers can be valuable to an event business. They already know your event and may be the first people who want tickets when the next date goes live. Throwing away a relevant, lawfully maintained audience by accident doesn't help anyone.

But a large contact count can hide a weak audience. You might have outdated addresses, people whose permission you can't explain, and contacts who signed up for something you no longer offer. The team still needs to know who can receive an announcement.

Use your event email marketing strategy to identify the audience and messages you actually plan to send. Review the purpose of the list against the events you run. An annual festival has a different buying rhythm from a venue announcing shows every week. A quiet period alone doesn't settle whether the relationship is over. Equally, an annual calendar doesn't justify keeping every old contact forever.

Set a relevance review that fits that rhythm. Consider the original expectation, the events you offer, the person's meaningful interactions and the information you need. Avoid turning an email open into proof of permission or a blanket reason to restart every retention clock.

Here's what's useful about separating contact records from send eligibility. You can keep information for a legitimate remaining purpose without treating the person as someone you may promote to. Each purpose gets its own decision.

Loopyah's attendee email tools keep buyers in contacts with their purchase information and whether they agreed to hear from you. They also remove opt-outs from promotional sending. That helps you reach the appropriate audience without building a fresh export for every campaign.

The retention policy still belongs to your business. A tool allowing contact storage doesn't establish how long you should store a particular record. Check the relevant privacy terms and available controls before assuming that an unsubscribe, account deletion or campaign setting removes every associated record.

An unsubscribe also needs careful handling. If you delete the only evidence that someone objected, an old import can put them back on the next campaign. Keep a minimum suppression record where justified so the objection continues to work. That record's purpose is preventing contact; it should never become another marketing list.

Treat the next import as a retention check

Before importing an old audience, ask where the file came from, why the people are there and whether the intended campaign fits. Check it against current objections and remove unnecessary fields.

A spreadsheet labelled "past attendees" doesn't tell you who bought, who received a transferred ticket or who subscribed. Nor does it tell you whether somebody unsubscribed after the export was created. Use current information.

Don't send a promotional "please confirm you want our emails" message as a workaround for missing permission. Whether you can send that message is itself a marketing question. Resolve the basis for contacting the person before using an email to resolve it.

Keep useful analysis without keeping every identity

You probably want to know which ticket release sold, where buyers came from and whether people return. Those questions can improve the next event's budget and sales plan. They deserve a defined answer rather than a folder full of old exports.

Ask whether each decision requires identifying someone. Comparing total sales by ticket type often doesn't. Following the purchase history of a particular customer does. That's the difference your retention plan needs to recognise.

Our post-event report guide explains how to turn the finished event into decisions for the next one. Preserve the figures and explanations you will use. Record what the totals represent, how refunds were handled and which date the report covers. The report becomes easier to understand later, and you may be able to remove the identifying details that were only needed while preparing it.

Be careful with the word "anonymous." Removing the name column isn't enough if an email, order number or combination of details can still identify the person. The ICO's anonymisation guidance distinguishes anonymous information from personal data. Replacing identities with codes can still leave personal data when people remain identifiable.

Small groups need attention too. A report about a single attendee in a distinctive category may reveal who they are even without a name. Think about the audience receiving the report and what else they know, especially before sharing it with sponsors or partners.

You can preserve useful commercial lessons without keeping every identity. "This ticket release sold earlier than expected" helps your planning. Detailed support messages usually don't answer that question.

Before sending a report to a sponsor, check what they actually need. Total attendance and relevant sales figures may answer their question without a named guest list. If a small group or a detailed breakdown reveals someone, change the grouping or remove the detail. Keep a note of what you shared and why, so the next team member doesn't send a more detailed version by habit.

Find the copies before you promise deletion

Your main system is only one place to look. Event teams download lists, forward attachments and print emergency backups. Contractors may receive files. The old copy is easy to forget because the current event is in a different folder.

Walk through how information leaves each system. Ask the people who work the event, not only the account owner. The door manager may know about a printed list; a freelancer may know about a shared drive; finance may know about an emailed invoice export.

Record the locations you can actually control. That might include ticketing, email tools, shared storage, staff devices and paper files. For external organizations, establish their role and the applicable agreement rather than assuming they follow your internal schedule.

An organization processing information on your behalf has different responsibilities from a venue or sponsor deciding its own uses. Under Article 28 of the EU GDPR, processor contracts must address deletion or return after the service ends, subject to applicable legal storage requirements. Check the arrangement you have, including any further providers involved.

Ask concrete questions when choosing a provider. What can the organizer delete? What remains for the provider's separate obligations? What happens to exports, backups and an account that closes? How are valid requests passed on, and what confirmation can you obtain?

Your team also needs appropriate access while records remain. Loopyah's event team access lets teammates sign in with their own accounts and gives door staff access to check tickets without seeing sales. Use the permissions available for the job, and review access when staff or contractors finish their work.

Access control and retention solve different problems. Restricting a file helps protect it while you need it. It doesn't justify keeping it after the purpose ends. A folder called "archive" still contains data, even when nobody opens it.

For backups, get the actual process in writing. The ICO's erasure guidance recognises circumstances where information leaves live systems before backup copies are overwritten. Those copies need to be beyond use during the remaining period. Your restore process should also prevent deleted information from returning to ordinary use.

Handle deletion requests without losing required records

An attendee doesn't have to wait for your next scheduled cleanup to ask about their data. Build a route for the team to recognise and pass on a request, including one received through a support inbox or at the event.

The ICO's right to erasure guidance says the UK right is not absolute. It generally requires a response without undue delay and within one month, with specific rules on timing and extensions. It also describes exceptions, including necessary processing for legal obligations and legal claims.

Don't reply with "we keep everything for accounting." Find out what you hold and which remaining purpose applies to each category. A required transaction record and an expired catering note need separate decisions. Tell the person plainly what you deleted, what you retained and why.

Keep identity checks proportionate. If someone writes from the address tied to their order, don't automatically demand a passport scan. Check what you actually need to establish the requester's identity and avoid creating a new store of unnecessary identification documents.

A complaint or threatened claim can require you to preserve relevant evidence. Ask the person responsible for legal matters which records belong in the hold, who may access them and when to review it. Document the reason. A specific dispute shouldn't freeze routine cleanup for unrelated attendees.

Once the exception ends, return the affected records to the appropriate retention process. Otherwise a sensible decision made during a dispute becomes a permanent archive long after everybody has forgotten the dispute existed.

Adjust the plan for the countries you operate in

If your events, customers and business cross borders, don't copy a UK schedule and assume you're finished. Applicability depends on the relevant law and your activities, not simply the venue's address.

For businesses covered by Australia's Privacy Act, the OAIC's APP 11 guidance explains the requirement to take reasonable steps to destroy or de-identify information no longer needed for a permitted purpose, with exceptions such as legal retention requirements. Check coverage and the relevant accounting, marketing and other obligations for your business.

In the United States, state privacy laws and sector requirements differ. California's Attorney General explains the CCPA's coverage and consumer rights, including deletion rights with exceptions. It applies to covered businesses, so "we sell tickets in California" isn't a complete assessment of your obligations.

Start by listing the countries you operate in and the people whose information you handle. Ask your adviser to identify the requirements that affect your actual categories. You can then keep one usable operational schedule with clearly documented differences where necessary.

Avoid asking the team to guess the law each time it opens a file. The schedule should carry the decision. If a requirement changes, update the relevant category, privacy information and system process together.

Make cleanup part of closing the event

The best time to establish these decisions is before tickets go on sale. You can also start during your event review.

Put retention into the same closeout work as payment reconciliation and supplier settlement. Assign someone to confirm that temporary files are gone, access has been reviewed and outstanding issues have a named owner. Assign cleanup before the next show.

Keep a short record of the actions, without reproducing the information you deleted. Note the record category, system, date and outcome. If an exception prevented deletion, record the reason and next review. You're trying to prove the process happened, not create another attendee database.

Then test it. Pick an expired export and confirm that the responsible person can remove it from the known locations. Pick an unsubscribe and check that a later import won't reactivate it. Ask what happens if a backup is restored. These practical checks tell you more than a policy everyone has signed but nobody can carry out.

Your team should be able to find the answer. Keep the necessary record for a defined, lawful purpose. Give it an owner and an ending or review point. Remove the details and copies that no longer serve that purpose.

Your next event needs a reliable audience, usable sales history and a team that knows where information belongs. It doesn't need every old spreadsheet.