[{"data":1,"prerenderedAt":227},["ShallowReactive",2],{"marketing-blog-blog\u002Fwhat-attendee-data-is-worth-keeping":3,"marketing-blog-related-blog\u002Fwhat-attendee-data-is-worth-keeping":208},{"id":4,"title":5,"author":6,"body":7,"category":188,"date":189,"description":190,"draft":191,"extension":192,"image":193,"imageAlt":194,"imageCredit":195,"imageCreditUrl":196,"meta":197,"navigation":198,"path":199,"readTime":200,"seo":201,"stem":202,"tags":203,"__hash__":207},"blog\u002Fblog\u002Fwhat-attendee-data-is-worth-keeping.md","What attendee data is worth keeping","The CheckInHub team",{"type":8,"value":9,"toc":179},"minimark",[10,14,17,22,25,28,31,47,56,60,63,66,72,76,79,146,154,158,161,169,173,176],[11,12,13],"p",{},"It is tempting to treat attendee data the way some people treat a loft: keep everything, just in case, because you might want it one day. With events, that instinct is a liability rather than a convenience. Every field you collect and every record you hold is something you have to protect, justify and eventually delete. The data that helps you run a better event is a small subset of the data you could collect, and the gap between the two is pure risk with no payoff.",[11,15,16],{},"The useful discipline is to ask, of every piece of information, what decision it helps you make. If the honest answer is none, you are holding it out of habit, and habit is not a lawful basis for keeping someone's personal details.",[18,19,21],"h2",{"id":20},"collect-for-a-reason-not-for-completeness","Collect for a reason, not for completeness",[11,23,24],{},"The over-collection usually starts at registration, where it is easy to add one more field. Dietary requirements, job title, company size, how they heard about you, a phone number just in case. Each feels harmless on its own. Together they form a registration form that takes too long, puts people off, and leaves you holding details you will never look at again.",[11,26,27],{},"Before a field goes on the form, it should pass a simple test: what will we actually do with this answer. Dietary requirements earn their place if you are serving food. A phone number earns it if you genuinely intend to call people, which most events do not. Job title earns it if it changes the experience you offer, and otherwise it is just sitting in your database as a future breach waiting to happen.",[11,29,30],{},"The fields that almost always justify themselves:",[32,33,34,38,41,44],"ul",{},[35,36,37],"li",{},"A name, so you can check someone in and address them.",[35,39,40],{},"An email, so you can send the pass, the reminders and any follow-up they consented to.",[35,42,43],{},"Whatever is needed for access, such as a ticket type or session.",[35,45,46],{},"Genuine requirements, such as dietary or accessibility needs, where you will act on them.",[11,48,49,50,55],{},"Everything beyond that should have to argue for its inclusion. We cover the up-front version of this decision in ",[51,52,54],"a",{"href":53},"\u002Fblog\u002Fwhat-to-capture-at-registration-and-what-to-skip","what to capture at registration, and what to skip",", and the post-event version, which fields to keep afterwards, is the subject of this one.",[18,57,59],{"id":58},"the-difference-between-running-the-event-and-keeping-the-data","The difference between running the event and keeping the data",[11,61,62],{},"There is a useful line between data you need to run the event and data you keep after it. During the event, you legitimately need quite a lot: the list, the check-in status, who is inside. That is operational data with an obvious purpose. The question that catches people out is what happens to it once the doors have closed and the event is over.",[11,64,65],{},"After the event, most of that operational detail has done its job. You rarely need to know the exact minute someone checked in to a conference last spring. What you might reasonably keep is a smaller, deliberate set: aggregate numbers for planning next year, and the contact details of people who agreed to hear from you again. Everything else can and should go.",[67,68,69],"blockquote",{},[11,70,71],{},"The safest data is the data you no longer hold. You cannot leak, lose or misuse a record you deleted when it stopped being useful.",[18,73,75],{"id":74},"a-simple-retention-model","A simple retention model",[11,77,78],{},"It helps to sort your data by how long it genuinely needs to live, then delete on a schedule rather than whenever you remember. The categories are usually clear once you look.",[80,81,82,98],"table",{},[83,84,85],"thead",{},[86,87,88,92,95],"tr",{},[89,90,91],"th",{},"Data",[89,93,94],{},"Why you hold it",[89,96,97],{},"Keep it for",[99,100,101,113,124,135],"tbody",{},[86,102,103,107,110],{},[104,105,106],"td",{},"Full registration records",[104,108,109],{},"Running the event",[104,111,112],{},"Delete soon after, once reconciled",[86,114,115,118,121],{},[104,116,117],{},"Check-in logs and audit trail",[104,119,120],{},"Resolving disputes, counting",[104,122,123],{},"A short, defined window",[86,125,126,129,132],{},[104,127,128],{},"Aggregate attendance numbers",[104,130,131],{},"Planning future events",[104,133,134],{},"Indefinitely, as anonymous figures",[86,136,137,140,143],{},[104,138,139],{},"Contacts who opted in",[104,141,142],{},"Marketing the next event",[104,144,145],{},"Until they unsubscribe",[11,147,148,149,153],{},"The exact windows depend on your situation, but the shape is the same: detailed personal data has a short life, anonymous aggregates can live on, and consented contacts stay only as long as the consent does. Writing this down as an actual policy, rather than leaving it to memory, is what makes it real. We lay out how to build one in ",[51,150,152],{"href":151},"\u002Fblog\u002Fa-data-retention-policy-for-events","a data retention policy for events",".",[18,155,157],{"id":156},"consent-is-not-a-one-off-tick","Consent is not a one-off tick",[11,159,160],{},"The contacts you keep for future marketing are a special case, because keeping them lawfully depends on consent that was freely given and clearly recorded. A pre-ticked box buried in a registration form does not count. A clear, separate opt-in to hear about future events does. And consent is not forever: if someone unsubscribes, that is a withdrawal you have to honour by removing them, not just stopping the emails.",[11,162,163,164,168],{},"This matters most at the moment you reach for the list to promote your next event. The temptation is to email everyone who came, on the grounds that they were obviously interested. Under GDPR, attendance is not consent to be marketed to. The people you can contact are the ones who said yes, recorded at the time, and nobody else. We go into the detail in ",[51,165,167],{"href":166},"\u002Fblog\u002Fconsent-and-the-post-event-email","consent and the post-event email",", and it is worth reading before you send a single follow-up.",[18,170,172],{"id":171},"less-data-less-to-defend","Less data, less to defend",[11,174,175],{},"The throughline of all this is that data is a responsibility, not an asset, until it earns its place. Every record you hold is something you must keep secure, be ready to produce if someone asks, and delete when its purpose ends. A lean dataset is easier to protect, cheaper to manage, and far less painful if the worst happens and something is exposed.",[11,177,178],{},"So keep what helps you run and improve your events, keep the consented contacts who want to hear from you, and let the rest go on a schedule you actually follow. The event-management payoff is real: a tidy, defensible dataset that answers the questions you genuinely ask. The risk you avoid is the loft full of details you collected out of habit and would struggle to explain if anyone ever asked why you still had them.",{"title":180,"searchDepth":181,"depth":181,"links":182},"",2,[183,184,185,186,187],{"id":20,"depth":181,"text":21},{"id":58,"depth":181,"text":59},{"id":74,"depth":181,"text":75},{"id":156,"depth":181,"text":157},{"id":171,"depth":181,"text":172},"Security & data","2024-08-09","Not every field you collect earns its place. Here is how to decide what attendee data to keep, what to bin, and how to stay on the right side of GDPR.",false,"md","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1669078952565-9acbe5db90e4?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop","A close-up of a red and white sign","Katie Currier","https:\u002F\u002Funsplash.com\u002F@curriedflute?utm_source=checkinhub&utm_medium=referral",{},true,"\u002Fblog\u002Fwhat-attendee-data-is-worth-keeping",6,{"title":5,"description":190},"blog\u002Fwhat-attendee-data-is-worth-keeping",[204,205,206],"security","data","privacy","hQKB-F9Z9ri4sYpdlSRfXJRooANVqIqNZT9HhumTNWc",[209,215,221],{"to":210,"title":211,"description":212,"date":213,"category":188,"image":214,"readTime":200},"\u002Fblog\u002Fworking-with-the-venues-security-team","Working with the venue's security team at your front door","Your check-in desk and the venue's security team are running the same door with different lists. How to brief them, where the handover goes wrong, and the one number both sides need to agree on.","2026-07-26","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1762474293029-6a7f3698312c?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",{"to":216,"title":217,"description":218,"date":219,"category":188,"image":220,"readTime":200},"\u002Fblog\u002Fmartyns-law-and-the-front-door","Martyn's Law and the front door: knowing who is in the building","The Terrorism (Protection of Premises) Act 2025 turns on how many people are present at once. What the standard and enhanced tiers ask for, and why an honest, live headcount is the quiet foundation under the procedures.","2026-06-30","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1633358050629-bb6a292616ff?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",{"to":222,"title":223,"description":224,"date":225,"category":188,"image":226,"readTime":200},"\u002Fblog\u002Fcounting-people-out-not-just-in","Counting people out, not just in","Most front-of-house effort goes into getting people through the door. Far fewer teams can say, at the end of the night, that the building is actually empty. Here is how to make departures as reliable as arrivals, and why it is about to matter more.","2026-06-25","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1540039155733-5bb30b53aa14?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",1787334031521]