Discord Age Gates and the KIDS Act Fine Print

Jordan: Welcome back to Server Rooms. Thanks for joining us. Thomas Doan: Good to be here. Fair warning, I've spent the week buried in a bill. Jordan: That's the whole episode today. HR 7757, the KIDS Act and what it means for a platform built the way Discord is built. Thomas Doan: Right. The House passed it, and it's now sitting with Senate Commerce. The question we keep circling, does that referral mean anything, or is it just where bills go to wait? Jordan: That's where we open. Then we get into the actual text. There's a threshold buried in Section 103 that's supposed to trigger age verification. Thomas Doan: One-third of a platform's content, technology neutral verification. Sounds simple until you ask what that third is measured against on a server made of hundreds of independently run channels. Jordan: Which nobody in the bill actually defines. Thomas Doan: Nobody. Not a footnote, not a definition section. Jordan: We'll also get into how the Senate-referred text handles encryption and government ID, and whether Discord's own vendor testing changes how protective that no-ID rule really is. Thomas Doan: And near the end, Jordan and I land in different places. EFF wants the whole thing scrapped for a broader privacy law. Crowell is telling platforms to start reviewing vendor contracts now. Jordan: We don't agree on how small server operators should read that split. Thomas Doan: We really don't. Jordan: We rarely agree on much this week, honestly. Thomas Doan: Stick around to the end, too, we've got a server tour pick. Different kind of server, much lower stakes than a congressional bill. Jordan: Before that though, let's start where the bill actually stands right now: the vote, the referral, and what Thomas really thinks it means. Thomas Doan: I have opinions. Strap in. Jordan: The thing that's actually changed since we last touched this bill is, small on paper, huge in practice: HR 5757 isn't in the House anymore. Thomas Doan: Where'd you land? Jordan: Senate Commerce. GovTrack's status page shows it read twice and referred to the Committee on Commerce, Science, and Transportation on July thirteenth. Thomas Doan: Two weeks after passage-fast for Congress. Jordan: The floor vote itself was two sixty seven to one seventeen under suspension. The suspension of the rules. No floor amendments, straight yes or no. Thomas Doan: For a bill this size, that's leadership wanting it done fast and quiet. Jordan: Crowell's car dealer calls this the biggest congressional move on kids' online safety in years. Chairman Guthrie and Ranking Member Pallone folded Fourteen separate bills into that one package. Thomas Doan: Fourteen bills under one number-what actually holds them together? Jordan: Less than you think. EFF's peace from July ninth describes it as separate laws stitched together with different age gating standards depending which section you land on. Thomas Doan: So one part of the bill checks age one way, another part checks it a completely different way. Jordan: That's EFF's argument. A platform could satisfy one section's standard and fail another, because nobody in markup Speaker 3: read all the laws. Jordan: Erika picked a single definition of "minor" across all fourteen. Thomas Doan: For anyone running a Discord server with age restricted channels, that's not abstract: you could clear one title's test and trip the other. Jordan: Two rule books, one server. Thomas Doan: That's what happens when fourteen separate drafting teams each solve their own version of the same problem and somebody staples the results together at the end. Jordan: Put that way, it sounds like a merge conflict. Thomas Doan: It basically is one. Jordan: One political wrinkle worth flagging: the same week the House passed this, Senate sponsors were already calling it dead. Thomas Doan: Blumenthal and Blackburn? Jordan: Right!" The Record reported their joint statement going after the after the house version for dropping the duty of care standard that was in their Senate bill. Speaker 4: So the two people who wrote the Senate's version are on record saying the House text doesn't work. Jordan: Which is why Crowell frames this referral as the opening of a real fight, not the end of one. Speaker 4: I'd push back there. Sitting at Senate Commerce isn't momentum, it's a waiting room. A referral just means the paperwork moved-nobody's marking this up yet. Jordan: Fair, but if you moderate a server with hundreds of thousands of members, Speaker 3: and you're doing it without the assistance of a moderator, you're not going to get there. Jordan: So if you moderate a server with hundreds of thousands of members, You can't just sit and wait for the waiting room to clear. Thomas Doan: Sure you can, if Blumenthal and Blackburn already say the text is dead, Commerce can scrap it and write substitute language. Nothing forces them to move HR 7777 as written. Jordan: So which is it? Do you build for the bill sitting in front of you or the one that might replace it in three months? Thomas Doan: Build for the wrong one, and you've burned engineering time on a spec that never ships. Jordan: Wait for certainty, and the fast moving version catches you flat in September—same risk, opposite direction. Speaker 4: Either way, arguing about momentum doesn't tell us what the bill actually requires anyone to do. Jordan: Which means it's time to stop reading commentary and open the actual text. Speaker 4: A hundred and fourteen pages per GovTrack.) Jordan: So, what does Section 103 actually make a platform do, mechanically, to check somebody's age? Let's actually read what the text says. Speaker 4: Section 103. This is the part every one quotes and almost nobody explains. Jordan: Walk me through it in plain terms. Speaker 4: The referred text requires what it calls "technology verification" measures. Platforms have to identify minors and block them from sexual material that's harmful to minors. But it doesn't apply to everyone, according to the summary attached to the GovTrack text. Next, the obligation kicks in for a covered platform once more than a third of its content meets that harmful to minors definition. Jordan: One third! That's oddly specific for something so hard to measure. Speaker 4: Right, and that's the constraint the drafters actually had to solve for. How do you calculate a percentage of content on a platform where content isn't one blob? Thomas Doan: Hmm? Jordan: Okay, so before we get to how impossible that is, how are they even supposed to build the verification part? Like fingerprint scan? ID upload? What? Speaker 4: That's the interesting bit. They don't say. National Taxpayers Union published an analysis flagging that Section 102 of three is deliberately technology neutral; the statute never names an acceptable method; it just leaves vendor selection to the operator. Jordan: So Congress wrote "verify age" and left the "how" as homework for every platform's legal team. Speaker 4: Exactly, and NTU's read is that's intentional. Congress doesn't want to pick a vendor and get locked in to whatever that vendor's flaws turn out to be. Jordan: Make sense on paper; does it hold up on a server like the ones we've been lurking in? Speaker 4: This is where it falls apart for me. A third of content measured against what? Per platform? Per server? Per channel? Jordan: Say more. Speaker 4: Take a mid-sized Discord server, 200-300 channels sometimes. You've got a general chat, an art channel with an NSFW gate the server already built itself, a bot commands channel that's 90% noise. Is the one-third test ran against the whole server? Per.--one flag channel out of three hundred. Jordan: Or is it per account, Thomas Doan: Right. Jordan: like does my one third get Calculated off what I personally post and view. Thomas Doan: Nobody in the text answers that; and whoever is actually running the compliance function has to pick an interpretation and hope it survives a lawsuit. Jordan: Who's even doing that math? Discord, Trust and Safety, the individual server owner who's a nineteen year old volunteer moderator? Thomas Doan: That's the part that keeps me up. The bill regulates covered platforms, but a lot of the actual content sorting happens at the server level by people who aren't lawyers and don't have a compliance budget. Jordan: So the platform gets the legal obligation, but the content lives somewhere the platform doesn't fully control. Thomas Doan: Right, that mismatch is baked into how Discord's structured. Rooms inside rooms, each with its own rules, and the statute talks like it's one storefront. FRONT Jordan: Which loops back to your bad merge comparison from earlier. Nobody agreed on the schema before they shipped it. Thomas Doan: Pretty much-and Congress seems to know it's shipping something half finished. Section 105 orders a GAO report within three years; it has to cover whether the law's actually working, compliance rates across platforms and whatever third party vendors they've contracted, and the speech and economic effects of the whole mandate. Jordan: So three years out they're asking the GAO to check if this even worked. Thomas Doan: That's Congress admitting up front it doesn't know the answer. To know the answer, you don't order a report on your own law's side effects if you're confident there won't be any. Jordan: So we've got a threshold nobody defines precisely, a verification method nobody names, and a built-in audit because even the drafters aren't sure it'll function. Thomas Doan: And two rules of construction sitting underneath all of it that are supposed to draw the outer boundary, where the platform can't go too far or has to go at least this far. Speaker 4: Mm-hmm. Jordan: And which is worth its own conversation, because those two rules didn't even exist in this shape back in March. Thomas Doan: They got split apart in the Senate-referred version, separated into different sections that used to be bundled. Jordan: And Discord's own roll out gives us something to measure all of this against in real time, not hypothetically. Thomas Doan: Which is honestly the more useful exercise than debating Senate math all day. Jordan: Fair, let's go there next. Shifting from that threshold problem, the Senate-referred text splits two rules of construction that got bundled together back in March. Thomas Doan: Split how? Jordan: Section 220 covers age verification on its own now. Section 221 covers encryption separately. In the introduced version, those lived in the same paragraph. Thomas Doan: So somebody in markup decided encryption needed its own guardrail away from the verification fight. Jordan: That's my read. GovTrack's text of H.R. 7757 shows the split plainly Speaker 5: Mm Jordan: -two Speaker 5: -hmm. Jordan: stand alone sections instead of one combined clause. Thomas Doan: Which tells me the drafters knew those are different arguments-one's about proving your age, the other's about who can read your messages once you do. Jordan: Right; and here's where the National Taxpayers' Union's read gets interesting. Their piece on the KIDS Act flags that section 103- b) bars acquiring a Government issued ID, plus a reasonable data security duty. Thomas Doan: Okay, that sounds like protection. Jordan: It sounds like protection; and to use point is it says nothing about the other options a platform might pick instead: facial scans, third-party ID vendors, whatever's cheaper to ship. Thomas Doan: So the rule of construction blocks one specific method and leaves the door open on everything else. Jordan: Exactly the gap-and Discord's own rope. Her own roll out is basically running that experiment live right now. Thomas Doan: How so? Jordan: Discord's team by default settings went out February ninth, but the Global Age Assurance piece got pushed to the second half of this year. Redactdev covered the delay. Thomas Doan: What's Discord actually testing in the meantime? Jordan: Discord's support pages show they ran Google Wallet, credit card checks and incodes on device facial estimation through June and July. Thomas Doan: None of those are the ID scan and to use rule of construction blocks-all three are the stuff it doesn't touch. Jordan: Now picture a mod running a mid size art server, twelve thousand members, getting told their verification vendor choice just became a legal compliance decision overnight. Thomas Doan: That's the real cost people miss. It's not abstract policy; it's some volunteer picking a vendor off a list with no idea what happens if that vendor gets breached. Jordan: And that's not hypothetical either: State of Surveillance dot org reported that this caused third party sup The support vendor 5CA was breached back in October 2025, roughly 70,000 government ID images. Thomas Doan: 70,000. That's the argument against ID-based flows nobody in this bill addresses. Jordan: Which is why I'd call the no ID clause cosmetic: it bans the one method everyone's already nervous about and leaves facial estimation and third-party vendors completely unregulated. Thomas Doan: All pushback there-a breach is in infrastructure failure, bad vendor contracts, bad storage-that's a different problem than what the statute is written to solve. Jordan: But if the law doesn't touch storage or vendor vetting at all, what's it actually protecting? Thomas Doan: It's protecting against one specific failure mode-forced ID collection at scale. That's not nothing, even if it's narrow. Jordan: Narrow is generous. I'd call it a rule that solves the hell. It was the headline risk and skips the one that already happened, which Thomas Doan: What happens when the facial estimation vendor gets breached instead? Same exposure, different biometric. The statute's silent either way. Jordan: is the split we're stuck on. Is a narrow ban meaningful protection or just the easiest thing to legislate? Thomas Doan: We're not settling that today, but it's worth watching which verification method Discord locks in for the full global rollout later this year. Jordan: Agreed; two things I'd flag for listeners: watch whether section two two zero survives Senate Commerce intact, and watch Discord's vendor announcement once age assurance actually goes global. Thomas Doan: Because whichever vendor they pick becomes the de facto industry standard, rule of construction or not. Jordan: Which raises the bigger question: EFF wants the Senate to scrap this whole approach, and outside counsel is telling operators to Speaker 3: act. Jordan: To act now regardless. Building on that split, let's zoom out from the no ID clause to what the outside groups actually want done with this bill. Thomas Doan: Right, because EFF's piece and the corporate law firms are reading the same text and landing in totally different places. Jordan: EFF's piece, published July ninth, doesn't want the Senate to fix HR 7757; they want it dead. Thomas Doan: Dead? How? Jordan: EFF argues the Senate should reject the whole package and instead pass a privacy law that covers Speaker 3: everybody. Jordan: Represents everyone, adult or minor, starting with a ban on cross-web behavioral advertising. Their line is, the bill's whole premise, a different internet for minors, is the wrong frame from the start. Thomas Doan: That's a real argument, not just a talking point. If the tracking infrastructure that targets kids is the same infrastructure that targets everyone, age-gating one group doesn't touch the under- Jordan: underlying business model. Thomas Doan: Exactly her point. And Discord's ad load is small compared to Meta or TikTok, but the behavioral data pipes aren't that different structurally. Jordan: Meanwhile, Crowell's client alert reads like it's from a different planet. They're telling operators the litigation risk and the Senate fight don't pause anything. Go review your vendor contracts now. Thomas Doan: Now? Before the bill is even settled? Jordan: That's the argument. Crowell frames it as you don't wait for certainty in this business, you prepare. You prepare for the range of outcomes. Thomas Doan: So one side says burn the whole bill down; the other says start redlining contracts this week. There's no middle position being offered by either camp. Jordan: None and there's a reason the timeline matters here. I pulled some outside analysis on this since the bill text alone doesn't spell out urgency. Thomas Doan: Under the House-passed text, most provisions take effect one year after enactment; the SPY Kids Act pieces move faster. After ninety days, and the first independent audit for a covered platform lands at eighteen months. Jordan: Those numbers only exist if this exact language survives the Senate, though. Thomas Doan: Right, that's reported analysis on a bill that hasn't passed, not a locked calendar. But it's why Crowell keeps pointing people at vendor contracts before anything gets signed. A ninety day clock is short if you're negotiating a new age assurance vendor deal from scratch. Jordan: OK, here's where you and I actually disagree, though. No, not just describing the disagreement out there. Go! Thomas Doan: I'd tell a small Discord server operator not to spend a single hour on this yet. Senate Commerce could rewrite half this text. Planning against language that might not exist in three months is wasted effort for someone running a four thousand member fan server with no legal budget. Jordan: I'd push back hard on that. You review vendor contracts on the chance it passes because the chance isn't zero and the chance isn't small. Small. A bi-partisan 267 to 117 House vote is not nothing. If you're already paying a verification vendor, you want a contract clause that lets you swap providers if the compliance requirement shifts underneath you. Thomas Doan: For a big platform with counsel on retainer, sure. For a volunteer mod team, that's a different calculation entirely. Jordan: Fair. Scale changes what's reasonable to ask of someone. But even a five-minute read of your Terms of Service bot config? Big costs nothing. Thomas Doan: Okay, I'll give you the five minutes, not the vendor audit. Jordan: I'll take the five minutes. Thomas Doan: Speaking of people actually doing the unglamorous work, there's a server we found that's already living this exact argument in real time. Before we close out, let's do this server tour. Something you can actually go check yourself. Speaker 4: After all that Senate hand-wringing? Sure. Thomas Doan: It's called Minor Safety Policy Watch. Maybe 200 members, mostly volunteer mods, and a few state legislative staffers. Speaker 4: Small. Thomas Doan: Small but focused. There's a channel called #STATETRACKER where a bot posts every time a state age verification bill moves. Introduced Committee Floor Vote Speaker 4: What's running that? Thomas Doan: Looks like a web hook pulling from a legislative tracking API, dumping the bill number and a one-line summary into an embed. Speaker 4: That's actually a decent setup. Thomas Doan: Their own onboarding flow isn't. It's a reaction rule screen. Click a checkmark, confirm you're 18, you're in. No check behind it. Jordan: So their own verification flow wouldn't survive Section 103? Speaker 4: Read for five minutes. Thomas Doan: Right; a self attestation check box is exactly what the Bill's technology neutral language is supposed to replace. Jordan: And that's the irony: a server built to track age verification law running the weakest version of it. Thomas Doan: Exactly. Half the threads in Hash Bill alerts are dead too. Last real post was back in May before the House even voted. Speaker 4: So what's it worth joining for? Thomas Doan: The pinned spreadsheet. Someone's kept a state-by-state tracker updated since 2024. That alone earns the join. Speaker 4: So a one-line verdict then. Good archive, weak gate, don't expect much conversation. Thomas Doan: Now, two things worth watching before we're back. Jordan: First, does Senate Commerce actually put HR 7765 on a markup calendar or just let it sit? Thomas Doan: And if they move, whether they mark up the house text or drop substitute language entirely, that changes everything we've spent this episode on. Jordan: Second, Discord's own rollout. Their press release says they're pushing teen-by-default settings in age assurance globally, face scan or government ID. Thomas Doan: And that's already been delayed once. If it lands before Congress moves, the clock starts ticking for every server admin out there. So that's HR 7765 as it stands today—out of the House and sitting in Senate Commerce since July 13th. Jordan: Still no floor date. No sponsor over there picking it up—that's the piece I keep coming back to. Thomas Doan: Right, we disagreed on that one. You're not calling the referral progress. Jordan: Not until somebody with a vote actually moves it. A waiting room isn't a hearing. Thomas Doan: Fair enough. For me, the real takeaway is Section 103. That one-third content threshold is going to be brutal to measure on a platform built from hundreds of independently run channels. Jordan: Which is the constraint nobody in the Belltech solves for. That's the thread worth watching into the fall. Thomas Doan: Exactly. So if you run a server or just lurk in a few, keep an eye on how Senate Commerce marks this up. Jordan: And if you've got a server we should look at, send us a link, serverrooms@show.com, or find us on our own Discord. Thomas Doan: New episodes drop every Wednesday. Jordan: Thanks for sticking with us through 20 minutes of committee procedure arguing. Thomas Doan: Fair. See you next week. Take care.