Privacy Policy
Effective 2026-10-01 · Last updated 2026-10-01
The short version. Your household profiles, allergies, meal plans and grocery lists stay on your device. Optional recipe imports use an online service: the public link and video you choose are processed by MealAce, ScrapeCreators and Google Gemini to create a recipe.
You do not need a MealAce account. We do not use household information or imported content for advertising or tracking.
Who this policy is from
This policy covers MealAce for iPhone and iPad and mealace.app. In this policy, “we” means the developer of MealAce.
What stays on your device
Household names, age bands, allergies, intolerances, exclusions, kitchen settings, meal plans, grocery checkmarks and cooking progress are stored in MealAce’s private storage on your device. Recipe importing does not send this information to our service or to our recipe-processing providers.
Saved recipes and your edits stay on your device. MealAce does not sync your household or saved recipe library between devices. Apple’s device backups may include this local data under Apple’s backup settings.
A random local identifier is kept in the device keychain for recognising local app data. It is not transmitted by the import service.
When you import a recipe
When you choose to get a recipe from a public video link, or save one through the Share extension, the link and source content are sent to MealAce’s import service. ScrapeCreators retrieves the public post, caption and media. Google Gemini processes the caption or video, including its audio when present, to draft the recipe. A source preview image may be saved with the recipe.
Only share public content you are entitled to use. A video can include its creator’s name, face, voice or other information in the original post. We do not send your household profile or meal plan with it.
Our service runs on hosted infrastructure in Singapore and is reached through Cloudflare. Apple verifies app and subscription transactions. Provider processing may occur in other countries. The providers’ privacy information is available from ScrapeCreators, Google, Cloudflare and Apple.
Import access and subscriptions
Apple handles subscription payments. We do not receive your payment card, billing address, Apple Account email or password.
To recognise import access, MealAce sends Apple-signed app transaction information to our service. If you have a subscription, it also sends signed subscription information, which we verify with Apple. These signed records are processed for verification and are not saved in our service’s persistent storage.
We retain hashed app and subscription identifiers, the included trial’s usage, import usage counts and service cost records. They are used to apply the one-time trial, verify paid access, prevent misuse and operate the service. They are not used for advertising. Hashing does not make these records anonymous: they still distinguish one import user from another.
There is no third-party purchase analytics SDK. Manage or cancel your subscription in your device’s Apple Account subscription settings. Deleting MealAce does not cancel a subscription.
Retention and deleting import data
Recent import links, results, preview images and job status are cached on our server for up to 24 hours. They may be removed earlier when the cache fills or when you delete them. Downloaded video is temporary; uploaded processing files are deleted after use, with cleanup retried if a provider is temporarily unavailable. Provider-side records follow the providers’ own terms and policies and may be retained longer than MealAce’s cache.
Use “Manage import data” in the import flow to export or delete recent server import data. Deletion does not delete recipes already saved on your device, reset your used trial or cancel an import already being processed. It does not delete records independently retained by our processing providers.
Minimal hashed identity, trial, subscription usage and cost records remain after recent import data is deleted, for as long as needed to operate import access and prevent abuse. Contact us with a privacy or deletion request; we will explain any records that must be retained.
Remove local recipes or other entries in the app, or delete MealAce to remove its local household data. Device backups are managed separately through Apple.
Children and allergy information
MealAce is designed for an adult managing a household. Children do not have separate accounts. Names and approximate age bands entered by the adult stay on the device, as does allergy information. Do not include private household or child information in links submitted for importing.
MealAce is a planning tool, not a medical device or medical advice. Imported recipes may contain estimates and are not checked against household allergies. Read the recipe and actual ingredient labels before cooking.
No advertising or tracking
MealAce has no advertising, attribution or third-party analytics SDK. We do not sell personal information or share it for targeted advertising. Lottie draws bundled animations and does not send app data over the network.
Internet requests necessarily pass through network infrastructure, which processes network information such as IP addresses to deliver and protect the service. Infrastructure providers may retain request and security diagnostics under their own policies. Our import application does not store request bodies, signed credentials or household profiles in access logs. Apple may provide its own aggregate app and sales reports.
Your choices and contact
Video importing is optional. Planning, grocery and library cooking features work independently of it. Close the import screen if you do not want to send a link for processing.
Depending on where you live, you may have rights to access, correct, export or delete personal information. For requests or questions, contact hello@mealace.app. If you contact us, we receive the information you choose to include in that message.
Changes to this policy
We update this policy when our practices change and update the date above. Material new uses of data will be explained before they begin, with permission requested where required.