Dinsy Privacy Policy
Last updated: 17 August 2026 Applies to: the Dinsy iOS app (AU/NZ)
The plain-English version
Dinsy is a dinner-planning app. To do its job, it needs to know things like which supermarket you shop at, your weekly budget, how many people you're feeding, and any dietary needs — and it remembers what it's suggested you before so it doesn't repeat itself. You sign in with your Google or Apple account, which gives us your email address — we use it to keep your plans yours, and for nothing else. We don't show ads, we don't use tracking or analytics tools, and we don't sell your data to anyone. Your meal-plan requests go to Anthropic, the AI company whose models write your plans — they see your food preferences and constraints, never your name or email. And if you add your family's food profiles, their names never leave your phone: our servers and the AI only ever see "adult 1" or "kid 2" with the relevant food needs attached.
The rest of this document sets out the detail the law requires. If anything below is unclear, contact us (see Contact us, below).
Who this policy covers
Dinsy is built and operated by Michael Turner, trading as Dinsy, a sole trader based in Gold Coast, Queensland, Australia.
Information we collect
1. Your account
To use Dinsy you sign in with Google or with Apple at the end of setup. Through that sign-in we receive and store your email address and the display name your provider shares (with Sign in with Apple you can choose to hide your real email — Apple then gives us a private relay address, which works the same way). We use these purely to operate your account: keeping your plans and preferences tied to you, enforcing fair-use limits, and letting you come back to your data. No password is ever created or stored with us, and we never see your Google or Apple password. Accounts created under the app's earlier anonymous model (no email) continue to work and are covered by this policy the same way.
1a. Your family's food profiles — names stay on your phone
If you add household members (the family/fussy-eater features) — their names, dislikes, allergies, and "will try" lists — that information is stored on your device. When a meal plan is generated, your family members are sent to our servers as anonymous slots ("adult 1", "kid 2") carrying only their food constraints; their real names never leave your phone. This matters most for children's information: our servers and our AI provider never receive a child's name, only "there is a kid who is allergic to peanuts."
2. Your food preferences
When you set up Dinsy (or change your settings later), you tell it:
- which supermarket you shop at (e.g. Woolworths, Coles, Aldi, IGA, New World, Pak'nSave)
- your weekly grocery budget
- your household size
- which nights of the week you want dinner planned for
- any dietary needs or restrictions (e.g. vegetarian, dairy-free, nut allergy)
- what "vibes" you're after (e.g. quick & easy, high protein)
- which kitchen appliances you have (e.g. oven, air fryer)
These preferences are stored locally on your device (in the app's own storage area, not a general-purpose folder other apps can read). They are also sent to our backend each time you generate a plan — see the next section for what happens there.
3. Meal plans and generation history
Each time you generate a plan, the app sends your current preferences to our backend, which asks Anthropic's AI to build a week of dinners that fits them. We keep a server-side record — tied to your account — of:
- the preferences you sent for that generation
- the resulting meal plan (recipes, ingredients, estimated prices, steps)
- the names of the recipes you were served
We keep this history for two honest, functional reasons, and nothing else:
- Variety: so Dinsy doesn't serve you the same dinner two weeks running.
- Fair use: so we can enforce a weekly cap on how many times you can generate a full plan, which keeps the AI costs (and the app) sustainable.
We do not use this history to build an advertising profile, and we do not share it with anyone except the AI provider needed to generate it in the first place (below).
4. What we do not collect
We do not collect: your location, your contacts, your photos (any family avatar you set stays on your device only), or any advertising/tracking identifiers. We do not run third-party analytics or ad SDKs. We do not show the Apple App Tracking Transparency prompt, because we don't track you across other companies' apps or websites.
5. Subscription and payment information
If you subscribe to Dinsy Plus, your payment is handled entirely by Apple through the App Store. Dinsy never sees or stores your card number, billing address, or other payment details — Apple shares with us only what's needed to know whether you have an active subscription (your entitlement status), not your payment method.
How we use your information
We use the information above only to:
- generate and personalise your meal plans and shopping lists
- remember your setup between sessions so you don't have to re-enter it
- avoid repeating recent recipes (variety memory)
- enforce fair-use limits on AI generations
- provide customer support if you contact us
- meet our legal obligations (e.g. responding to a lawful request from an authority)
We do not use your information for advertising, do not build cross-app tracking profiles, and do not sell or rent it to third parties.
Who we share information with
- Anthropic (our AI provider): each time you generate a plan, your current preferences (store, budget, household size, dietary needs, appliances, and a list of recent recipe names to avoid repeating) are sent to Anthropic's API to produce the plan. This does not include your name, email, or any other identifier that could reasonably identify you — the AI only ever sees your preferences, not who you are. Anthropic processes this as our service provider and does not use it to identify you personally.
- Supabase (our backend/database provider): stores your account, generation history, and enforces access rules so only your account can read your own data. Hosted in Sydney, Australia.
- Apple: processes your subscription payment and provides us with your entitlement status (active/inactive), as described above.
We do not share your information with data brokers, advertisers, or any other third party.
Where your data is stored
Your on-device preferences stay on your device, in the app's own protected storage. Server-side data (your account and generation history) is hosted with Supabase in Sydney, Australia, in line with Dinsy's AU/NZ Privacy Act commitments below. If that changes, this policy will be updated to name the new location and any additional protections that apply.
How long we keep your data
- On-device preferences: kept until you delete the app or clear them yourself.
- Generation history (plans, recipe names, the preferences behind each generation): kept against your account for as long as you use Dinsy, so the variety-memory feature keeps working. We look back at roughly the last four weeks of history to avoid repeat recipes; older rows are not actively used for that purpose but may still be retained unless you request deletion.
Deleting your data
You can delete your Dinsy data at any time from Settings → delete my data. This removes your locally stored preferences from your device and asks our servers to delete your account entirely, including your generation history and your sign-in identity. This action can't be undone. Deleting your data does not cancel an active Dinsy Plus subscription; cancel that separately through your Apple ID subscription settings.
If you'd rather not use the in-app option, or run into a problem with it, email us (see Contact us) and we'll delete your account data manually within a reasonable timeframe. Because your account is tied to a real, verified sign-in (your Google or Apple identity), we can confirm a deletion request genuinely came from you before actioning an email-based request.
Children's privacy
Dinsy is not directed at children, and we do not knowingly collect information from children. The app is rated 13+ on the App Store and is intended for household meal planning by people responsible for grocery shopping. Family food profiles you add for your own children (their dietary needs) are your data about your household, and their names never leave your phone (see 1a above).
Your rights (Australian Privacy Principles)
Dinsy is developed in Australia and is intended to comply with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). Depending on where you are, you may have rights to:
- ask what personal information we hold about you
- ask us to correct information that's wrong or out of date
- ask us to delete your information (see Deleting your data, above)
- make a complaint about how we've handled your information
To exercise any of these, contact us using the details below. If you're not satisfied with our response, Australian users can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au; New Zealand users can complain to the Office of the Privacy Commissioner at privacy.org.nz.
International users
Dinsy is built primarily for people shopping at Australian and New Zealand supermarkets. If you use Dinsy from outside Australia, your information will still be processed and stored as described in this policy (intended to be within Australia — see Where your data is stored).
Changes to this policy
We may update this policy as the app changes — for example, when accounts, sign-in, or new features ship. We'll update the "Last updated" date at the top when we do. Material changes (anything that changes what we collect or who we share it with) will be flagged in the app.
Contact us
Questions about this policy or your data: support@dinsy.app