Privacy policy
Last updated: 28 October 2026
This policy explains what Macrowala, a service operated by Vishal Tayade trading as Macrowala, collects and why. We do not sell your personal data and we do not show advertising.
What we collect
- Device code. A random identifier stored in your browser when you first visit the website or open the app. It links your data to your device; there is no password. The support code shown in the app is derived from it and does not reveal it. A move code you create to open your account on another device works once and expires after 15 minutes; your device code is then stored on both devices.
- Profile and goals. The name or nickname you enter, the calorie and protein targets you choose, the kind of food you usually eat, how much oil, butter or ghee your cooking usually has, and whether you have joined the Board. Until you choose the kind of food you usually eat, we assume it from your device's time zone: Indian food in India, a mix of cuisines elsewhere.
- Food logs. Meals you record, with estimated nutrients, meal type and date, and your time zone so each day matches your local calendar. If you correct an estimate, check one before logging it, or change the oil, butter or ghee it assumed, we keep the original estimate with the meal, so we can see how accurate our estimates are. We also count which foods several people have logged, across everyone and without names, device codes or anything else about who logged them, to decide which foods to add checks and Quick add buttons for. If you typed or spoke the meal, we keep those words with it, so that logging the same words again gives the same numbers. An estimate you were asked to check but didn't log is deleted within two days.
- Meal plans. Your latest meal plan and the choices you made it with: food type (such as vegetarian, vegan or Jain), fasting days, cooking time and anything you typed, so your next plan starts from the same choices. Making a new plan replaces the old one. Food type and fasting days can say something about your beliefs: we use them only to build your plans. Unless you switch it off on the plan screen, a plan can also include the meals you log most often, with their foods and numbers from your food log.
- Photos, descriptions and links you submit. Food and menu photos, spoken or typed descriptions, and recipe links are processed to produce estimates. We do not keep your photos after the analysis; we keep the resulting estimates, and the words of a typed or spoken meal with the meal it produced. If you speak rather than type, your browser turns speech into text using its own speech service (run by your browser's maker, such as Google or Apple) before anything reaches us.
- Subscription details. The email you enter at checkout, and from our payment partner your email address, name, subscription ID and status, and renewal dates. If you don't complete a purchase, we delete that email after 30 days. We never receive your full card or bank details.
- The homepage sample. If you try the sample on our homepage, the meal you type is sent to our AI service provider to produce the estimate. We don't store it with your device code or anything else about you: the question and its answer stay in our server's memory for up to a day, so a repeated question gets the same answer, and are then discarded. To limit tries, we count them against your device code and IP address in our server's memory for a day. That you tried the sample is recorded as a usage event (below), without what you typed.
- Your currency. The website and the plans screen show a rough price in your currency, worked out in your browser from your device's time zone and language settings. Nothing extra is sent to us for it.
- Free meals. How many meals your device has logged without a subscription, so we know when the free ones are used, and (in our server's memory for a day) how many logging calls came from your device code and IP address, to limit abuse.
- Usage events. Which steps of the app you reach (for example trying the homepage sample, opening the app, logging a first meal, finishing set-up or starting checkout), any creator code or link tag you arrived with, and when. We use this to see which parts of the app and which partners work. We don't use advertising trackers.
- Reminders. If you turn on meal reminders, your browser gives us a notification address and the times you chose. We use it only to send those reminders; turn them off in the app or in your browser settings.
- Share images. Share cards are made on your device. We don't receive them unless you share them with us yourself. The suggested headline on a meal card is written by our AI service provider from the meal's name and description, and is kept with that meal until you delete it.
- Technical data. Server logs, including IP addresses, kept for security and troubleshooting.
How we use it
To run the service, calculate your daily totals, generate meal plans, manage your subscription, apply fair-use limits, prevent abuse, and answer support requests.
Who processes it for us
- A cloud hosting provider that runs our servers and stores the database.
- An AI service provider that analyses the photos, descriptions (including meals typed into the homepage sample), menus and recipe pages you submit and returns estimates, builds meal plans from your goal, targets, the choices you make and anything you type (and, unless you switch it off, the meals you log most often), and suggests headlines for share cards.
- Our payment partner, which acts as merchant of record for checkout, billing, tax and receipts, under its own privacy policy.
- Open Food Facts, a public product database, receives the barcode number when you scan one.
- Your browser's push service (run by your browser's maker, such as Apple, Google or Mozilla) delivers reminders if you turn them on.
These providers may process data outside your country. We share only what each needs to do its job.
Health-related information
Food logs and goals can reveal things about your health. Apart from you, only we and the providers above can access them, and we use them only to provide the service and to answer your requests. The one exception is the Board, which is off unless you join it: if you do, other subscribers see an anonymous name with how many days you logged that week and your average protein. You can leave it at any time.
How long we keep it
We keep your profile, logs, free-meal count and subscription records while your subscription is active and for up to 12 months after it ends (or, if you never subscribed, for up to 12 months after you last used the app), then delete them automatically, unless you ask us to delete them sooner or the law requires us to keep billing records longer. Usage events, which include the device code (for visitors too), are kept for about 13 months (400 days). Server logs are kept for up to 30 days and do not record the query part of web addresses.
Your choices and rights
You can delete individual log entries in the app at any time. To get a copy of your data or have it deleted, email hello@macrowala.com with the support code shown on your Profile screen (or at the bottom of the plans screen if you haven't subscribed). Depending on where you live, you may have further rights, including to complain to a data protection authority.
Children
The service is not intended for anyone under 18, and we do not knowingly collect their data.
Changes
If we change this policy in a meaningful way, we will update the date above and let subscribers know by email.
Contact
Macrowala is operated by Vishal Tayade, Mumbai, India. Email: hello@macrowala.com.
Terms · Privacy · Refunds & cancellation · hello@macrowala.com