Privacy Policy

MealWisp ("we", "us") is your AI meal companion — you send us a recipe video or link, we turn it into a structured recipe you can save, rate, collect, and shop for.

This policy explains what we collect, why, and how to get it deleted.

What we collect

Account. Email and password, or a Google or Apple sign-in. From Google we receive your Google account ID and the email Google reports for it; from Apple we receive your Apple user identifier and the email Apple reports for it — which is a private relay address if you chose Hide My Email, and one we can only use to reach you through Apple's relay. Your display name and an optional avatar image.

Onboarding preferences. Country, time zone, cuisine preferences, dietary restrictions/allergens, and your primary goal — used to personalize recommendations, route grocery availability, and show times in your own clock. Optional: how you heard about us.

Your country and time zone are read once from your device's own settings when you create your account, and you can change both at any time under Settings. We don't work them out from your IP address, we don't store your location, and we don't re-read them afterwards — once you've set them, they're yours.

Recipe content. The links or videos you submit, the media itself (temporarily, to extract a recipe), and the structured recipe we produce from it — ingredients, steps, nutrition estimates. Extraction uses speech transcription, image/frame analysis, and an LLM. If a video or photo names a dish but doesn't show how it's made, an AI model writes a recipe for that dish instead, and the app labels it as written by AI rather than taken from what you shared.

