🎧 Prefer to listen?
I build AI products for a living, and when OpenAI announced ChatGPT for Teens, my first thought wasn’t “good for them.” It was “how much did this cost them in legal fees before they got here?” They didn’t add teen safety features out of the goodness of their hearts. They did it after Florida sued them over chatbot interactions linked to teen mental health crises. That’s a liability gap, and OpenAI’s IPO filing makes it even more awkward.
ChatGPT for Teens ships three protections: a guided Study Mode, cheat-detection nudges, and parental controls with Quiet Hours. Google took the opposite route, positioning Gemini as a tutor instead of a companion. If you’re a solo builder with an AI product that touches users under 18, both approaches contain pieces worth copying, and you can implement the core layers for about $50/month.
What does ChatGPT for Teens actually include?
Three components, each targeting a different failure mode.
Study Mode — instead of handing over answers, ChatGPT asks guiding questions and walks teens through problems step by step. The point is understanding the process, and parents can make Study Mode the default so kids have to opt out of it.
Homework reminders — when the system detects a teen trying to cheat rather than learn, it pushes a nudge toward Study Mode. Think of it as a soft gate: “are you sure you want the answer instead of the process?”
Parental controls — parents manage settings, receive safety notifications, and set Quiet Hours. OpenAI previously introduced family tools that now plug into the teen experience.
The content filters follow OpenAI’s Under-18 Principles, which they claim are informed by developmental science. OpenAI also partnered with CodeAI to help teens learn how AI works, including how to question it rather than only use it.
Why did Google take a different path with teens?
While OpenAI was getting sued, Google packed Search and Gemini with new AI study tools focused on learning assistance rather than safety guardrails. The move sidesteps the “AI as a friend” problem entirely: Google positions Gemini as a tutor, not a companion. That’s a design choice with real consequences for how teens interact with the system.
For solo builders, this split matters. OpenAI builds trust through parental oversight; Google builds it through utility. You’ll need to pick the approach that fits your product, because trying to do both usually means doing neither well.
Why does user trust decide whether parents allow your product?
Users are getting skeptical of what AI tells them. Bill Gates recently said we’ve passed AI’s danger thresholds, which is a strong claim, but it points to something real. A tool called QueryStory is built around exactly this idea: it wants you to verify AI outputs instead of accepting them.
The skepticism shows up in numbers. A 2025 Pew Research study found that 52% of Americans feel more concerned than excited about AI’s role in daily life. For teen-focused products, that concern translates directly into parental gatekeeping. If parents don’t trust your system, their kids never open it.
Here’s what I’ve learned building my own products: trust is a design constraint you build around from day one, not a feature you bolt on later. OpenAI learned this the hard way. You don’t have to.
How can a solo builder add teen safety features without a big team?
You don’t need OpenAI’s engineering staff. I’ve done this in my own projects, and here’s the actual stack:
- Content filtering — OpenAI’s Moderation API plus a custom blocklist. The API catches obvious stuff; my blocklist handles edge cases specific to my user base. Total cost: about $50/month for moderate traffic.
- Usage nudges — if a user under 18 sends more than 10 messages in 5 minutes, the system pauses and asks if they want to switch to a guided mode. It’s imperfect, but it slows the “just give me the answer” impulse.
- Parental dashboard — a basic view-only dashboard on Supabase. Parents see usage time, topic categories, and flagged interactions. No message content; that’s a privacy line I won’t cross. Development time: two weekends.
- Age verification — self-declaration plus a secondary email verification sent to parents. Not foolproof, but it creates a paper trail that helps in liability situations. OpenAI uses similar logic, though theirs has more engineering behind it.
Start with the minimum viable safety layer, then iterate on real user behavior. I’ve shipped three versions of my parental dashboard in six months, and each one got simpler because parents told me what they actually needed. It wasn’t what I assumed.
Which approach should you copy?
Steal the parts that match your product’s relationship with its users. If your product functions like a study tool, Google’s tutor-first framing costs you almost nothing and avoids the companion problem altogether. If it’s conversational, you need OpenAI’s parental-oversight layer, and you need it before launch, not after a lawsuit forces it. Either way, the four implementation pieces above — filtering, nudges, a view-only dashboard, and age verification — cover the baseline for roughly $50/month and a couple of weekends.
FAQ
Do I need age verification if my product isn’t aimed at teens? If teens can reach it, treat them as part of your user base. A self-declaration form plus a parent email verification takes a weekend to build and creates a record of your good-faith effort, which matters if regulators or plaintiffs come asking later.
How much does a teen safety layer cost to run? In my experience, about $50/month for moderate traffic, mostly OpenAI’s Moderation API fees plus Supabase hosting. The bigger cost is development time: two weekends for a view-only parental dashboard and another few days for usage nudges and age checks.
What should a parental dashboard actually show? Usage time, topic categories, and flagged interactions. Do not show message content. Parents I’ve worked with care about patterns, not transcripts, and withholding raw messages protects both the teen’s privacy and your liability position.
Is Study Mode-style guidance hard to implement? No. The core is a system-prompt change that instructs the model to ask guiding questions before answering, plus a detection rule (like my 10-messages-in-5-minutes check) that triggers a nudge. It won’t be as polished as OpenAI’s version, but it changes user behavior measurably.