Privacy Policy

1. Who we are

Lazy Meal Planner is a meal-planning app for Android, operated by MediGuard Limited, trading as Lazy Meal Planner. MediGuard Limited is a company registered in England and Wales (company number 14120982), with its registered office at 71–75 Shelton Street, Covent Garden, London WC2H 9JQ. We are the data controller for the information described in this policy, registered with the Information Commissioner’s Office under registration number ZB587486. That means we decide what is collected and why, and we are responsible for looking after it.

You can reach us at contact@lazymealplanner.co.uk.

This policy covers the Lazy Meal Planner app and this website.

2. The short version

We collect what we need to plan your meals, and not much else.

• Your name, email address and password are needed to have an account.
• Details of the people you cook for, and what they will not eat, are needed to plan meals they will actually eat.
• If you choose to set calorie and macro targets, we collect the body measurements needed to calculate them.
• Some of this is sent to our AI provider, currently OpenAI, a company based in the United States, so that it can build your plan. Before anything is sent, we replace your name and the names of the people in your household with labels such as “Member A”, so the AI never sees anyone’s name. Section 6 explains exactly what is sent.
• We never see your card details. All payment goes through Google Play.
• The app contains no advertising and no analytics tracking. It uses four Android permissions. Three are granted when you install the app, without asking you: internet access, checking whether your phone has a network connection, and Google Play Billing for subscriptions. The fourth, the microphone, is only for speaking to the chat, and the app asks you for it the first time you tap the microphone button.
• The app does not ask for access to your camera, photos, contacts or location. If you add a photo to one of your own recipes, you pick or take it through Android’s own photo picker or camera, and only that one photo reaches us.
• This website sets no advertising or analytics cookies.

The rest of this policy is the detail.

3. What we collect, and why

Your account

The people you cook for

If you add household members, we store each person’s name, their age group and the ingredients they will not eat. Section 5 covers this in more detail, because those people are not our users and have not agreed to anything.

Your food preferences

Cuisines you like, how long you are willing to cook for, how much variety you want, the number of servings you usually make, ingredients you like, ingredients you dislike, and any dietary preferences you set.

We also record how you behave in the app: which meals you rate, which you swap out, which you mark as a permanent no, and when you last cooked something. This is how the plans get better without you filling in a form.

Things the app learns about you

The app builds short written notes about your household from your conversations with it and from your behaviour, for example a note about a recurring preference. These are stored as free text and are sent to the AI when it plans your week. Notes suggested by the AI are shown to you for approval before they are saved.

Your plans and shopping

Your weekly plans, the meals in them, the written summaries the AI produces, your shopping lists and which items you have ticked off, your cookbooks, and your favourites.

Recipes you import

If you import a recipe from a web address, we store the recipe and the address you imported it from. Imported recipes are private to your account and are never shown to other users.

If you import by pasting recipe text, that text is sent to our AI provider so it can be turned into a recipe (section 6). Any ingredient line we cannot match to our own ingredient list is kept as you wrote it, and can appear on your shopping list.

Photos of your recipes

You can add a photo to a recipe that belongs to you, such as one you imported or one the AI created for you. You choose the photo through Android’s own photo picker, or take it with your phone’s camera app, so the app never has access to the rest of your photos.

• We keep two resized copies of the photo, not the original. Before they are stored, everything hidden inside the image file is removed, including the location where it was taken and details of the camera.
• Your photos are stored privately. Only you can see them. They are never shown to other users, and there is no public web address for them.
• When you remove a photo, replace it, delete the recipe or delete your account, the photo itself is deleted. We keep a small record that a photo existed (which recipe, when, and why it was removed), with no image in it.
• Nobody at Lazy Meal Planner looks at your photos. If we ever have to remove one, our tools let us do it without seeing it.

For a recipe the AI wrote, the app may create a photo for you. Section 6 explains what is sent to make it.

Speaking to the chat

If you subscribe, you can hold the microphone button and speak a chat message instead of typing it. The app does not record, store or send your voice. It asks your phone’s own speech service to turn what you say into text, and the words appear in the chat box for you to check. Only that text is sent, when you tap send, exactly as if you had typed it.

Your phone’s speech service belongs to your phone, not to us. On most Android phones it is Google’s. Depending on your phone and its settings, it may process your voice on the phone or send it to Google to be recognised, under Google’s own terms. We never receive the recording.

If you speak a message, the app can read the reply aloud using your phone’s own text-to-speech. You can turn this off.

Records we keep to run the service

