For many parents, the struggle to monitor a teenager’s digital footprint is a constant balancing act between trust and safety. But for one father, that struggle evolved into a technical battle with a platform’s internal architecture after his daughter lied about her age to join Discord.
The situation, which began as a common teenage deception to bypass age gates, spiraled into what has become a Discord age verification nightmare. After his daughter’s account was compromised, the father—who identified himself as Frey—discovered that while Discord’s systems internally recognized his daughter as a minor, the platform continued to treat her as an adult for the purposes of data collection and advertising.
Frey, who noted that his family are “not rookies on technology,” uncovered the discrepancy after requesting a data dump of his daughter’s account. The resulting files revealed a confusing duality in how the platform categorizes its youngest users, raising questions about whether age verification is designed to protect children or simply to satisfy regulatory checkboxes while maintaining profit margins.
The gap between internal data and user settings
The core of the issue lies in the difference between a user’s self-reported age and the platform’s internal classification. When his daughter first created her account, she set her age to 18 or older to ensure unrestricted access to the platform’s features. But, the data export provided by Discord told a different story.
Frey discovered an internal field labeled age_group that was set to “13–17.” This indicated that Discord’s backend systems had, at some point, correctly identified the user as a teenager. According to the data, this update occurred on March 9, roughly nine days before the account was hacked on March 18.
Despite this internal acknowledgment, a second field—is_underage—remained set to “false.” To a software engineer, this distinction is critical. While the age_group might be used for general analytics, the is_underage flag is typically the “master switch” that triggers stricter privacy protections and limits the type of data a company can collect under laws like the Children’s Online Privacy Protection Act (COPPA).
“They changed the age on their side, even though One can’t change the age on ours,” Frey said. He argued that this discrepancy is significant because the underage flag likely controls whether stricter ad protections for kids are applied.
A timeline of technical failure
The frustration for Frey was compounded by a series of failed attempts to correct the record through official channels. Even after the account was hacked and subsequently restored, the platform’s refusal to update the is_underage status persisted.
| Date | Event | Internal Data Status |
|---|---|---|
| March 9 | Discord updates internal record | age_group set to 13–17 |
| March 18 | Account is compromised/hacked | is_underage remains “false” |
| Post-Hack | Account restoration process | Updated twice; still marked “not underage” |
Frey noted that the platform updated the settings twice—once shortly after the hack and again after the account was restored. Despite repeated messages to support forums explicitly stating that the user was 13 years old, the is_underage flag remained “false.”
This technical persistence suggests that the platform could continue to build “a detailed behavioral ad profile” on the teenager, even while its own systems had already categorized her within the 13–17 age bracket.
Privacy advocacy and the profit motive
The case has drawn attention from digital rights advocates who argue that these “glitches” are not accidental but are instead a byproduct of the business models driving modern social media. Samantha Baldwin, a policy and research staff technologist for the Electronic Frontier Foundation (EFF), suggests that the hesitancy to formally recategorize accounts as minor is telling.
Baldwin argues that many current age verification laws are less about the actual safety of children and more about creating frameworks for surveillance and censorship. According to Baldwin, the refusal to recategorize a minor’s account demonstrates that the primary goal is data acquisition.
“Discord is in the business of making money by selling their users’ personal data. They are implementing ‘age verification’ to meet regulatory compliance and to collect more data about their customers, not protect children.”
For parents, this creates a “support nightmare” where the tools provided to manage a child’s safety are secondary to the platform’s need for high-value user data. When a user is marked as an adult, they are more valuable to advertisers, creating a perverse incentive for platforms to ignore or complicate the process of correcting an age to a younger bracket.
Navigating the digital safety gap
This incident highlights a broader systemic issue in the tech industry: the “age-gate” is often a superficial barrier. While Discord’s Terms of Service require users to meet minimum age requirements, the mechanism for correcting that age once an account is established is often opaque and managed by automated systems that lack nuance.
When a teen lies about their age, they effectively opt into an adult data ecosystem. As Frey’s experience shows, even when a parent intervenes with proof and support tickets, the internal “flags” that govern privacy and advertising may remain unchanged, leaving the minor exposed to behavioral tracking that they are legally supposed to be protected from.
The next critical checkpoint for these types of privacy disputes often occurs during quarterly regulatory reviews or through individual complaints filed with the FTC, which oversees COPPA enforcement. As more parents utilize data export tools to audit their children’s accounts, more discrepancies between “reported age” and “internal classification” are likely to surface.
Do you have experience dealing with social media support when trying to protect your children’s privacy? Share your story in the comments below or reach out to our tech desk.
Related reading
