Privacy Policy for Nonna's Cookbook

Last updated: 6 November 2026Nonna's Cookbook is run by Caleb Terranova, a sole trader in Western Australia. In this policy, "we" and "us" mean that sole trader. You can reach us at [email protected].We collect as little as we can. We don't track you, we don't show ads, and we don't sell your information. We follow the Australian Privacy Principles.What we collectYour CookbookYour Recipes, photos, Meal Plan, Shopping Lists (with their Aisle order and forgotten items), Favourites, Cooked it log (who cooked, the day and any note) and notes are stored in your private iCloud (CloudKit) storage, which Apple runs. We can't see them there. Your app settings and your place in Cook mode stay on your device. Step timers run on your device through Apple's alarms and aren't saved to iCloud.If you start a Family, the Cookbook is stored in the Creator's iCloud storage and shared with the Members and Guests the Creator invites, through Apple's iCloud sharing. They see your Recipes and your name as Apple shows it to them. Only they can read it.AccountsAccounts are being introduced in stages and may not be available to you yet. If you create one, we collect:• Your name and date of birth, which you enter. We use your date of birth only to check you're old enough for an account and to apply the protections for under-18s described under Children. We don't show it to anyone else.• Your email address and a sign-in identifier from the way you sign in: Sign in with Apple, Sign in with Google or a one-time code sent to your email. With Sign in with Apple you can choose to hide your email, and we then get a private relay address from Apple.• Basic sign-in records: when your account was created and when you last signed in, and the IP address and device details of each sign-in, which we keep for a short time to keep accounts secure.If you sign in more than one way with the same verified email address, those sign-ins belong to one account, and we tell you when a new one is added.For now your Cookbook stays in iCloud, as described above. We'll update this policy before any of it moves to our servers.Google user data. If you use Sign in with Google, we receive your name, email address and Google account identifier, and nothing else from your Google account. We use them only to sign you in and run your account. We don't use them for advertising, sell them, or let anyone read them except as needed to run the app or comply with the law. Nonna's Cookbook's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.The CommunityUnless you mark a Recipe as a Family secret, the Creator's device Publishes it to the Community, a public database that everyone using the app can read. A Community recipe contains the whole Recipe as written (title, Ingredients, steps, Tags, yield, times, equipment, notes and Nutrition values) plus the Family name, and is signed "From the [Family name]". It doesn't carry Members' names. The record also carries an identifier Apple's CloudKit assigns to the Creator's iCloud account; it isn't your name or email address. Photos are never Published. Don't put anything private in a Recipe you Publish.We can read the Community recipes you Publish, and every Report and Save you make. A Report holds the Recipe, the reason you chose (Not a recipe, Offensive, Copied without permission or Other) and your Apple identifier. A Save holds the Recipe and your Apple identifier. Neither has your name, but that identifier is the same one on your Family's Community recipes, so anyone who queries the database directly could tell that your Family's Creator reported or saved a Recipe.Importing a RecipeWhen you import from a photo, a web page, text or a file, the app reads it with Apple's on-device Foundation Models. That happens on your device: we don't send the text or photos to us or to any AI service. When you import from a link, your phone asks that website for the page, so the site sees the request and your IP address. For a TikTok link the app asks tiktok.com for the caption, and for a YouTube link it fetches the video's page. Those sites' own privacy policies apply to that request.NutritionThe app estimates a Recipe's Nutrition on your device from a food table bundled with the app and saves the estimate with the Recipe. Estimates are only estimates, not medical or dietary advice. The app doesn't use HealthKit or any health records. Nutrition is part of the Recipe, so it's Published with it unless the Recipe is a Family secret.BlockingWhen you hide a Community Family, its key and name are saved in your iCloud key-value storage and synced across your devices. We can't see it.PurchasesNonna's Plus isn't on sale yet. When it is, Apple will take payment under its own terms, and we won't receive your card or Apple Account details. A record that you bought it will be kept in your private iCloud.When you contact usIf you use Send feedback, the app opens your Mail app with a message to us, or shows our email address so you can write to us yourself. We get your email address, your message, the app version and build, iOS version and device model, and anything you attach. We use it only to reply and fix problems, never for marketing. It's stored by Apple (iCloud Mail), whose servers may be outside Australia. We keep it for up to 2 years, then delete it, and sooner if you ask. If you're under 18, we reply only about your message and delete it once it's sorted out.Diagnostics"Share Diagnostics" in Settings makes a text file only when you choose it. It goes wherever you send it.What we don't do• No tracking, analytics or advertising, and no third-party advertising or analytics code in the app.• We don't sell or share your information for marketing.• We don't build a profile of you.Who stores it, and where• Apple stores iCloud and CloudKit data, including the public Community database, on servers that may be outside Australia, including in the United States, under its own privacy policy (apple.com/legal/privacy).• Supabase hosts accounts for us, in its Sydney, Australia region. Supabase is a US company, and its staff may access the data from outside Australia to support the service.• Google handles Sign in with Google if you choose it, under its own privacy policy (policies.google.com/privacy).• Backups. We back up the account database every day. Each backup is encrypted before it leaves our computer and stored in our iCloud Drive (Apple). Backups are deleted after 14 days.We chose these providers and take reasonable steps for them to handle your information in line with the Australian Privacy Principles.Who can see what• Your Cookbook, photos, Meal Plan, Shopping Lists, Favourites and Cooked it log: you, and your Family if you have one.• Your account details (name, date of birth, email): you and us. Never other people using the app.• Community recipes you Publish: everyone using the app.• Reports and Saves: us, and anyone who queries the public database. No name, but each carries an Apple identifier that can be linked to your Family's Community recipes.• Imported photos, files and pasted text: only your device.• Links you import from: that website (or TikTok or YouTube) sees the request and your IP address.How long we keep it, and deleting it• Your account stays until you delete it. You can delete it in the app at any time, and a parent can ask us to delete their child's account by writing to [email protected]. We then delete your name, date of birth, email and sign-in identifiers, and revoke the app's Sign in with Apple access. Deleted data can stay in encrypted backups for up to 14 days until they're replaced.• Unfinished sign-ups. If you start signing up but don't finish, we delete what you gave us within a day.• Your Cookbook stays until you delete it. A deleted Recipe goes to Recently Deleted and is removed for good after 30 days, the next time you open the app, or sooner if you choose Delete Now. A Family's Creator can end the Family, and a Member who leaves takes no copy of the Cookbook with them.• Community recipes come down from the public database when the Creator's device next syncs after the Recipe is deleted or marked a Family secret. If that device never syncs again, the record can stay public. Write to us and we'll remove it.• Reports are kept for 12 months after we review them and used to hide a Recipe that three people report and to review it. Saves are kept until the Recipe or your account is deleted and used to count how often a Recipe was saved. Taking a copy out of your Cookbook doesn't delete its Save.• To have something deleted, write to us. We'll answer within 30 days. Your private Cookbook is in your iCloud, so you delete it with the app or your iCloud settings.• Takedown. We can remove any Community recipe. That doesn't remove a copy someone already Saved to their own Cookbook.ChildrenYou must be at least 13 to create an account, or older where local law requires: 16 in Australia and Brazil, 14 in South Korea and Canada, and 18 in India. Apple's age check (Declared Age Range) is used first where it's available, and if it and the date of birth you give disagree, we go by the younger age.If you're under the minimum age, we don't create an account. We delete the name and date of birth you gave us, and keep only a scrambled (hashed) form of your Apple ID and email, for up to 3 years, so the same details can't be used to sign up again.If you're between the minimum age and 17, your account has extra protections: you can't Publish to the Community, we don't send you marketing or ask you to rate the app, and your date of birth stays hidden. They end automatically when you turn 18.The app's age rating is 13+, or 16+ in Australia, 14+ in Canada and Korea. We don't knowingly collect information from anyone younger than the minimum age. If you think we have, write to us and we'll delete it.Your rightsYou can ask us to show you or correct the personal information we hold about you, or to delete it, by writing to [email protected]. We'll answer within 30 days. Your Cookbook lives in your own iCloud, so you can already see, change and delete it in the app.ChangesIf we change this policy we'll update the date above and say so in the app's What's New. If a change affects information we already hold, we'll tell you in the app before it takes effect.