What Robin actually reads (and what it never will)
The NestBoard team · 2026-07-29
What you give Robin
Robin sees what you deliberately hand it. That's the rule.
You can tap the mic and ask a question out loud. You can paste a block of text: a recipe, a message from school, a complicated insurance form. You can drop in a photo of a pantry shelf or a medicine bottle label. You can forward an email about soccer practice times or a dinner reservation confirmation.
All of that is fair game. Robin reads it, answers your question or updates the calendar or adds the item to your pantry, and moves on.
What Robin never touches
Robin doesn't crawl your inbox. It doesn't browse the web on your behalf or scrape your browser history. It doesn't watch what you do in other apps or listen to conversations unless you press the button.
NestBoard doesn't train AI models on your family's data, and the model providers behind Robin run on no-training tiers, so your messages aren't used to improve anyone else's models either. Your grocery lists and medication schedules and meal-planning notes stay yours. They're not anonymized and folded into someone else's training set. They're not "aggregated for insights." They just sit in your household database, doing their job.
This is a privacy contract. Robin works for you, not the other way around.
The honest part about us
One thing we want to say plainly, because burying it would be worse: NestBoard staff can review Robin conversations when there is a real operational reason, such as investigating a safety concern, debugging a reported problem, or checking that Robin answered accurately. That access is rare, limited to the purpose at hand, and logged on our side. It is never used for advertising, never sold, and never fed into model training. If you ever want to know whether your household's conversations have been accessed, email hello@mynestboard.com and we will tell you.
One conversation, not five
Robin lives in two places: a quick-access popup that floats over whatever you're doing, and a standalone screen where you can see the full thread.
Both surfaces show the same conversation, one shared household thread. That's intentional. When your partner asks Robin about dinner plans and you ask about the grocery list ten minutes later, Robin remembers both. The context doesn't fragment across individual accounts.
Some AI assistants give every person their own private chat. That makes sense for work tools, but it's wrong for a household. Families don't operate in silos. The question "Did we already buy milk?" shouldn't require checking three separate threads to find out who last talked to the bot about groceries.
One conversation means less repetition, less coordination overhead, and fewer moments where you're solving a problem someone else already solved five minutes ago.
Why this matters
AI assistants are everywhere now, and most of them operate on the assumption that more data is better. More access, more context, more surveillance.
We think that's backwards for a family tool. The whole point of NestBoard is to reduce the invisible labor of running a household, and that labor includes worrying about what software knows about you.
Robin is powerful because it's constrained. It knows what you hand it and what's already in your NestBoard, and nothing else. That stays scoped to your household: Robin can't see other households, and other households can't see yours.
Two things reach past that line, and both are on this page rather than buried in a policy. Your question goes to the AI provider that answers it, on a no-training tier. And NestBoard staff can read a conversation under the narrow, logged conditions described above. That's the whole list, and that's enough.