Skip to main content
NestBoard

← Journal

Why your meal plan never leaves your household's devices

The NestBoard team · 2026-07-20

When you add a recipe to NestBoard or plan Tuesday's dinner, that data writes to your household's devices and stays there. It doesn't get copied to our servers. It doesn't get backed up to the cloud.

This isn't an oversight. It's a deliberate architecture choice we made early, and it shapes how meal planning works across the app.

What stays local

Your meal plans, saved recipes, grocery lists, and pantry inventory all live in a local database on each device in your household. When you import a recipe URL on your phone, NestBoard downloads the ingredients and steps, then syncs that data peer-to-peer to your partner's phone and the kitchen tablet. Our servers never see the recipe itself—just enough routing information to connect your devices.

The same goes for your weekly plan. If you're meal prepping on Sunday and dragging recipes onto the calendar, those decisions sync directly between your family's devices. We never store a server-side copy of what you're eating this week.

Why we drew the line here

Meal data feels different from calendar events. Your doctor's appointment or your kid's soccer practice exists in the world—other people already know about it. But your meal plan is a window into daily rhythms, dietary restrictions, budget choices, and health details that don't need to be anyone else's business.

We've written before about what Robin actually reads (and what it never will). Meal planning sits in the same category: private by default, not because we think it's sensitive in every household, but because it could be, and you shouldn't have to think about it.

The trade-offs

Local-first architecture means no web dashboard for your meal plan. It means if you lose every device in your household at once, your saved recipes are gone. It means we can't offer "restore your meal plan from backup" as a feature.

We decided that was acceptable. Most households keep at least one device around. Recipes can be re-imported from their original URLs. And the peace of mind—knowing your grocery list isn't sitting on a server somewhere—felt worth the inconvenience.

What this doesn't cover

To be clear: your shared calendar events do sync through our servers. So do chores, medication reminders, and allowance tracking. Those features need reliable sync and account recovery, and they're not as tightly tied to the intimate details of how your household eats.

But meal planning? That stays between your devices. We built it that way on purpose, and we don't plan to change it.