eait — last updated 27 September 2026
eait estimates the nutrition in your meals from photographs and from what you type, and compares the result against a daily target calculated from details you provide. This policy describes every category of data involved, why it exists, and what happens to it. It is written to be checkable: where a claim is about how the software behaves, the behaviour is the claim.
The data controller is Kirill Malyshev, Lisa-Fittko-Str. 15, Berlin, Germany. For any question about this policy or about your data, write to lets@eait.fit.
| Data | Collected | Linked to you | Why |
|---|---|---|---|
| Health data — dietary restrictions, allergies, and the free-text medical note you may write during onboarding | Yes | Yes | The daily target and the per-meal verdicts are computed from it. Without it the app cannot do the one thing it is for. |
| Fitness data — weight, height, year of birth, sex, activity level, goal and pace | Yes | Yes | These are the inputs to your calorie and macronutrient targets. |
| Meal records — the items, weights and nutrition figures for each meal you log, and any corrections you make | Yes | Yes | This is your diary. It is the product. |
| Apple Health data, if you connect it — a daily summary of your weight, height, body fat, lean mass, energy burned, steps, exercise minutes, workouts, distance, sleep, resting heart rate, heart-rate variability and VO2 max | Yes | Yes | Your weight keeps your calorie target current; the rest is shown to you as a trend. See “Apple Health” below. |
An account identifier — either a random device identifier generated on your phone, or the
opaque subject identifier (sub) supplied by Apple or Google if you sign in |
Yes | Yes | It is what separates your diary from everyone else's. |
| User content — the messages you send in Chat and the captions you add to photos, kept as the conversation | Yes | Yes | The Chat tab is the conversation you have had with the app, and it opens on it. Whatever you typed is kept as you typed it, and erased with your account. |
| Email address | Only if you sign in | Yes | Apple or Google gives us the address when you sign in, and we store it against the account. It is not how you are identified — that is the provider's own identifier — and there is no address at all on an account that never signed in. See Your email address below. |
| Name | No | — | Never requested from either sign-in provider. |
| Photographs | Yes | Yes | Kept with the meal they logged — see “Your photographs” below. |
| Contacts, location, advertising identifiers, usage analytics | No | — | The app contains no analytics SDK and no advertising SDK. Contacts are never requested from either sign-in provider either, and the app asks iOS for no contacts permission. |
Connecting Apple Health is optional, and nothing is read until you connect it. iOS asks your permission first, and you can change or withdraw it at any time in Settings › Privacy & Security › Health › eait — you do not need to ask us.
We store daily totals, not your individual readings. Your phone reads the underlying samples, reduces them to one row per day, and sends only that. Every individual measurement — each weigh-in, each night's sleep segment, each heart-rate reading — stays on your phone and is never transmitted to us.
Your most recent weight updates the weight on your profile, which is what keeps your calorie target from going stale. Nothing else changes your target: your activity is already counted once, in the activity level you chose during onboarding.
We also write back. Meals you log are written into Apple Health as nutrition entries, so Health's own figures include what you ate. Those entries are yours and live on your phone — we cannot read them back or reach them from our servers. Deleting your account from the app also deletes the entries we wrote, on that phone. If you have used eait on more than one device, or you delete the app before deleting your account, entries can remain in Health on the others; you can remove them yourself at any time in Health › Browse › Nutrition, or by deleting all data from eait under Health › Sources.
None of this data is used for advertising or marketing, is never sold, and is never included in anything sent to the model that analyses your photographs.
A photograph of a meal is sent to the model that estimates its nutrition and then kept with the meal, in our database in Germany, for as long as that meal exists. The diary shows it back to you. When you correct a meal in words, or ask the app to re-read the photo, it is sent to the model again. We also check corrected meals against their photographs ourselves, to measure and improve the estimates; nothing is sold, shared or used to advertise.
Delete the account and the photograph goes with it. It remains in the encrypted database backups until those expire (see “How long we keep it”). On your phone, every photograph the app captures is deleted after the upload; photographs fetched back for the diary are cached by the app and cleared when you sign out or delete the account.
Signing in gives us your email address. Sign in with Apple and Sign in with Google both return it, and we store it against your account. Signing in is optional: the app works without an account, and an account that never signed in has no address on it.
We use it for one thing and no others: to reach you about your account — something that has gone wrong, or something you have to know. We send no newsletter to it, no advertising, and we never share it with or sell it to anyone.
It is erased when you delete your account, along with everything else — the same deletion, at the same moment, with nothing kept back. If you want the address gone but the account kept, write to lets@eait.fit.
Apple lets you hide your real address behind a private relay (@privaterelay.appleid.com) at sign-in. That is fine and nothing here depends on knowing which you chose. Apple sends the address only the first time you authorise the app, so an account that signed in before this version has no address stored and we cannot ask Apple for it again.
The web server records each request it receives: the time, the path, the response code and the size. On eait.fit that is all it records. On the API the record also includes the IP address the request came from, which we keep in order to detect and limit abuse — the lawful basis is our legitimate interest in keeping the service available and its costs bounded (GDPR Art. 6(1)(f)). Each log is capped at 50 MB and the oldest entries are discarded as new ones arrive, so nothing accumulates indefinitely; and nothing joins these logs to an account.
| Processor | What reaches them | Why |
|---|---|---|
| OpenRouter (OpenRouter, Inc.) and, through it, the model provider that serves the model we use | The photograph or the text you typed, together with the dietary restrictions and targets needed to interpret it. No account identifier, no name, no email. | This is what performs the nutrition estimate. |
| Apple / Google, only if you choose to sign in | The sign-in exchange itself. We request the email scope and nothing else, so we receive an opaque identifier and your address — no name, no contacts. | So your diary survives losing your phone. |
| Hetzner Online GmbH (Germany) | Hosting for the server and its database. | The data has to live somewhere. |
Your data is not sold, and it is not shared with anyone else. There are no advertisers and no data brokers involved, because there is no advertising in this app.
On servers in Germany. The model provider processing your photographs may operate outside the European Economic Area; where that is the case, the transfer relies on the European Commission's Standard Contractual Clauses.
Open Settings in the app and choose Delete everything. This erases your account, your profile, your meal history, your conversation and your sign-in link, immediately and permanently. What remains is a genuinely new, empty anonymous account — not your old one with the diary hidden. There is no recovery afterwards, including by us.
You may also write to lets@eait.fit to request deletion, a copy of your data, correction of it, or a restriction on how it is used.
Your diary is kept until you delete your account. Sign-in tokens are revoked when you sign out. A meal proposed in chat but never confirmed expires within the hour and is deleted at the next proposal or restart; the sentence that proposed it stays in your conversation. Encrypted database backups are kept on the server for 14 days. Where an off-site copy is kept, it is encrypted before it leaves the server and held for 30 daily and 12 weekly snapshots, then destroyed.
If you are in the European Economic Area or the United Kingdom, the General Data Protection Regulation gives you the right to access your data, correct it, delete it, restrict or object to its processing, and receive it in a portable form. Health data is processed on the basis of your explicit consent, which you give by entering it and may withdraw at any time by deleting your account. You also have the right to complain to your national data protection authority.
eait is not for anyone under 16, and onboarding refuses an age below it. The reason is safety rather than paperwork: a calorie target computed for a growing body is a target that should not be computed by an app.
All traffic between the app and the server is encrypted with TLS. Every read and write in the database is scoped to your account identifier, which is resolved from your credentials and never taken from a request. Error messages are logged on the server and never returned to the app, because an error from deep in the stack can carry the text of the prompt, and the prompt can carry what you wrote about your health.
The numbers are estimates from photographs, not measurements, and the app says so on every screen that shows one. Calorie targets never go below a fixed floor regardless of what the arithmetic produces. None of it is medical advice. Talk to a doctor before making a significant change to what you eat, particularly if you have a medical condition.
If this policy changes materially, the updated version is published here with a new date before the change takes effect in the app.