{"id":"cmp07ut180014o34bn4so86qt","slug":"why-kid-accounts-work-differently","title":"Why kid accounts work differently","excerpt":"NestBoard has separate flows for adults and children under 13. Here's why that matters for a family app, and how parental consent gates work.","body":"## Two kinds of accounts\n\nWhen you add someone to your NestBoard household, we ask whether they're an adult or a child. It sounds simple, but that choice triggers completely different paths through the app.\n\nAdults get full accounts—email login, password recovery, the ability to join multiple households or start their own. Kids get something lighter: a seat in the household with no email required, managed by the parents who invited them.\n\nThe law draws a bright line at age 13. In the US, COPPA (the Children's Online Privacy Protection Act) requires verifiable parental consent before we can collect personal information from anyone younger. That includes email addresses, profile photos, or persistent identifiers tied to a child.\n\n## The under-13 flow\n\nIf you're adding a child under 13, NestBoard never asks them to create an account. They don't get a login email. They don't set a password. Instead, the parent who invites them provides consent, and the child gets a household-only profile.\n\nThat child can see shared calendar events, complete chores, check medication reminders, and interact with family meal plans—all the collaborative parts of NestBoard. But their data lives inside the household, managed by the parents who control the workspace.\n\nWhen a child turns 13, we don't automatically flip a switch. Parents can choose to invite them to create a full account, or keep the managed profile as-is. Some families prefer that lighter setup even for teenagers.\n\n## Why this matters for calendar apps\n\nMost productivity tools are built for individuals or coworkers. Adding kids is an afterthought, if it's possible at all. But a household calendar exists specifically to coordinate people of different ages—school pickups, pediatrician appointments, whose turn it is to feed the dog.\n\nIf we treated every family member as a standard user, we'd either exclude young kids entirely or collect data we shouldn't. The two-tier system lets the whole household show up in the app without putting seven-year-olds through email verification or handing their information to third parties.\n\nIt also means parents stay in control. You decide what your child sees, when they graduate to a full account, and whether they interact with features like Robin. (We apply the same care to what Robin can access across the household—more on that [here](/blog/what-robin-actually-reads-and-what-it-never-will).)\n\n## No email, no problem\n\nThe no-email kid seat solves a practical headache, too. Most children under 13 don't have email addresses. Creating a burner account just to satisfy an app's signup flow is busywork, and it trains families to treat consent forms as obstacles instead of safeguards.\n\nNestBoard skips that. Add your child's name, confirm you're the parent, and they're in. One less password to remember, one less inbox to monitor, one fewer terms-of-service click-through.\n\nThe regulations exist for good reasons. We built the kid-account flow to respect those reasons without making family coordination harder than it needs to be.","category":"Privacy","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfejtg0008twzguq794y6u","publishedAt":"2026-05-15T13:01:34.334Z","scheduledFor":"2026-05-15T13:00:00.000Z","createdAt":"2026-05-10T20:19:23.133Z","updatedAt":"2026-05-15T13:01:34.517Z"}