Privacy

This describes how the Weekly Plan software handles information. Each household runs its own instance; the person who operates that instance is its data controller, and their contact appears inside the app under Privacy.

Everyone in a household sees everything

The plan, kitchen, shopping list, and notes belong to the household, not to one person — anyone who can sign in to an instance sees all of it, and it all prints on the sheet. Weekly Plan does not need a diagnosis or medical history; a household should not enter anything it does not intend to share with everyone who signs in.

Google Calendar (optional)

If a household connects Google Calendar, Weekly Plan requests read-only access (calendar.readonly) and uses it for one thing: to display the event titles and times from the calendars you choose, for the week being viewed, next to the meal plan.

Weekly Plan's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is used only to show your events in the app; it is not retained in the saved plan, is not transferred to anyone, is not used for advertising, and is not used to develop, improve, or train generalized models.

Calendar events are fetched live for the displayed week and are not retained as part of the saved plan. If you install the app for offline use, a copy of the pages you have already viewed — which can include those event titles — is cached on your own device so the week still shows without a connection; clearing the app's data removes it. You can disconnect at any time from the app's Settings, which removes the local connection and asks Google to revoke the grant; you can also remove access from your Google account.

What else is stored

On the household's own instance: the plan and notes, saved recipes, kitchen ingredients and shopping items; the name, email, and profile image from the sign-in service; and anonymous per-day feature counts. Sensitive fields — notes, ingredient names, custom meals, custom shopping items, and the calendar/grocery access tokens — are encrypted at rest. IP address and browser user-agent are not stored. Nothing is sold, used for advertising, or used for cross-context tracking.

Other services

When configured by the operator, an instance may send ingredient names to a recipe service for suggestions, and send search terms plus a ZIP code to a grocer for price estimates. If a member connects their own grocer account, the app can also add the shopping-list items to that account's cart. None of these receive your name, email, notes, or calendar. Each is optional and off by default.

Your choices

Inside the app you can download all of a household's plan data, delete it, and disconnect any integration. To exercise a legal right or ask a question, contact the operator of your instance — their details are on the in-app Privacy page.

Last updated 30 August 2026.