• Login sessions, stored as one-way encrypted values rather than usable tokens.
• Password-reset requests, stored as one-way encrypted values, valid for thirty minutes and usable once.
• A record of each time you use an AI feature, with how much processing it used and what it cost us, so we can apply fair-use limits. It holds no text from your requests or the replies.
• Records of errors on our server, so we can fix them: the time, the part of the service involved, technical details of the fault, and your account identifier if you were signed in. Never your name, email address, IP address or anything you typed. They stay on our own servers, are not shared with anyone, and are deleted after 90 days. When a new kind of error appears we email ourselves a summary through Resend; it contains no account identifier or personal details.
• Server logs recording the request path, the response status and your account identifier. We do not log the contents of your requests, and web addresses are stripped of anything that could carry a token.
• A short-lived cache of recent responses, kept for twenty-four hours, so that an action performed while your phone was offline is not applied twice when it reconnects.

On your own phone

The app keeps a copy of your profile, household, health details if you set targets, plans, ratings, cookbooks, shopping list and your recipe photos on your device, so it works quickly and offline. Your login tokens, with your name and email address, are held separately in your phone’s secure storage. When you log out or delete your account, the app deletes this local copy. Uninstalling the app removes it too.

None of this is copied to Google’s cloud backup or moved to a new phone. Everything comes back from our servers when you log in again.

4. Health information

This section applies only if you choose to set calorie and macro targets. If you do not, none of it is collected and every one of these fields stays empty.

If you do, we collect your biological sex, your year of birth, your height, your weight, your activity level and your goal. We use them to calculate a daily calorie target and a macronutrient split, using a standard published formula, with a floor based on NHS guidance.

Two things are worth being precise about.

We store one current weight, not a history. When you update your weight, the previous value is replaced rather than kept.

Your body measurements are never sent to the AI. Only the calculated result goes — the daily calorie and macro totals, the target for each meal slot and, if you use chat, the nutrition totals of the day you are viewing. The AI is told “this household is aiming for a certain number of calories a day”. It is never told your weight, your height, your age or your sex.

Lazy Meal Planner is a meal-planning tool. It does not give medical, dietary or nutritional advice.

5. Information about other people in your household

When you add someone to your household, you are giving us information about a person who is not our user. They have not agreed to this policy and they cannot log in to see, correct or delete their own record. Some of them may be children.

We ask you to add only what is needed to plan meals: a name, an age group, and the foods they will not eat. We only ever record the food, never the reason. We do not ask why someone avoids a food, there is nowhere to write it, and the app will not keep a learned note that says a person in your household has an allergy or intolerance. For us, a household member’s list is a food preference, like a dislike: the planner keeps those foods out of every meal, but it is not an allergy service, and you should always check packaging yourself.

Please let the people you add know that you have done so, and point them to this policy.

Household members’ names are never sent to our AI provider. Before a request leaves our server, each name is replaced with a label such as “Member A (child)”, and the label is turned back into the name in the reply you see. The AI receives each person’s age group and the foods they won’t eat, never their name. We replace the names you have entered wherever they appear, including in what you type in chat. A nickname we don’t know about, such as one you type in chat but never entered as a household member, is sent as you typed it.

You are responsible for making sure you are entitled to share information about the people you add. If a household member wants their record removed, you can remove them in the app, or contact us at contact@lazymealplanner.co.uk and we will do it.

We do not knowingly allow anyone under the age of 18 to create an account.

6. Who we share your information with

We do not sell your information. We do not share it for advertising. The list below is complete.

Our AI provider — the artificial intelligence that plans your meals

This is the most significant disclosure in this policy, so it is set out in full.

When the app generates a plan, suggests a swap, answers a question in chat, searches in plain English, imports a recipe you have pasted in, creates a recipe, or creates a photo for a recipe the AI wrote, it sends a request to our AI provider. That provider is currently OpenAI, a company based in the United States. If we change provider we will update this policy.

What is sent:

• The age group of every household member, with a label such as “Member A” in place of their name.
• Your dietary requirements and the ingredients your household cannot or will not eat.
• The written notes the app has learned about your household.
• Your cuisine preferences, cooking-time preference and how much variety you want.
• The meals you have eaten in the past four weeks.
• If you use calorie targets, the calculated daily calorie and macro figures and the target for each meal slot.
• If you use calorie targets and chat: your daily calorie and macro targets, the nutrition totals of the day you are viewing, and the names of the meals planned for that day. This is sent with every chat message, not only when you ask it to balance a day. The changes it suggests are worked out by the app and are never sent to the AI. The balance-a-day button sends nothing to the AI.
• Anything you type into the chat or into a free-text instruction. Chat has no memory on their side, so the whole conversation so far is re-sent with every message you send.
• Recipe text you paste in to import.
• What you type into a search, when the app uses the AI to understand it.
• When you ask the AI to create a recipe, your request, to check whether it names a specific dish you might already have. Only a yes/no likelihood comes back.
• The text of a learned note when it is saved or suggested, to check whether it mentions a food allergy, an intolerance or a health detail, so we can apply our consent and safety rules. Only a yes/no likelihood comes back.
• The name, description and ingredients of a recipe you import from a web address or paste in, to label its cuisine and to check it is not wrongly marked vegetarian or vegan.