Activity. Ratings, collections, meal plans, chat messages with the meal assistant, and usage counters (how many conversions/recommendations you've used) so we can enforce your plan's limits.

Dish ideas. When you use "What should I eat?", we keep the dishes it suggested to you — your last 20, with their pictures — whether or not you saved them, so you can find them again on any device you sign in on. Saving one adds it to your library as a recipe.

Device. A push notification token, if you enable push.

Subscription status. Whether you're on Free/Plus/Pro and when it expires. Billing itself runs through the Apple App Store or Google Play — we never see your card number. We receive purchase/renewal/cancellation events from our billing partner, RevenueCat, keyed to your account.

Grocery (where available). If you use the "Shop" feature, we send your ingredient list to our grocery partner to build a cart. We don't send it unless you tap Shop.

What we don't collect

No phone number is required or collected as part of signup or verification. No payment card details ever reach our servers.

Why we collect it

• To run the core product: turn what you send us into a recipe, save it, and recommend more of what you like.
• To enforce plan limits and process subscriptions.
• To send push notifications you've opted into.
• To fix bugs and understand how features are used. These analytics events are linked to your account rather than anonymous, so we can tell whether a problem hit one person or everyone — see PostHog below.
• To respond to support requests.

We do not sell your personal data, and we do not use it for third-party advertising.

Who we share it with

We use a small number of service providers ("subprocessors") to run MealWisp, each bound to only use your data to provide their service to us:

• Google — OAuth sign-in; push notification delivery (via Firebase Cloud Messaging); underlying AI models used for recipe extraction and the meal assistant.
• Cloudflare — storage for recipe and dish-idea pictures, and for videos while they are being processed.
• RevenueCat — subscription/entitlement management (see above).
• Apple — Sign in with Apple, if you use it; push notification delivery to iOS devices (APNs), if you enable push.
• Apple / Google — app store billing, for in-app purchases.
• Instacart (only when you use Shop) — your ingredient list, to build a cart.
• PostHog — product analytics and session replay. We record which features you use and when (for example: you converted a reel, you hit a plan limit, you saw the paywall), tied to your account ID. We also record replays of your app sessions — screenshots of the screens you moved through, and where you tapped — with all text and images masked before they leave your phone, so a replay shows the shape of a screen rather than what it said. We never send your recipe content, chat messages, or the text of anything you write.
• DeepInfra — the AI that answers in chat, writes recipes and meal plans, and turns the speech in a shared video into text.
• OpenAI — reads the video frames and photos you share, answers food-safety and allergy questions, and stands in when DeepInfra is unavailable.
• Replicate — draws the pictures for recipes the AI writes. It receives the dish name and description, nothing else about you.
• Cloud infrastructure and database providers — we use third-party infrastructure providers to host the servers, database and cache that run MealWisp. Your data is stored on their systems on our behalf, under contract, and they may not use it for anything else.

How MealWisp uses AI

MealWisp is built on AI models, and the EU AI Act asks us to be plain about where and how.

Where a model is involved

• Recipe extraction. When you share a reel, link or photo, a model reads the audio, the video frames or the picture and writes out the ingredients and steps.
• The meal assistant. The AI Chat tab is a conversation with an AI model, not with a person. It asks about your goals, proposes meals and can suggest changes to a recipe.
• Recipe suggestions and generated images, where those features are available to you.

Everything else in the app — your library, collections, ratings, the shopping list — is ordinary software with no model involved.

What is labelled

Content a model wrote carries a visible label in the app: AI-generated where a model invented the recipe — including one written for a dish a video named but didn't show how to make — and AI-assisted where it read a source you chose and wrote out the structure. Recipes saved before we started recording this are left unlabelled rather than guessed at.

You decide, always

The assistant proposes; nothing changes until you tap to accept it. No recipe is modified, saved or deleted on a model's say-so, and nothing about you is decided automatically in a way that has legal or similarly significant effects.

Your content is not used to train AI models

Your recipes, photos, voice clips and chat messages are sent to our AI provider to produce your answer, and are not used to train or improve their models. We do not train models of our own.

Where it goes

AI processing runs on the providers listed above — DeepInfra, OpenAI and Replicate — on servers in the United States. Speaking into the app never leaves your phone: dictation is transcribed by your own device, and we never receive the audio. The soundtrack of a video you share is transcribed by DeepInfra and discarded — no recording is kept.

AI gets things wrong

Models misread labels, mishear speech and invent plausible numbers. Cooking times, quantities and anything touching an allergy or a health condition are worth checking against the original before you rely on them.

Where your data is processed

Our servers and database are in Germany. Some of our providers process data outside the European Economic Area, principally in the United States — this includes AI processing, which runs in the United States.

Where data leaves the EEA, we rely on the safeguards those providers offer for international transfers: the European Commission's standard contractual clauses, and — for providers certified under it — the EU-US Data Privacy Framework. You can ask us for details of the safeguards that apply to a particular provider.

Your rights

• Delete your account. In-app, under Settings → Delete Account. Your account enters a 30-day grace period (signing back in cancels the deletion); after that, it's permanently and irreversibly deleted, including your recipes, collections, and preferences.
• Access or export your data. Email us at privacy@mealwisp.com and we'll send you a copy of your data. We may need to confirm you control the account's email address before we do.
• Correct your data. Most fields are editable in-app under your profile; for anything else, email us.

The three above are the ones you can act on directly. Depending on where you live, the law may give you more.

If the GDPR applies to you (broadly, if you're in the EU, EEA or UK), you may also have the right to ask us to restrict how we use your data, to object to a particular use, to receive your data in a portable machine-readable form, and to withdraw consent where our use of your data rests on consent — each subject to the conditions and exceptions in the law. Email privacy@mealwisp.com for any of these.

You can also complain to a regulator. If you think we've mishandled your personal data, you can lodge a complaint with the data protection authority in the country where you live, where you work, or where you think the problem happened. You're welcome to raise it with us first, but you don't have to.

If you're in California, the rights above map broadly to your CCPA rights.

We aim to respond to any verified request within 30 days.

Data retention

We keep your data while your account is active, plus the 30-day deletion grace period above. Dish ideas are the one exception that goes sooner: we keep only your most recent 20, and each older one — with its picture — is deleted automatically as a new one arrives, unless you saved it to your library. Aggregated, de-identified usage data (that can't be traced back to you) may be kept longer to understand product trends.

Children

MealWisp is not directed at children under 13 (or the minimum age in your country), and we don't knowingly collect their data.

Changes to this policy

If we materially change what we collect or how we use it, we'll post the update here and, for significant changes, notify you in-app.

Contact

MealWisp is operated by Salman Ahmed, who is the data controller for the personal data described in this policy.

privacy@mealwisp.com