AI processing disclosure
Last updated: August 30, 2026
This page explains what happens when you choose an AI-powered feature in Nibble. AI is optional; disabling AI in the app or web account settings stops new AI requests. Manual and barcode logging remain available without managed AI.
1. Features that can use AI
- Food photo analysis and nutrition estimates.
- AI Coach conversations and meal suggestions.
- Recipe generation, nutrient explanations, and pattern insights.
- Supported Watch and Siri interactions that request an AI response.
2. What may be sent
- A meal photo you choose to analyze.
- Meal logs, nutrition values, and recent meal context relevant to your request.
- Dietary preferences, allergies, goals, cooking preferences, and taste preferences.
- Your calorie budget, remaining budget, and derived activity totals when those are needed for the request.
- The text, voice transcript, or chat message you provide.
- For Watch or Siri requests, the context needed by that feature can include your goal, weight, activity-derived budget, recent meals, and dietary preferences.
Normal phone requests do not send your account name or raw Apple Health samples to AI providers. Derived activity-related numbers can be included when you have enabled Apple Health and chosen an AI feature.
3. How the request is routed
Nibble sends an approved request from the device to its server-side AI service. On iPhone, a paid accountless request uses a short-lived pseudonymous RevenueCat entitlement token; it does not create a Nibble or Supabase account. The web dashboard still requires sign-in. Nibble keeps provider credentials and the upstream model route out of the app, records limited operational metadata, and routes approved tasks through LiteLLM to the server-configured `gemini-3.5-flash-lite` model route.
4. Retention and model providers
Nibble's AI API and self-hosted LiteLLM routing service are configured not to retain request or response content after processing. Operational metadata such as route, status, latency, token counts, and model cost units is retained for up to 30 days. The paid iPhone request uses the pseudonymous RevenueCat ID only for entitlement and abuse controls, not for account creation or advertising.
The current upstream provider is the Google Gemini API. Google may process or temporarily retain request content under its applicable terms; Nibble does not use submitted content for advertising. Do not submit information you do not want processed by an AI provider.
5. Your choices
AI consent can be withdrawn in the app settings or web account settings. You can use manual or barcode logging instead, and you can delete synced records or your account through the signed-in web dashboard or app. AI output is informational, may be wrong, and should be reviewed before you rely on it.