What is never sent:

• Your name, or the name of anyone in your household. They are replaced with labels before anything is sent, as described above.
• Your email address.
• Your password, in any form.
• Your weight, height, age or biological sex.
• Any billing or payment information.
• Any device identifier.
• Your account identifier.

Your dietary requirements and exclusion lists can reveal things about you that are not written down anywhere as such. A list of ingredients you never eat can indicate an allergy, a medical condition, or a religious or philosophical belief. We want to be straightforward that this is the case, rather than rely on the fact that no field is labelled “allergy” or “religion”.

Photos for recipes the AI wrote. To create one, we first send OpenAI the recipe’s name to check it is suitable, then send a short instruction made only from the recipe’s name, its cuisine, and whether it is vegetarian or vegan. No conversation, ingredients, name, email or account identifier is sent. OpenAI receives a scrambled code in place of your account identifier, used only to help it detect misuse. Any name of yours or your household’s in the recipe name is replaced with a label first. A recipe name can still contain other personal words if you asked for them, so treat it as something you have shared.

OpenAI does not use what we send it to train its models. It may keep requests for up to 30 days to detect misuse, unless the law requires longer.

Everyone else

We may also disclose information if we are legally required to, for example in response to a valid court order.

7. Where your information goes

The app’s backend and our database run on a virtual server rented from Hostinger, which also hosts this website. We will host that server in the United Kingdom.

Some of the companies above are outside the United Kingdom. Our AI provider, currently OpenAI, is based in the United States, as are RevenueCat and Resend. Cloudflare, which also stores our backups and your photos, and Google operate globally.

Every one of these companies handles your information under a data processing agreement with us. When information leaves the UK, it is protected in one of two standard ways. Resend and Cloudflare are certified under the UK extension to the EU–US Data Privacy Framework, which the UK government recognises as giving adequate protection. For OpenAI and RevenueCat, the agreement includes the European Commission’s standard contractual clauses with the UK’s International Data Transfer Addendum. Either way, the company must look after your information to UK data protection standards wherever it is processed.

8. Our lawful bases for using your information

Under UK GDPR we must have a lawful basis for everything we do with your information.

9. How long we keep your information

We keep your information only for as long as we need it.

• While you have an account, we keep your account details, preferences, plans, recipes and photos until you delete your account. When you delete it, we delete everything in it.
• People you remove from your household are permanently deleted, with the foods they won’t eat, 30 days after you remove them.
• Learned notes you delete, and suggestions you decline, are permanently deleted 30 days later. A suggestion you declined may then be offered again.
• Login sessions expire after thirty days, and our record of them is deleted 30 days after they expire or you log out.
• Password-reset links expire after thirty minutes and can be used once.
• The offline-safety response cache is cleared after twenty-four hours.
• Records of errors on our server are deleted after 90 days.
• Records of your use of AI features, which we use to apply fair-use limits and manage costs, are deleted after 13 months.
• Subscription notifications we can’t match to an account are deleted after 12 months.
• Records of actions our staff take on accounts are kept for 2 years, for accountability. They identify your account only by an internal reference number, never by your name or email address.

We back up our database every night. Each backup is kept on our own server for 14 days and copied to Cloudflare R2 storage. No backup is kept for more than 30 days.

If you turn on calorie and macro targets, we keep a dated record that you gave consent, and that you withdrew it if you do. That record holds no health details, and we keep it until you delete your account.

Inactive accounts. If you don’t sign in to or use the app for two years, we email you to say we are going to delete your account. If you still haven’t signed in 30 days after that email, we delete your account and everything in it, in the same way as if you had deleted it yourself. We never delete an account while it has an active subscription, including Google Play’s grace period, or premium membership we have given you. Signing in at any time stops the deletion.

10. What happens when you delete your account

You can delete your account from the app’s settings. You will be asked for your password to confirm. Our account deletion page sets out the steps, and how to ask us by email if you no longer have the app.

