Meze
Legal

Privacy Policy

Last updated: October 20, 2026

Meze has no accounts. Your recipes, meal plans and shopping lists stay on your phone. We do not sell your data, show ads, or track you across other apps or websites.

1. Who we are

Meze is made by Mohammad Mesum Hussain Qureshi, Pakistan. Contact: hussainmesum8@gmail.com.

2. What stays on your phone

Your recipes and their photos, meal plans, shopping lists, favourites and settings are stored only on your phone, and in your phone’s own backup if you use one. We cannot see them. A backup file, including your recipe photos, is created only when you export one, and you choose where it goes. Deleting the app deletes this data.

3. What leaves your phone

Importing a recipe from a link. Only after you allow AI recipe reading, Meze sends the link, and for a website the recipe text from the page, to its recipe reader, a server we run in Nuremberg, Germany. To write the recipe, the reader sends that text, or a post’s public caption, to OpenAI. If the caption has no recipe, the reader tries to import it from the video’s audio and on-screen text. For this it sends the audio and a few still pictures to OpenAI, and deletes them within minutes. The finished recipe is kept on the reader for up to 30 days, not linked to you, so the same link loads faster. You can turn AI recipe reading off in Settings; website recipes are then read on your phone only. Recipes from photos and cookbook pages are always read on your phone and are not uploaded.

Free imports. To count the 5 free imports each week, the app sends a random install code with each import. The reader keeps only a scrambled form of it, and deletes it after that week. The code is kept in your device’s keychain, so it stays the same if you delete and reinstall Meze.

Ingredient pictures and notes. The app asks the reader for these by the ingredient’s name only. When the reader has none yet, OpenAI writes the notes or draws the picture from that name.

Purchases. Apple or Google handle payment. We never see your card. RevenueCat confirms your subscription using the random install code and your purchase records.

Usage and crash reports. Only if you tap “Share” when Meze asks “Help improve Meze?” in its introduction, Google Firebase receives usage events (such as screens opened) and crash reports, tied to a random app identifier rather than to you, with your device model, app version and approximate region, which Google works out from the connection. Nothing is sent before you answer. They never include your recipes, links or anything you write. You can change your answer in Settings with “Share usage and crash reports”.

Server logs. The reader keeps a short log of requests, with only part of your network address, for 7 days to stop abuse.

4. Who receives it

We do not sell or share your data for advertising. Each of these companies protects your data to the same standard as this policy, or better. Some of them process data in other countries, including the United States, under their own data protection terms.

5. How long it is kept

6. Your choices and rights

Depending on where you live, you may have the right to access, correct or delete your data, to object to its use, and to complain to your local data protection authority. Because there are no accounts, we hold very little. To make a request, email hussainmesum8@gmail.com.

7. Children

Meze is not meant for children under 13, and we do not knowingly collect their data.

8. Changes and contact

If this policy changes, we will update the date at the top of this page. Questions: hussainmesum8@gmail.com.