Privacy

Your email address or phone number — whichever you sign in with — your display name, your language, and the times you signed in.

What you tell us when you set up a plan: your birth year, and optionally your sex, height and weight; your goal, your fitness level, where you train and what equipment you have; any injuries, medical conditions (such as diabetes, hypertension, a heart condition, asthma, arthritis, osteoporosis, pregnancy or a thyroid disorder) and dietary needs; and anything you type into the notes field.

What you log day to day: water, sleep, workouts you complete or skip, and meals — each with the date it was logged for.

If you join a family: which household you belong to, your role in it, and which categories of your data you have chosen to share with the family admin.

A record of the consent you gave — what you agreed to, when, and which version of this page was in force at the time.

If you turn on smarter reading on the meals screen: whether you turned it on, and when. The words you type are not kept. What is kept is a fingerprint of them (a one-way hash, which cannot be turned back into the words) next to the list of ingredients read from them, and the lines written about suggested dishes; both are shared by everyone who asks the same thing and are not linked to you. A photo you send is never written to our database: it waits in our job queue only until it is picked up to be read — normally within seconds — and is removed from the queue at that moment, and one that is not picked up within five minutes is deleted unread. We also keep a record of each request — what kind it was, when it happened, how long it took, what it cost and whether it worked — with no copy of the text or the photo.

Your health details are used to build a workout plan that leaves out what is not right for you, and to suggest meals that fit what you eat. What you log is used to show you your own progress, and to show a family admin the categories you chose to share. That is the whole list.

Your workout plan and your meal suggestions are made by fixed rules written into this app, not by a machine-learning model, and nothing about your health, your account or your family is sent to an outside service to be analysed.

There is one optional exception, and it is off unless you turn it on. On the meals screen you can choose smarter reading. Then what you type into the kitchen box — "thoda atta, 2 aloo" — or a photo you take of your fridge, your shelves or a shopping receipt, is sent to Google, whose Gemini AI model turns it into a list of ingredients for you to check. When it is on, the dishes we suggest are also sent, with which of their ingredients you have, so it can write one line about why each one fits; it is never told your diet, your health or anything else from your profile, and it does not choose the dishes. Only those words and that photo are sent: not your name, your account, your profile or anything about your family. Child accounts, and anyone whose birth year means they may be under 18, cannot turn it on. You can turn it off at any time, and nothing is sent after that.

You can see everything about yourself. A family admin can see only the categories you have chosen to share, and turning a category off hides it from them — being an admin does not override your choice. Nobody else has access.

Nothing here is sold, rented or shared for advertising, and this app runs no analytics, no advertising tags and no third-party tracking scripts of any kind.

Three companies run the infrastructure and therefore store this data on our behalf: Supabase (database and sign-in), Render (the application server) and Vercel (the website). Sign-in emails are delivered by Brevo. If you turn on smarter reading, Google also receives what you type into the kitchen box or photograph, and the dishes it is asked to describe, through its paid Gemini API, whose terms do not allow it to use that to improve its products. None of them may use the data for their own purposes.

The database is hosted in Mumbai, India. The application server that reads it runs in Singapore, so your data does leave India in the course of being served back to you.

Until you delete it. There is no automatic expiry: what you logged two years ago is still there unless you remove your account. The one exception is what smarter reading keeps — the ingredient lists read from typed text and the lines written about dishes — which is not linked to anyone and is deleted after 30 days. Photos are not kept at all.

See it — everything stored about you is shown in the app itself.

Correct it — your details can be edited at any time from the plan screen.

Delete it — there is a Delete my account button below Sign out. It removes your profile, everything you logged, your workout plan, the record of your smarter-reading requests and your family membership, and it is not a request queued for somebody to action: those records are gone when it finishes. The email address or phone number you sign in with is held separately by the sign-in provider and is not removed by that button.

Withdraw consent — deleting your account withdraws it, because there is nothing left to process. Smarter reading can be turned off on its own, from the meals screen, without deleting anything.

A family can include child accounts, and a family admin can see the categories that child has shared. If you are setting up an account for someone under 18, you are responsible for their consent as their parent or guardian. Nothing about a child is used for advertising or behavioural profiling, because nothing about anyone is. Child accounts, and anyone whose birth year means they may be under 18, cannot turn on smarter reading, so nothing they type or photograph is ever sent to Google.

You can use this app as a guest, without giving an email or phone number. A guest account is real and its data is stored the same way — but it can only be reached from the browser that created it. Add an email or phone number to keep it.

Everything travels over HTTPS. Your session lives in a cookie that JavaScript cannot read. Every request to the server is checked against a signed token, and the database refuses direct access from outside the application entirely.

Each version of this page carries a date, and the consent you gave records which version you agreed to. If this page changes in a way that affects what is done with your data, you will be asked to agree again rather than told after the fact.