The short version
MealTomato turns a food photo into a recipe after you confirm or correct the dish it identifies. A generated recipe is a practical interpretation of the dish, not its original restaurant or creator recipe.
The app can start with an anonymous session and uses an email address for account verification. We process the photos you submit, recipe-generation information, an account identifier, and subscription information needed to operate the service. Some information stays on your phone; submitted photos and generated recipes also have server-side copies. An email account is not a promise that local recipes, photos, meal plans or preferences are synchronized to another device.
This policy covers the MealTomato mobile app and website. Questions and privacy requests: support@mealtomato.com.
What we ask your phone for
| Permission | Purpose | When requested |
|---|---|---|
| Camera | Photograph a dish for a recipe | When you choose to take a photo |
| Photo library or system photo picker | Choose an existing dish photo or screenshot | When you choose an image |
You may refuse access. You can use another available image source if you do. Without an image, the photo-to-recipe feature cannot proceed. MealTomato does not request access to your microphone, location, contacts, calendar or health records for this feature.
What we process
Account and identity. Supabase provides an account identifier and session used to associate server records with your account. When you verify an email address or sign in with one, that address is processed for authentication. Password-based access is also supported for accounts configured with a password. Do not send passwords or verification codes to support.
Your dish photo. Before upload, the app resizes the image to a maximum long edge of 1536 pixels and re-encodes it as JPEG. The preprocessing is intended to discard the original image metadata, including embedded camera location metadata. Upload photos of food, avoiding people, documents and other personal information.
What you tell us about the dish. This includes the dish name you confirm or correct, servings, language and units, and the recipe generated from that information. The service also processes task and usage records to complete requests, handle retries and enforce your allowance.
A copy of the dish photo, kept on your phone. When you save a recipe, the app keeps a local copy of its photo alongside the recipe. This local file is separate from the server copy used for analysis. It remains with the saved recipe and does not expire on the server's photo-retention schedule.
Your week, your marks and preferences. The meals you plan for the week, recipes marked as favourites, cooking marks, recipe corrections, and answers you gave when you first opened the app are stored on your device. These local stores are not currently synchronized to our server.
The allergies and restrictions you told us about, and your usual meal size. These are kept on your phone and are not uploaded to us or to the model for recipe generation. The app compares supported declared allergens with the ingredients a generated recipe says it may contain. Free-text restrictions are stored and shown back to you, rather than interpreted as a safety guarantee.
An image cannot establish whether a dish is safe or free of allergens. The app can warn that an ingredient may be present; it cannot rule out hidden ingredients or cross-contamination. Read the labels of the ingredients you use and do not rely on MealTomato to manage allergies or a medical condition.
Subscriptions. Apple or Google processes store payments. RevenueCat processes purchase history, subscription status and our app user identifier to validate purchases and enable Plus. The app associates its RevenueCat identity with the Supabase user identifier. We do not receive your full payment-card details from the stores.
Website support. If you send a support form or email, we process your reply address, optional name, topic and message to respond. The website sends support-form messages through Lovable's email connector and Resend to support@mealtomato.com. Do not include payment-card details, passwords, verification codes or unnecessary sensitive information in a message. The homepage FAQ assistant matches questions locally; it is not a human live agent.
Why we process information
We use this information to identify a likely dish, generate the recipe you request, operate accounts and sessions, validate subscriptions, enforce allowances, respond to support and privacy requests, understand website use, and protect the service against misuse and errors.
Where applicable law requires a legal basis, processing needed to provide requested account, recipe and subscription services is based on performing our agreement with you. Security and support processing may rely on our legitimate interests, subject to your rights. We use consent where applicable law requires it. Device permission choices do not replace any separate consent that the law requires.
We do not sell your personal information or use your submitted photos for advertising. We do not operate an advertising network in the app or use the photos to train our own models.
Where your photo goes and who processes information
Supabase hosts authentication, the backend database and private storage. Access controls associate your account with its own records and photo paths. A private bucket does not mean the image is never transmitted: our server creates a short-lived signed URL, configured for two minutes, for the image-analysis provider to retrieve the submitted photo.
OpenAI receives the submitted image for dish identification and the confirmed dish information for recipe generation through our backend. Provider processing and retention are governed by the service configuration and applicable provider terms; this policy does not promise that our storage-deletion schedule deletes every provider log or retained copy.
USDA FoodData Central receives ingredient queries when the service requests reference nutrition information. It does not receive the submitted photo for that lookup.
RevenueCat, Apple and Google process the account or transaction information needed for subscription services. Lovable and Resend process website support-form delivery as described above. These service relationships are different from selling information or using it for cross-app advertising.
Information may be processed outside your country, including in the United States. Applicable safeguards and local privacy rights depend on the processing and laws involved. You may contact us about the safeguards and privacy rights applicable to your information.
Analytics and service records
Website traffic statistics. Our website host, Lovable, measures page visits, traffic sources, country and device type for aggregate website reporting. We use these statistics to understand website use and improve the pages. This website measurement is separate from mobile-app recipe generation and subscription processing.
We do not currently send the app's own product-action events to a separate product-analytics service. Authentication, subscription validation, hosting, security and provider requests still require processing records. RevenueCat also uses purchase information for subscription reporting.
How long we keep things
Recipes and account records. Server recipe records remain associated with your account until deletion, subject to the anonymous-account expiry described below once implemented. Your saved local recipes remain on your device until you remove them or clear the app's data. Signing in with an email address does not, by itself, upload or restore local history.
Local photos and preferences. A local photo remains with its saved recipe. The planned week, favourites, recipe corrections, allergies and preferences remain until changed or cleared. They are separate from the server photo-retention job.
Dish photos on our servers are deleted after 30 days. A daily cleanup runs at 06:15 UTC and selects photos whose storage creation time is older than 30 days. Eligible photos are removed on the next successful cleanup, rather than at the exact instant they reach the threshold. This schedule applies to the server copy, not the photo kept with a saved recipe on your phone or records retained independently by service providers.
Verified 2026-10-30: 1 object deleted during a controlled check of the photo-retention process; a newer test image was preserved. This checks the server cleanup, not deletion of copies retained independently by service providers.
Anonymous accounts. Automatic deletion of anonymous accounts after 90 days of inactivity is not currently active. Until that cleanup is activated, anonymous account records and their server recipes remain until account deletion. Removing the app does not remove these server records. If you lose the anonymous session, we may be unable to verify which records belong to you. Use the in-app deletion control before removing the app, or contact support if you still have information that can establish account ownership.
Support and operational records. We retain support correspondence as needed to handle the request and applicable recordkeeping obligations. Service providers may retain their own security, transaction or legally required records. Retention depends on the purpose of the record, applicable legal obligations and the relevant provider's policies; the photo-retention period does not apply to every category of record.
Deletion and your choices
In Settings, Delete all my data requests deletion of your MealTomato account and associated server photos, recipes, tasks and quota records, followed by the local recipes, photos, every favourite, meal plans, allergies, restrictions and preferences. The app reports a failure if deletion cannot be completed, so you can retry.
Deleting one saved recipe removes its local photo, corrections and favourite pointer. It is not a promise that this action deletes the corresponding server recipe record; use account deletion for the full server-account deletion flow.
Deleting the app does not delete server data and does not cancel a subscription. An anonymous session may be lost when local app data is removed. Email verification does not automatically back up local history, and recovery of local content must not be assumed. Manage subscription cancellation separately through the store account that made the purchase.
For an external deletion request or a privacy question, contact support@mealtomato.com. We must verify ownership before acting and may need the account email or account identifier. Never send a password, session token or one-time verification code. If an anonymous session has been lost and ownership cannot be verified, we may be unable to identify or delete a specific account on the basis of an email alone.
Deletion from our service does not cancel a store subscription or erase the stores' transaction records. Separate RevenueCat, store and service-provider records may be retained under their own policies or legal obligations; the in-app button is not a promise to erase every independent third-party record.
Depending on applicable law, you may have rights to access, correct, delete, receive a copy of, restrict or object to processing of your personal information, and to complain to a supervisory authority. Contact the address above to exercise a right. We may need proportionate ownership verification and may have legal reasons for retaining particular records.
Children
MealTomato is intended for people aged 13 and over and is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided information, contact support@mealtomato.com so we can investigate and take appropriate action. Where local law requires parental permission for a younger user's use, that requirement also applies.
Changes and contact
We will keep the current policy at this address and communicate material changes as required by applicable law before they take effect.
E AI Agent Systems LLC — Florida, United States
Website: mealtomato.com
Privacy contact: support@mealtomato.com