Why we store your meal plan locally first
The NestBoard team · 2026-06-30
When you import a recipe URL or jot down "Tuesday: pasta, use up the basil," that information lives on your kitchen tablet first. It doesn't bounce to our servers unless you explicitly turn on sync for other devices.
This isn't a privacy marketing angle. It's a technical choice that shapes how the app feels.
The default is yours
Most apps treat the cloud as the source of truth. You tap something, it uploads, then your other devices pull it down. That model makes sense for collaboration tools or services that need to process your data.
But a meal plan is different. It's often one person thinking out loud on a Sunday afternoon. You're clipping recipes, moving things around, deleting half of Wednesday because you forgot about soccer practice. It's rough-draft thinking, not a shared document.
We wanted that roughness to feel private by default. So the tablet is the source of truth. Your notes, your imported recipes, your "maybe lasagna?" scribbles — they stay there unless you decide otherwise.
Sync when it helps
If you do want your meal plan on your phone while you're at the grocery store, you can turn on sync. Then the data moves through our servers, encrypted in transit, and appears on your other signed-in devices.
But that's an opt-in. The starting point is local storage, and you can stay there indefinitely if that's what works for your household.
What this means in practice
It means you can plan meals without an internet connection. It means we don't see your recipe URLs or notes unless you've chosen to sync. It means the app doesn't slow down waiting for a server round-trip every time you drag Thursday's dinner to Friday.
It also means sync is a feature, not the architecture. That forces us to make sure the single-device experience is complete and calm, because that's what most people will use most of the time.
Why we keep coming back to this
We make choices like this across NestBoard — medication data that doesn't upload by default, pantry notifications that don't nag, an AI assistant that processes images on-device when possible.
Each one is small. Together, they add up to a different feeling: the sense that the app works for you, in your kitchen, without needing permission or a handshake with a server farm every time you think about dinner.
Your meal plan starts local because that's where meal planning actually happens. Syncing is there when you need it. But the default is yours.