CosmoYum
You can change an item’s name and its weight. Change the weight and every figure recalculates on the spot; change the name and fresh nutrition is looked up for the new one. You can also delete an item, add another one to the same meal, and file the meal under a different time of day.
You cannot type a calorie or macro figure in directly. That is deliberate: the numbers belong to the item and its weight, so a hand-typed calorie count would sit detached from both and be overwritten by the next weight change. When something you eat often comes out wrong at the right weight, correcting the name is usually what fixes it.
A meal is filed under whichever day is open in the diary, not under today — so to log something you forgot on Sunday, move to Sunday first and add it there.
Because they are estimates, and every app estimates differently. A photo does not show how much oil went into the pan or what a portion weighs. Treat the figures as a good starting point and correct what looks off — the corrected record is what counts towards your day.
Open the item and change the name. Your correction is kept alongside the original estimate, which is how we find out where the model is systematically wrong.
Product data comes from Open Food Facts, a public database filled in by volunteers, so plenty of local products simply aren’t there. When that happens the app offers to read the nutrition label from a photo — aim at the panel with the numbers, not the front of the package. If the label carries no figures either, the app can look the product up by name or estimate typical values for it.
If you ever photographed that package’s label, the app is answering from your copy of it rather than from the database, and deliberately so: you stood in front of the actual package, a crowd-sourced entry for the same code is no more authoritative than that, and yours is the only version that also works offline.
The catch is that re-scanning cannot fix a label that was read wrong, because photographing one is only offered when a lookup fails — and yours now succeeds. Delete the product in Settings → “Photographed labels”, and that barcode goes back to the public database on the next scan.
If the figures came from the database instead, they were typed in by volunteers and can simply be wrong. Correct the name or the weight in your own entry; nothing you change is sent back to Open Food Facts.
Both lists of them — the shortcut rows at the top of the add-meal sheet and the fuller “Recent” list behind Favorites — look back two weeks. A meal eaten longer ago than that stops appearing in either. The list earns its place by being short: a fortnight of eating is already more rows than anybody scrolls through to save a tap.
Repeats collapse into a single row, so a breakfast you eat every morning sits there once, in its most recent version, rather than fourteen times.
If you want a meal to stay within reach for good, save it to Favorites — the star on the result screen. Favorites never expire, they are searchable, they sort themselves so what you log most often comes first, and logging one costs no recognition. That is the real difference between the two lists: recent is a memory of the last two weeks, favorites are a decision.
One recognition each: a photo of a meal, a dictated description, a typed description, a photo of a nutrition label, and renaming an item — the new name has to be looked up.
Not counted at all: logging from a barcode, from favourites, from recent meals or from your own saved products, and changing an item’s weight, which is arithmetic done on the phone. Like all adding, these need Premium — they just cost no recognition.
The limit is 10 a day during the free trial and 30 with a paid subscription, and it refills at midnight. It exists because every analysis is a paid request to an AI model: the cap is what keeps that cost survivable for a project this size, and what stops one account from exhausting it for everyone.
The list is your own words rather than a fixed menu: write “hazelnut” or “buckwheat” and every dish is checked against it.
Add an allergy later and your existing entries are not re-flagged — the diary is a record of what happened, not a warning system for the past. A saved favorite or a recent meal, though, is checked against the new word the next time you log it, which is the moment it actually matters.
It is sent to be analysed and is not kept. The photo travels over an encrypted connection to our server, which passes it to Google’s Vertex AI; once the answer comes back it is stored neither on the server nor in our logs. The file itself stays on your phone — the app records only the path to it. The full account is in the privacy policy.
That follows from the answer above, and it is the one consequence worth stating plainly: the diary is in the cloud, the photographs are not. The app keeps each photo as an ordinary file on the phone and stores only the path to it, so on a new phone — or after reinstalling on the same one — every entry returns and the pictures do not.
Nothing else is lost: names, weights, calories, meals, goals and weight history are all there. An entry whose photo is missing simply looks like one that never had a photo. The same applies if you clear the files yourself.
Because a favorite is a snapshot, not a link. Saving one copies the numbers as they stood; logging one copies them again into a new entry. From then on the two are independent: improving the favorite improves every future log of it and leaves past meals exactly as they were eaten, and correcting a logged meal does not alter the favorite behind it.
This is intended rather than a limitation. A diary that quietly rewrote last month whenever you adjusted a recipe would stop being a record of what you ate.
No account is needed to use the app. Your diary belongs to an anonymous identifier created on first launch and kept in the phone’s Keychain — no name, no email address.
That identifier does not travel. To carry your diary to a new phone, sign in with Apple or Google (Settings → Account): that attaches the data you already have to something you can sign in as again. Sign in on the new phone with the same one and the diary is there.
From the Mifflin-St Jeor equation — the formula mainstream calorie apps use. It takes your sex, date of birth, height and weight to estimate what your body burns at rest, multiplies that by the activity level you picked, then adds or subtracts for the pace you set towards your target weight. A floor is built in: it will not recommend eating below 1500 kcal for men or 1200 for women, however aggressive the pace.
It is a starting estimate, not a prescription, and the number is yours to overrule: Settings → Daily calorie goal. “Reset to recommended” puts the calculated one back.
The diary does. Days, entries and edits are written on the phone first and sync when a connection returns, so you can log and browse offline. Logging from favourites and recent meals works offline too — those figures are already on the device.
Recognition does not. Naming a dish from a photo, from speech or from text is a request to a model, and that needs the network.
Adding food needs CosmoYum Premium — a monthly or yearly subscription through the App Store, with a 7-day free trial for new subscribers. The current price is on the Premium screen in the app, in your own currency. Without Premium the diary stays yours: you can open it, look through the statistics, edit and delete entries — only adding new food is closed. There is no advertising.
To cancel: iPhone Settings → your name → Subscriptions, or “Manage subscription” in the app. Premium stays until the end of the period already paid for, and refunds go through Apple. The full terms are in the Terms of Use.
You can do it in the app: Settings → Account → “Delete account and data”. Nothing to ask us for, and nothing to wait on.
Deleting the app itself is not deleting your data: the identifier that owns it lives in the phone’s Keychain and outlives the app, so the cloud data stays where it is. What exactly goes, what stays, and what to do if the app is already gone are on the “Delete account” page.
If you have Premium, deleting the account does not cancel it: the subscription belongs to your Apple ID, and Apple keeps charging until you cancel it in iPhone Settings → your name → Subscriptions.
Write to support@cosmoyum.app. The support page says what to include so the first reply is a useful one.