When you do, we permanently delete your profile, your preferences, your household members, your plans, your ratings, your learned notes, your cookbooks, your imported recipes, your photos, your meal slots, your login sessions and your subscription records. This is a real deletion, not a flag. Photos are removed from storage within minutes of the rest.

A few things are worth knowing.

Removing something inside the app is not always immediate deletion. If you remove a household member or delete a learned note, it is hidden straight away and permanently deleted 30 days later. If you archive a cookbook, it is kept, hidden, so that plans you made in the past still make sense. All of it is genuinely deleted when you delete your account.

Deleted information stays in our backups for up to 30 days. Each nightly backup is a copy of the whole database, so information you delete remains in the backups made before you deleted it until they roll off, which takes up to 30 days.

We ask RevenueCat to delete its record too. When you delete your account, we ask RevenueCat to stop your subscription renewing and to delete the record it holds about you. If that request fails, we follow it up by hand. Google Play keeps its own record of your purchases under Google’s terms.

If we delete an account on your behalf, a record of that action is kept. If you contact us and we remove your account manually rather than you doing it in the app, our internal audit log keeps a record of the action so that we can show who did what and when. It identifies your account only by an internal reference number, not your name or email address, and it is deleted after 2 years. Deleting your own account from within the app does not create such a record.

We may also hold records of subscription events received from Google Play that we were unable to match to any account. These contain no name or email address, and are deleted after 12 months. Records of errors that happened while you were signed in may carry your account identifier for up to 90 days after your account is deleted, and are then deleted.

To ask us to delete something, write to contact@lazymealplanner.co.uk.

11. Your rights

Under UK data protection law you have the right to:

• See what we hold about you. The app has a built-in export that produces a file containing your profile, preferences, household, targets, learned notes, ratings, plans, shopping lists, cookbooks, imported recipes and your photos (as download links that work for 24 hours). It does not include our records of your AI use or your subscription events. Ask us and we will provide those, and anything else we hold.
• Correct anything that is wrong. Most of it you can edit directly in the app.
• Have your information deleted. See section 10.
• Take your information elsewhere. The export file is machine-readable JSON.
• Object to how we use it, where we rely on legitimate interests.
• Restrict how we use it while a query is being resolved.
• Withdraw your consent to us using your health details at any time. In the app, go to More, then Goals & Health, and choose Withdraw health-data consent. This erases your weight, height, year of birth, biological sex, activity level, goal and how quickly you want to reach it, macro preset and split, and targets, and turns calorie and macro targets off. Plans you have already made keep their portion sizes. The erased details stay in our backups until those roll off, which takes up to 30 days, as section 10 explains for deleting your account. It does not affect anything done before you withdrew it. We keep a dated record that you gave consent, and that you withdrew it. That record holds no health details, and we keep it until you delete your account.
• Withdraw your consent to us using allergy, intolerance and medical food information. In the app, go to More, then Food safety, and choose Withdraw and delete. This deletes every food you avoid, removes gluten-free and dairy-free from your dietary requirements, and deletes any learned note that mentions an allergy or intolerance. The foods the people you cook for won’t eat are not covered by this consent, so they stay until you change them. As with health details, these stay in our backups until they roll off, and we keep a dated record, with no details, that you gave and withdrew consent.

To exercise any of these, write to contact@lazymealplanner.co.uk. We will respond within one month.

If you are unhappy with how we have handled your information, you can complain to the Information Commissioner’s Office, the UK’s data protection regulator, at ico.org.uk or on 0303 123 1113. We would prefer you came to us first so we can put it right.

12. How we protect your information

Passwords are stored only as one-way encrypted hashes, never as text. Login and password-reset tokens are stored the same way. Traffic between the app and our servers is encrypted. Text you type is fenced before it reaches the AI, so that the AI treats it as information rather than as instructions — this is a safety measure against misuse and not a form of anonymisation, and your information is still sent in full.

No system is perfectly secure. If something goes wrong that puts your information at risk, we will tell you and the Information Commissioner’s Office where the law requires it.

13. This website

This website sets no advertising cookies and no analytics cookies. We do not track you across other sites. Nothing you do here is profiled.

The fonts used on this site are served from our own server, so loading this page sends nothing to Google.

Our web host, Hostinger, keeps standard server logs including IP addresses, as any web server does.

14. Changes to this policy

If we change this policy we will update the date at the top. If a change materially affects how we use your information, we will tell you in the app before it takes effect.

15. Contact us

MediGuard Limited, trading as Lazy Meal Planner
Registered in England and Wales, company number 14120982
ICO registration number ZB587486

contact@lazymealplanner.co.uk

71–75 Shelton Street, Covent Garden, London WC2H 9JQ