Why kid accounts work differently (and why we never ask for a child's email)
NestBoard · 2026-05-15
Two kinds of seat
When you add someone to your NestBoard household, you pick a role: Adult, Caregiver, Child or Guest. It sounds like a small question. It sends the first two and the last two down completely different paths through the app.
Adult and Caregiver are logins. An email address, password recovery, the usual. Child and Guest are seats in the household with no email required, managed by the adults who set them up. The rest of this post is about that second kind, because it is the one that works differently from every other app on your phone.
That difference is not a shortcut. It comes from two things pushing the same way: a law that draws a hard line at age 13, and a piece of infrastructure most family apps ask parents to fake.
The fake email problem
A lot of family apps require every household member to have a verified email address, even if that member is six years old. So parents end up creating emma.smith.2018@gmail.com for a child who will not touch email for another five years.
It is awkward infrastructure for a reality that does not exist yet. The inbox is never read, the verification link gets clicked once and never again, and it trains families to treat consent flows as obstacles to route around rather than safeguards.
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. If you are comparing apps on exactly this point, which family organizer lets kids have their own profile without an email lays out how Cozi, FamilyWall and NestBoard each handle it.
The under-13 flow
In the US, COPPA, the Children's Online Privacy Protection Act, requires verifiable parental consent before a service can collect personal information from anyone under 13. That includes email addresses, profile photos, and persistent identifiers tied to a child.
So NestBoard never asks a child to create an account. Add a member with the Child role and the consent notice appears there and then, before anything else happens. They do not get a login email. They do not set a password. The adult adding them provides the consent, and the child gets a household-only profile.
That child can do the collaborative parts of NestBoard: see shared calendar events, complete chores, check medication reminders, interact with the family meal plan. Their data lives inside the household, managed by the parents who control the workspace.
How parent vouching works
The trust model is simple. If you control the household, you control who is in it. When you create a kid profile, you are asserting that this person belongs to your family. We trust that assertion because you are the account holder, and because the assertion is not doing much work.
That last part matters more than it sounds. This model would be irresponsible on a social network, where a fake profile can reach strangers. NestBoard is not one. Kids are not sending friend requests or posting publicly. They are marking off chores, checking the dinner plan, and looking up what time their soccer game starts. Contained scope and a small risk surface are what make a lighter trust model appropriate rather than reckless.
Parents stay in control of what sits inside that scope. Robin is for the grown-ups, and that is enforced on our servers rather than hidden in the app, so a kid profile is refused even if it reaches the Robin page. The gate is on the profile rather than the person, so a tablet signed in as a parent is still a screen a child can type into, which is why Robin keeps its language family-appropriate as well. Adults decide which events are marked adults-only, which parts of the app the household shows, and when a child graduates to a login of their own. We apply the same care to what Robin can access across the household.
The tradeoff, stated plainly
Skipping email verification is not free, and we would rather name the costs than let you find them later.
No login of their own, so no password to recover. A no-email profile isn't an account. The child taps their name on a device the household is already signed in on, which means there's nothing for them to forget and nothing for us to reset. It also means access to that profile is exactly access to that device. Less convenient, and more honest about who is really in charge of security here.
No individualized email to children. We cannot send a child their own messages, which is almost certainly a feature. Nobody needs an eight year old getting their own stream of household notifications. The kitchen tablet shows what needs to be shown, and an adult reads anything that has to arrive by email.
Both point at the same thing: in a house with young children, the adult who set things up is the real security layer. We would rather build around that than paper over it.
Why this matters for family apps specifically
Productivity tools are mostly built for individuals or coworkers, and a household calendar is a different problem by definition: it exists to coordinate people of different ages, from school pickups to whose turn it is to feed the dog.
Treating every family member as a standard user lands you in one of two bad places. Either young kids are excluded and the app becomes a parent tool the rest of the family merely appears in, or every six year old needs an inbox that exists only to satisfy a signup form, and the consent step that inbox was supposed to carry becomes a formality.
When kids do get email
Sooner or later a kid has their own email address and wants more autonomy. Nothing happens automatically at that point, and it is worth being precise about why: NestBoard does not work out a child's age by itself. The under-13 marker is yours to set, and no switch flips on a birthday. An adult can invite the child to a full login whenever that is the right time, or leave the managed seat exactly as it is. Plenty of households prefer the lighter setup even for teenagers, and that is a choice rather than a delayed upgrade.
When the change does happen, it is not a migration. The existing seat upgrades to a full login, and none of the chore history or progress attached to it is lost along the way.
The regulations exist for good reasons. Making a parent create a burner inbox for a toddler is a bad answer to a real problem, so we built a model without one.