Privacy

Last updated 19 October 2026

What stays on your device

Everything you log in the app — food, exercise, weight, height, sleep, how you feel and the rest — is stored in your browser on your own device. Unless you turn on sync (below), it is not sent to our server and we cannot see it. Clearing the browser’s data for this site deletes it, so use Export in the You tab if you want a copy. The app also keeps, on your device, each change you made to your last three days, so that a day can be put back the way it was (Bring today back, in the You tab); that stays on the device too. The one exception is Memory, the study topics described further down: those are kept on our server as well.

The move to eatnmove.in

EatNmove moved from vishalrao.in to eatnmove.in in October 2026. A browser keeps what the app logged separately for each address, so the first time you open EatNmove after the move, what this browser logged at the old address is carried across. It is encrypted in your browser, with a key that never leaves it, before it is sent; our server holds only that encrypted copy, which it cannot read, until the new address collects it (at most 30 minutes), and then deletes it. Nothing is removed at the old address.

How you feel

If you answer the morning and night questions about how you feel, the words you tap are kept with that day, like the rest of what you log: on your device, and on our server only if you turn on sync (encrypted, if your sync has a passphrase). They are not shared, not sent to anyone, and not used for anything but showing them back to you. The city you may give, for finding help near you, is kept with your profile in the same way. The questions are not a test or a diagnosis.

If you tap Find near me (in Someone to talk to), the app asks your phone for its location (from its GPS), once, and sends it with the kind of help you chose to our server, which searches for the nearest places and sends them back. Neither the app nor our server keeps your location: it is used for that one search and not stored or logged. The search itself is made with Google Places, or with OpenStreetMap’s public Overpass service, which receive the location and what was searched for under their own policies. If you search by a city instead, its centre is found with OpenStreetMap’s Nominatim service, and the city’s name and centre are kept on our server for a month, without who searched for it, so that each city is looked up only once. We count how many searches an account makes in a day, to keep within the services’ limits, and keep nothing else. The Google Maps searches by city or “near me” open in Google Maps itself, which uses your location only if you let it.

Sync across your devices (optional)

Sync is off unless you turn it on yourself, in the You tab of the app. With sync on, your profiles and everything you log — body details such as weight, height and age, food, exercise, sleep, how you feel, supplements and your settings — are also stored on our server, under the Google account you signed in with, so that your other signed-in devices can show the same data. The server keeps what the app itself keeps: for each profile, its 90 most recent logged days. So that a day can be put back the way it was (Bring today back, in the app), the server also keeps each day’s earlier versions for three days, at most 100 of them a day, then deletes them; they are stored exactly as the day itself is (encrypted, if your sync has a passphrase), and deleted with it.

When you turn sync on, you choose whether to protect it with a passphrase.

With a passphrase. Everything is encrypted on your device before it is sent, with a key that only your devices hold. The passphrase never reaches us, and the key is kept on our server only in a form locked by that passphrase, so we cannot read what is stored: not the profile names, nor anything you logged. What we can still see is that your account uses sync, how many entries it holds, the dates of the days you logged, how large each entry is and when it was last changed. If you forget the passphrase, we cannot recover it or the copy on the server; your devices keep their own data. The encryption is done by the app, which comes from this site: it protects your data against anyone reading our database, and it relies on the app itself being the genuine one.
Without a passphrase. It is stored as it is, so the person who runs EatNmove can read it.
You choose which profiles are synced. A profile you keep out is not stored on the server; only a mark that it is kept out is (with the profile’s name, unless you use a passphrase).
Either way, it is used only to keep your devices up to date with each other. It is not sold, shared or used for advertising.
Turning sync off, in the app or on the Account page, deletes the copy on the server at once. Your devices keep what they have. Cloudflare’s routine database backups may hold deleted data for up to 30 days more.

Memory: the topics you study

Memory, on the Today tab, is the part of the app that reminds you to recall what you studied. If you use it, the topics you add are stored on our server as well as on your device, whether or not sync is on. That is what lets the server remind you while the app is closed, and what brings your topics to your other devices. For each topic we store its name, any questions and notes you wrote for it, the day you studied it, how each recall went and when the next one is due, under your account and the name of the profile; and for each profile, the time of day you chose for reminders. If you never add a topic, nothing is stored.

