Event Brew

There are occasional genuine observations buried in the episode - the CSV leak discovery trick, QR code data stripping risk, fake email canary technique - but roughly a third of the runtime is occupied by beverage banter, a Burger King anecdote, and WiFi hotspot tangents that contribute nothing actionable to a B2B operator.

“The QR codes are usually super data rich too. Like you can if, unless they're really smart. And the QR code is one that is only information, uh, to an uh, attendee id. There's usually information baked into that that you could just take a camera and strip away from people, just any phone, any person.”

“We didn't fix that problem. We didn't sit back and go how can we be more ethical about the way we do this? We capitalized on it, we overused it, we abused it and then we got it taken away.”

The observation that B2B attendees operate under a different social contract around data visibility (they already wear name badges with PII) is a mildly interesting reframe, and the cycle-of-abuse analogy connecting email marketing to facial recognition has some teeth, but the broader takeaways - be transparent, vet your vendors, get legal advice - are entirely standard issue.

“the social contract of attending a B2B event is based around visibility”

“all these people that are like, oh, I hate being tracked and the government's always following me...but they're the same people that live on Google Maps because it gives them the fastest route to where they're going”

The guests are genuine mid-level event industry practitioners - Nick has hands-on experience at a data/analytics event tech company and shares a credible canary email anecdote; Will produces event tech content - but none are C-suite operators who have deployed these systems at real scale, and the conversation stays at the practitioner level rather than producing hard-won strategic insight.

“the company I work for, Zenith, is the kind of cure to this...we don't collect any personal information. We, uh, we don't record pictures, we don't record videos. Uh, instantly the camera is a lens that translates your face into numbers.”

“I worked for, uh, a trade show where we would insert an email address. Every fake, uh, email address, uh, with every one of the exhibitors, uh, and if anything was emailed, uh, to that.”

The Mobile World Congress GDPR case is a real and named example with a rough fine figure, and the canary-email technique is concrete and verifiable; however, the fine amount is fumbled and approximate, the TechCrunch article is never cited properly, and most prescriptive recommendations ('ask tough questions,' 'third-party audit') remain unanchored to any specific process, vendor, or metric.

“they're looking at what looks like a fine of uh, $200,000. 224American cover the four divided by. It's a quarter million dollars.”

“We had 50, you know, 50 email addresses, 50 exhibitors. Uh, you know, insert one of them into that list. Uh, if anything, you know, if they sold that list or moved that list wherever, we could say who it came from.”

The host asks a couple of structurally useful questions - specifically the EU-versus-US jurisdiction split and whether attendee litigation is becoming a systemic risk - but almost every claim goes unchallenged, the conversation drifts repeatedly into unrelated banter, and there is no genuine pushback or productive disagreement across the episode.

“How much of this is like an issue just for the fact that it's taking place in the EU which has like the strict like GDPR rules. Like do you think that this same ex potentially would happen in America with our lack of there for data privacy laws?”

“do you think that we're at risk that more and more events should be concerned about their attendees potentially taking legal action for potentially even a mistake they're not 100% aware even happened?”