Both keep everything on this device only—there is no cloud account in this build. Guest skips the username/password screen; a named profile gives you a sign-in you recognize when you return on this browser. Pick whichever fits; neither syncs to another phone or laptop.

No. Credentials are validated against profiles stored locally, and this version has no email recovery server. Use Forgot username or password? on Sign In for the on-screen explanation, or start a new profile / guest session if you’re fine leaving the old data behind on this device.

The username is the key your saved profile is stored under in this browser. To “switch” identities, sign out and use Sign In with a different account (or guest) rather than editing the name in place.

Not in this release. Each browser profile holds its own copy. Moving to a new phone or laptop means starting fresh unless you manually copy data outside the app (this build does not ship a built-in export).

No. Meals, goals, and weigh-ins live in browser storage only. If you need archives for a clinician or backup, plan on a future workflow or third-party tooling—CaloriEat doesn’t bundle a one-tap export here.

In-app clear removes logged meals and weigh-in history but leaves your profile fields and saved usual meals. Wiping site data in the browser settings removes everything the site stored, including your profile—use that when you want a full reset. See Privacy for the formal description.

It uses your device’s local clock and calendar. Travel or manual clock changes can shift which meals fall on “today” for rings and summaries until the device time matches your expectation.

Quick Log on the home screen is a shorter path for same-day entries when you already know the numbers. Use Log Food when you need the full food search, a different date (catch-up logging), or meal-type-based quick picks from your profile.

Presets are grouped by meal type. On Log Food, tap Breakfast, Lunch, Dinner, or Snack first; the chips for that time of day load from what you saved for that slot.

You can remove an entry from your log with the delete action beside that row, then add a corrected meal. There isn’t a separate “edit in place” flow—delete and re-log keeps the logic simple.

Treat database values as estimates. Brands reformulate, portions vary, and crowd-sourced lines can be wrong. Override calories and macros manually on Log Food when you have a label or scale measurement you trust more.

The dashboard stays scannable on first load. Each chart sits behind a row you expand; it stays open until you collapse it again so you can compare several at once without re-opening every time.

Your browser builds a PNG from the tracker view. Nothing is uploaded to CaloriEat—the file is saved or handed to your OS share sheet so you choose where it goes next. Charts that were collapsed may be opened briefly so the image is complete.

That opens CaloriEat Assistant: short, practical answers about using the app. With no custom server configured, replies come from built-in guidance; your team can point CALORIEAT_AI_CHAT_URL at a backend for richer chat. It is not medical advice.

After the first successful load, core screens and storage work offline. Chart.js and fonts may still need an initial download (or a warm cache) depending on your browser and CDN availability.

Private / incognito sessions, strict anti-tracking settings, or browsers configured to clear storage on exit can wipe localStorage. Use a regular window and allow persistent storage for this site if you want data to survive closing tabs.

Charts and some assets may load from public CDNs; your browser requests them directly. If your organization needs everything self-hosted, review Security and your deployment policy.