Privacy Policy

Last updated: 22 October 2026

This Privacy Policy describes how 3211 Labs (“we”, “our”) collects, uses, and protects your information when you use DinnerPlan (“the Service”).

1. Information We Collect

Account information

When you register, we collect your email address. If you set a PIN before we retired PIN sign-in, it is kept only as a secure hash, never in plain text. We also store whether your email has been verified. If you share a household, we also store the email address of each person in it, the first name they give us (if any), and who invited them.

Family & preference data

To personalise your meal plans, we collect information you provide including: family size, number of adults and children, children’s ages, allergies, dietary needs (including religious ones such as halal or kosher), dietary style, cuisine preferences, ingredients to avoid, busy nights, and any notes or requests you type in.

Usage data

We collect data about how you use the Service, including: meal plans generated, saved recipes, pantry items, and shopping list interactions. We also keep a timestamped record of key actions in your account — such as signing up, signing in, generating or locking in a plan, swapping a meal, adding or reading in a recipe (if it came from a link, including the name of the website), and subscribing, renewing or cancelling (on the web or through the App Store) — so we can understand whether DinnerPlan is genuinely useful week to week. This data is used to improve your experience and the Service.

Subscriptions through the App Store

If you subscribe in the iPhone app, Apple takes the payment and RevenueCat (see section 4) tells us about the subscription: which plan, whether it’s in Apple’s free trial, when it renews or ends, and whether it has been cancelled or refunded, or has a payment problem. We use this to know whether your household can plan, to spot anyone being charged twice, and to count our subscriptions. We never see your card details or your Apple ID.

Your ratings and feedback

If you rate a dinner (“Have again”, “It was okay” or “Never again”, with optional reasons such as “too much effort” or “kids loved it”), we store the rating with your account and use it to shape your future plans — for example, a dish you rate “Never again” won’t be suggested again, and “Have again” adds it to My recipes. You can see and undo “Never again” choices in the app.

If you send feedback from the app, we store your message with your account and email it to our support team, together with the screen you were on, your screen size and your browser and device type, so we can reproduce problems and act on suggestions. If you tell us not to contact you about it, your email address is left out of that message and we won’t reply.

How you found us

When you arrive at DinnerPlan we remember how you got here: the campaign tags in the link you followed (such as utm_source or utm_campaign), any ad-click identifier added by Google or Meta, the website that referred you (without its query string), the first page you landed on, and when. This is kept in your browser for up to 30 days and, if you create an account, stored with your account, so we can tell which marketing reaches households who find the Service useful. If you came from one of our Facebook or Instagram ads, see “Advertising on Facebook and Instagram” below for what we tell Meta.

Analytics

We use Google Analytics, a web analytics service provided by Google, to understand how visitors find and use DinnerPlan — for example which pages are viewed, which campaign or website referred a visit, and whether steps such as signing up, generating a plan or opening the shopping list are completed. Google Analytics sets cookies in your browser and receives your IP address and device and browser information. When you’re signed in, we also send a random ID (never your email), so visits from your phone and computer count as one person. We never send your email address, family details or meal plans, and we remove sign-in links and other private parts of page addresses before any address is sent. Google may process this information outside Australia, including in the United States.

You can opt out by installing the Google Analytics opt-out browser add-on or by blocking cookies in your browser.

Our host, Cloudflare, also counts page views and measures how quickly pages load (Cloudflare Web Analytics). It doesn’t set cookies, record anything after the “?” in a page address, or keep your IP address.

Advertising on Facebook and Instagram

We advertise DinnerPlan on Facebook and Instagram and use two Meta tools to see whether those ads work. We keep what Meta receives to a minimum:

• The Meta Pixel, on our home page only. When you visit the DinnerPlan home page, the pixel (a script from Meta Platforms) records that the page was viewed. Meta receives the page address, the page that sent you, your IP address and your browser and device information, and may set a cookie. The pixel isn’t used anywhere in the app, so Meta never sees your household profile, allergies, dietary needs, children’s details, meal plans or shopping lists.
• Free trials that start from our ads. If you tap one of our Facebook or Instagram ads and start a free trial within 7 days, our server tells Meta that a trial started. It sends only the ad-click identifier Meta added to the link and your browser and device type — never your email address, your name or anything about your household. We don’t tell Meta about sign-ups that didn’t come from a Meta ad.

Meta uses this to measure our ads, may use it to show our ads to people who have visited DinnerPlan, and uses it for its own purposes under the Meta Privacy Policy. Meta may process it outside Australia, including in the United States. You can limit how Meta uses information from other websites for ads in your Facebook or Instagram ad preferences, opt out of interest-based advertising at aboutads.info/choices, or block cookies in your browser.

Technical data

We automatically collect limited technical data including IP addresses (for rate limiting and security) and request metadata.

2. How We Use Your Information

