Your privacy, in plain ink.
Peelmeal is a personal cookbook. We collect what is needed to save recipes, sync your account, run recipe imports, generate recipe images when you ask, manage subscriptions, and keep the product reliable. We do not sell personal information, run ads, or use your recipe content for advertising.
LAST UPDATED June 25, 2026
Summary
This Privacy Policy applies to the Peelmeal mobile app, the Peelmeal website, and related support messages. Peelmeal is operated by Zen Zero Pty Ltd, an Australian company. You can contact us at [email protected].
- Your recipes, plans, shopping items, cook logs, and settings are private to your account.
- Recipe imports keep structured recipe data and attribution, not source videos, raw captions, full transcripts, or page HTML as permanent records.
- AI recipe images are generated from your saved recipe details, not copied from source sites or source-platform photos.
- Recipe image generation may use content-safety checks, and reported generated images include provider metadata for review.
- Product analytics are first-party and do not include recipe text, source URLs, emails, or display names.
- Subscriptions are handled through the App Store or Google Play, with RevenueCat used to mirror entitlement state into Peelmeal.
What we collect
Account and app identity
Peelmeal starts with an anonymous account so you can use the app before linking Apple or Google. We process your app user ID, auth provider, account state, and, if you link an account, the email address and display name returned by that provider.
For free AI starter credits, the app may send an app-scoped installation identifier to our servers. We hash it server-side and use it to prevent simple quota abuse. The raw identifier is not stored as a customer profile.
Your cookbook data
We store the content you choose to save in Peelmeal: recipes, ingredients, steps, photos you upload, AI-generated recipe images you create, image metadata, tags, notes, favorites, meal plans, shopping items, cook sessions, cook logs, serving preferences, nutrition estimates, and app settings.
Imports and AI
When you import or generate a recipe, we process the URL, pasted text, public page text, public captions, temporary audio, or other source material needed to produce the requested recipe. Successful imports keep the structured recipe, source URL, creator or site attribution when available, and import status metadata. Source media, raw transcripts, raw captions, page HTML, and imported source images are not kept as permanent cookbook records.
When you generate a recipe image, Peelmeal sends a short prompt derived from the saved recipe title and main visible ingredients to an image generation provider. We do not send source URLs, creator handles, source photos, captions, transcripts, blog prose, or your profile details for recipe-image generation. The generated image is stored as the recipe photo until you remove it, replace it, delete the recipe, or delete your account. We may process provider safety flags for generated images and, if you report a generated image, store the fixed reason, image URL or path, and provider metadata needed to review that report while the recipe and account still exist.
Purchases, analytics, and website visits
If you subscribe, we process store product IDs, transaction identifiers, entitlement state, renewal or expiry status, and related purchase metadata. We do not receive your full card number from Apple, Google, or RevenueCat.
We collect small first-party analytics events so we can understand if people reach the core value moments: importing, cooking, seeing a paywall, purchasing, restoring, and deleting an account. We may also collect device, app version, crash, log, and website request metadata needed for reliability and security.
How we use information
We use the information described above to:
- create and maintain your account;
- save, sync, display, edit, and delete your cookbook data;
- turn user-chosen URLs, pasted text, generated prompts, and image prompts into app features;
- show subscription status, enforce Premium access, restore purchases, and prevent quota abuse;
- run content-safety checks, review generated-image reports, and prevent misuse of AI features;
- send transactional or service messages, if needed;
- respond to support, privacy, deletion, and takedown requests;
- protect the app, debug issues, and understand product health without placing your personal recipe content into analytics.
We do not sell personal information, use advertising identifiers, build ad audiences, buy data from brokers, or track you across other apps and websites for advertising.
Legal bases
Where EU or UK data protection law applies, we rely on these legal bases:
- contract, to provide the app, sync your data, and manage subscriptions;
- legitimate interests, to secure the service, prevent abuse, run first-party product analytics, and improve reliability;
- consent, where a platform permission or law requires it, such as optional notifications or photo access;
- legal obligations, where we must keep records, answer lawful requests, or enforce rights.
Service providers
We use service providers to run the app. The exact provider set can change as the product matures, but the categories are:
| Category | Purpose | Examples |
|---|---|---|
| App infrastructure | Authentication, database, storage, server functions, hosting, analytics, and logs. | Firebase and Google Cloud |
| Purchases | Store subscriptions, receipts, entitlement mirrors, refunds, and purchase support. | Apple, Google Play, RevenueCat |
| AI and transcription | Recipe structuring, recipe generation, recipe image generation, content-safety checks, nutrition estimation, and source-media transcription where needed for recipe imports. | OpenAI, Runware, Groq, or comparable processors |
| Public source retrieval | Fetching public recipe page or public social-post metadata for a user-chosen import. | Direct public web fetches and limited public-source retrieval providers where needed |
| Support and operations | Customer support, email, security review, and legal compliance. | Operational vendors selected as needed |
Retention
- Account and cookbook data are kept until you delete them or delete your account.
- Account deletion removes your private Firestore data, private Storage objects, server-owned quota docs, and Firebase Auth record from the active service.
- Generated recipe images follow the recipe photo lifecycle: removing or replacing the photo removes it from your private recipe. Reported generated images may be retained for review only while the recipe and account still exist. Recipe deletion or account deletion removes the related generated-photo objects and report records from the active service.
- Deleting your Peelmeal account does not cancel an App Store or Google Play subscription. You must cancel it through the store account that billed you.
- Temporary import processing files are kept only as long as needed to complete, retry, debug, or secure the request. Extraction audio paths are designed for short-lived retention, currently up to 24 hours on failure paths.
- Security logs, backups, transaction records, and aggregate analytics may be retained longer when needed for fraud prevention, legal obligations, accounting, or service integrity.
Choices and rights
You can edit or delete recipes inside the app, unlink or link supported sign-in providers, and delete your account from Settings. See Delete your account for the current steps.
Depending on where you live, you may have the right to access, correct, delete, export, restrict, object to, or ask us not to sell or share your personal information. Peelmeal does not sell personal information, but we will still honor applicable privacy requests. Contact [email protected] to make a request.
If EU or UK data protection law applies, you may also have the right to lodge a complaint with your local data protection authority.
Peelmeal is operated from Australia, and we handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. You can ask us to access or correct the personal information we hold about you. If you are not satisfied with how we handle a privacy issue, you can raise it with us first and then complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.
Security, transfers, and children
We use technical and organizational safeguards such as authenticated access, per-user data ownership rules, server-side entitlement checks, rate limits, and provider secrets kept out of the mobile app. No internet service can be perfectly secure, but Peelmeal is designed to keep private cookbook data private to the account that owns it.
Peelmeal and its providers may process information in countries other than the one where you live. Where required, we rely on appropriate legal safeguards for those transfers.
Some of our service providers are located overseas, so providing the app can involve disclosing personal information to recipients in other countries, such as the United States, consistent with Australian Privacy Principle 8. If a data breach is likely to result in serious harm, we will respond under the Notifiable Data Breaches scheme, including notifying affected individuals and the OAIC where the law requires it.
Peelmeal is not directed to children under 13, or to anyone below the age required to consent to online services in their country without parental approval.
Changes and contact
We may update this policy as Peelmeal changes. If a change materially affects your privacy, we will take reasonable steps to make it visible in the app or on the website.
Questions, privacy requests, and support messages can be sent to [email protected].