If your sync has a passphrase, topics are encrypted on your device with the same key before they are sent, and a made-up id stands in for the profile’s name. We cannot read them. What we can still see is how many topics there are, how large each is, when it was last changed and when its reminder is due. A notification can then say only how many topics are due, not which.
Otherwise they are stored as they are, so the person who runs EatNmove can read them, and a notification names the topic.
Notifications. If you turn on notifications for Memory, your browser gives us an address at its maker’s push service and two keys, which we store in order to send your reminders. A reminder is encrypted for your browser, so the push service that carries it cannot read it. Turning notifications off in the app, or signing out there, removes that address from our server.
Deleting a topic, or the profile it belongs to, deletes it from our server and from your other devices. Cloudflare’s routine database backups may hold deleted data for up to 30 days more.
It is used only to remind you and to keep your devices in step with each other. It is not sold, shared or used for advertising.

Your own food and exercise figures

If you change a figure in Food and exercise figures (the ⓘ at the top of the app) — a food’s calories, protein or vitamins, an exercise’s MET or calories — the figures you changed are stored on our server under your account, for that profile, whether or not sync is on, with the profile’s name. That is what brings them to your other devices; changing them needs a connection. Only the changed figures are stored, not anything you logged. Restoring the app’s own figures deletes them from our server. They are not encrypted, so the person who runs EatNmove can read them; they are not sold, shared or used for advertising.

Auto ask

Auto ask (a switch on the Today tab, on unless you turn it off) asks for a meal whose time is over and nothing is logged for it, and at the end of dinner what you did that day. To ask you with the app closed, the app sends our server the times to ask at for the next few days — which meal, and when — under the profile’s name. Nothing of what you ate or did is sent: a meal you have logged simply drops out of the list. The notifications use the same browser address as Memory’s, and only reach you if you allowed them. Turning Auto ask off removes the times still to come; ones already used are deleted after two days.

The same goes for Nutrients low today (Alerts tab, on unless you turn it off): to tell you with the app closed, the app sends our server the message it will show that evening — the names of the vitamins, minerals or protein low so far that day, and foods that carry them — and the time to send it. Nothing else of your log is sent. It is replaced whenever it changes, and deleted two days later.

Reviews

If you write a review, we store its stars, its text, the name you chose to show with it and when it was written and last changed, under your account. Its stars, text, name and the date it was written are shown publicly on this site, marked “Verified buyer”, “Free trial” or “Free access” (and “edited” if it was changed later); your email address is never shown. To know who may review, we also keep a note that your subscription has been paid for, and when we first saw that. Deleting your review (Account, Your review) removes it at once.

What we store

From Google sign-in: your Google account ID, email address and name. We do not get your password or access to anything else in your Google account.
About your subscription: the Razorpay subscription ID, its status and dates. We do not receive or store card numbers, UPI IDs or bank details; those are held by Razorpay.
A sign-in cookie in your browser so you stay signed in.
Only if you turned on sync: the data described under sync above.
Only if you use Memory: the study topics described under Memory above and, if you turned its notifications on, your browser’s push address and keys.
Only if you write one: your review, as described under Reviews above.
Only if you change any: your own food and exercise figures, as described above.

Who else is involved

Razorpay handles payment and holds your payment details under its own privacy policy.
Google handles sign-in. The app also loads Google’s translate widget; if you use it, the page text is sent to Google for translation. If you search for help near you, the search is made with Google Places or opens in Google Maps.
OpenStreetMap, through its public Overpass service, may be searched for help near you instead of Google, with the location of that one search; and its Nominatim service finds a city you search by.
Cloudflare hosts the app, holds the database behind it and keeps routine request logs (such as IP address and time).
Your browser’s push service (run by Google, Mozilla, Apple or Microsoft, depending on the browser) delivers Memory’s notifications, if you turned them on. It cannot read them; it can see that EatNmove sent your browser a message, and when.

What it is used for

Only to know which account has a live subscription, to contact you about it, if you turned on sync to keep your devices up to date, and if you use Memory to remind you of the topics you added. Nothing is sold or shared for advertising.

Deleting your details

To delete synced data, turn sync off in the app or on the Account page. To delete Memory’s topics, delete them in the app (Today tab, Memory, All topics). To delete everything, write to vishal.rao.physics@gmail.com from the email address you signed in with: your account record will be deleted, and with it any synced data, study topics, food and exercise figures, notification addresses and review. Cancel your subscription first, or ask us to.

Back to EatNmove