Why is an account one person?
Because a food record is personal in the plainest sense: it holds what one body ate, against targets that one person chose, in one time zone. There is no family plan, no household view, and no supported second profile, shared diary or delegated-logging workflow. Two people in the same kitchen who both want a record keep two accounts.
That is a boundary rather than a missing feature. A shared diary would mean one person's figures sitting under another person's name, one person's targets applying to another person's day, and one person reading what the other ate; none of that is something a record should make easy. The export, the deletion and the account page are each one person's too.
What the two of you do share is the cooking, and that is where the work actually is. A pot of chilli cooked on Sunday is described once by each of you, with the share that landed on your own plate: "about a third of the tray" and "about half". The ingredients are the same sentence twice; only the share differs.
How do two people record the same pot?
Each in their own conversation, with their own assistant, saying what went in and what they took. The assistant is asked to work out the share and to record it as an estimate that states the assumption, so both records say how they were built rather than presenting a figure as weighed.
| The situation | What each person says | What each record holds |
|---|---|---|
| A pot cooked for two | The ingredients, then "about half" | One estimated item each, with the share stated |
| A tray for four, two of you eating | The ingredients, then "a third" and "a quarter" | Two different estimates from the same pot |
| One of you weighs their plate | "380 g of the chilli on my plate" | Both still estimates, one built on a weight instead of a fraction |
| Leftovers the next day | The same dish, said again with the new share | A second meal, dated to the day it was eaten |
| A dish only one of you eats | Only that person says it | Nothing in the other account |
Bottom line: describe the pot once each, and the difference between your two days is the share you took.
Weighing your own plate is the upgrade worth knowing about, and it only has to be one of you: "380 g of the chilli" is a weight rather than a fraction, and the split inside the dish is the only thing left to assume.
What does one evening look like in two accounts?
IZeat is the calorie tracker inside ChatGPT, Claude or any other assistant. Tell the assistant you already use what you ate instead of searching for foods and entering them one by one. A Sunday, one pot, two accounts.
- 19:40, first account — "Chilli: 500 g of beef mince at 15 percent, two tins of beans, a tin of tomatoes, two tablespoons of oil, cooked for the two of us. I had about half."
- 19:41 — The receipt names one estimated item with the half stated, and the day so far.
- 19:50, second account — "The same chilli, and I had a bit less, maybe 40 percent, with 150 g of rice."
- 19:51 — The receipt holds a different estimate from the same pot, plus the rice as a reference value.
- Monday 12:30, either account — "The rest of the chilli, about a quarter of what was left." Recorded for Monday, in that account only.
Two accounts, two different days, one pot. Neither record knows the other exists: the second person's rice is not in the first person's day, the targets are each their own, and the week each of them reads counts only their own recorded days. The ingredients were said twice because the sharing happens in the kitchen, not in the software.
IZeat has no household feature today, and none is announced. Two accounts means two subscriptions, two exports and two separate records, and nothing in IZeat compares them or shows one to the other. If what you wanted was a shared family diary, this is not the product that has it, and the page would rather say so than imply otherwise.
Frequently asked questions
Short answers to the questions people type, each one sourced above.
Can two people share one IZeat account?
No. An account is one person's food, read by them, with their own targets and their own time zone; there is no family plan, and no supported second profile, shared diary or delegated-logging workflow. Two adults who both want a record keep two accounts, and what they share is the cooking rather than the diary.
Does IZeat have a family plan?
No, and none is announced. Each account is billed on its own, exports on its own and is deleted on its own; nothing is visible across two accounts and nothing compares them. The prices are on the price card, and two people means two trials and then two subscriptions. If a shared household view is what you are looking for, this is not the product that has it.
Can I log my partner's meals for them?
There is no supported delegated-logging workflow, and nothing in the product is built for it: an account holds what one person ate under their own name, against their own targets. Anything you dictate from your account is recorded as your own food, so doing it for somebody else would simply put their meals in your diary and your targets on their eating. If they want a record, they open their own account and keep it themselves.
Is it worth weighing the dish rather than guessing a share?
It helps, and only one of you has to do it: a weighed plate takes one assumption out, the share, and leaves only the split inside the dish, though the row is still recorded as an estimate, because a mixed dish always is. A workable middle is weighing the dense things and calling the rest a share.
What about cooking for children?
An IZeat account belongs to one person of eighteen or over, so there is no place in it for a child's day and nothing in it is meant to hold one. What you cook for the household is yours to describe in your own account for your own portion; the rest of the pot is simply not in it. Anything about a younger person's eating belongs with a parent and a professional.
Can we compare our two records?
Not inside IZeat: nothing is shared, visible or comparable across two accounts by design. What each of you can do is export your own record as CSV or JSON, with one download for each format, and do whatever you like with the two files. That is a deliberate boundary: a record that made one person's eating visible to another is not what this product is for.