• Personalisation: Your family and preference data is used to generate tailored meal plans
• Meal plan generation: Your household’s meal-planning details are sent to our AI provider, Anthropic, to write your plans, swaps and recipes (see section 4)
• Recipe import: When you add a recipe from a link, we fetch that one page from our servers. When a page has no complete recipe card, or you paste or type a recipe in, or add a photo, we send that text or photo to our AI provider, Anthropic, to read the recipe. DinnerPlan doesn’t keep your photos. When you ask DinnerPlan to adapt a recipe to your family, we send that recipe, with your household’s food rules and the family details described in section 4, to Anthropic. The recipe you save is stored with your household’s data and deleted with it.
• Planning reminders: Once you have planned a week with DinnerPlan, we may email you — and, if you use the iPhone app and allow notifications, send a notification to your phone — the day before your week starts if next week isn’t planned yet. You can turn these off from the link in any reminder email or in Kitchen; account emails such as sign-in links are not affected
• Notifications on your iPhone (optional): If you allow notifications, the DinnerPlan app gives us a push token for your phone, which we keep with your account to send the weekly planning reminder. The nightly reminder to start cooking is set on your phone by the app and never sent by us. Signing out of the app removes your phone’s token if the phone is online at the time; turning off the weekly planning reminder in Kitchen stops it on all your phones
• Calendar feed (optional): If you use “Add to calendar”, we create a private link to a calendar of your locked-in dinners — meal names, cooking times, ingredients and recipe steps, never your name or email address. The calendar app you subscribe with (for example Apple Calendar, Google Calendar or Outlook) fetches it from us every few hours, and its provider keeps a copy under its own privacy terms. Anyone who has the link can see your dinners, so keep it to yourself; if it’s shared by mistake, use Reset link in the app (Kitchen, then Reminders & calendar) and the old link stops working straight away, or turn the feed off
• Security: IP addresses are used for rate limiting and abuse prevention
• Service improvement: Aggregated, non-identifying usage patterns, and the feedback you choose to send us, are used to improve the Service
• Analytics & marketing measurement: Understanding how visitors find DinnerPlan, which features help households most, and which of our marketing brings people who keep using the Service, including whether our Facebook and Instagram ads lead to free trials

3. Data Storage & Security

Your data is stored securely with encryption at rest and in transit. Sign-in links and codes are short-lived and single-use. Any PIN set in the past is kept only as a secure hash.

Sessions can be revoked at any time by logging out.

4. Third-Party Services

We use these service providers to run DinnerPlan. Each receives only what it needs for its part:

• Cloudflare — hosting, data storage, security and page analytics for the Service, and the emails we send, such as sign-in links and account notices.
• Anthropic — the AI (Claude) that writes your meal plans, swaps and recipes. When you ask for one, we send your household’s meal-planning details: family size and children’s ages, allergies and dietary needs (including religious ones such as halal or kosher), foods to avoid, busy nights, pantry items, your saved recipes, past dinners and ratings, anything you type in a note or request, and, when you add a recipe, the page text, text you paste or type, or photo it comes from. We don’t add your email address or anyone’s name, and Anthropic doesn’t use any of it to train its AI.
• Stripe — subscription payments on the web. Stripe receives your email address and handles your card details; we never see or store your card number.
• Apple — subscription payments in the iPhone app, through the App Store, under Apple’s own privacy policy. We never see your card details or your Apple ID.
• RevenueCat — checks App Store subscriptions for us and tells us their state. It receives your household’s random account ID (never your email address or anyone’s name), Apple’s record of the purchase and, from the app, your device’s IP address and basic device and app details. We keep the App Store purchase record with RevenueCat after you delete your account, so we can trace a subscription that is still being charged; it never includes your email address or anyone’s name.
• Expo — delivers the iPhone app’s notifications to Apple. It receives your phone’s push token and the words of the notification and the link it opens, never your name, email address or anything about your household.
• Google and Meta — website analytics and advertising measurement, as described in section 1.

These providers may store or process your information outside Australia, including in the United States.

We do not sell your data. We never share your household profile, allergies, dietary needs, children’s details or meal plans with an analytics or advertising provider.

5. Data Retention

Your data is retained for as long as your account is active. The app shows your 12 most recent past weeks; older meal plans stay stored with your account until you delete it. When you delete your account, all associated data — including how you found us, your activity record, your meal ratings and any feedback you sent from the app — is permanently removed from our systems. Feedback already emailed to our support inbox is kept there as ordinary correspondence.

The App Store purchase record we keep with RevenueCat is not removed when you delete your account: it lets us trace a subscription that is still being charged, and it never includes your email address or anyone’s name.

Google Analytics data is retained by Google for up to 14 months and then deleted automatically. It is not linked to your email address and is not removed by account deletion before then.

Information Meta receives through the pixel or a reported trial start is kept under Meta’s own retention rules. Deleting your DinnerPlan account doesn’t recall a trial start we have already reported.

6. Your Rights

You have the right to:

• Access: View all data associated with your account within the app
• Correction: Update your preferences and profile information at any time
• Deletion: Permanently delete your account and all associated data from Kitchen in the app, apart from the few records described in section 5
• Portability: Export your meal plans using the copy/export feature

To exercise any of these rights, use the features within the app or contact us at support@3211labs.com.

7. Children’s Privacy

DinnerPlan is designed for use by adults managing their household’s meal planning. We do not knowingly collect personal information from children under 18. Children’s ages are collected only to tailor meal suggestions and are stored as part of the parent’s account.

8. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated via the app. The “Last updated” date at the top reflects the most recent revision.

9. Contact

For privacy-related questions or requests, contact us at support@3211labs.com.