[{"data":1,"prerenderedAt":217},["ShallowReactive",2],{"marketing-blog-blog\u002Fwhat-attendee-data-you-should-and-shouldnt-keep":3,"marketing-blog-related-blog\u002Fwhat-attendee-data-you-should-and-shouldnt-keep":199},{"id":4,"title":5,"author":6,"body":7,"category":177,"date":178,"description":179,"draft":180,"extension":181,"image":182,"imageAlt":183,"imageCredit":184,"imageCreditUrl":185,"meta":186,"navigation":187,"path":188,"readTime":189,"seo":190,"stem":191,"tags":192,"__hash__":198},"blog\u002Fblog\u002Fwhat-attendee-data-you-should-and-shouldnt-keep.md","What attendee data you should, and shouldn’t, keep","The CheckInHub team",{"type":8,"value":9,"toc":167},"minimark",[10,14,17,22,25,28,31,34,38,41,76,79,85,89,92,118,121,125,128,131,145,149,157,161,164],[11,12,13],"p",{},"The instinct when building a registration form is to ask for everything. Name, email, phone, company, job title, dietary needs, accessibility requirements, how they heard about you, their interests, maybe a dropdown of their seniority for the sponsors. It all seems useful, the form takes a minute longer, and you tell yourself you might want it later. Then the data sits in a spreadsheet for three years until someone asks, under GDPR, exactly why you are still holding the phone numbers of 600 people who attended a conference you ran in 2023.",[11,15,16],{},"The safest attendee data is the data you never collected. Every field you ask for is something you then have to store securely, justify holding, and eventually delete. The discipline of keeping less is not just good privacy practice; it is less risk, less work and a faster form that more people finish. The question for every field is not \"could this be useful\" but \"do I genuinely need this, and for how long.\"",[18,19,21],"h2",{"id":20},"need-to-run-the-event-versus-nice-to-have","Need to run the event versus nice to have",[11,23,24],{},"Start by sorting every piece of data you are tempted to collect into two honest piles. The test is whether the event can run without it.",[11,26,27],{},"The first pile is what you actually need to admit a guest and run the day: enough to identify them at the door, enough to contact them about the event itself, and anything required for their safety or access. This is a short list. A name and an email get most events through registration and check-in.",[11,29,30],{},"The second pile is everything else: data you want for marketing, for sponsors, for analysis, for a \"just in case\" that rarely comes. None of it is needed to run the event. Some of it is reasonable to collect with clear consent. Much of it is collected out of habit and never used.",[11,32,33],{},"Be ruthless about the second pile. Every field in it is a liability you are choosing to take on, and the cost lands later, when you have to secure it, explain it, and delete it.",[18,35,37],{"id":36},"what-is-usually-worth-keeping","What is usually worth keeping",[11,39,40],{},"A practical list of what genuinely earns its place for most events:",[42,43,44,52,58,64,70],"ul",{},[45,46,47,51],"li",{},[48,49,50],"strong",{},"Name",", to identify the guest at the door and on a badge.",[45,53,54,57],{},[48,55,56],{},"Email",", to send the pass, send essentials before the day, and follow up after.",[45,59,60,63],{},[48,61,62],{},"Accessibility and dietary needs",", where relevant, because you need them to look after people. Note these are sometimes special-category data and deserve extra care.",[45,65,66,69],{},[48,67,68],{},"Ticket or registration type",", so the door knows what each guest is entitled to.",[45,71,72,75],{},[48,73,74],{},"Check-in record",", the fact and time of arrival, which is the legitimate output of running the event.",[11,77,78],{},"That is enough to register, admit, look after and follow up with a guest. Most events do not need more, and the ones that do should be able to point at a specific, current reason for each extra field.",[80,81,82],"blockquote",{},[11,83,84],{},"If you cannot say why you are keeping a field, you have your answer about whether to keep it.",[18,86,88],{"id":87},"what-to-think-twice-about","What to think twice about",[11,90,91],{},"Some commonly collected fields carry more risk than reward and deserve a second look before they go on the form.",[42,93,94,100,106,112],{},[45,95,96,99],{},[48,97,98],{},"Phone numbers",", rarely needed and awkward to justify holding long-term. Collect only if you will actually use them, such as day-of logistics for speakers.",[45,101,102,105],{},[48,103,104],{},"Free-text fields",", which attract data you never asked for and cannot easily manage. People write all sorts of things in an open box.",[45,107,108,111],{},[48,109,110],{},"Anything special-category"," under GDPR, such as health beyond a stated dietary or access need. Collect only with a clear lawful basis and treat it carefully.",[45,113,114,117],{},[48,115,116],{},"Sponsor wishlists",", the extra demographic fields added because a sponsor asked. Question each one; consent must be real, and \"the sponsor wanted it\" is not a lawful basis on its own.",[11,119,120],{},"The pattern is the same throughout. Collect for a current, specific purpose, or do not collect at all.",[18,122,124],{"id":123},"keeping-is-not-forever","Keeping is not forever",[11,126,127],{},"Collecting less is half the discipline. The other half is not keeping what you did collect any longer than you need it. GDPR expects data to be held no longer than necessary, and \"necessary\" for most event data is measured in months, not years.",[11,129,130],{},"Decide a retention period before the event, not after someone complains. A workable default is to keep what you need for the event and the follow-up window, then delete or anonymise the rest. The check-in record can often be reduced to anonymous counts once the analysis is done; you rarely need to know that a named individual arrived at 09:14 two years later, but you may well want the headline figure that 580 of 600 turned up.",[11,132,133,134,139,140,144],{},"This is where a system that handles deletion cleanly matters. Pulling personal data out of a sprawl of spreadsheets, emails and exports is the reason retention promises go unkept. When the attendee data lives in one place, deleting it on schedule is a deliberate, doable act rather than an archaeology project. ",[135,136,138],"a",{"href":137},"\u002Fblog\u002Fgdpr-for-events-without-the-panic","GDPR for events without the panic"," walks through the practical side of this, and ",[135,141,143],{"href":142},"\u002Fblog\u002Fkeeping-the-guest-list-the-guest-list","keeping the guest list the guest list"," covers stopping the data from spreading in the first place.",[18,146,148],{"id":147},"less-data-better-numbers","Less data, better numbers",[11,150,151,152,156],{},"There is a quiet upside to collecting less. A short form is finished by more people, so your registration data is actually more complete, not less. And the data you do keep is cleaner, because you are not maintaining fields nobody uses. The analysis that matters after an event, who came, how many, when they arrived, comes from the check-in record, not from a wishlist of demographic fields. For the figures genuinely worth pulling afterwards, ",[135,153,155],{"href":154},"\u002Fblog\u002Fthe-numbers-worth-pulling-after-the-doors-close","the numbers worth pulling after the doors close"," is the companion piece.",[18,158,160],{"id":159},"the-closing-thought","The closing thought",[11,162,163],{},"Treat every field as a cost, not a freebie. Collect what you need to admit, look after and follow up with a guest, refuse the habitual extras, and set a deletion date before the day rather than after a complaint. Less data is less risk, less work, and a form people actually finish.",[11,165,166],{},"CheckInHub keeps attendee data in one place, which is what makes the unglamorous part, deleting it on schedule, something you can actually do rather than something you keep meaning to. The aim is to run a great event and hold as little of its data afterwards as the job honestly requires.",{"title":168,"searchDepth":169,"depth":169,"links":170},"",2,[171,172,173,174,175,176],{"id":20,"depth":169,"text":21},{"id":36,"depth":169,"text":37},{"id":87,"depth":169,"text":88},{"id":123,"depth":169,"text":124},{"id":147,"depth":169,"text":148},{"id":159,"depth":169,"text":160},"Security & data","2026-03-06","The safest attendee data is the data you never collected. A practical guide to keeping what you need and refusing the rest under GDPR.",false,"md","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1460925895917-afdab827c52f?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop","An analytics dashboard open on a laptop","Carlos Muza","https:\u002F\u002Funsplash.com\u002F@kmuza?utm_source=checkinhub&utm_medium=referral",{},true,"\u002Fblog\u002Fwhat-attendee-data-you-should-and-shouldnt-keep",6,{"title":5,"description":179},"blog\u002Fwhat-attendee-data-you-should-and-shouldnt-keep",[193,194,195,196,197],"security","data","gdpr","privacy","retention","8tI853cTXedGF-Y3QyNjW6SyEVq6wfM4xK8l7F4lbJo",[200,206,211],{"to":201,"title":202,"description":203,"date":204,"category":177,"image":205,"readTime":189},"\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",{"to":142,"title":207,"description":208,"date":209,"category":177,"image":210,"readTime":189},"Keeping the guest list the guest list","A guest list is personal data the moment you collect it. How to hold it responsibly without slowing down the door or drowning in compliance.","2026-04-24","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1518186285589-2f7649de83e0?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",{"to":212,"title":213,"description":214,"date":215,"category":177,"image":216,"readTime":189},"\u002Fblog\u002Fwriting-a-follow-up-email-people-open","Writing a follow-up email people open","A good post-event follow-up earns opens and respects the data you hold. Here is how to write one that lands without crossing a line.","2025-12-12","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1526628953301-3e589a6a8b74?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",1782495582121]