The Dialog Leak Isn't a Story About a Secret Society. It's a Story About View Source.

By now you’ve probably seen the headlines about Peter Thiel’s “Dialog” the invite-only retreat that’s been quietly running since 2006, compared in every write-up to Bilderberg, populated by senators, a NATO four-star, Treasury Secretary Scott Bessent, half the PayPal Mafia, and apparently a session called “Build-a-Cult” moderated by the founder of a Christian dating site. The internet has spent two days arguing about whether this is a harmless retreat for rich nerds or a parallel government in waiting.

I don’t really care about that argument. I care about how the data got out, because that’s the part nobody outside the OSINT and infosec world is actually talking about and it’s the part that should worry these people far more than which sessions made the agenda.

What actually happened

Strip away the conspiracy framing and here’s the technical reality. Swiss researcher Maia Arson Crimew the same person who previously surfaced the U.S. government’s No Fly List and breached the surveillance camera company Verkada got an anonymous tip and found a directory of 113 names tied to Dialog sitting embedded directly in the source code of the organization’s own website. Not behind a login. Not in a database that required a breach. The directory had been sitting in plain sight, served to anyone who simply viewed the page’s source.

That’s not a hack. That’s a “right-click, View Page Source” discovery. I want to sit with that for a second, because it’s the entire story.

Separately, Dialog’s participant records live in Airtable a commercial, off-the-shelf database and for each person it tracks membership status, every retreat they’ve attended, a biography, a home city, and a private access token that functions as a login credential. A source gave Wired the full 2026 registration list separately, which is how the broader 222-name roster for the August retreat surfaced. WIRED chose not to publish the tokens or the personalized account links that contained them, which tells you those tokens were live and functional, not some sanitized export.

So you’ve got a 20-year-old organization, run by people who built some of the most consequential surveillance, data brokerage, and identity infrastructure on the planet, whose own membership directory was exposed the same way a junior dev’s side project gets exposed: hardcoded into client-facing HTML and parked in a SaaS tool with default-ish access controls. Crimew’s quote on this is the one worth remembering, not the session titles: it shows how confident the people who run the world are in their own safety, since they don’t bother with basic operational security even for the off-the-record gatherings where they discuss the world’s future.

That’s the headline. Everything else is color.

Why this matters more than the gossip

I spend my working life on the other side of this exact failure mode. When I’m tracing a fraud network or doing diligence on a counterparty, the breakthrough almost never comes from some exotic zero-day or a dark web breach dump. It comes from exactly this: someone treated a low-friction tool — a shared spreadsheet, a forum profile, a website’s own source code as private, when it was never actually locked down. People conflate “obscure” with “secure.” Dialog has no public-facing site, no published member list, two decades of media silence. That obscurity bred a false sense of security, and false security is precisely where OPSEC discipline goes to die.

The irony, and it’s a real one, is who’s on the list. This isn’t a retreat of marketing executives. Howie Liu, the founder and CEO of Airtable itself, is a listed participant — the same Airtable that hosted the unsecured records. The roster includes people who built or run the largest data brokerage, ad-tech, and surveillance companies in the country, gathering specifically to discuss, among other things, the future of AI-driven information control, and their own membership records were sitting in a tool with the access discipline of a fantasy football league.

If you only take one lesson from this story for your own organization, take this one: your threat model has to account for low-effort, high-embarrassment exposure, not just sophisticated attackers. Nobody breached Dialog’s infrastructure with anything resembling skill. Somebody looked.

The part that should worry the attendees more than the press coverage

The leaked records include personal email addresses, mobile phone numbers, birthdates, and emergency contacts for the people on the list — for sitting senators, a NATO commander, a Treasury Secretary, and assorted billionaires. That’s not reputational risk. That’s a physical security and targeting risk. Emergency contact information for a sitting general or cabinet official, tied to a home city and a verified attendance history at private events, is exactly the kind of dataset that turns into a social engineering or physical security problem in someone else’s hands. None of them appear to have used government email addresses to register, which tells you the attendees themselves understood there was something worth keeping separate from their official lives — they just didn’t extend that same instinct to the platform holding their personal data.

This is the gap I see constantly in this work: people are good at compartmentalizing what they say. They’re bad at compartmentalizing the infrastructure that holds what they say. Dialog reportedly went to the trouble of building a private, members-only dating feature inside its participant directory, including whether someone was looking for love at Dialog events — a level of granular personal detail most people wouldn’t hand to a stranger at a bar, sitting in the same unsecured system as phone numbers and birthdates for a four-star general.

What I’d tell a client in this position

If you ran an organization like this and frankly, if you run any organization that maintains a membership list, a donor list, an investor list, or a client roster with personal contact data attached here’s the unglamorous checklist that this leak should put back on your radar:

Audit what’s actually rendered in your site’s client-side source, not just what’s behind authentication. Browsers render everything sent to them; “not linked from the navigation” is not the same as “not exposed.” Crimew didn’t break anything. She viewed source.

Treat third-party SaaS tools Airtable, Notion, Google Sheets, anything with a shareable link as a primary attack surface, not a convenience layer. These tools are popular precisely because they’re frictionless, and frictionless almost always means permissive defaults somewhere.

Separate identity data from preference data. A membership directory with names and bios is one risk tier. A membership directory with phone numbers, birthdates, emergency contacts, and dating preferences attached to the same record is a completely different risk tier, and it should never live in the same table, let alone the same access scope.

Rotate and scope access tokens like you mean it. The fact that Dialog’s tokens functioned as standing login credentials, embedded in personalized links, means a leaked link wasn’t just exposure it was account takeover waiting to happen.

None of this requires a six-figure security budget. It requires someone in the organization whose job is to ask “what does our public-facing footprint actually expose,” and to keep asking it as the org grows. Dialog is reportedly building a permanent campus and scaling its membership. Growth without a parallel growth in data discipline is how you end up the subject of a Wired story instead of the host of one.

The bigger picture

I’ll leave the “is this a secret society shaping world events” debate to the political commentators that’s a worthwhile conversation, but it’s not mine to adjudicate here. What I’ll say as someone who does this kind of digging for a living is that this leak is a near-perfect case study in why “we’re private, not public” is not a security posture. It’s a hope. Dialog had twenty years of media discipline and zero years of basic web hygiene, and the web hygiene is what got them.

The people in that room are going to spend a week in August discussing how to survive World War III and whether money buys happiness. I’d suggest they spend twenty minutes first on whether their own vendor stack can survive someone hitting Ctrl+U.