Skip to main content
NestBoard

← Journal

Why we don't require email verification for kid accounts

The NestBoard team · 2026-06-24

The fake email problem

A lot of family apps require every household member to have a verified email address, even if they're six years old. So parents end up creating emma.smith.2018@gmail.com for a child who won't touch email for another five years. It's awkward infrastructure for a reality that doesn't exist yet.

We decided not to do that. When you add a child to NestBoard, you vouch for them. No email required. No verification link sent to an inbox nobody checks.

How parent vouching works

The trust model is simple: if you control the household, you control who's in it. When you create a kid account, you're asserting that this person belongs to your family. We trust that assertion because you're the paying account holder.

This works because NestBoard isn't a social network. Kids aren't sending friend requests or posting publicly. They're marking off chores, checking the dinner plan, and asking Robin when their soccer game starts. The scope is contained, and the risk surface is small.

If you've set up kid accounts before, you know they already work differently—permissions, kiosk mode, allowance tracking. Not requiring email is part of that same philosophy. Children participate in the household system on terms that make sense for their age.

The privacy tradeoff

There is a tradeoff. Without email verification, we can't offer password recovery for kid accounts. If a child sets a passcode and forgets it, a parent has to reset it. That's less convenient, but it's also more honest about who's actually in charge of account security in a family with young kids.

We also can't send individualized emails to children, which is probably a feature. Nobody wants their eight-year-old getting notifications about household updates or promotional messages. The kitchen tablet shows what needs to be shown. Everything else can wait.

When kids do get email

At some point, your teenager will have their own email address and want more autonomy. When that happens, they can link an email to their existing account and take over password management themselves. The transition is smooth because the account already exists—it just gains a new credential.

We built this system because we kept hearing from parents who felt silly creating burner email accounts for toddlers. It didn't match the way families actually work. So we designed a trust model that does.