nibb
Updated September 13, 2026

Privacy

Nibb stores a food log for your account. Some features send data to other services. This page explains which ones.

What we store

Your sign-in identifier, profile and targets, meals and entry text, saved meals, weights, uploaded photos, and connected-client permissions. If you turn on Apple Health sync, Nibb also stores the weight and daily activity records it imports. Draft entries may remain on your device until they are sent or removed.

Meal estimates

When you send an entry for estimation, Nibb sends its text and meal photos through OpenRouter to the selected model provider. The service can use relevant journal history and settings to interpret your request. The current model is supplied by Google. Food or web searches can send food names, brands, and related query terms to external lookup services.

Progress photos are stored separately and are not sent for meal estimation. When you connect an external MCP client, it can read journal data, including synced activity, and make changes after you approve access. Its provider's data rules apply to what it receives.

Notifications

Meal reminders are scheduled on your device. If you turn on entry alerts, Nibb stores an app installation ID and Apple push token for your account. Apple receives the logged meal names, calories, macro totals, and an entry identifier when processing finishes. These details can appear on your lock screen, depending on your iPhone notification preview settings. Photos, your original message, and weight are not included in the alert. You can turn off entry alerts in Settings. Unsent alerts expire after one hour; delivery records are removed after seven days.

Services that process data

These services may process data in other countries. Their retention rules can differ from Nibb's. See Supabase, Vercel, OpenRouter, Google, and AgentMail for their policies.

Apple sign-in

For supported Apple sign-ins, we keep an encrypted Apple refresh token to disconnect Apple when you delete your account. If Apple is unavailable, cleanup retries. We erase the stored token when revocation succeeds. If no usable token is available, you may need manual disconnection.

Apple Health

Health sync is optional. The iPhone app asks for access to specific data types. It can write logged nutrition to Health, sync weight, and read steps and activity. Manage permissions in Apple Health or iPhone Settings. Stopping sync does not delete records already stored in Nibb or Health.

Nibb does not sell Health data or use it for advertising. Do not connect an external client unless you want it to have access to your journal. Do not send sensitive details that are not needed for your entry.

Usage and error reports

We count public page views, entry/signup actions, and connection-address or example-request copies by page and broad source. These counts do not contain meal text, photos, weight, Health values, email addresses, or a visitor identifier. Counts are not a count of unique people. Browser Do Not Track and Global Privacy Control requests disable these optional counts.

For MCP use, we record the first connection day and whether a meal was created through a public MCP connection. We use these account records to count connections and repeat logging, without copying meal contents into analytics. Deleting a meal removes it from these counts; deleting your account removes its connection record. Do Not Track or Global Privacy Control on MCP requests disables this optional measurement. We do not link it to advertising sources.

Separate error reports can include an account identifier, app build, timing, and a request reference. Native crash and freeze reports include limited technical data. Nibb's error reporting excludes entry text and image content. Hosting providers also keep their own network and access logs.

Storage and retention

Journal data stays while your account is active, unless you delete a record. Support requests and security records are stored to answer requests and investigate problems. Deleted data may remain in provider backups or logs until those copies expire; we do not promise immediate removal from every backup.

Nibb uses cookies for sign-in and local storage for drafts and preferences. Public-page counts use session storage to avoid repeats and keep a broad visit source, such as a coach invitation or Instagram, for up to 30 minutes in one tab. The counts receive no account identifier, meal text, full URL or referrer. They do not connect a person’s journal to a promotion. Do Not Track and Global Privacy Control turn these counts off. Support abuse controls keep a daily keyed hash of the network address, not the raw address, and clears it after seven days in a scheduled cleanup.

Your choices

You can edit or delete meals, weights, and photos in the app. Settings includes a journal export and connection controls. To delete your account, open nibb.io and choose Settings → Delete account. Confirming removes your Nibb journal and connected-client access. Sign-in removal retries if the authentication service is unavailable.

We retain a deletion reference, account identifiers, dates, and cleanup status so old sessions cannot restore the account and failed cleanup can retry. These records do not contain your email or journal. Deletion does not remove Apple Health records, support messages, or copies already held by connected services. Provider logs and backups follow their retention rules. Devices may still hold cached data; sign out or remove the app on those devices. If you signed in with Apple, you can also disconnect Nibb in Apple’s settings.

For data help, open a private support request. We verify account ownership before acting. The support page gives you a private link to check the reply; it does not send email.

Who runs Nibb

Nibb is an independent app operated by Noah VanSickle. Use Nibb support for privacy questions. Nibb's beta is for adults aged 18 and over.