This Privacy Policy describes how FridgeChef AI ("the App", "we", "us") handles information when you use our mobile application. We keep things simple: no account, no email sign-up, and no tracking beyond what is listed below.
When you scan your fridge, the image is compressed on your device, sent over an encrypted (HTTPS) connection to our backend, and passed to an AI model that lists visible ingredients. The image is never stored on our servers, never used to train AI models, and never shared with any third party other than the AI processor in section 4. You can also type ingredients manually, which involves no images at all.
The ingredients, meal type, cook time, diet, and servings you choose are sent to the backend to generate recipes. They are processed in memory and not tied to your identity (there is no account).
The App shows ads through Google AdMob, which collects your device's Advertising ID and basic ad-interaction data to serve relevant ads, measure performance, and prevent fraud. You can reset or limit your Advertising ID in your device settings.
Recipes you save, your language choice, and your shopping list are stored locally on your device only. They never leave your phone and are deleted when you uninstall the App.
If you use voice input, audio is processed by your device's built-in speech-to-text service. Only the resulting text is sent to our backend — we never receive your audio.
| Third party | What's shared | Why |
|---|---|---|
| Cloudflare | Compressed photos, ingredient lists, preferences (transient — not stored) | Runs the AI that detects ingredients and generates recipes |
| Google AdMob | Advertising ID, ad interactions | Shows ads that keep the App free |
Their policies: Cloudflare · Google.
FridgeChef AI is not directed at children under 13, and we do not knowingly collect data from them.
Because we don't collect personally identifying information, there is no profile to access or delete. To remove all local data, uninstall the App or clear its data in your device settings. You can reset your Advertising ID in your device's privacy settings. If you are in the EU/UK (GDPR) or California (CCPA), you may contact us to confirm what we hold — the honest answer is nothing personally identifiable.
All traffic between the App and our backend uses HTTPS/TLS. The backend API is protected by a shared token and per-IP rate limits.
If we change how the App handles data, we will update this policy and the "Last updated" date above.
Questions? Email mohakhi16@gmail.com.