Privacy
Last updated November 6, 2026
IZeat is operated by Soltea (Pty) Ltd, registered in South Africa under 2024/051691/07. Write to hello@izeat.app for anything on this page.
What we store
- Your email address, and your first and last name if you gave them to your assistant.
- Your meals, exactly as your assistant recorded them: the description, the calories, protein, carbohydrate and fat, and where each number came from — a label, your own words, or the assistant’s estimate.
- Your daily targets, with the date each one started.
- The assistants you have connected, when, the permissions you granted, and the technical tokens needed to keep each connection working.
- Your time zone, kept in a small cookie so a late dinner lands on the right day.
- The recipes proposed or opened while signed in, once per account, recipe and UTC day, so a creator can be told how often their recipe is shown. A successful request for a complete recipe through your assistant is recorded separately as a use for creator royalties. It does not prove you cooked it; recording a meal does not add another use. Signed out, a recipe page only adds one to that day’s total, with nothing that identifies you.
If you send us a recipe
Creators who send a recipe through the partner form give us their email address, their partner code, the recipe as a link or as text, and the photos or video they attach. We keep them to review the recipe, answer you and, if it is accepted, publish it credited to you. The files sit in a private storage space at Supabase in London; the email that tells us about a new recipe carries links to them that expire after 7 days. Write to hello@izeat.app to have a submission deleted.
Why
To create and secure your account, record the information you ask us to record, show your days and longer periods, keep assistant connections working, provide subscriptions and support, and diagnose failures. We do not use it for advertising or model training.
Where
Your account and nutrition data sit in a database run by Supabase in London (region eu-west-2). The website and MCP server run on Vercel, also in London. The service providers below receive only what they need to perform their part of the service.
Who handles it on our behalf
- Supabase — the database and the sign-in.
- Vercel — the hosting.
- Resend — the emails we send you: sign-in codes, password links; and the email that tells us about a recipe a partner sent.
- Google — only if you sign in with Google, which gives us your email and name and nothing more.
- PostHog EU — anonymous analytics of the public website, without cookies or user profiles: the pages viewed, how far they are read, what is clicked, how fast pages load and the country a visit comes from, which our host reads from the connection without passing on your IP address. It never measures the signed-in app. We remove form values and any URL parameter that could identify you before an event is sent. Checkout events contain only the chosen plan and outcome. PostHog never receives your email, account id, food, weight, payment details or a nutrition target.
- Sentry — error reports when something breaks, so we can fix it.
- Polar — subscription, payment and refund records when you buy a plan. IZeat does not receive your complete card number.
- Affonso — our partner programme, only if you arrived through a partner’s link: it records the visit, receives your email address when you create your account, and credits that partner if you buy a plan. It never receives what you ate or your targets.
What your assistant sees
The assistant is yours — Claude, ChatGPT, or another — and what you say to it is governed by that provider’s own policy. Our server receives only the tool request the assistant sends to IZeat, such as a meal to record, a target to set or a period to summarize. We return only the account data needed to answer that request. Your assistant provider receives that response so it can show it to you; IZeat never receives the rest of your conversation.
When you connect an assistant, IZeat may also share your verified email address through the standard OpenID UserInfo endpoint so the provider can confirm which IZeat account is connected. You approve this on the authorization screen and can revoke the connection from your Assistants page.
What we never do
- Sell your data, or share it with anyone for advertising.
- Show you advertising.
- Send what you ate or your nutrition targets to any analytics service.
- Use your data to train a model.
How long we keep it
As long as your account exists. You can ask for the account to be deleted at any time from the account page. Your assistants are disconnected on the spot. Then there is a 30-day grace period during which signing in again cancels the deletion. After it, your email, name, sign-in and connections are removed for good; your meals and targets are kept without any link to you, so they no longer point at anyone.
Your rights
You can export everything, whole, as CSV or JSON, with one download for each format, from the account page. You can delete the account yourself. For anything else — a question, a correction, a complaint — write to hello@izeat.app and a person answers.
Cookies
Two: the one that keeps you signed in, and the one that remembers your time zone. Two more, from Affonso, are set for 90 days only if you arrived through a partner’s link, so the partner who sent you can be credited. Analytics creates no cookie or other browser identifier.
Children
IZeat is not for people under 16.
A note on health
What you eat and the targets you choose are health-related data. IZeat stores them only to keep your journal and show it back to you, with the consent you give when you create your account. You can export or delete them at any time.
IZeat records what you tell it and compares it to a target you chose. It does not diagnose, treat, or tell you what to eat, and it never turns red because you ate. If you are unwell, talk to someone qualified, not to a calorie counter.